Definition · Pillar

What is AI SEO?

AI SEO is the umbrella term for optimizing a site's visibility across the whole AI-search landscape — generative answers, AI crawlers, and the technical infrastructure that makes a site legible to both.

Ritik Namdev Ritik Namdev ·Published September 2026 ·12 min read ·Last verified September 2026

The quick answer

AI SEO means optimizing a site's visibility across the whole AI-search world. That includes three things: getting cited in generative AI answers (GEO), showing up in classic and voice answer surfaces (AEO), and staying technically reachable by AI crawlers at all.

It is a category label, not one single technical practice. Think of it the way you'd think of "digital marketing" — a name for a whole area, not a specific tactic.

What this page establishes
  • AI SEO is the umbrella above three narrower disciplines: GEO (being cited in generative answers), AEO (answer surfaces including non-generative ones), and the technical crawler-access work that makes either possible.
  • The three sit in a strict dependency order — access, then content structure, then measurement. Each layer only pays off if the one beneath it already works.
  • The most consequential distinction inside the umbrella is retrieval bot versus training crawler. A retrieval bot fetches a page live and produces the citation; a training crawler feeds a future model and affects nothing today.
  • The field has one peer-reviewed causal study (Aggarwal et al., KDD 2024) and a large body of correlational vendor analysis. Almost every confident "ranking factor" claim in AI search rests on the second kind.
  • "AI SEO" names a category, not a strategy. Every claim on this page that describes what actually moves citation is graded tactic by tactic in the tactic evidence scoreboard — this page deliberately does not repeat that detail.

How AI SEO sits above GEO, AEO and LLMO

AI SEO sits above the more specific terms. GEO targets generative answer platforms specifically. AEO covers a wider set of answer surfaces, including non-generative ones. LLMO is mostly a technical synonym for GEO.

It is a nesting structure. AI SEO is the outer box; inside it sit GEO, AEO, LLMO and the technical crawler work that makes any of them possible. Each inner term names a narrower problem with its own tactics and its own evidence base, and the terminology comparison sets out exactly where each scope starts and ends.

This page is the umbrella. Three narrower pillars sit under it, and each one is the canonical page for its layer: What is GEO? for the generative-citation layer, the AI bot registry for crawler access, and the measurement standard for reporting. Anything more specific on this site hangs off one of those three.

The nesting matters in practice. If someone says they "do AI SEO", you still do not know what they do. Ask which layer: getting cited in ChatGPT answers, winning featured snippets, or making sure OAI-SearchBot is not blocked in robots.txt. Those are three different jobs, and the answer differs again per engine — a strategy tuned for one may not transfer.

So the umbrella is worth having and worth distrusting. It names a real shift quickly, and it is not a strategy by itself.

Which discipline do you actually need?

If this is your situationThe disciplineStart here
You don't know whether AI bots can reach your site at allTechnical crawler accessThe AI bot registry
Bots reach you, but you're never quoted in generated answersGEOThe tactic evidence scoreboard
You want to know which tactics have real evidence behind themGEO, evidence layerThe scoreboard and the null results registry
You can't tell whether anything you did workedMeasurementThe measurement standard
You're being asked to explain the acronyms to a stakeholderTerminologyGEO vs AEO vs LLMO
Organic traffic dropped and you suspect AI answersDiagnosis firstThe AI traffic loss calculator

What the umbrella covers

Content strategyWriting and structuring content so generative AI cites it. See the tactic scoreboard for what actually works.
Technical accessMaking sure AI crawlers can reach and read your site at all. Covered in the AI Bot Registry.
MeasurementTracking citation rate and share of voice across engines. See the measurement standard.

Which layer should you fix first?

The stack, in the order it has to be fixed
  1. 1 Technical access Can a retrieval bot fetch and read the page at all? Binary, and nothing above it matters until it is clean.
  2. 2 Content structure and substance Can a clean, self-contained answer be lifted from the page? This is where the evidenced tactics live.
  3. 3 Measurement Are you actually being cited, and is it moving? Useless without the first two, and the weakest layer industry-wide.

Those three areas aren't equally urgent. They stack. Each one only pays off if the layer beneath it already works. Get the order wrong and you spend months on content that no AI system can even reach.

Layer one: technical access. Can an AI retrieval bot fetch your page at all? This is binary. If OAI-SearchBot is blocked in your robots.txt, ChatGPT Search cannot cite you, no matter how good the page is — and more sites block it by accident than on purpose.

Rendering is the second access failure. If your content only appears after client-side JavaScript runs, a bot that doesn't execute JavaScript sees an empty shell. Whether AI crawlers render JavaScript at all is an open question, and even for Google, JavaScript costs roughly nine times the crawl time of HTML. Nothing else on this list matters until this layer is clean. The AI bot registry — the crawler-access pillar under this umbrella — lists every documented user agent and which ones to allow, with each operator's own documentation linked per bot.

Layer two: content structure and substance. Once a bot can read the page, can it lift a clean answer from it? This is the GEO layer, and it is where the tactics with actual evidence live. This page deliberately stops at naming the layer: which specific tactics survive scrutiny, and which are merely repeated, is graded one by one in the tactic evidence scoreboard.

Layer three: measurement. Are you actually being cited, and is it changing? This layer is last because it's useless without the first two. There's nothing to measure until a bot can reach a page worth citing. It's also the layer where the industry is weakest, since no two vendors define "visibility" the same way. The measurement standard proposes a fix.

Most sites get this backwards. They buy a visibility dashboard before checking whether their robots.txt blocks the retrieval bots. That's paying to watch a number that a five-minute config change would move more than any content strategy could.

How AI SEO differs from classic SEO

The two overlap heavily. The differences are the part worth knowing, because that is where habits from classic SEO quietly mislead you.

Classic SEOAI SEO
The goalRank a page in a listBe quoted inside an answer
The unit that winsA whole pageA specific passage on a page
How many targetsEffectively one dominant engineSeveral engines that disagree
Main success signalRanking position, clicksCitation presence, often without a click
Measurement maturityDecades of tooling and shared definitionsNo shared definition of "visibility" yet
Evidence baseLarge, if imperfectOne peer-reviewed causal study; mostly correlational otherwise

Read the "unit that wins" row twice. It's the one that changes daily writing habits most. In classic SEO, a page competes as a whole document. In AI search, one clean, self-contained paragraph can get lifted while the rest of the page is ignored entirely — and the click that used to follow may not, which Ahrefs has measured and the CTR hub collects. That's why answer-first writing matters more here than it ever did for ranking.

What has not changed

A lot of AI-search content implies you need to throw out what you know. That is oversold. Crawlability still decides everything — a page a bot cannot fetch cannot rank and cannot be cited; the bot list changed, the principle did not. Clear structure still wins, for the same reason it always did: the content is easier to segment.

Genuine expertise still separates you, though the causal evidence that it moves citation is thinner than the confident advice suggests. And speed and clean HTML still help — not as a citation factor, since Core Web Vitals were never designed to be one, but because a well-formed page fetches reliably and parses cleanly. The rest of that checklist is the technical GEO audit.

The honest summary: the technical foundation carries over, and the tactics layered on top need re-testing. That is a meaningful shift, not a reset.

Why the evidence is thinner than the advice

Most introductions to AI SEO leave this part out. The field has far more published advice than published evidence.

Trace the most-repeated statistics in this space and a pattern shows up. A small handful of original sources, mostly vendor blog posts and one peer-reviewed academic study, get cited by writers who then cite each other. The number looks well-established because it appears everywhere. It's actually one data point, repeated. The provenance audit traces twelve of these numbers hop by hop and shows which ones survive the trip. Even the well-run vendor roundups describe their own panel rather than the web, which is a different claim than the headline usually makes it sound.

The causal-evidence gap is even wider than the sourcing gap. Almost every published finding in AI search is correlational. It observes that cited pages tend to have some property. It doesn't show that adding that property causes citation. Those are very different claims, and the difference decides whether a tactic is worth your time.

That changes how you should read every AI SEO article, including this one. Ask two questions of any claim: what is the source, and is it correlational or causal? Most confident advice in this field fails at least one. The response is to weight tactics by evidence, which is what the tactic scoreboard exists to do, and to publish the results that came back empty, which is what the null results registry is for.

A one-hour AI SEO audit

This first pass fits in an hour. It is diagnostic, not a fix list: the point is to find out which layer is your real bottleneck.

  1. Open your robots.txt. Read every rule. Look specifically for wildcards or blanket "block AI" blocks that catch retrieval bots alongside training crawlers. A single misplaced rule here outweighs months of content work.
  2. Fetch three key pages with plain HTTP. No browser. Search each raw response for a sentence you know is on the page. If it's absent, that content depends on client-side rendering and is at risk.
  3. Read the first forty words of your five most important pages. Ask whether each one answers its own title. Most don't. This is usually the single cheapest fix available.
  4. Count the sourced numbers on those pages. Not claims, numbers with a named source and a date. Zero is a common answer, and it's a direct gap against the tactics with the strongest evidence behind them.
  5. Check your server logs for AI bot user agents. Are the retrieval bots visiting at all? If they've never fetched a page, citation isn't your problem yet. Access is.
  6. Run five real questions through two AI engines. Record who gets cited. This is your before-picture, and you can't reconstruct it later.

The free tools here cover most of the mechanical parts, and every method we use ourselves is published in the studies index.

Whichever step surprises you most is where the real work is. For many sites it is step one or step two, which is good news: those are config changes, not a content programme.

A realistic 90-day starting plan

Ninety days, in the order the layers have to be fixed
  1. Days 1-14Fix access

    robots.txt, rendering, raw-HTML verification

    Explicitly allow retrieval bots. Decide separately about training crawlers. Confirm by re-fetching raw HTML, not by assuming the deploy worked.

  2. Days 46-75Build the measurement habit

    15-30 frozen questions, run monthly, logged

    A changing question list produces numbers that look like a trend and are not one.

  3. Days 76-90Read your own data

    Crawler activity and citation log against baseline

    Look for direction, not precision. Two signals tell you whether to keep investing or go back to layer one.

Two things about that shape matter. Access work comes first, and it is confirmed by re-fetching the raw HTML — not by assuming a deploy worked. The question panel in the third window stays frozen, because a changing question list produces numbers that look like a trend and are not one.

Do not expect fast movement. The crawl-to-citation latency study covers why the wait is longer than most people budget for. Notice too that no step involves buying a visibility platform: a tool is worth more once access is fixed and you know what you are looking at.

Common mistakes with the term

Treating "AI SEO" as a single checklist you can finish. It is an umbrella over several distinct disciplines, each with its own open questions and evidence base.

Assuming everything from classic SEO transfers. Some does, some does not, and the tactic scoreboard grades each tactic on evidence rather than assuming carry-over.

Skipping to content while the access layer is broken. The most expensive error on the list, because the work feels productive. You can write excellent pages for months and get nothing while a robots.txt rule quietly excludes you from the engines you are writing for.

Measuring one engine and calling it "AI visibility." Given how little the engines appear to agree, a ChatGPT-only view can miss real progress on Perplexity, or the reverse. The engines are also not remotely the same size, which the market share hub covers.

How do you know it is working?

Retrieval bots appear in your logsThe earliest signal and the most underrated. Crawling has to happen before citation can.
Crawl frequency risesA single visit is discovery. A repeating pattern is closer to inclusion.
You appear on narrow questions firstAlmost nobody's first citation arrives on a broad, competitive query.
Citations repeat across runsAnswers are non-deterministic. Once is luck; the same question weeks apart is the considered set.
Referral traffic, lastDeliberately last. Volume stays small and much citation value never produces a click at all.

AI search gives worse feedback than classic search. There's no rank tracker, no impressions graph, no clean before-and-after. That makes it easy to work for months without knowing whether anything changed. A few signals help, roughly in the order they show up.

The ordering is the useful part. Referral traffic sits last deliberately: AI referral volume stays small for most sites, and much citation value never produces a click at all. Make it your primary success metric and you will conclude the work failed while the four earlier signals are all trending the right way. Referral traffic statistics covers what that value actually looks like.

Where to go next

Start with layer one. Run your site through the AI Overview checker to see whether you appear on the questions you care about — that is the fastest read on whether access or content is your bottleneck.

Then pick the layer the decision table sent you to: the bot registry for access, the tactic scoreboard for content, or the measurement standard for reporting. If you are considering handing any of that work to an agent, what an agent does reliably and where it breaks are worth reading in that order. If you would rather have new findings arrive than go looking for them, the newsletter carries each study when it publishes.

How to cite this
Namdev, R. (2026). What is AI SEO? (v1). Retrieved from https://ritiknamdev.com/blog/what-is-ai-seo

Published under CC BY 4.0 — reuse freely with attribution.

Related work on this site

For the sharpest-defined sub-discipline, see What is GEO?. For the technical foundation, see the AI Bot Registry. For the field-wide picture, see the state of AI search.

§ References

Sources

Figures attributed to third parties above have not been independently verified unless stated otherwise.

Aggarwal et al. (arXiv) — GEO: Generative Engine Optimization, the field's one controlled studyarxiv.org/abs/2311.09735 GEO — full paper PDFarxiv.org/pdf/2311.09735 Wikipedia — Generative engine optimizationen.wikipedia.org/wiki/Generative_engine_optimization Google Search Central — AI features and your websitedevelopers.google.com/search/docs/appearance/ai-features Google Search Central — AI optimization guidedevelopers.google.com/search/docs/fundamentals/ai-optimization-guide Google Search Central — Overview of Google crawlers and fetchersdevelopers.google.com/search/docs/crawling-indexing/overview-google-crawlers Google Patents — US11663201B2, query decompositionpatents.google.com/patent/US11663201B2 Search Engine Journal — Query fan-out in AI Mode, new details from Googlewww.searchenginejournal.com/query-fan-out-technique-in-ai-mode-new-details-from-google/552532 Ahrefs — How much do AI search engines overlap in what they citeahrefs.com/blog/ai-search-overlap Ahrefs — AI Overviews reduce clicks to top-ranking pagesahrefs.com/blog/ai-overviews-reduce-clicks-update Ahrefs — AI SEO statistics roundupahrefs.com/blog/ai-seo-statistics Semrush — AI Overviews studywww.semrush.com/blog/semrush-ai-overviews-study Seer Interactive — 87% of SearchGPT citations match Bing top resultswww.seerinteractive.com/insights/87-percent-of-searchgpt-citations-match-bings-top-results OpenAI — Overview of OpenAI crawlersdevelopers.openai.com/api/docs/bots Perplexity — Official crawler documentationdocs.perplexity.ai/docs/resources/perplexity-crawlers Anthropic — Does Anthropic crawl the web, and how to block itsupport.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler llms.txt — The proposed standardllmstxt.org Search Engine Journal — llms.txt shows no clear effect on AI citationswww.searchenginejournal.com/llms-txt-shows-no-clear-effect-on-ai-citations-based-on-300k-domains/561542 Onely — Google needs 9x more time to crawl JS than HTMLwww.onely.com/blog/google-needs-9x-more-time-to-crawl-js-than-html web.dev — Defining the Core Web Vitals thresholdsweb.dev/articles/defining-core-web-vitals-thresholds StatCounter — Global search engine market sharegs.statcounter.com/search-engine-market-share Statista — Global monthly ChatGPT userswww.statista.com/statistics/1659718/global-monthly-chatgpt-users Similarweb — Generative AI usage statisticsaisearch.similarweb.com/blog/gen-ai-stats Ziptie — How original research wins AI citationsziptie.dev/blog/how-original-research-wins-ai-citations
FAQ

Frequently asked questions

Is "AI SEO" the same as GEO?
No. AI SEO is the broad umbrella term. It covers GEO, AEO, technical AI-crawler work, and classic SEO adapted for AI search. GEO is one specific piece of it.
Do I need to learn a whole new discipline?
Mostly no. Classic technical SEO still matters: crawlability, clear structure, good sourcing. What is new is how generative AI retrieves and cites content.
Is there a risk in using such a broad term?
Yes, if you use it to avoid getting specific. Saying 'we do AI SEO' says almost nothing you can act on. Use the term to name the category. Then get specific about which sub-discipline a task actually needs.
Who should actually spend time learning this?
Anyone whose site depends on being found: SEOs, content marketers, and founders of content-driven businesses. If AI answers are already replacing some of your organic clicks, this affects you now, not later.
Which of the three layers should I fix first?
Technical access, always. It is binary: if a retrieval bot cannot fetch the page, no amount of content work can produce a citation. Content structure is second, measurement third. Fixing them out of order is the most expensive mistake on this page, because content work feels productive while it is being wasted.
What is the difference between a retrieval bot and a training crawler?
A retrieval bot fetches your page live to answer someone's question, and it is what produces a citation today. A training crawler collects content to build future models and has no effect on current citations. Blocking the wrong one is the most common expensive mistake in this field.
Do I need to buy an AI visibility platform to start?
No, and buying one first is the common ordering error. A dashboard measures layer three, which is meaningless while layer one is broken. Check whether your robots.txt blocks retrieval bots before paying to watch a number a config change would move more than any content strategy could.
Can I just measure ChatGPT and call that AI visibility?
You can, but the number will hide more than it shows. The engines appear to disagree substantially about what they cite for the same question, so a ChatGPT-only view can miss progress happening on Perplexity, or the reverse. Measure each engine separately.
How long before any of this shows up?
Longer than most people budget for, and no rigorous study we found pins the interval down. The earliest visible signal is not a citation at all — it is retrieval bots appearing in your server logs, which has to happen before citation can.
Does AI SEO replace classic SEO?
No. It is an added lens on work a competent SEO function already does: technical SEO with an updated bot list, content quality with a sharper emphasis on sourcing and answer-first structure, and reporting with a new set of questions.
Ritik Namdev
Written by

Ritik Namdev

Growth · SEO · GEO

Growth marketer documenting a brand-new site's climb into Google and the AI engines - in public, with real numbers. Every tactic here is tested on real sites before it's published.

The Lab · Weekly

One experiment. Every week.

The field notes in your inbox - one thing I tested, the raw numbers behind it, and what it means for getting cited by AI.

Free forever. Unsubscribe anytime.