Fundamentals · The map
The AI visibility stack
Three disciplines, one outcome. The value of thinking in layers is diagnostic: when you're not getting cited, the stack tells you which layer to go and fix.
AI visibility is not a fourth discipline — it is the outcome of three stacked ones: SEO makes a page findable, AEO makes a passage answerable, and GEO makes that passage worth quoting.
Each layer depends on the one below it. A brilliant original statistic on a page that returns a 403 to GPTBot has zero visibility. A perfectly crawlable page that never answers a question has almost as little.
The mapFour layers, bottom to top
SEO — findability
Can a machine fetch, render, parse and index this URL, and does the site's link structure tell it this page matters?
AEO — answerability
If a retrieval system splits this page into chunks, does any single chunk stand alone as a complete answer to a real question?
GEO — quotability
Given five sources that all answer the question, is there a reason to quote this one? A number, a date, a name, a claim nobody else made?
AI visibility
Measured share of citations and recommendations across ChatGPT, Perplexity, Claude, Gemini, Copilot and AI Overviews.
01What each layer actually controls
| Layer | Unit of work | Primary levers | Symptom when broken |
|---|---|---|---|
| SEO | The page | robots.txt, sitemaps, render budget, Core Web Vitals, internal links, canonicals | Zero AI crawler hits in server logs; page absent from Google index |
| AEO | The passage | Question-shaped H2/H3, 40–60 word answer blocks, one topic per URL, tables and lists | Crawlers fetch the page constantly, but you're never quoted |
| GEO | The claim | Original data, named sources, direct quotes, expert authorship, freshness dates | You get cited occasionally, but competitors get the recommendation |
| Entity | The brand | Wikidata, Wikipedia, LinkedIn, consistent schema, third-party mentions | Engine cites your page but names a bigger competitor as the answer |
That last row is the one most teams miss. Being cited and being recommended are separate outcomes. An engine will happily use your page as a source and then name a better-established brand in the sentence. Fixing that is an entity problem, not a content problem — see get cited faster.
02How a modern answer gets built
Understanding the pipeline makes the layer model concrete. When someone asks a complex question, most retrieval-augmented systems do roughly this:
- Query fan-out. The assistant decomposes the question into several narrower sub-queries and searches each separately. “Best VPN for streaming in Europe” might become three searches. Your page only needs to win one of them.
- Retrieval. Candidate documents are fetched from a search index, a proprietary index, or a live crawl.
- Chunking and ranking. Documents are split into passages and scored for relevance to each sub-query. This is where page structure decides your fate: a passage that references “as mentioned above” loses its meaning the moment it's separated.
- Synthesis. The model writes an answer from the top-scoring passages and attaches citations to the sentences it drew from.
Every layer of the stack maps onto a step. SEO gets you into retrieval. AEO gets your chunk ranked. GEO gets your chunk chosen for the sentence that carries the citation.
Practical implicationQuery fan-out is the reason narrow pages beat omnibus guides. A 4,000-word “ultimate guide” competes for one broad query. Twelve focused pages compete for twelve sub-queries, and sub-queries are what the engine is actually searching for.
03Diagnosing your own stack
Run these four checks in order and stop at the first failure.
Are AI crawlers reaching you?
Grep your access logs for
GPTBot,OAI-SearchBot,ClaudeBot,PerplexityBotandGoogle-Extended. Zero hits means a robots.txt rule, a WAF rule, or a CDN bot-management default is blocking you. Fix this before anything else.Does any single chunk answer a question?
Take your most important page, delete everything except one 300-word section, and read it cold. If it doesn't make sense standing alone, no chunk of it will either.
Is there anything only you can say?
If every claim on the page is available on ten other domains, an engine has no reason to prefer you. First-party data is the cheapest durable advantage most teams have and the one they use least.
Is your brand a resolvable entity?
Search your brand name plus your category. Do Wikidata, LinkedIn, and your own
Organizationschema all agree on what you are and what you do? Inconsistency here caps recommendation share regardless of content quality.
Next: start at the bottom with SEO foundations, or skip to the layer your diagnosis flagged.
Questions engines askFrequently asked questions
Is AEO just a rebrand of SEO?
There is real overlap, and some practitioners argue the distinction isn't worth drawing. The useful difference is the unit of optimization: SEO optimizes a page to rank, AEO optimizes a passage to be extracted as a direct answer. That changes concrete decisions — where you put the answer, how you phrase headings, whether one page should cover three questions or one. Keep the distinction if it changes your work; drop the labels if it doesn't.
Which layer should I fix first?
Always the lowest broken one. Check crawl access and indexation before you touch content structure, and fix content structure before you invest in original research. The diagnostic table on this page maps each symptom to the layer that causes it.
Can I skip SEO and go straight to GEO?
No. Answer engines overwhelmingly retrieve from the live, indexed web. If a crawler can't fetch your page, or your CDN is blocking AI user agents by default, nothing downstream matters. Cloudflare's shift to blocking AI bots by default (blog.cloudflare.com, July 2025) has silently removed a large number of sites from AI answers — check your configuration before you write a single new word.