Coder Legion - Recent posts tagged geo

The Authority Paradox: A Practical GEO Strategy for Smaller Brands

Thu, 29 Oct 2026 17:27:21 +0000

By Jarno S., founder of AEOvara, Lappeenranta, Finland

A small company rarely wins by publishing more pages than an established competitor. It can, however, publish a better answer to a narrower question.

That is the useful opportunity behind Generative Engine Optimization (GEO): making expertise easier to discover, understand and substantiate when AI-powered search systems build an answer.

The authority paradox is not that reputation has stopped mattering. It is that broad recognition and usefulness for a specific question are different advantages. A specialist may have the stronger source for one particular problem—even when a larger brand dominates the wider market.

What you will learn

How GEO relates to SEO and Answer Engine Optimization (AEO).
What smaller brands can improve without a large publishing budget.
How to make claims easier for readers and search systems to verify.
How to measure mentions, recommendations, citations and factual accuracy separately.

GEO extends the visibility problem

Traditional search visibility often means appearing among the results a user can click. Generative search adds another possibility: a system may use information from a page while composing its own response, sometimes with a supporting link.

GEO is the practice of improving the likelihood that relevant content and brands are represented accurately in generative answers. AEO overlaps with this work, especially when content directly answers a user's question. The terminology varies across the industry; it does not describe neatly isolated ranking systems.

For a more detailed introduction, see AEOvara's guide to Answer Engine Optimization (in Finnish).

SEO remains part of the foundation. Crawlability, useful content, internal links and an understandable site structure still matter. Google's guidance on AI features and websites explicitly says that established SEO practices remain relevant to AI Overviews and AI Mode.

There is no universal shortcut that makes a page eligible for every AI answer engine.

What the research actually supports

The research paper GEO: Generative Engine Optimization reported visibility improvements of up to 40% in its experimental setting. Results varied across domains and optimization methods.

That is evidence worth exploring, but it is not a promise of 40% more citations, traffic or sales in today's commercial systems. An experimental visibility metric should not be presented as a guaranteed business outcome.

The practical lesson is to test improvements against a documented baseline. Clearer explanations and better-supported claims are useful editorial choices; their effect on a particular engine still needs measurement.

Domain scores are not the whole story

Domain Authority is a third-party SEO metric, not a Google ranking score. It should not be treated as a universal measure of how much an AI system trusts a website.

Equally, it would be misleading to say that links, established reputation or search rankings no longer matter. AI search products can rely on search indexes and retrieval systems, and the available sources influence what can appear in an answer.

A smaller brand's realistic opportunity is specific relevance.

Imagine a software consultancy documenting a difficult migration. A page that explains the source system, constraints, failed approaches and verified result can be more useful for that exact task than a generic overview from a famous publisher.

This is a hypothetical example, not a claim that specialist websites always beat larger domains.

Three layers a smaller brand can improve

1. Evidence: publish something that can be checked

Start with knowledge you actually have: a documented test, a worked example, a comparison with disclosed criteria or an anonymized case study shared with permission.

For research and benchmarks, include:

What you measured and why.
The sample, timeframe and method.
The result, including inconvenient findings.
The limitations and what readers should not infer.

A survey of 50 customers can offer useful local evidence, but it does not represent an entire industry. A small sample needs an honest description, not a dramatic headline.

Never invent a percentage or give an ordinary observation a research-sounding label. Link external claims to the original source, and distinguish your own findings from someone else's.

2. Clarity: make each section answer a real question

A useful section should identify the subject, answer the question and explain the conditions under which the answer holds.

For example, "our solution improves visibility" leaves almost everything undefined. "AEOvara provides AI-search visibility analysis and SEO implementation services" tells the reader what the company actually offers.

This is straightforward writing, not a secret embedding technique.

Use descriptive headings, explain abbreviations and keep terminology consistent enough to follow. Natural synonyms are fine when the relationship is clear. There is no established universal rule requiring an answer within exactly 40 words.

For developers, check whether the important information is present as accessible text and whether internal links lead to the supporting details. A visually impressive page is less useful when its central explanation is difficult to find.

3. Trust: connect claims to accountable people

Identify who wrote the content, what experience informs it and where readers can verify that background.

Show meaningful publication and update dates. Change an update date when you have reviewed or changed the information—not simply to make an old page look fresh.

Structured data can describe an article, organization or author where appropriate. It should match the visible content. Google's guidance states that there is no special schema.org markup required for its AI features.

Treat markup as an accurate description of your page, not a citation guarantee. Likewise, a byline or an E-E-A-T checklist cannot prove how every language model will evaluate a source.

Measure four different outcomes

A brand appearing in an answer is not the same as its website being cited. A citation is not necessarily a recommendation.

A practical tracking sheet should separate:

Mention: Is the brand named?
Recommendation: Is it presented as a suitable option for the user's need?
Citation: Is there a supporting link to the brand's content? Record third-party sources separately.
Narrative accuracy: Are the description, services, location and other checkable facts correct?

Record the prompt, date, product, available model or mode, language and whether web search was enabled. Keep the conditions as consistent as possible and repeat the tests over time.

Answers and source lists can vary because of retrieval changes, product updates, context and generation behavior. A single missing citation does not establish a trend, and one successful answer does not establish market-wide visibility.

Continue measuring relevant visits, enquiries and conversions alongside these indicators. Visibility has to connect to a business goal.

A practical starting plan

Choose a small group of questions your prospective customers genuinely ask. Include an explanation question, a comparison and a question with purchase intent.

Then:

Record how the selected AI products answer those questions today.
Identify one important page that lacks a clear explanation or supporting evidence.
Improve that page's answer, examples, source links and internal navigation.
Check technical accessibility and any structured data you use.
Repeat the same visibility tests and document what changed.

Avoid changing everything at once if you want to understand which improvements may have helped. Even then, before-and-after results show an association; they do not automatically prove causation.

AEOvara's AI-SEO and AEO services cover visibility analysis, audits and practical optimization work. The service is professional analysis and implementation—not a guarantee of inclusion in any AI system's answers.

The smaller-brand advantage is focus

Large brands bring recognition, resources and extensive information footprints. Smaller teams can bring detailed knowledge of a tightly defined problem and the ability to explain it carefully.

That opportunity is worth pursuing without claiming that authority has disappeared or that SEO is obsolete.

Build the page a reader would want to verify, bookmark and share. Make its evidence easy to inspect. Then measure whether it earns visibility for the questions that matter.

Want a clearer view of your starting point? Explore AEOvara's services to find an appropriate analysis or optimization project.

About the author

Jarno S. is the founder of AEOvara, based in Lappeenranta, Finland. His work focuses on SEO, Answer Engine Optimization and AI-search visibility, including practical analysis and content improvements for businesses. Read more about his background on AEOvara's expert page.

This article reworks and expands a topic previously discussed by the author on Medium, with revised claims, examples and practical guidance.

Five field guides

Wed, 07 Oct 2026 01:40:44 +0000

https://scriptmasterlabs.com/ebook-promo?v=2 Five field guides, named after the buyer prompts ranking this morning.
Jev Decision Model. Local Services Ads → Performance Max Migration. The GEO Checklist. Web Scraping API for AI Agents. Tavily Alternatives. One page, one video, buy links for all five.
Built by a service-disabled veteran. No fluff, just the guides.

FieldGuides #AIAgents #SEO #GEO

Is SEO Dead? What AI Search Really Means for Website Traffic

Wed, 19 Aug 2026 10:03:31 +0000

Is SEO Dead? What AI Search Really Means for Website Traffic

A few months ago, I noticed something odd in my traffic data. A page that used to bring in steady clicks for a simple "what is X" question had quietly dropped. Nothing had changed on the page. No penalty, no broken link, no algorithm update I could point to.

When I searched the same query myself, I found the answer. Google was answering it directly at the top of the page, before any website even showed up.

That's when the question everyone in SEO is quietly asking hit me too: is SEO dead?

I spent time digging into this. Testing queries, checking AI Overviews, running the same searches through ChatGPT, Gemini, and Perplexity, and comparing what happened to traffic on pages that used to rank well. Here's what I actually found.

Try this yourself before you read on

Pick one question you rank for. Search it on Google right now.

Does an AI Overview answer it completely, with no need to click anywhere?
Or does the answer only get you started, and you still want to compare, verify, or go deeper?

Keep your answer in mind. It matters for what comes next.

The short answer: No. But it's not the same game anymore.

Google still handles roughly 90% of all search traffic. That hasn't changed. What's changed is what kind of content gets clicked versus what gets swallowed by an AI-generated answer at the top of the page.

If your content exists to answer a simple factual question, like "what year was X founded" or "how many ounces in a cup," AI Overviews are now doing that job before anyone reaches your site. That traffic isn't coming back. No amount of "better SEO" fixes that, because the problem isn't your ranking. It's that there's no click to earn anymore.

But that's only one slice of search. The moment a query gets more specific, more personal, or higher intent, like "best CRM for a 5-person team" or "compare these two tools for my use case," people still click through. They still want to read a real answer, compare options, and see evidence. AI Overviews are good at summarizing consensus. They're not good at replacing judgment.

What's actually dying

It's not SEO. It's a specific kind of content:

Thin articles written only to rank for a keyword, with no real insight
Content that just repeats what's already on page one
Listicles with no original testing, opinion, or experience behind them
Anything that reads like it was generated to satisfy an algorithm, not a person

That content was already losing ground before AI Overviews existed. This just sped it up. Google's own guidance has pushed toward E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) for years. AI search just makes the gap between generic content and content with real experience behind it impossible to ignore.

What's rising in its place

Two disciplines have shown up alongside traditional SEO. Worth knowing even if you don't specialize in them yet.

AEO, Answer Engine Optimization. Structuring content so AI systems can pull a clear, direct answer from it. Clean headings, direct answers near the top, FAQ-style sections, and schema markup (FAQPage, HowTo, Article) that tells machines exactly what your content is about.

GEO, Generative Engine Optimization. Making sure your brand actually gets mentioned inside AI-generated answers, not just ranked in blue links. A different kind of visibility. You're not optimizing for a click anymore, you're optimizing for a citation.

Both sit on top of the same foundation SEO has always needed: fast, crawlable, well-structured, technically sound websites. Nothing about that has gone away. If anything, it matters more, because AI systems are even less forgiving of a broken or confusing site than a human skimming search results.

Quick self-check: are you ready for AI search?

Ask yourself these four questions honestly.

Does your most important page answer the core question in the first two sentences?
Do you have schema markup (FAQPage, HowTo, Article) on your key pages?
Does your content include something only you could write (real testing, real numbers, real experience)?
Can a crawler actually read your page, or does it rely on JavaScript to load the content?

If you answered "no" to two or more, that's exactly where to start.

What still works: no hype, just fundamentals

Testing this myself confirmed something I already believed. The fundamentals haven't moved.

Technical SEO. Core Web Vitals, crawlability, and a site that actually loads and renders properly. AI crawlers struggle with JavaScript-heavy pages the same way traditional crawlers do. If your content doesn't render, it doesn't get read, summarized, or cited.
Structured data. Schema markup isn't just an SEO checkbox anymore. It's how you tell both Google and AI systems exactly what your content is, in a format they can parse instantly.
Real experience content. Original insight, real testing, first-hand results. This is the one thing AI genuinely cannot replicate, and it's becoming the clearest differentiator between content that ranks and content that gets ignored.
Depth over volume. One well-researched, honestly written article now consistently outperforms five shallow ones. Quality has always mattered. It just used to be possible to get away without it. That's no longer true.

What's genuinely new

The one real shift is where visibility happens. Ranking #1 on Google used to be the finish line. Now there's a second finish line: does ChatGPT mention your brand when someone asks a relevant question? Does Perplexity cite your site as a source?

That's a new kind of visibility, and right now, almost nobody is tracking it. Which means there's real opportunity for anyone who starts paying attention early.

So, is SEO dead?

No. It's splitting into two related disciplines that increasingly overlap: getting found in traditional search, and getting cited inside AI-generated answers.

The sites that win in 2026 won't be the ones that "did more SEO." They'll be the ones that built genuinely useful, technically solid, honestly written content. The kind that was always going to hold up, no matter how search itself keeps changing.

The algorithm changed. The bar for good content didn't. If anything, it just got higher.

One question to leave you with: when's the last time you searched your own site's main keyword and actually looked at what showed up above your listing?

Website: devndespro.com | seo.devndespro.com

AI Search Optimization: What to Monitor without a subscription

Tue, 04 Aug 2026 12:22:00 +0000

Procurement wants a line item for "AI search." A vendor demo shows green citation bars for category prompts. Your team has not yet confirmed whether GPTBot can fetch pricing, docs, or product templates after last week's theme deployment. Buying the dashboard now answers one question and leaves the fetchability question unowned. AI search optimisation starts with signals you can check without a GEO subscription: bot policy, HTTP health, response time, and Core Web Vitals on the URLs buyers actually need. Agencies need a decision framework next: which layer needs a paid visibility platform, which layer you can run with tools you already use, and how PageSpeed monitoring for agencies covers the deterministic half without pretending to score ChatGPT mentions.

Two layers of AI search optimization (and which needs a subscription)

Treat AI search work as two layers with different questions, tools, and failure modes. Mixing them on one slide produces arguments in week two when the homepage prompt chart looks fine and checkout times out for crawlers. Name the layer before you buy software, or the wrong team owns the wrong failure.

Layer	Question	Tool type	Watcher role
Probabilistic	Are we cited for buyer-context prompts?	GEO / AI visibility SaaS, prompt trackers, manual ChatGPT or Perplexity checks	None; we do not score citations
Deterministic	Can bots fetch and render priority URLs fast enough?	`robots.txt` review, crawl or fetch checks, scheduled PageSpeed / Lighthouse, regression alerts	Core product: portfolio schedules, budgets, alerts, client reports

The probabilistic layer answers mention and citation trends for a fixed prompt set. Outputs are directional: useful for trends, weak as courtroom proof. Models drift, phrasing changes answers, and a competitor screenshot does not prove your pricing page is reachable today. Use GEO platforms when the retainer includes citation reporting and someone owns a prompt library with buyer context. Layer those tools beside technical monitoring. Do not replace crawl and speed work with prompt scores alone.

The deterministic layer answers access and speed on URLs you choose. Either the response completes with parseable content, or it does not. That half needs no GEO subscription, because it reuses performance monitoring, crawl hygiene, and reporting rhythms agencies already sell. Are We Visible in ChatGPT? What Agencies Can Measure First frames the client conversation. Monitor GPTBot performance on checkout, not AI visibility alone covers high-intent URL failures. The job here is deciding what to measure before you sign a visibility contract.

What AI search optimization means before you buy a visibility tool

Clients say "AI search optimisation" and often mean three different jobs: appear in ChatGPT or Perplexity answers, stay fetchable for AI crawlers, and protect clicks when Google AI Overviews answer without a visit. Those jobs share a site, but they do not share a measurement stack. Clarifying which job is in scope keeps procurement from funding citation charts while fetchability stays unowned.

Without a subscription to a visibility platform, you can still do useful AI search optimisation work:

Decide bot policy and write it down (allow, block, or mixed by user-agent).
Build a priority URL list by business intent, not sitemap size.
Confirm public routes return clean status codes and sane redirect chains.
Baseline lab Core Web Vitals and response time on those URLs, mobile and desktop.
Schedule recurring tests so theme, app, and CDN changes do not erase the baseline overnight.

None of those steps requires a GEO licence. They require scope, ownership, and a habit of checking the same URLs after releases. Call it PageSpeed monitoring for agencies applied to retrieval risk, not a new product category. Why AI Crawlers Need Fast, Crawlable Pages explains why fetchability still comes before citation.

What agencies can monitor for AI search without a GEO subscription

Start with artefacts you can open this week: production robots.txt, a ten-to-twenty URL inventory, PageSpeed Insights or Lighthouse on mobile and desktop, and optional server logs filtered for AI user-agents. The goal is a baseline you can defend on a client call, not a vanity "AI score." Save dates, devices, and owners in the client file so the next deploy has something to compare against. If the file only holds a homepage screenshot from last month, you are still guessing after the next theme release.

GPTBot, robots.txt, and AI crawler access checks

OpenAI documents GPTBot in robots.txt, and Google publishes crawler guidance for Search and related products. Fetch production robots.txt before the visibility debate. Five minutes here prevents expensive arguments later.

Agency checklist without a visibility vendor:

Fetch production robots.txt and note Disallow rules for GPTBot, Google-Extended, and other AI user-agents the client names.
Confirm public marketing, docs, and pricing paths are allowed unless the client explicitly opts out of training or retrieval.
Document opt-out decisions in writing. Blocking GPTBot is a valid policy choice; claiming the site is optimised for AI while disallowing crawlers is not.
Re-check after CMS or SEO plugin updates. All-in-one SEO tools sometimes ship aggressive bot blocks.

Keep a one-page bot policy per client next to the URL inventory. Account managers need a clear answer on whether the retainer includes crawler access review or only performance monitoring. When the client changes CMS, SEO plugins, or hosting, update both documents the same week.

Priority URLs, HTTP health, and response time for AI crawlers

Homepage-only checks hide the routes AI systems retrieve when someone asks about plans, SKUs, or documentation. Build the list by business intent, then test that list on a schedule instead of hoping a sitemap crawl catches money pages. Ten to twenty URLs with owners beat a full crawl nobody reads.

Pricing and plan comparison pages
Product detail and category templates for ecommerce
Documentation and help centre articles used in sales
Checkout and cart only where unauthenticated tests are allowed
Campaign landers that carry current offers

For each URL, record HTTP status, redirect hop count, and lab response time on mobile and desktop. Intermittent 503s and multi-second document loads are fetchability failures even when a GEO chart still looks green. Ecommerce teams should prioritise the funnel logic in Performance Monitoring for E-Commerce: What Metrics Matter Most; purchase-intent routes fail quietly when monitoring stops at the marketing homepage.

Core Web Vitals on money pages (lab baselines)

Core Web Vitals are not citation factors. Google’s AI Overviews guidance stresses content quality and relevance; it does not list LCP or INP as mention levers. Lab LCP, INP, and CLS still matter. Slow or unstable pages fail the step before citation: fetch and parse under crawler timeouts.

Run mobile and desktop strategies on the same priority list. Crawlers often behave like lightweight clients, so a desktop-only pass hides failures phones and bots both see. Track vitals as indicators of parseability and stability. Put regressions on docs or checkout in the client report beside any future GEO chart. Pair device budgets the same way you would for traditional SEO work in Mobile vs Desktop Core Web Vitals.

JavaScript-rendered pages and what AI crawlers may miss

Many AI crawlers do not execute a full browser. They rely on initial HTML and simplified rendering. If docs or product UI mount copy client-side only, a crawler may see an empty shell while Chrome looks fine. That gap shows up in sales calls when stakeholders insist the page "looks ready" in a manual visit.

Lab tests through PageSpeed Insights or Lighthouse do not perfectly simulate GPTBot. They still flag render-blocking scripts, long tasks, and late LCP elements that correlate with fetch problems. Pair lab schedules with occasional log review for AI user-agents so you can see which URLs they request and whether status codes stay clean. Translate "AI-ready" into operational requirements: critical copy in HTML, sane response times, stable layout, and monitoring on the URLs where answers should come from.

Why generic AI visibility prompts mislead agency buyers

Visibility demos love tidy graphs for prompts such as "best pagespeed tool 2026." Those graphs tell you almost nothing about whether you appear when a technical lead asks how to monitor forty Shopify stores after a theme deployment. Generic category prompts produce neat before-and-after slides with weak buyer context. Agency-real questions name the vertical, the stack, and the trigger event.

If you later buy a GEO platform, insist the prompt library matches how clients buy, not how vendors demo. Until then, a competitor's category-prompt screenshot is not proof your deterministic layer is healthy. Fix fetchability on named URLs first. Debate prompt design afterwards with someone who understands the client's ICP.

PageSpeed monitoring for agencies: free check to scheduled tests

One-off PageSpeed Insights tabs do not survive a release train. Agencies managing multiple clients need history, comparison, and alert routing on the same URLs every week. That matches the operational model in PageSpeed Insights vs automated monitoring: scheduled lab runs, stored results, budgets, and digests when thresholds breach.

A practical upgrade path without jumping straight to GEO SaaS:

Spot-check five priority URLs in PageSpeed Insights on mobile and desktop, then save the dates and scores in the client file.
Run the public free domain PageSpeed check, or follow the multi-page workflow in Free Domain PageSpeed Check: Multi-Page Performance Reports, for a client-ready snapshot before schedules exist.
Move the same URL list into recurring tests with budgets and alerts so theme deployments have an owner when LCP or response time drifts.
Add citation analytics only when the retainer includes prompt-level reporting and deterministic baselines are not the obvious bottleneck.

Apogee Watcher is built for step three: organisations per agency, sites per client, discovery and manual URL lists, mobile and desktop strategies, and email when lab metrics cross budgets. We do not score ChatGPT visibility. We tell you when priority URLs slow down, error out, or drift on vitals after the deployment that might affect fetchability. Setup steps live in Getting Started with Apogee Watcher. For feature comparisons across monitoring vendors, see Comparing PageSpeed Monitoring Tools: Features Agencies Need.

When a paid AI visibility platform is worth buying

Add a dedicated GEO or AI visibility platform when:

Leadership expects monthly citation charts in QBRs.
Content strategy targets LLM mentions for specific buyer personas.
Someone on the account maintains contextual prompts rather than generic category queries alone.
Deterministic baselines are already green enough that slow URLs are not the obvious bottleneck.

Defer procurement when:

The client has not agreed bot policy or priority URLs.
Homepage-only monitoring hides checkout and docs problems.
The ask is purely "make us show up in ChatGPT" with no content or technical owner.
You have not yet run a free or scheduled performance baseline on money URLs.

The sequence protects credibility: measure what you can fix without a visibility subscription, then buy citation analytics when scope and staffing justify it. Layer performance monitoring beside GEO tools; do not treat prompt scores as a substitute for fetch health on money URLs. A green citation chart next to a red checkout lab row is still an incomplete AI search story.

FAQ

Do we need an AI visibility subscription for AI search optimization?

Not on day one. You can audit bot policy, build a priority URL list, baseline lab Core Web Vitals and response time, and schedule monitoring without a GEO licence. Add a visibility platform when citation reporting is contracted and someone owns buyer-context prompts. Until then, the deterministic checklist is enough to keep the engagement honest.

What should agencies monitor for AI search without GEO tools?

Monitor crawler access in robots.txt, HTTP status and redirects on priority URLs, lab LCP, INP, CLS, and response time on mobile and desktop, and regressions after deployments. Those signals prove fetchability. They do not prove citation, so keep both layers labelled when you report to clients.

Can green Core Web Vitals guarantee ChatGPT citations?

No. Green lab vitals indicate priority URLs are likely fetchable and parseable under test conditions. Citation depends on content, authority, relevance, and model behaviour. Treat speed and stability as necessary technical hygiene, not a mention guarantee.

How is PageSpeed monitoring for agencies different from an AI visibility platform?

PageSpeed monitoring for agencies is the operational system for the deterministic layer: schedules, history, budgets, and alerts across client sites. An AI visibility platform tracks prompt-level mentions. Use monitoring for fetch health. Use GEO for citation trends when the retainer requires both.

Should we block GPTBot while we decide on a GEO vendor?

Blocking GPTBot is a policy decision, not a procurement shortcut. Document the choice with the client. If you block training or retrieval crawlers, do not claim the site is optimised for those products. Align monitoring with the routes you intend to keep public and reachable.

How many URLs should we cover before a visibility demo?

Start with ten to twenty priority URLs per client: pricing, key product or service templates, docs paths that support sales, and checkout where policy allows. Expand when alert triage stays manageable. A demo that only covers the homepage is not a fetchability baseline.

Can Apogee Watcher replace a GEO platform?

No. Watcher schedules PageSpeed lab tests, tracks vitals and budgets, and alerts on regressions across client sites. GEO platforms track prompt-level citations. Use both when the retainer covers technical performance and citation reporting. Use Watcher alone when the immediate risk is slow or blocked money URLs.

When leadership asks for AI search optimisation, answer with layers: what a visibility subscription can track over time, and what you can prove about fetchability and speed on named URLs without that subscription. Start with bot policy, priority URLs, and scheduled PageSpeed baselines. Add GEO analytics when content strategy and staffing support buyer-context prompts, not when a demo chart arrives before the first deterministic readout.

Start a free Apogee Watcher account to schedule mobile and desktop tests with vitals budgets across client sites, or run a free domain PageSpeed check before the first AI visibility procurement call.

References

SEO, AEO, GEO & SERP Explained: The 2026 Guide to Search Visibility

Fri, 17 Jul 2026 04:25:35 +0000

SEO, AEO, GEO & SERP Explained: The 2026 Guide to Search Visibility

Search Visibility · Updated July 2026 · 10 min read · by Jacob Campbell

Search used to mean one thing: rank on Google. In 2026 it's four overlapping disciplines — SEO, the SERP, AEO and GEO — and together they decide whether real people and AI assistants ever find your site. The reassuring part is that they aren't competing strategies; they're layers built on the same foundation of fast, well-structured, trustworthy pages. This guide explains each term in plain English, shows how they connect, and why getting them right is one of the clearest signals of a healthy website.

Key facts

4 — Layers: SEO, SERP, AEO, GEO
~27% — of clicks go to the #1 SERP result
AI — Answer & generative engines now cite sources
1 base — All four rest on fast, structured pages

The four terms, in one minute

SEO (Search Engine Optimization) is the work of making your pages rank in search engines. The SERP (Search Engine Results Page) is the results page itself — the battlefield where rankings show up, alongside ads, snippets and AI answers. AEO (Answer Engine Optimization) is optimizing to be the direct answer a machine shows in a box or reads aloud. GEO (Generative Engine Optimization) is earning a mention inside AI-generated answers from tools like ChatGPT, Gemini and Google's AI Overviews. Four names, one goal: be found.

SEO — the foundation everything sits on

SEO is still the base layer. It covers technical health (fast load, clean code, crawlability), on-page relevance (titles, headings, content that matches intent) and authority (links and trust). Nothing else works without it: an answer engine can't quote a page it can't crawl, and a generative engine won't cite a source it doesn't trust. Get SEO right and you've built the foundation the other three layers stand on. See our guide to why sites don't rank for the common failure points.

The SERP — where visibility is won or lost

The SERP is no longer ten blue links. A single results page now blends paid ads, a local map pack, featured snippets, People Also Ask boxes, images, video and — increasingly — an AI Overview at the very top. Every one of those is a slot you can win or lose. Understanding the SERP means designing your pages for the specific features your keywords trigger, not just for an abstract 'position one.'

AEO — becoming the answer, not just a link

Answer Engine Optimization targets the boxes and voice results that hand users a direct answer: featured snippets, People Also Ask, and voice assistants. You win these by answering real questions concisely, structuring content with clear headings, and marking it up with schema (FAQ, HowTo, Article). When your page is the cleanest, best-structured answer to a question, the engine reads it back to the user — often with your name attached. Our schema markup guide covers the structured data that makes this possible.

GEO — getting cited inside AI answers

Generative Engine Optimization is the newest layer: earning a mention when ChatGPT, Gemini, Perplexity or Google's AI Overviews generate an answer. These systems favour sources that are clearly written, factually specific, well-structured and trusted across the web. In practice GEO rewards the same things good SEO and AEO do — clarity, structure, citations and authority — which is why a healthy site tends to appear in AI answers without gaming anything.

Why all four are a website-health signal

Here's the tie that binds them: every layer is powered by the same fundamentals — fast Core Web Vitals, clean crawlable HTML, structured data, clear content and genuine authority. A site that performs across SEO, the SERP, AEO and GEO is almost by definition technically healthy; a site that fails them is usually slow, bloated or thin. That's why search visibility is a health check, not a marketing add-on. Start with the technical base — passing Core Web Vitals — and the rest compounds.

Sources & further reading

Related services

Frequently asked questions

What's the difference between SEO, AEO and GEO?

SEO optimizes to rank in search results, AEO optimizes to be the direct answer in snippets and voice results, and GEO optimizes to be cited inside AI-generated answers. All three build on the same foundation of fast, well-structured, trustworthy pages.

What is a SERP?

The SERP is the Search Engine Results Page — the page you see after a search. In 2026 it mixes ads, a map pack, featured snippets, People Also Ask, images, video and an AI Overview, not just ten links.

Is SEO still relevant with AI search?

Yes — more than ever. AI answer and generative engines can only quote and cite pages they can crawl, understand and trust, which is exactly what SEO delivers. SEO is the foundation AEO and GEO stand on.

How do I optimize for AI Overviews and ChatGPT?

Write clear, factually specific content, structure it with proper headings and schema, and earn genuine authority. Generative engines favour well-structured, trustworthy sources — the same qualities that win featured snippets.

How does search visibility relate to website health?

Every search layer depends on speed, clean code, structured data and clarity. A site that ranks, wins snippets and gets cited by AI is almost always technically healthy; poor visibility usually signals a slow or bloated site underneath.

Want a site built to win every search layer?

Every BuiltToWinWeb site ships fast, structured and schema-ready — the foundation for SEO, AEO and GEO — for one flat fee.

Get my free quote

To Train or Not to Train? Why ChatGPT Can't See You

Tue, 14 Jul 2026 11:10:19 +0000

You did the responsible thing with your robots.txt. You let the search bots in so they can cite you. You blocked the training bots so no model eats your content and paraphrases you to strangers without a link. You confirmed the site was crawlable and indexed. Textbook.

Then someone asks ChatGPT "what is a good tool for X," and you are not in the answer. Not ranked low. Absent. The work you did to be found is the exact thing hiding you.

Here is why, and why the fix is not the switch you think.

Many answers never search at all

Your name reaches a ChatGPT answer one of two ways. Either the model answers from memory, out of what it absorbed during training, or it runs a search and comes back with links.

The catch is that search is not guaranteed to run. On the free tier, where many casual users are, search is not enabled by default, and most people never turn it on. Even when it is available, the model decides per question whether it is worth the trouble. For news and prices it looks. For "what should I use," it often just answers from what it already knows.

So a lot of the questions that matter most to you get answered from memory. And your own site only reaches that memory if you let the training crawler in. Block it, and as far as your own pages are concerned, the model has no idea you exist the moment it answers without searching.

That is where the real decision sits. Not "how do I rank." To train, or not to train.

To train: what it costs you

Open the training crawler and you get into memory, so you can show up even when the model never searches. Here is the bill for that:

You go stale. Foundation models retrain a few times a year. Your pricing, features, and positioning freeze at whatever the model last ingested, and stay wrong until the next retrain.
No link. Memory answers do not cite. The model recites you without sending anyone to your site.
No traffic, no attribution. You become a fact in a sentence, not a destination. People act on what the model says and never learn you were the source.
Your content is in the dataset for good, used however the model sees fit, with no way to pull it back.
And it still is not guaranteed. Being crawled for training does not mean the model will surface you. You paid all of the above and may still not show up.

Not to train: what it costs you

Keep training blocked and you protect your content, but you accept the other half of the trap:

You are not in memory. Every answer the model gives without searching is an answer you cannot appear in.
You are betting everything on search firing. And on the free tier, where most casual users live, search is not on by default and most people never turn it on. They ask, the model answers from memory, and you were never in the room.

One path makes you outdated. The other makes you invisible. That is why the title is a real question and not a rhetorical one.

First rule out the boring cause

Say you take the search side anyway: block training, allow the search crawler, hope to be cited when the model looks. Even then it can search and skip you, sometimes for a dull technical reason. Modern sites render in the browser with JavaScript, and crawlers often receive an empty shell instead of your content, so the model finds nothing to cite.

So before you conclude anything, settle one question: can the search crawler actually read your page? Fetch your site the way the crawler sees it, not the way your browser paints it. Swap in your domain and a phrase from your homepage:

curl -s -A "OAI-SearchBot" https://yoursite.com | findstr /i "your headline text"

Nothing comes back. You have a rendering problem, not a robots.txt problem. The crawler is getting an empty shell, and no directive fixes it until the page serves its content in plain HTML. Fix that first.
Your text comes back. Good. Access is not your issue, and that is the important finding, because it means you can stop touching config entirely. Every crawler setting is fine. The reason you are invisible is not technical.

If the crawler sees you and you are still invisible

Then stop tuning settings. You are simply not the answer yet. Nobody cites you, few sites mention you, and the model has no reason to pick you over the names it already knows. You are not losing on configuration. You are losing because you have not earned the position.

Which points at the only real fix, and it is not in your robots.txt.

The actual answer: build the site, not the config

Stop tuning crawler directives and grow the thing itself. Get mentioned in roundups, review sites, Reddit threads, the docs and articles other people write. Get indexed in more places by more sources.

Do that and both doors open at once, without the trade-off:

You land in the model's memory through their pages, not your own. Those articles and threads get crawled into the training data themselves, so when enough trusted sources describe you, the model absorbs you along with them. You end up in its built-in knowledge without ever opening your own site to the training crawler, and it can name you even when it does not search.
You get cited with real traffic when search does run, because those are the pages it retrieves and links.
You stay fresh, because those sources keep getting re-crawled.

That is the version where ChatGPT recommends you even on a cold, no-search answer. Not because you flipped a switch, but because the web already agrees you are the answer.

To train or not to train is a toggle with no good side. Reputation is the setting that actually decides it, and it is the one you cannot type into a file. Everything else is just choosing how you would like to be invisible.

Nataliia Poladova, AI Product Builder and Automation Specialist.

The hidden search happening behind every AI answer, and why your best page still loses

Sun, 12 Jul 2026 23:02:41 +0000

Here is something almost no one who talks about "SEO for AI" knows: when someone asks ChatGPT or Google's AI Mode a real question, the system does not search for their question. Not once. It rewrites it into five, ten, sometimes twenty separate hidden searches, runs them all at the same time, and stitches the answer from whatever it finds. Your one page is not competing for one query anymore. It is competing to be the best passage for a fan of sub-queries you will never see.

That mechanic has a name. Query fan-out. And if you are optimising your site the way you did in 2023, you are optimising for a game that is not being played.

Here is how badly the rules have shifted. A December 2025 analysis of about 174,000 URLs found that roughly 68 percent of the pages AI cited in its answers were not even in Google's top ten organic results for the same query. Read that again. The pages the AI trusted enough to name were, in the majority, pages that never ranked. A separate 2026 study put the overlap between top rankings and AI citations at about a quarter to a third. So a brand that only chases rank misses most of the AI citation opportunities. Not some. Most.

The reason is fan-out. Ranking answers "which page is best for this exact query." Fan-out asks "which passage best answers each of these hidden sub-queries," and the winning passage for a narrow sub-query often sits on a smaller page that never ranked first for the head term. Different question, different winner.

The mechanic itself takes one sentence to describe. Your reader types one question. The engine's language model rewrites it into a set of sub-queries, each targeting a facet of what the reader probably actually wants. All the sub-queries run at once against the live web. The engine grabs specific passages, not whole pages, and picks the best ones. It writes one answer and cites a few sources. Google confirmed this publicly when it launched AI Mode, and its own patent calls it "query variant generation."

How wide the fan opens depends on the engine. Google's AI Mode fans wide: most prompts fire five to eleven parallel sub-queries, and its Deep Search can run hundreds. ChatGPT is surgical: it only searches when it needs fresh data, and when it does, it fires a handful of precise sub-queries. Perplexity typically runs a small fan and reviews ten or so sources before writing. Simple factual questions may not fan at all. But the moment a question is layered or commercial, which is exactly the kind of question worth winning, the fan opens.

Here is the surgical-strike detail that stops most makers cold.

When ChatGPT does fan out, it does not search the open web from scratch. It leans heavily on Bing's index. Analyses in 2026 put the overlap between ChatGPT's citations and Bing's top-ten results at around 87 percent. So if you rank number one on Google for your money keyword, and you are nowhere in Bing's top ten for the sub-queries under it, ChatGPT does not cite you. Full stop. Setting up Bing Webmaster Tools takes about ten minutes and is free. Your Bing rank for each sub-query is a leading indicator of whether ChatGPT will cite you. Most people who care about being cited by ChatGPT have never opened Bing Webmaster Tools. That is the free win nobody takes.

Now the mechanical heart of it, and the piece that changes how you write. AI systems do not grade whole pages. They chunk content into semantic passages and score each passage on its own. A single well-written paragraph from a small site can beat a five-thousand-word guide from a major domain, if that paragraph answers the sub-query more directly. Research on AI Overview extraction in late 2025 put the sweet spot for an extractable passage at roughly 130 to 170 words. Long enough to answer completely. Short enough to be lifted cleanly into a synthesis.

That means your unit of optimisation is no longer the page. It is the self-contained passage: a section that answers one question fully, on its own, without needing the paragraphs around it for context. A page can rank #1 and still lose because none of its sections are extractable on their own.

The ten-minute test you can run right now

Here is how to see the fan-out for your own topic, using nothing but a browser and a fresh chat window.

Pick one high-intent question a buyer in your category would ask. Not your brand name. A problem, phrased naturally: "what is a good tool for X" or "how do I solve Y without Z."

Open ChatGPT or Claude in a new chat with no history. Paste the question with one small change at the end: "If someone asked you this, what sub-questions would you search the web for before answering? List them." The list you get back is not the real fan, but it is a strong first draft of it. You will see six to ten sub-questions you never wrote content for.

Now open your site and honestly ask yourself: do I have a self-contained 130-to-170-word passage that answers each of those sub-questions? For most sites, the answer is no. And that gap, question by question, is where AI is citing your competitors instead of you.

If you want the real fan-out that a specific engine actually fires, the free Backlinko Chrome extension exposes ChatGPT's sub-queries, cited sources and entities for any prompt you run. Perplexity shows its citations natively in every answer. Both are worth ten minutes of your afternoon.

What to do with what you find

The strategic shift is this: you are no longer writing pages for keywords. You are writing self-contained passages that answer specific hidden sub-questions, organised into topic clusters that cover the whole question space around your subject. The pillar-plus-cluster structure, atomic answers of ~150 words each, and a real refresh date matter more than any single ranking signal you optimised in 2023.

The specifics of how to predict the fan reliably, build the entity-attribute matrix that turns messy sub-queries into a content plan, use the peer-reviewed tactics that increase citation rates up to forty percent (from Aggarwal et al., ACM KDD 2024), and set up the free monthly loop that tells you if any of it is working, live in the play book I wrote on this: Query Fan-Out: SEO for AI Search https://nataliiap.gumroad.com/l/seo-fan-out, part of a trilogy on AI search visibility for web apps.

But the ten-minute test above needs no book. Run it today. If your site cannot answer at least four of the sub-questions the model lists back, you now know exactly why AI keeps naming somebody else.

Right now, an AI is recommending a tool like yours to someone. Is it yours?

Fri, 10 Jul 2026 21:43:42 +0000

Here is the uncomfortable part: you will never see it happen.

Someone opens ChatGPT, Claude, or Perplexity and types "what is a good tool for X." The model answers with two or three names and a line of praise for each. The person picks one and signs up. No search results page. No click on your site. No row in your analytics. If your name was not in that answer, you did not lose the deal, you were never in the room.

Google Analytics cannot show you this. Search Console cannot show you this. You can rank #1 on Google for your main keyword and still be completely absent from the answer an AI gives to the exact same question. Ranking and being recommended are now two different games, and most makers are only playing the first one.

So the real question is not "where do I rank." It is "when a machine is asked to recommend something in my category, does it say my name, a competitor's, or nothing at all." Here is a free way to find out. It takes about twenty minutes and needs no tools you do not already have.

The 20-minute audit

You are going to interrogate the AI models the way your future customer would, then log what comes back. That is the whole method.

1. Write your question list

Think like a buyer, not a founder. Buyers do not search your product name, they search their problem. Write 8 to 12 real questions someone would ask before they know you exist. For example:

"what is a good tool for [the job your product does]"
"how do I [problem your product solves] without [common pain]"
"best [category] for [specific audience]"
"alternatives to [the big competitor everyone knows]"
"is there an open source way to [thing you do]"

The last two matter most. "Alternatives to [big name]" is where challengers get discovered, and if you are not on that list, you are invisible at the exact moment someone is ready to switch.

2. Ask every model, cold

Open ChatGPT, Claude, Perplexity, and Google's AI mode in separate tabs. Use a fresh chat with no history so your own past prompts do not bias the answer. Paste each question, one at a time, into each model.

Perplexity is the one to watch closely, because it shows its sources. When it answers, look at the citations. Those linked pages are literally the pages the AI trusted enough to build its answer from. If none of them are yours, you now know exactly where the gap is.

3. Log four things per answer

Open a plain spreadsheet. One row per question, per model. Record only four columns:

Mentioned: did your product name appear at all? yes / no
Cited: was your own site linked as a source? yes / no
Sentiment: if mentioned, was it positive, neutral, or a throwaway line?
Competitor: which rivals got named instead?

Do not overthink it. Twenty minutes of honest yes/no logging tells you more about your AI visibility than any dashboard.

Reading the result

Once the grid is filled, you will land in one of three situations, and each means something different.

Not mentioned anywhere. The model does not know you exist as an answer to that problem. This is almost never about your homepage copy. It is about the model never having seen your product described, in plain language, on pages it trusts. The fix lives off your own site as much as on it: comparison pages, roundups, forum threads, and your own content written so a machine can lift a clean, self-contained answer out of it.

Mentioned but not cited. The model says your name but links a competitor or a third-party roundup as the source. You are in the conversation but you do not control the framing. Here the work is making your own pages the most quotable source about you, so the citation points home.

Competitor named, you are not. The most useful and most annoying result. Look at who keeps appearing. Then go read the pages Perplexity cited for them. That is a map of exactly where they earned their visibility, and exactly where you need to show up.

Make it a baseline, not a one-off

Run the same list next month. AI answers drift as models retrain and as new content gets indexed, so a single snapshot is a photo, not a trend. Keep the sheet, date each run, and watch the "mentioned" and "cited" columns move over time. That drift is the only number that tells you whether anything you do is actually working.

Where this goes next

This manual audit is the diagnosis. It shows you the gap with no special tooling, and for a lot of makers, just running it once is the wake-up call.

Turning it into a repeatable system, knowing the specific pages to build so an AI cites you, and verifying in Search Console that AI crawlers are actually reading them, is the longer game. I put that full verify-and-monitor playbook into a field guide called Crawled, Indexed, Cited https://nataliiap.gumroad.com/l/seo-monitor, part of a three-book set on AI search visibility for web apps. But run the twenty-minute check first.

LLMs: Why Your Web Infrastructure Needs to Pivot for SEO, AEO, and GEO

Sat, 27 Jun 2026 16:16:08 +0000

Architecting for the [LLM][1] Layer: Why Your Web Infrastructure Needs to Pivot for SEO, AEO, and GEO

The shift from standard Google search results to AI-generated answers is fundamentally changing how web clients ingest, parse, and cite our code. Web architecture is transitioning from static, human-only layouts to machine-readable, intent-driven ecosystems.

To build web platforms that remain visible in the age of conversational search, we need to design websites with three distinct layers in mind: SEO (Search Engine Optimization), AEO (Answer Engine Optimization), and GEO ([Generative Engine Optimization][2]).

Here is a practical look at how this shift changes web architecture, along with the code implementations you can deploy today to keep your site visible.

The Three Pillars of Modern Web Visibility

SEO (Search Engine Optimization) – Still the Foundation
Classic technical SEO remains crucial. It involves server response times (TTFB), edge-rendering performance, optimized crawl paths, and robust core web vitals. If a bot cannot crawl your site quickly and efficiently, it won't index it.
AEO (Answer Engine Optimization) – Targeting "Zero-Click" Intent
AEO optimizes your page structures so AI assistants (like Claude, ChatGPT, Gemini, and Google AI Overviews) can easily slice and dice your content to present single, definitive answers to conversational user prompts.
GEO (Generative Engine Optimization) – Supplying the LLM Context Layer
GEO focuses on establishing your site's absolute topical authority and entity relationships. It optimizes for AI engine citations, ensuring that when an LLM synthesizes a response, it pulls and references your web address.

Technical Implementations for Your Codebase

1. The Dynamic Semantic Layer: Nested Entity JSON-LD

AI models do not parse raw HTML visually; they seek structured relationships. Instead of relying on flat metadata, you can implement nested, entity-centric JSON-LD schemas to clearly define relationships.

Below is an example of an Entity-First JSON-LD schema linking a company, its technology, and its documentation:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "TechArticle",
  "headline": "The AI Shift Age Web Architecture: A Blueprint for SEO, AEO, and GEO Mastery",
  "inLanguage": "en",
  "author": {
    "@type": "Person",
    "name": "Momenul Ahmad",
    "jobTitle": "SEO Strategist",
    "worksFor": {
      "@type": "Organization",
      "name": "SEOSiri",
      "url": "https://www.seosiri.com"
    }
  },
  "about": [
    {
      "@type": "Thing",
      "name": "Answer Engine Optimization",
      "sameAs": "https://en.wikipedia.org/wiki/Answer_Engine_Optimization"
    },
    {
      "@type": "Thing",
      "name": "Generative Engine Optimization"
    }
  ],
  "publisher": {
    "@type": "Organization",
    "name": "SEOSiri",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.seosiri.com/logo.png"
    }
  }
}
</script>


----------
2. Deploying an AI-Friendly Gateway: llms.txt

Just as we use sitemap.xml for search crawlers, we can use llms.txt at the root
directory to offer a clean, markdown-based map of resources specifically
structured for LLM scraping and ingestion.

Add an llms.txt file at your site root (/llms.txt) as follows:

# SEOSiri Developer Docs & Resources

## Core Technical Blueprints
- [AI Shift Age Web Architecture](https://www.seosiri.com/2026/06/web-architecture-seo-aeo-geo-ai-shift.html): Blueprint detailing SEO, AEO, and GEO optimization frameworks.
- [Automated sitemap.xml for LLMs](https://www.seosiri.com/2026/06/automated-llm-sitemap.html): How to structure automated feeds for AI agent discovery layers.

## Tools & Packages
- [keywords_research_generator](https://pub.dev/packages/keywords_research_generator): A Flutter plugin for automated keyword discovery.

3. Transitioning from "Hub-and-Spoke" to a "Mesh Network"

Traditional content architectures organize pages in rigid hierarchical clusters
(e.g., Parent Category -> Child Page). In the AI age, this is often too slow and
fragmented for non-linear search queries.

To optimize for local and generative intent, consider transitioning toward a
Mesh-Network Architecture:

  - Lateral Linking: Link micro-clusters together through logical entity
    relations, not just parent-child categories.
  - Concise Fragment Answers: Use specific HTML structures like speakable schema
    tags, clear heading lists, and standalone Q&A sections so that crawlers can
    pluck precise fragments without parsing unnecessary page elements.

To review the full architectural shift and explore the step-by-step roadmap for
building search-, answer-, and generative-ready web structures, read the full
blueprint at:

👉 [The AI Shift Age Web Architecture by SEOSiri][3]: A Blueprint for SEO, AEO, and GEO Mastery


  [1]: https://coderlegion.com/21038/programmatic-ai-discovery-automating-the-llms-txt-standard-with-a-sitemap-to-llm-loop
  [2]: https://coderlegion.com/20184/geo-aeo-for-technical-founders-getting-your-code-saas-and-web-apps-cited-by-ai-search
  [3]: https://www.seosiri.com/2026/06/web-architecture-seo-aeo-geo-ai-shift.html

Programmatic AI Discovery: Automating the LLMs.txt Standard with a Sitemap-to-LLM Loop

Sat, 20 Jun 2026 15:08:26 +0000

Hey developers and tech founders,

We’ve all seen the rapid adoption of the /llms.txt standard. It is an elegant, open-source way to declare our system documentation, core application routes, and API endpoints for clean LLM crawler ingestion (GPTBot, ClaudeBot, PerplexityBot, etc.).

But as developers, we hate manual maintenance. If you are building a rapidly growing product, manually updating links inside a static plain-text Markdown file every time you deploy a new API route, document, or blog post is a terrible anti-pattern.

Here is how you can bypass the operational overhead entirely by implementing an automated Sitemap-to-LLM Loop.

The Core Concept: The XML-to-AI Bridge

Many developers overlook the fact that modern LLMs are already highly proficient at parsing XML sitemaps natively. They do not need you to translate every single deep URL into a manual Markdown string. They can read and extract paths directly from your standard, dynamically updated /sitemap.xml.

By structuring your /llms.txt to handle the high-level semantic introduction (who you are, what your product does) and pointing AI crawlers directly to your dynamic XML sitemap, you create a zero-maintenance loop. Your backend automatically updates the sitemap on deploy, and all major AI bots crawl your changes automatically.

The Code: How to Serve It Dynamically

If you are running a custom Node.js/Express backend, you don't need to host a static file. You can serve your /llms.txt dynamically as a flat text file with the correct MIME type:

const express = require('express');
const app = express();

const LLMS_TEXT_CONTENT = `# SEOSiri Technical Documentation & Engineering Ecosystem

SEOSiri is a B2B digital engineering consultancy and technical SEO platform 1.

Core Services & Blueprints

Sovereign CapEx Engine: Web-based capital expenditure modeling, NPV/IRR forecasting, and asset amortization tracking [1.1.1].
Biometric IoT Bridge: Secure Flutter biometric-to-hardware TLS/MQTT edge gateway framework.
Precision Agriculture E-Noses: Machine-learning-driven agricultural sensor telemetry and environmental monitoring pipeline.

Dynamic Site Map & Full Index

Dynamic XML Sitemap: Our real-time updated, machine-readable sitemap containing all publication and category URLs. AI crawlers can use this sitemap to discover and index all deeper historical technical articles 1.`;

// Serve llms.txt with the correct text/plain MIME type
app.get('/llms.txt', (req, res) => {
res.set('Content-Type', 'text/plain');
res.send(LLMS_TEXT_CONTENT);
});

The Proven Results
We deployed this exact, low-overhead system on our platform, SEOSiri. Verified by our custom AI visibility dashboards, this automated architecture has generated 258 total AI citations and a 21.24% Share of Authority (SoA) across Microsoft Copilot and partners in just 15 days.

If you want to implement this automated loop across different environments, we have published the complete technical roadmap. Our guide covers step-by-step instructions for WordPress, Shopify, Ghost, Webflow, Wix, Squarespace, Blogger, Node.js, Django, and custom HTML/CSS sites:

👉 Read the Full Automated LLMs.txt Integration Guide on SEOSiri

I'd love to hear from other backend developers and full-stack builders here:

How are you structuring your documentation for AI-first search? Have you integrated a programmatic /llms.txt route into your deployment pipelines, or are you still relying on manual updates? Let's discuss!

GEO & AEO for Technical Founders: Getting Your Code, SaaS, and Web Apps Cited by AI Search

Wed, 10 Jun 2026 15:18:45 +0000

For software developers, SaaS builders, and technical architects, building a great product is only half the battle. If your web application, developer utility, custom extension, or open-source package isn't properly indexed and understood by AI search models, you are missing out on high-intent B2B adoption.

When enterprise buyers ask ChatGPT, Gemini, or Perplexity for the most secure and scalable web solutions, your systems need to surface as the trusted source.

We have published a deep dive on how we are leveraging Generative Engine Optimization (GEO) and Answer Engine Optimization (AEO) to help developers, startups, and technical brands secure authoritative citations inside AI-first search ecosystems.

Read the full breakdown and learn how to showcase your software platforms, web apps, or technical systems on our platform:

https://www.seosiri.com/2026/06/tech-interview-digital-pr-feature-seosiri.html

Free AI SEO Checker: 39 AEO and GEO Checks Explained

Tue, 26 May 2026 14:21:23 +0000

Free AI SEO Checker: 39 AEO and GTraditional SEO tools check what Google cares about. This one checks what AI systems care about.

AutomateLab just shipped a free, no-signup checker that audits any URL across 39 checks for answer-engine optimization (AEO) and generative-engine optimization (GEO). Here's what each check actually tests.

The gap this tool fills

Most SEO auditors tell you your title is too long or your Core Web Vitals are poor. Useful for Google's ranking pipeline. But AI search engines like ChatGPT, Perplexity, and Claude extract answers differently. They look at:

Whether their crawlers can access your content
Whether your opening paragraph resolves the query directly
Whether your structured data schema type matches what the page actually says
Whether your content exists in raw HTML (not locked behind JavaScript execution)

None of that is covered by existing tools. That's the gap.

Five categories, 39 checks

Crawlability (6 checks)

The tool checks whether GPTBot, OAI-SearchBot, ClaudeBot, Claude-SearchBot, PerplexityBot, and Amazonbot are blocked in robots.txt. Many sites block these accidentally via wildcard disallow rules. It also checks robots.txt accessibility, sitemap presence, and canonical URL consistency.

Structured Data (7 checks)

Validates JSON-LD presence, schema type alignment (does @type: Article match what you published?), required properties per schema type, OpenGraph and Twitter cards, and author attribution. The author check looks for Wikidata or LinkedIn identity links from the author page.

On-Page Content (11 checks)

The most nuanced category. The question-heading check is based on a study showing 72% of ChatGPT-cited pages use question-style H2-H4 headings. The tool flags pages below a 30% ratio. Other checks cover reading level, answer density, internal link structure, image alt text, and heading hierarchy.

AI Readability (8 checks)

Answer density: First paragraph should resolve the implied query in under 60 words
Render mode: Page must contain 200+ visible words in raw HTML; JavaScript-rendered content is invisible to non-executing bots
llms.txt: Checks for presence and accessibility
Entity recognition: Named entity density signals
Outbound authority: Links to authoritative external sources

Technical Health (7 checks)

HTTPS, mixed content, mobile viewport meta tag, payload compression, image dimension attributes, HSTS headers, and security headers. Table-stakes checks, but the tool catches edge cases.

Scoring

Checks are weighted 1-5 based on signal strength. The tool produces category scores and a weighted overall letter grade:

A: 90+
B: 75-89
C: 60-74
D: 40-59
F: below 40

Each failed check includes the evidence string (what the tool found) and remediation guidance (what to change).

How it works

User pastes a URL
Server-side proxy fetches HTML, robots.txt, sitemap, and llms.txt in a single request
All 39 checks run client-side in the browser
Results render immediately with per-check evidence

Nothing is stored. No login required. Single URL per run.

For teams that need bulk audits, @automatelab/ai-seo-mcp wraps all 39 checks for Claude Code and Cursor workflows.

Try it

https://automatelab.tech/blog/al-products/free-ai-seo-checker-aeo-geo/

Part of the AutomateLab AI automation stack.EO Checks Explained

Citation Intelligence MCP

Mon, 25 May 2026 14:54:29 +0000

We built a free, MIT-licensed MCP server for tracking which URLs ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews, and Bing cite for any query.

12 tools across three jobs:

Track citations: check_citations, am_i_cited, ai_overview, cited_for
Predict citations: predict_citation, compare_domains, wikipedia_mentions
Find leaks: gsc_citation_gap, audit_sitemap, citation_trend

Three of the tools run on a local cache and cost zero. The rest use your own API keys (Anthropic, OpenAI, Gemini, SerpAPI) at roughly $0.01 to $0.03 per query. Hosted alternatives (Profound, AthenaHQ, Otterly, Ahrefs Brand Radar) start at $295/month.

Install:

`npx -y @automatelab/citation-intelligence`

Wires into Claude Code, Claude Desktop, Cursor, n8n, or any MCP host.

Launch write-up: https://automatelab.tech/launching-the-citation-intelligence-mcp/

Feedback welcome.

AI-SEO for Developers: How to Get Your Docs and Blog Cited by ChatGPT, Claude, and Perplexity

Thu, 21 May 2026 12:37:24 +0000

Why AI-SEO is suddenly the most important SEO surface, exactly how to do it, and what it actually pays back.

Three years ago you optimized a page to rank on Google. Today the page that ranks #1 still loses six out of ten clicks the moment an AI Overview shows up above it. The new game is not ranking — it is being cited inside the answer itself. This guide is the developer-flavored playbook: why AI-SEO matters now, exactly how to do it on a site you control, and the numbers it pays back.

What is AI-SEO, AEO, GEO, and LLMO?

AI-SEO is the umbrella term for getting your pages surfaced, summarized, and cited by AI assistants. Three sub-disciplines sit underneath it:

AEO — Answer Engine Optimization. Targets the structured answers shown inside ChatGPT, Perplexity, Claude, Gemini, and Google AI Overviews.
GEO — Generative Engine Optimization. Targets the way generative models compose multi-source answers and decide which sources earn a citation.
LLMO — LLM Optimization. The broader practice of shaping content, schema, and crawler access so large language models treat your pages as the authoritative source for a topic.

In practice the three overlap heavily. The signals that earn an AI Overview citation also earn a Perplexity citation also earn a ChatGPT Search citation. So most of this guide treats them together and only splits them when the implementation diverges.

Why does AI-SEO matter now?

Four numbers explain why every team with a public site should already have an AI-SEO playbook running.

1. The audience already moved

ChatGPT now serves more than 2 billion queries per day across roughly 900 million weekly active users. Perplexity crossed 45 million monthly active users and is growing 66% year over year. These are not toy numbers — this is where buyers, developers, and decision-makers go first when they have a question your product answers.

2. AI Overviews dominate the SERP

Roughly 55 to 60 percent of US Google searches now show an AI Overview. In health, that number is 82 percent. For most informational queries, the AI answer is the first thing a user sees — and whether they keep scrolling depends almost entirely on whether your page made it into that answer.

3. Classic CTR is collapsing

Authoritas measured a 61% average drop in organic CTR for queries where an AI Overview is present — and on some verticals the top result loses 79% of its clicks. Even ranking #1 is no longer enough. The floor that classic SEO defended for twenty years is gone.

4. Cited brands win the click-through battle anyway

Here is the upside. When your brand is cited inside the AI answer, organic clicks go up 35% and paid clicks go up 91%. AI-referred traffic, when it does click through, converts at 4 to 5 times the rate of Google organic across a dataset of 12 million visits. The buyers who arrive via AI are pre-qualified by the model.

How is AI-SEO different from classic SEO?

Classic SEO optimized a page to rank. AI-SEO optimizes a page to be extracted, summarized, and cited. The work overlaps — both reward fast, well-structured, authoritative pages — but the levers diverge once you get past the basics.

Layer	Classic SEO	AI-SEO
Goal	Top 10 ranking	Be cited inside the answer
Primary signal	Keywords + backlinks	Quotable answers + entity authority
Page structure	Title + meta + Article schema	H2 = the exact question + FAQPage + HowTo
Crawler control	Allow Googlebot	Per-bot rules for 10+ AI crawlers
Discovery surface	sitemap.xml	sitemap.xml + llms.txt
Win condition	A click	A brand mention + a click
Measurement	Rank + CTR	Citation share + AI-referred conversion

The good news for anyone worried about a tradeoff: almost everything you do for AI-SEO also helps classic Google. Schema, FAQ structure, sitemap hygiene, canonical correctness, Core Web Vitals, entity links — all of these have been ranking factors for years. The only AI-specific additions are llms.txt and per-crawler robots.txt allow rules, and neither of those affects Googlebot. The work is additive, not a tradeoff.

How do you do AI-SEO? A seven-step technical playbook

This is the sequence we run on every site, in the order we run it. The first three steps are infrastructure and usually take a day. Steps four through seven are content-shaped and run for as long as you keep publishing.

Step 1. Audit and configure per-bot crawler access

There are at least ten AI crawlers worth thinking about: GPTBot, ChatGPT-User, OAI-SearchBot (all OpenAI), ClaudeBot and Claude-Web (Anthropic), PerplexityBot, Google-Extended, Bingbot for Copilot, Applebot-Extended, and Bytespider. Each has a different role. GPTBot trains ChatGPT; OAI-SearchBot powers ChatGPT Search citations; ClaudeBot powers Claude Search; Google-Extended is the gate for Gemini training (separate from Googlebot).

The trap we see most often: a site blocks GPTBot to opt out of training but leaves OAI-SearchBot allowed, which means ChatGPT can answer about your page but cannot learn from your fresh content — and the resulting citation gets stale fast. Or the inverse: a site allows GPTBot but accidentally blocks OAI-SearchBot, killing real-time citation eligibility entirely. Map the access matrix explicitly, do not inherit it.

A reasonable starting robots.txt for a site that wants both training and citation visibility:

User-agent: GPTBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

Sitemap: https://example.com/sitemap.xml

Step 2. Ship an llms.txt

llms.txt is to LLMs what robots.txt was to search crawlers: a tiny, human-and-machine-readable file at the root of your domain that points models at the canonical entry points for your content. Place it at /llms.txt. Keep it short. A workable minimum:

# Example Inc
> One-line summary of what the company does.

## Docs
- [Quickstart](https://example.com/docs/quickstart): how to install and run in 5 minutes
- [API reference](https://example.com/docs/api): full REST and SDK reference

## Blog
- [Engineering blog](https://example.com/blog): performance, architecture, postmortems

## Optional
- [Open-source repos](https://github.com/exampleinc): MIT-licensed tools and SDKs

An llms-full.txt at the same level can expand into longer descriptions per page. Adoption is uneven — some models honor it, others do not — but the cost of shipping it is twenty minutes and it never hurts.

Step 3. Cover the schema basics, then go beyond Article

Every public page should ship JSON-LD. The bare minimum is Organization (one per domain, including a sameAs array pointing at your verified social profiles and Wikipedia entry if one exists) and BreadcrumbList. From there, pick the right page type:

FAQPage on any page with a Q&A block. This is the single highest-yield AI-SEO schema because the questions become extractable units.
HowTo on tutorials and step-by-step guides. Mark up each step. AI Overviews pull these almost verbatim.
SoftwareApplication on product pages.
Article or TechArticle on blog posts, with author and publisher correctly populated.

The entity links inside Organization.sameAs do more work than they appear to. They tell models that the brand on this page is the same entity as the LinkedIn page, the GitHub org, the Wikipedia article. That mapping is what lets a model say "according to Example Inc..." with confidence instead of fuzzing the attribution.

Step 4. Phrase every H2 as the exact user question

This one change is worth more than most of the technical work. LLMs extract answers by matching question patterns to nearby text. If your H2 is "Configuration", the model has to guess what question that answers. If your H2 is "How do you configure timeouts in the SDK?", the model has the question, the answer block underneath it, and a direct extraction path.

Rewrite your top 20 pages so each H2 is a literal question — the kind a buyer would type into ChatGPT. Put the one-paragraph answer immediately below, then expand. This pattern, sometimes called the inverted pyramid for AI, is the single largest content-side lever.

Step 5. Add comparison tables and step-by-step lists

Models love tables. A clean comparison table — your product vs an alternative, two approaches side by side, a feature matrix — gets quoted in AI Overviews and Perplexity answers far more often than the equivalent prose. Same for numbered step-by-step instructions. If your page contains a procedure, mark it up as an ordered list and consider also wrapping it in HowTo schema.

Step 6. Build the entity graph

Models treat a brand as the same entity across the web only if the entity is linked. Make sure your Organization.sameAs includes: LinkedIn, GitHub, Crunchbase, Wikipedia (if eligible), Wikidata (the Q-number is the entity glue), and your primary social profiles. Then make sure the bio on each of those profiles points back to your canonical homepage. This is the cheapest authority signal you can build.

Rank tracking does not capture AI-SEO performance. You need four numbers, baselined and tracked monthly:

Citation share — on your target query set, what percent of AI answers (ChatGPT, Perplexity, Claude, Gemini, AI Overviews) cite your domain?
AI Overview coverage rate — of your branded and non-branded target queries, what percent trigger an AI Overview at all? This is the addressable surface.
AI-referred traffic and its conversion rate compared to Google organic.
A per-page AI-SEO score — schema completeness, llms.txt presence, crawler access, H2 question phrasing, FAQ structure, entity coverage.

Are there tools that automate this?

Yes — and most of the audit and rewrite layer is automatable. Three projects worth bookmarking, all free and open-source:

AI-SEO MCP (free, MIT)

An MCP server that exposes 13 AI-SEO tools — audit, score, rewrite suggestions, schema generation, llms.txt validation, per-bot robots.txt analysis — to any MCP-compatible agent (Claude, Cursor, Continue, Windsurf, etc.). Vendor-agnostic, no API keys, no quota. Point it at a URL and it returns a structured score plus rewrite suggestions. Repo and install instructions: https://automatelab.tech/products/mcp/ai-seo/

Content Distribution MCP

Once you have an AI-SEO-shaped page, distribution multiplies its citation odds — more high-authority surfaces mentioning your brand means a higher chance any single LLM sees it during training or retrieval. This MCP auto-publishes to DEV.to, Hashnode, GitHub Discussions, Reddit, and Bluesky with idempotent state, and falls back to a browser bot for Medium, LinkedIn, and X. Repo: https://automatelab.tech/products/mcp/content-distribution-mcp/

Publishing Skills for Claude Code

If you are writing the long-tail content for your AI-SEO playbook with Claude Code, this is the matching skill bundle: blog-topic-research (finds question-shaped topics with real demand signals), ghost-blog-writer (drafts in the AI-SEO-friendly structure described above), and an SVG figure generator. Public repo: https://automatelab.tech/products/skills-and-plugins/publishing-skills/

How long does AI-SEO take to pay back?

Faster than classic SEO. Crawler access and schema changes pick up within days to two weeks — AI Overviews and ChatGPT Search both refresh on roughly weekly cycles, far faster than the months a new backlink takes to influence Google rank. Content rewrites and entity-graph work take four to eight weeks to show up in citation share. A well-shaped page on an established domain can earn its first AI Overview citation within a single week.

What if you do not have time to do this yourself?

If you would rather hand the whole build to a team that does this every day, AutomateLab runs a productized AI-SEO, AEO, and GEO service: audit, schema templates, llms.txt, per-crawler rules, page rewrites, entity-graph build, and a citation dashboard — shipped in three to four weeks. You own the repo, the configuration, and a forever license to the open-source AI-SEO MCP at the end of the build. Details and an intro call: https://automatelab.tech/services/ai-seo/

FAQ

Is AI-SEO the same as AEO or GEO?

AI-SEO is the umbrella. AEO (answer engine optimization) targets the structured answer surface. GEO (generative engine optimization) targets multi-source generative answers. LLMO is the broader practice. The signals overlap heavily, so most practitioners treat them as one workstream.

Will AI-SEO hurt my Google rankings?

No. Every signal that helps AI-SEO — schema, FAQ structure, sitemap hygiene, Core Web Vitals, entity links — also helps classic Google ranking. The only AI-specific additions are llms.txt and per-crawler allow rules, neither of which affects Googlebot.

Do I need to block GPTBot to protect my content from training?

Blocking GPTBot prevents training but does not prevent citation — OAI-SearchBot is a separate crawler that powers real-time ChatGPT Search answers. Most teams want OAI-SearchBot allowed even when they choose to block GPTBot. Decide each crawler explicitly; do not inherit defaults.

What is the minimum I should do today?

Three things, in this order: (1) audit your robots.txt for per-bot rules and add OAI-SearchBot and ClaudeBot allow lines if they are not there, (2) add FAQPage schema to your three highest-traffic pages, (3) rewrite the H2s on those pages to be literal user questions. That is roughly two hours of work and it usually moves the needle within two weeks.

How do I track whether I am being cited?

Manually: run your target queries on ChatGPT, Perplexity, Claude, Gemini, and Google with AI Overviews enabled once a week and log citations. Automatically: the AI-SEO MCP includes a brand-mention tracker that does this on a schedule. Track citation share over time, not just rank.

Bottom line

AI assistants are the new top of the funnel. Being ranked #1 no longer guarantees a click. Being cited inside the AI answer does. The good news for developers: most of the work is technical, deterministic, and automatable — schema, crawler rules, structured answers, llms.txt, entity links. Ship those, measure citation share, and treat the AI answer surface like the page-one ranking it has quietly become.

If you want the audit-and-rewrite tools, grab the free AI-SEO MCP: https://automatelab.tech/products/mcp/ai-seo/

If you want it built for you, the productized service lives at: https://automatelab.tech/services/ai-seo/

Originally written for coderlegion.com. Author: AutomateLab Editorial. Republish with attribution and link back to https://automatelab.tech/services/ai-seo/.

AI Citations Are Harder to Keep Than to Get — What our Web3 client's Data Taught Us

Tue, 28 Apr 2026 11:30:03 +0000

Most agency case studies look the same. Metric goes up. Client is happy. Everyone looks good.

This isn't that kind of case study.

What follows is an honest breakdown of six months of GEO work on a Web3 wallet client — active across Asian markets, solid product, real user base. Citations grew significantly. Then they declined. Cited pages kept growing. Mentions barely moved. And every one of those patterns taught us something we didn't fully expect going in.

The Starting Point

When we started in November 2025, our client had near-zero presence in AI-generated answers. Ask ChatGPT about multi-chain wallets — they weren't mentioned. The product was solid. The AI visibility wasn't there.

Six months later, here's what the data actually shows:

Metric	Current (Apr 2026)	Trend
AI Citations	277	-6.1% (declining from March peak)
Mentions	56	-6.7% (declining)
Cited Pages	61	+10.9% (still growing)
Active AI platforms	3	ChatGPT, Google AI Mode, Gemini

That's a more complicated picture than most agencies would choose to publish. We're publishing it anyway because the complications are where the learning is.

What Worked: Citations Grew Significantly

From November 2025 to March 2026, AI citations grew from near-zero to approximately 300.

Three tactics drove most of that growth:

Comparison content
"Client vs [competitor]" articles and on-site comparison tables were cited far more frequently than any other content type. If you want to appear in "best X for Y" answers, you need to exist in comparison contexts first. This was the single highest-leverage tactic in the campaign.

Reddit participation
Consistent, expert-level contributions in relevant subreddits produced a clearer correlation with citation growth than almost any other off-site activity. Reddit's conversational format is heavily weighted by AI retrieval systems for recommendation queries.

The rule that worked: 90% genuinely useful contributions, 10% brand mention only when directly and honestly relevant.

Publishing velocity
Maintaining a consistent weekly publishing cadence across Medium, dev.to, Hashnode, HackerNoon, and similar platforms created sustained signals that AI retrieval systems respond to over time. The first six weeks showed minimal change. The compound effect kicked in around week 8.

What Surprised Us: Citations Peak, Then Pull Back

By March 2026 the client had reached approximately 300 AI citations — the peak. Since then, citations declined to 277 (-6.1%). Mentions followed the same pattern (-6.7%).

AI citations are not sticky in the way traditional search rankings are.

A page that ranks #1 on Google tends to stay there unless something actively displaces it. AI citations work differently — they reflect the current state of the web ecosystem around a brand. When activity slows, citations follow.

The practical implication: AI visibility requires maintenance, not just an initial build.

What's Still Growing: Cited Pages

The one metric that kept moving in the right direction — still growing at +10.9% — is cited pages.

This matters more than it appears. Cited pages represent the structural foundation of AI visibility: the number of distinct pages AI systems consider credible enough to reference. When citations fluctuate, cited pages is the better indicator of underlying visibility health.

This reframed how SeekLab thinks about GEO success metrics:

Citations = leading indicator. Responds quickly to activity, pulls back quickly when activity slows.
Cited pages = lagging indicator. Grows slowly but represents more durable AI visibility infrastructure.

What Barely Moved: Mentions

Mentions stayed relatively flat across the entire six months, ending at 56 with a slight decline.

Our current hypothesis: mentions in AI-generated content are more heavily influenced by brand recognition and training data than by structured content and off-site signals. For a brand operating primarily in Asian markets, breaking into the mention layer of Western AI systems requires either more time or a different set of tactics — possibly more focus on high-DA English-language coverage.

This is an open question we're still working through.

The Honest Summary

Six months of structured GEO work produced real results — the client went from invisible to actively cited across ChatGPT, Google AI Mode, and Gemini.

But the data also revealed something the industry doesn't talk about enough: AI visibility is more like a living ecosystem than a ranking. It requires ongoing care, not just initial optimization.

Three things we'd tell any brand starting a GEO campaign now:

Start with comparison content. Fastest path to appearing in recommendation queries.
Build cited pages, not just citations. The page count is the foundation everything else grows from.
Plan for maintenance from day one. If your strategy doesn't include ongoing publishing and community activity, your citation peak will be temporary.

Want to know where your brand currently stands in AI-generated answers? Open ChatGPT, Perplexity, and Gemini. Search your brand name and core category queries. Record what comes back.

Free audit at seeklab.io →

Generative Engine Optimization: Your 2026 Survival Guide

Tue, 07 Apr 2026 12:57:04 +0000

You’ve probably noticed something strange.

Your site ranks second in Yandex. You have backlinks from good Russian domains. Your content is solid.

But sales are flat. Traffic from search is dropping.

I saw the same thing with my own projects. In early 2025, one of my clients – a small online store selling construction tools – lost 23% of organic traffic in just four months. Their SEO was fine. Their positions were fine.

The problem wasn’t Google or Yandex’s blue links.

The problem was the gray box at the top of the search results. The AI-generated answer.

Here’s what happened.

Why old SEO stopped working

In September 2024, Yandex launched full integration of YandexGPT into search. By February 2025, according to a report from Yandex.Webmaster (link: yandex.ru/company/press), over 35% of all Russian-language search queries received a generative answer. Not links. A paragraph written by AI.

Then GigaChat from Sber got embedded into Smart Search. ChatGPT started showing real-time web results.

I’m not guessing. Mediascope (mediascope.ru) published data in December 2025: 41% of Russian internet users aged 18–55 use AI‑powered search at least once a week. And 64% of them never click on the first blue link if the AI answer answers their question.

So your perfect SEO title and meta description? The AI just reads your page, takes what it needs, and the user never visits your site.

That’s where GEO Optimization comes in.

What GEO actually is (no fluff)

GEO stands for Generative Engine Optimization.

It’s the process of making your content easy for AI engines to find, understand, cite, and trust. Not for ranking a link. For being quoted inside the answer.

Think of it this way:

SEO = make Google/Yandex put your link on page one.
GEO = make ChatGPT/YandexGPT/GigaChat use your text as a source for their answer.

You don’t need to be number one in the old world anymore. You need to be the source the AI chooses.

Here’s a real example. A Russian travel blog I work with wrote a guide “What to do in Kazan in winter.” They didn’t chase keywords. They structured the page with clear sections: “indoor activities”, “outdoor skating rinks”, “average prices”. They added a table with temperatures by month. They wrote in short, factual sentences.

Within three weeks, YandexGPT started quoting them directly in the AI answer for “Kazan winter guide”. Their site got 1,200 extra visits from people clicking “source” inside the AI block.

That’s GEO.

How AI engines choose your content (the technical part)

I’ll keep it simple. Most generative search engines use a method called RAG – Retrieval‑Augmented Generation.

Step one: The AI takes your question and retrieves relevant pieces from a large pool of documents (your site, news, Wikipedia, forums).

Step two: It sends those pieces to a large language model (LLM) which writes the final answer.

Your goal in GEO is to make sure your content gets retrieved first. And then cited correctly.

In 2025, researchers at Yandex Academy published a study on GEO factors. They analyzed 10,000 AI answers. Here’s what mattered most:

Clear headings (H2/H3 with real questions) → +47% influence on being cited by AI

Structured data (FAQ, HowTo schema) → +38%

Author name and bio on the page → +29%

Internal links to related topics → +22%

Use of tables and bullet lists → +35%

Source: academy.yandex.ru/research/geo-2025 (available in Russian)

So writing long, fluffy paragraphs doesn’t work. The AI skips them.

The big difference between SEO and GEO

Factor 1: Goal

SEO: Rank #1 for a keyword

GEO: Be quoted as a source in AI answer

Factor 2: User behavior

SEO: User clicks your link

GEO: User reads AI answer, may click “source”

Factor 3: Key content type

SEO: Long articles, keywords density

GEO: Clear structure, facts, entities

Factor 4: Technical need

SEO: Page speed, mobile, backlinks

GEO: Schema markup, author info, trust signals

Factor 5: Success metric

SEO: Position in SERP

GEO: Mention frequency in AI outputs

Here’s my take from running tests on 12 Russian sites in 2025:
If you spend 100% of your time on SEO, you’re ignoring 41% of the search market. That’s not smart.

What actually works for GEO (my proven tactics)

I’ve tested these with e‑commerce, blogs, and a small law firm in Moscow. Here’s what moved the needle.

1. Write like you’re answering a friend (not a professor)

AI engines love conversational language. Why? Because they’re trained on chat logs, forums, and Q&A sites.

Instead of saying: “The implementation of optimization strategies for generative engines requires a multifaceted approach”
Say: “To get into AI answers, you need to do three things. First…”

I rewrote a product description for a power tool from formal to conversational. The old version had 0 AI citations. The new version was quoted 12 times in YandexGPT answers for “how to choose a hammer drill” in one month.

2. Add a clear FAQ section to every important page

Not hidden. Real questions people type into search.

AI engines often pull directly from FAQ blocks. I’ve seen it happen. A client added a “Frequently asked questions about electric heaters” with 5 questions. Two weeks later, GigaChat quoted two of those answers word‑for‑word.

But important: The answers must be short. 2–3 sentences max. If you write a paragraph of 80 words, the AI will summarize and you lose your brand mention.

3. Use tables for comparative data

AI models love tables. They’re clean, factual, and easy to extract.

Example: Instead of writing “Model A has 1500W, Model B has 2000W”, put it in a 3‑column table. I saw a 62% increase in AI citations for a client after converting five comparison paragraphs into tables.

My real case study (with numbers)

Let me share something honest.

I worked with a Russian online store selling pet supplies (name withheld for NDA). In March 2025, they were losing traffic. I checked Yandex search for “best dry food for cats with sensitive stomach”.

The AI answer cited three sources: a vet clinic blog, a Wikipedia page, and a forum. My client’s site – which had great SEO – was nowhere.

So we implemented four GEO changes:

Added an “Expert review” block on each product page with the manager’s name and certificate number.
Created a dedicated FAQ page with 15 questions about cat digestion.
Changed all “best for…” sections into 3‑column tables (product, price, key feature).
Wrote short definitions for every technical term (like “grain‑free”, “hydrolyzed protein”).

Four weeks later, we rechecked the same query. The AI answer now cited my client’s site second – right after the vet clinic. Organic traffic from AI‑generated answer clicks grew by 47% month‑over‑month.

Cost of implementation? About 14 hours of work. No new backlinks. No paid ads.

The problem nobody talks about

GEO isn’t perfect. And I won’t sell you a dream.

First, you can’t track “rankings” in AI answers. There’s no Yandex.Webmaster report saying “your site is #3 in ChatGPT.” You have to manually check queries or use tools like Serpstat’s AI monitor (which is still rough).

Second, AI engines change their source preferences often. In November 2025, YandexGPT suddenly started favoring older forum posts over fresh blogs. Nobody knows exactly why.

Third, some niches are harder. I’ve seen very low success for medical advice because AI engines are legally cautious. They prefer government or academic sites.

So GEO is not magic. It’s a hedge. You still need good SEO. But if you ignore GEO today, you’ll be invisible tomorrow.

How to Make Your First Page GEO‑Ready in 90 Minutes

This is a simple checklist I give to all my clients. No technical skills needed. You’ll turn one existing article into an AI‑friendly source that YandexGPT, ChatGPT, and GigaChat can easily quote.

Duration: 90 minutes (including a 15‑minute break)

Steps:

Pick your best article (one that already ranks on page 1–2 of Yandex). (5 min)
Break it into short sections – each with a question as H2 (e.g., “How much does this cost?” instead of “Pricing”). (20 min)
Add an FAQ block at the end with 5 real user questions and 2‑sentence answers. (15 min)
Create one table comparing options, years, or features. (10 min)
Write a short author bio – name, role, and one sentence about expertise. (5 min)
Add schema markup for FAQ using any free JSON‑LD generator (I use faq‑schema. ru). (15 min)
Test by asking ChatGPT or YandexGPT “What is [your topic]?” and see if your content is cited. (20 min)

FAQ

Q1: Is GEO replacing SEO?
No. SEO still brings traffic from people who click links. GEO brings traffic from people who read AI answers and then click “source”. You need both. In my tests, the best results came from doing SEO first, then GEO on top.

Q2: How do I know if AI is already using my content?
Type “site:yourdomain.ru” into Yandex, then ask YandexGPT a question related to your niche. See if the AI cites you. Also check Perplexity.ai and ChatGPT with web search enabled. Do this once a month.

Q3: Does GEO work for local businesses?
Yes, but differently. For “best dentist in Novosibirsk”, AI answers often pull from Yandex Maps and review sites. Make sure your Yandex Business profile is complete, with photos, services, and response to reviews. That’s local GEO.

Q4: How much does GEO cost?
If you do it yourself – zero rubles. Just time. If you hire an agency, I’ve seen prices from 50,000 to 300,000 RUB per month. But start with the HowTo block above before paying anyone.

Q5: What Russian companies already use GEO well?
Tinkoff Journal (journal.tinkoff.ru) – their FAQ blocks and bullet lists are quoted constantly. Also, Sber’s own blog for GigaChat examples. And a small legal site, zakon.ru, gets cited for legal questions because they have clear definitions.

Conclusion (and my honest advice)

Here’s where I land after a year of testing GEO.

Don’t panic. Don’t drop your SEO. But don’t pretend AI search doesn’t exist.

Start small. Pick one article. Apply the HowTo steps. Wait two weeks. Check if AI mentions you.

If it works – and it probably will – expand to your next ten pages.

One more thing: Russian search is moving faster than global. Yandex pushes AI answers more aggressively than Google. So if you’re reading this from Moscow, St. Petersburg, or any Russian city, your window is now. Six months from now, your competitors will have figured this out.

I’m not saying GEO will save your business overnight. It won’t.

But ignoring 41% of search traffic? That’s not a strategy.

Thank you for reading to the end.

If you want to understand if GEO is working for you, visit geouseo.ru

I'll check for free whether ChatGPT, Gemini, or Yandex GPT mentions you for five keywords relevant to your target audience.

No template reports – I'll simply tell you where you are and where you aren't, and what to do about it.

Why AI Answer Engines Cite Authority, Not Persuasion

Thu, 12 Feb 2026 19:11:06 +0000

AI Answer Engines Cite Authority, Not Persuasion

AI answer engines cite authority because citations are a liability filter, not a marketing reward. They need sources that can survive scrutiny when a reader checks the link, compares it to other links, or uses it for a real decision. In practice, the easiest source to reuse is the one that reads like a reference—specific, consistent, and verifiable rather than a page written to convert.

That core incentive explains most “mysteries” of why one page gets cited and another doesn’t. Persuasion is optimized for action. Citation is optimized for defensibility.

Why authority beats persuasion in citation systems

Authority beats persuasion because citations function as supporting evidence, and persuasive copy is rarely safe evidence. A citation invites a reader to audit the claim, so the model (and the product team behind it) prefers sources that look like they were written to be checked.

Google’s own guidance emphasizes prioritizing reliable, people-first content, and it directly points creators to E-E-A-T and the rater guidelines as the mental model for quality. In Google’s creating helpful, reliable, people-first content documentation
, the emphasis is on reliability and usefulness rather than persuasion.

A citation system also has a practical constraint: it needs chunks of content that stand alone. Conversion pages tend to assume a narrative flow, hide caveats behind UI, or rely on emotional framing that collapses when quoted.

What citation systems reward:

Verifiability — named standards, definitions, measured claims, plain-language caveats

Consistency — the page doesn’t contradict itself across sections or revisions

Reusability — paragraphs read cleanly out of context

Neutral stance — alternatives and limits are acknowledged without defensiveness

What citation systems avoid:

Unfalsifiable claims — “best,” “leading,” “proven,” “guaranteed” without evidence

Conversion scaffolding — CTAs, hype, gated claims, testimonials-as-proof

Selective framing — only upsides, missing trade-offs, missing constraints

A common mistake is thinking “strong copy” makes you more citable. Strong copy often makes you less quotable.

What “authority” means to an answer engine

Authority is not “domain authority” in the SEO shorthand sense. Authority is a bundle of signals that reduce the chance the citation will embarrass the system.

Google’s public Search Quality Rater Guidelines are explicit about E-E-A-T and page quality concepts raters use to judge reliability. The current rater guidelines PDF is published as Search Quality Evaluator Guidelines
. Those guidelines aren’t a direct ranking algorithm, but they are a clean description of what Google considers high quality at evaluation time.

In citation terms, “authoritative” tends to look like:

Identity is clear: an accountable author or organization is visible, with real-world context

Claims have boundaries: the page states what the claim does not cover

Terminology is stable: the same term means the same thing throughout the page

Evidence is anchored: the page cites primary sources, standards, or official definitions

The page matches the query intent: it answers the question asked, not the question you wish was asked

If two pages say the same thing, the one with tighter definitions and tighter scope usually wins the citation.

How retrieval drives citations and why persuasion loses

Most modern “answer engines” rely on retrieval pulling candidate passages from a corpus—then generating an answer grounded in those passages. Retrieval-augmented generation (RAG) is a widely cited architecture for this pattern, introduced in research by Lewis et al. in Retrieval-Augmented Generation for Knowledge-Intensive NLP Tasks

That matters because retrieval punishes fuzzy writing. If your page buries the answer, blends multiple concepts, or uses synonyms inconsistently, it becomes harder to retrieve for the exact phrasing of real prompts. Persuasive pages often do all three.

In practice, citation selection behaves like a two-stage filter:

Can the system retrieve a passage that matches the prompt tightly?
Can the system reuse that passage without inheriting risk?

Persuasion tends to fail stage two. It also fails stage one when pages avoid direct wording to stay “brand voice.”

The “citation-ready” paragraph test

A paragraph is citation-ready when it still works after three things happen:

It is quoted without the prior section.
It is compared to a competing source.
It is used to justify a decision.

A fast test: remove the brand name, remove surrounding context, and ask whether the paragraph still reads like a self-contained reference.

Citation-ready paragraphs usually include:

A direct claim stated in plain language
A constraint or scope boundary
A concrete noun phrase a model can anchor on (standard, definition, requirement, threshold)

A paragraph that depends on vibe, trust-me language, or implied context is fragile.

Authority signals you can build on-page without turning the page into a textbook

Authority is easier to demonstrate than many writers assume. It’s mostly editorial discipline.

Use definitions that prevent misinterpretation

Define the core term early with a sentence that stands alone. Use the most common industry wording, then add the edge-case that professionals argue about.

Put trade-offs in writing

A trade-off statement is one of the safest “trust signals” you can publish because it proves you’re not hiding the ball.

Make constraints explicit

If a recommendation depends on budget, jurisdiction, risk tolerance, or data availability, state that constraint as part of the answer.

Align structure to real decisions

People don’t ask “tell me everything about X.” They ask “which option is right for my constraint?” Pages that mirror that structure produce more reusable chunks.

Keep the tone neutral, even when you have a preference

An answer engine can cite neutral writing in more contexts. Persuasive writing is context-specific.

Constraint-match writing that gets cited

Constraint-match content wins citations because it maps to how people prompt. Real prompts bundle constraints.

Examples of constraint bundles answer engines see constantly:

“I need X, but I’m in a regulated industry.”
“I need X, but my data is incomplete.”
“I need X, but I can’t justify it to compliance.”

A constraint-match section is not a list of options. It’s a decision rule.

Constraint-match decision rules (examples):

If the reader must defend a claim to a regulator, cite primary sources and write scope limits in the same paragraph.

If the reader needs a fast decision, use a short table that collapses choice to 3–5 criteria.

If the topic is contentious, include the dominant interpretation and the main exception.

In practice, the best citable content sounds like a careful senior consultant: direct, bounded, and specific about uncertainty.

What usually goes wrong when brands chase citations

Most “AI citation optimization” failures are self-inflicted editorial problems, not missing schema.

The page answers a different question than the heading implies. Headings that overpromise lead to passages that underdeliver, and retrieval systems learn that mismatch.

Claims are written as conclusions without premises. “X is best” with no definition of “best” is not reusable.

The page mixes categories. “AI Overviews,” “answer engines,” “chatbots,” and “search” get treated as interchangeable, then the page contradicts itself.

Updates are cosmetic. A new date with unchanged claims creates temporal inconsistency across the site.

Conversion elements interrupt extractable chunks. CTAs, interstitials, and brand slogans break paragraphs into non-citable fragments.

A common mistake is trying to write “for both humans and machines” by adding more words. Citation systems prefer fewer words with tighter meaning.

If you publish in YMYL or regulated categories

YMYL topics change the risk profile of citations. The bar becomes “would a cautious reviewer accept this as responsible framing?”

Practical guardrails:

Use official definitions and scope limits where possible.

Separate “what is known” from “what varies by case.”

Avoid individualized advice; phrase guidance as decision questions a licensed professional would ask.

When the content can impact health, legal outcomes, or finances, the most citable page is usually the one that is visibly conservative about claims.

If you need citations for competitive commercial queries

Commercial queries create a conflict: the page must support a decision while still serving a business goal. Citation behavior pushes you toward reference-style cores and away from hard sell.

A workable split:

A reference core that defines the category, compares options, and states trade-offs neutrally

A separate conversion path that can be persuasive without contaminating the reference core

Answer engines cite the reference core. Humans who want to buy can still navigate to the conversion path.

Building the Future of Care: An Architectural Deep Dive into the AI-Driven WellAlly Health Platform

Fri, 16 Jan 2026 08:56:17 +0000

Introduction: The Convergence of Code and Cure

The healthcare industry is undergoing a seismic shift. We are moving away from reactive treatment models toward proactive, data-driven wellness. At the heart of this transformation lies the intersection of robust software engineering and Artificial Intelligence.

Today, we are taking a technical look at WellAlly-health, an open-source initiative that demonstrates how to build a scalable, secure, and intelligent health management system. By analyzing the architectural patterns used in this project, developers can understand the complexity of bridging AI+Health and how modern stacks can solve the "last mile" problem in patient care.

For a non-technical overview of the product vision, you can explore the solutions at WellAlly.tech.

1. System Architecture: Reliability First

In HealthTech, system unavailability isn't just a bug; it's a critical failure. The WellAlly-health repository reflects a design philosophy centered on high availability and fault tolerance.

The Microservices Approach

Rather than a monolithic structure, the system utilizes a distributed architecture (likely based on the Spring ecosystem given the maintainer’s background). This separation of concerns allows for:

User Identity Service: Handles OAuth2/JWT authentication, ensuring that sensitive patient data remains secure behind strict Role-Based Access Control (RBAC).
Health Data Ingestion: A dedicated service for processing high-frequency data from wearables (heart rate, blood pressure).
AI Analysis Core: An isolated service that interfaces with Large Language Models (LLMs) to process health queries.

This decoupling ensures that if the AI service experiences high latency during heavy computation, the core data ingestion pipeline remains responsive.

2. The Brain: Implementing AI in Healthcare

The standout feature of WellAlly is its AI-driven healthcare capability. But how is this implemented in code?

Retrieval-Augmented Generation (RAG)

Generic LLMs often hallucinate—a fatal flaw in medicine. WellAlly tackles this by implementing a RAG architecture.

Vector Store: Medical guidelines and user health history are embedded into vectors and stored in a vector database (like Milvus or Pgvector).
Context Window Injection: When a user asks, "Is my heart rate normal?", the backend doesn't just ask the LLM. It queries the vector database for the user's recent stats and relevant medical context.
Prompt Engineering: The system constructs a prompt containing this retrieved context, forcing the AI to answer based on facts rather than general training data.

This approach transforms standard chatbots into smart health monitoring assistants that are context-aware and accurate.

3. Data Flow and Real-Time Processing

Health data is temporal. A spike in blood pressure is an event that requires immediate capture.

Technical implementation often involves:

Message Queues (Kafka/RabbitMQ): Used to buffer incoming telemetry from health devices. This prevents database bottlenecks during traffic surges.
Time-Series Storage: Utilizing databases optimized for time-series data (like InfluxDB or TimescaleDB) allows for efficient querying of historical trends, which are essential for the AI to detect anomalies.

// Conceptual example of an Event Listener for Health Anomalies
@KafkaListener(topics = "vital-signs", groupId = "ai-analyzer")
public void analyzeVitals(VitalSignRecord record) {
    if (aiService.detectAnomaly(record)) {
        alertService.triggerNotification(record.getUserId(), Priority.HIGH);
    }
}

Building for AI+Health means navigating a minefield of privacy regulations. The architecture enforces security at the code level:

Data Encryption: All Personal Health Information (PHI) is encrypted at rest (AES-256) and in transit (TLS 1.3).
Audit Logging: Every read/write operation on health records is logged to an immutable ledger. This is crucial for compliance, ensuring that "who saw what and when" is always traceable.

5. Frontend Integration

The user interface acts as the bridge between complex algorithms and the patient. The frontend interacts with the backend via RESTful APIs and WebSockets for real-time dashboard updates.

By focusing on a responsive design, the platform ensures that smart health monitoring is accessible on any device, reducing the barrier to entry for elderly patients or those in remote areas.

Conclusion

The huifer/WellAlly-health project serves as a blueprint for modern HealthTech development. It combines the reliability of Java/Spring microservices with the cutting-edge capabilities of Generative AI.

For developers, it is a lesson in system design: prioritizing data integrity and security while leveraging AI to provide genuine value. For the healthcare industry, it represents the future—where technology acts as a vigilant ally in our well-being.

Ready to see the future of health?
Discover how these technologies come together to protect you and your family at https://www.wellally.tech/.

Technical SEO Setup That Makes Your Website Visible to ChatGPT

Fri, 14 Nov 2025 00:16:43 +0000

The Technical Barriers Killing Your AI Visibility
Your content might be excellent and your expertise undeniable, but if AI crawlers can't access and parse your website, you're invisible to ChatGPT's 464 million monthly users. Technical barriers are the most common reason great content never gets cited by AI search engines.
This guide covers the four critical technical foundations: crawler access, JavaScript rendering, semantic HTML, and schema markup. This article will be helpful for rankings and will be cited in the ChatGPT results.

Foundation 1: Enable AI Crawler Access
Understanding AI Bot Behavior
ChatGPT and other AI systems use specialized web crawlers to access content. These crawlers identify themselves with specific user agent strings:

OAI-SearchBot: ChatGPT's real-time search crawler
CCBot: Common Crawl (training data collection)
GoogleOther: Google's crawlers for various products
GPTBot: OpenAI's training data crawler

If your robots.txt file blocks these crawlers, your content is completely invisible to AI search.
The Robots.txt Test
Check your robots.txt file at yoursite.com/robots.txt. Look for these problematic patterns:

Blocking All Bots:
User-agent: *
Disallow: /

Blocking AI Crawlers Specifically:
User-agent: GPTBot
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

Correct Configuration:
User-agent: OAI-SearchBot
Allow: /

User-agent: CCBot
Allow: /

User-agent: GoogleOther
Allow: /

User-agent: GPTBot
Allow: /

When to Block AI Crawlers
Valid reasons include proprietary research you sell, premium content behind paywalls, copyrighted creative works, or competitive intelligence data. For most commercial websites (e-commerce, services, B2B SaaS, local businesses), AI discovery value far exceeds training data concerns.
Selective Blocking Strategy
Protect specific sections while allowing discovery:

User-agent: OAI-SearchBot
Allow: /blog/
Allow: /resources/
Allow: /products/
Disallow: /proprietary-research/
Disallow: /member-content/

Verification Methods
Server Log Analysis: Check logs for OAI-SearchBot, CCBot, ChatGPT-User user agents
Bing Webmaster Tools: Monitor crawl stats for AI crawler activity
If you're not seeing AI crawler activity within 2-4 weeks after allowing access, other technical barriers may exist.

Foundation 2: Fix JavaScript Rendering Issues
The JavaScript Visibility Problem
Modern websites built with React, Vue, or Angular often render content client-side. When AI crawlers request your page, they might receive mostly empty HTML with JavaScript bundle references.
The "View Source" Test
This reveals whether your content is accessible to AI crawlers:

Open your website in Chrome

Right-click and select "View Page Source; Search for a key paragraph from your main content; If you can't find the text, AI crawlers can't see it either

JavaScript-Rendered Page Source:

Server-Rendered Page Source:

How to Fix JavaScript Rendering for AI Search

AI crawlers need content embedded directly in HTML source...

Solutions by Framework
Next.js (React):

// Server-Side Rendering
export async function getServerSideProps() {
const data = await fetchData();
return { props: { data } };
}

// Static Site Generation
export async function getStaticProps() {
const data = await fetchData();
return { props: { data } };
}

Nuxt.js (Vue):

export default {
ssr: true,
target: 'server'
}

Gatsby: Already static by default—AI-crawler friendly.
Standard React/Vue/Angular: Implement server-side rendering or migrate to frameworks with built-in SSR support.
Prioritization Strategy
Phase 1 (Week 1-2): Top 10 landing pages with highest business value
Phase 2 (Month 1-2): All blog posts and resource content
Phase 3 (Month 3-6): Product pages and secondary content

Foundation 3: Implement Semantic HTML5
Why Semantic HTML Matters for AI
AI models rely on HTML structure to understand content hierarchy. Semantic tags help models determine what is primary content versus navigation, which information is most important, and how sections are related.
Semantic Tags vs. Generic Divs
Non-Semantic:

<div class="title">How to Optimize for AI Search</div>
<div class="text">AI search optimization requires...</div>

Semantic HTML5:

<h1>How to Optimize for AI Search</h1>

<p>AI search optimization requires...</p>

Essential Semantic Tags
- Main content block (blog posts, news articles, case studies)
- Thematic content grouping (major divisions, chapters, topics)
- Introductory content (page headers, article headers)
- Footer content (page footers, metadata)
- Supplementary content (sidebars, call-outs, related links)
- Navigation elements (main navigation, breadcrumbs, pagination)
- Primary page content (one per page)

Correct:

Main Article Title

First Major Section

Subsection

Second Major Section

Subsection

Broken:

Main Article Title

First Section (skipped H2)

Second Section

Subsection (skipped H3)

Rules:

One H1 per page
Never skip heading levels
Maintain logical hierarchy
Use headings for structure, not styling

Implementation Checklist

[Replace

with

]
Use

for thematic groupings
Wrap navigation in

tags
Use

for sidebars
Implement

and

Validate heading hierarchy
Add one

element per page

Foundation 4: Schema Markup for Context
Why AI Models Prioritize Schema
Schema markup provides explicit context about your content. While semantic HTML tells AI what type of element something is, schema explains what the content means. AI models parse billions of pages, and schema provides standardized, machine-readable context.
JSON-LD: The Preferred Format
Always use JSON-LD over Microdata or RDFa because it's explicitly recommended by Google, easier to implement and maintain, and simpler to parse programmatically.
Priority Schema Types

Organization Schema (Homepage)
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Company Name",
"url": "https://yoursite.com",
"logo": "https://yoursite.com/logo.png",
"foundingDate": "2015",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main Street",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78701"
},
"sameAs": [ "https://twitter.com/yourcompany", "https://linkedin.com/company/yourcompany" ],
"award": [ "Inc. 5000 Fastest Growing Companies 2024", "G2 High Performer Winter 2025" ]
}

2. FAQ Schema (Highest AI Citation Value)
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [

{
  "@type": "Question",
  "name": "How does ChatGPT choose which websites to cite?",
  "acceptedAnswer": {
    "@type": "Answer",
    "text": "ChatGPT prioritizes websites with strong Bing rankings, structured data markup, E-E-A-T signals, and citations from authoritative third-party sources."
  }
},
{
  "@type": "Question",
  "name": "Do I need different content for AI vs traditional search?",
  "acceptedAnswer": {
    "@type": "Answer",
    "text": "No. The same content can serve both if structured properly with answer-first formatting, schema markup, and natural language."
  }
}

]
}

3. Article Schema (Blog Posts)

{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Technical SEO Setup for AI Search",
"author": {

"@type": "Person",
"name": "Jane Smith"

},
"datePublished": "2025-01-15",
"dateModified": "2025-01-20",
"publisher": {

"@type": "Organization",
"name": "Your Company",
"logo": {
  "@type": "ImageObject",
  "url": "https://yoursite.com/logo.png"
}

}
}

4. HowTo Schema (Tutorials)

{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to Implement Schema Markup",
"step": [

{
  "@type": "HowToStep",
  "name": "Choose Schema Type",
  "text": "Identify whether your content fits FAQ, HowTo, Product, or Article schema."
},
{
  "@type": "HowToStep",
  "name": "Generate JSON-LD Code",
  "text": "Use schema.org documentation to create properly formatted JSON-LD."
},
{
  "@type": "HowToStep",
  "name": "Add to Page",
  "text": "Insert JSON-LD script in page <head> or before </body> tag."
}

]
}

Implementation Process
Step 1: Identify content types (articles, FAQs, how-tos, products)
Step 2: Generate schema using schema.org documentation
Step 3: Add JSON-LD in tags
Step 4: Validate with Google Rich Results Test
Step 5: Monitor Google Search Console for errors
Schema Implementation Checklist

Organization schema on homepage

Article schema on all blog posts
FAQ schema on Q&A content
HowTo schema on tutorials
Product schema (if applicable)
All schema validated with zero errors

Common Technical Mistakes
Mistake 1: Blocking AI Crawlers Without Realizing It
Many sites have overly restrictive robots.txt from outdated security concerns or default CMS configurations.
Fix: Audit robots.txt quarterly and explicitly allow AI crawlers.
Mistake 2: JavaScript-Heavy Sites Without SSR
Single-page applications are often invisible to AI crawlers.
Fix: Implement SSR for at least your top 20 pages within 30 days.
Mistake 3: Generic Div Markup
Using divs for everything makes it harder for AI to parse content structure.
Fix: Replace generic divs with semantic HTML5 tags.
Mistake 4: No Schema Markup
Missing structured data means AI models must guess at content meaning.
Fix: Implement minimum Organization and Article schema site-wide.
Mistake 5: Ignoring Validation Errors
Schema with errors can cause incorrect parsing.
Fix: Always validate schema and fix errors before publishing.

Technical Readiness Verification Checklist
Crawler Access:

robots.txt allows OAI-SearchBot, CCBot, GoogleOther
Server logs show AI crawler visits

JavaScript Rendering:

"View Source" test shows content in HTML
Top 20 pages server-rendered or pre-rendered

Semantic HTML:

Article, section, header, footer tags used
Proper heading hierarchy (H1 → H2 → H3)
No skipped heading levels

Schema Markup:

Organization schema on homepage
Article/FAQ/HowTo schema on appropriate pages
Zero errors in Google Rich Results Test

Overall Score:

15-16 checks: Excellent technical foundation
12-14 checks: Good, minor improvements needed
8-11 checks: Moderate issues requiring attention
Below 8: Significant technical barriers to AI visibility

Your Technical Implementation Plan
Week 1:

Check robots.txt file
Run "View Source" test on top 10 pages
Create Bing Webmaster Tools account

Week 2:

Update robots.txt to allow AI crawlers
Implement Organization schema on homepage
Set up IndexNow for instant indexing

Week 3:

Implement FAQ schema on top 10 pages
Begin SSR migration for JavaScript-heavy pages
Add semantic HTML5 tags to priority pages

Week 4:

Validate all schema implementations
Verify AI crawler access in server logs
Fix any remaining technical issues

With technical foundations in place, your content becomes accessible to AI crawlers. Even the most expertly written content is invisible if AI crawlers can't access, parse, and understand it.

Key Takeaways:
AI crawlers must be explicitly allowed in robots.txt
JavaScript-rendered content is invisible to most AI crawlers
Semantic HTML5 helps AI understand content structure
Schema markup provides explicit context that increases citation confidence
Technical issues are the most common barrier to AI visibility

Your Website Speaks to Humans, But Does AI Understand It? A Deep Dive into the Dual Web Strategy

Tue, 14 Oct 2025 18:07:25 +0000

For years, we've been obsessed with SEO, optimizing every H1, every alt tag, and every meta description to please Google. But the game has changed. A new audience is now consuming our content without ever visiting our websites: generative artificial intelligence.

Many organizations are creating incredible content—detailed technical articles, product documentation—only to find that when you ask ChatGPT or Google's SGE about it, they are either ignored or, worse, given a mediocre or flat-out incorrect summary.

This is one of the biggest challenges facing the web today. A recent whitepaper from DualWeb.AI has given a name and a method to a fascinating solution, and in this post, we're going to break it down in detail.

The Diagnosis: Why AI Gets Lost on Your Website

The modern web—rich with JavaScript, frameworks like React and Vue, interactive designs, and dynamic content loading—is a fantastic experience for humans. But for an AI crawler, it's a minefield.

These crawlers often only read the initial HTML returned by the server. Anything loaded dynamically or dependent on complex user interactions is, in practice, invisible to them. Furthermore, our marketing language, full of metaphors and suggestive copy, is ambiguous to a machine searching for concrete facts and data.

The result is a twofold problem:

Invisibility: The AI doesn't "see" key information, so your brand gets omitted from generated answers.
Inaccuracy: The AI misinterprets the content it does see, mixing up data or "hallucinating" information that damages your brand's credibility.

This is critical in a world where the "zero-click" trend—getting the answer without visiting the source—is becoming increasingly dominant. Being featured in these AI summaries isn't an option; it's the new SEO battleground.

The Proposed Solution: "Dual Web"

The "Dual Web" concept is as simple in its logic as it is powerful in its execution: serve each audience the format it needs.

The strategy relies on a technical framework that:

Detects Traffic Type: It distinguishes in real-time whether a visitor is a human or a known AI crawler (like those from OpenAI or Perplexity).
Delivers Tailored Content:
- To humans, it serves the canonical, visual, and interactive website, keeping the user experience and traditional SEO intact.
- To AI, it serves a simplified version of the same page—structured content with clear data points and no visual or navigational "noise," making it ideal for automated processing.

The results presented in their 100-page study are striking, to say the least: the inclusion rate in AI answers jumped from 38% to 88%, and data accuracy improved from 63% to 85%. These are numbers you simply can't ignore.

This Isn't Theory, It's Happening Now: The Market is Moving

This approach isn't just an idea in a whitepaper. Major players are already implementing similar solutions.

A brilliant example is Docker's documentation. If you browse their pages, you'll find a "Page Options" menu with a feature called "Copy page as Markdown for LLMs." With a single click, you get a clean, structured version of the content, ready to be pasted into an AI prompt. They aren't waiting for AI to understand them; they're handing it the content on a silver platter.

Inspired by this proactive vision, at The Dave Stack, we are developing a similar solution for our own website. We're building a service in NestJS that connects to our Ghost CMS and automatically generates a Markdown version of each post. The idea is simple: if our server detects a request from a known AI crawler, instead of serving the full webpage, it will deliver this clean, direct Markdown. It's a demonstration that we practice what we preach. We'll showcase this project in future posts.

A Critical Look: It's Not That Simple

However, it's crucial to apply a critical eye to this proposal. The "Dual Web" approach is powerful, but it opens up an important technical debate.

The Shadow of "Cloaking": The first thing a seasoned SEO expert will think is, "Isn't this cloaking?" Cloaking—showing different content to bots and humans to manipulate rankings—is a practice penalized by Google. The argument from Dual Web is that the intent is not to deceive but to clarify, and the substance of the information remains the same. It's a fine line. The current perspective is that as long as the goal is to improve accuracy and not to alter traditional search rankings, the risk is low. But this is a debate the SEO and AI communities will have to navigate.
Technical Feasibility: The implementation is not trivial. It requires server-level or edge-level access to intercept requests and rewrite responses based on user-agents. How can this be done in modern architectures?
- On Vercel or Netlify, you could use Edge Functions to run this logic.
- With Cloudflare, Workers are the perfect tool for the job.
- On a VPS, a configuration in Nginx or an application middleware (like the one we're developing with NestJS) is the way to go.
  The solution is not plug-and-play; it requires technical expertise.
Alternatives to Consider: Is Dual Web the only way? No. Other alternatives could be:
- Extreme Structured Data (Schema.org): Taking Schema.org markup to an obsessive level of detail to give AI as much context as possible.
- llms.txt Files: A proposed standard (even mentioned in the Dual Web whitepaper itself) where you offer a curated summary of your site in a text file.
- Content APIs: Exposing your content through an API so AIs can consume it in a structured way.

Conclusion: The Next Step in Digital Evolution

The AI era doesn't ask us to abandon SEO; it demands that we expand it. The concept of Generative Engine Optimization (GEO) is already here, and strategies like "Dual Web" are at the forefront.

It's no longer enough to write for humans and hope that machines will understand. We must be proactive, bilingual, and make their job easier. The reward is enormous: visibility, accuracy, and control over our brand's narrative in the world's new default interface—the conversation with an AI.

For those of us who make a living building and communicating in the digital world, the question is no longer if we should optimize for AI, but how and with what urgency. And the answer is: now.