- A traditional results page ranks pages and shows ten links. An AI answer retrieves candidate pages, picks a subset, and writes a short answer that names a few brands directly.
- Both start from a similar base — Google's own AI features are built on its core Search index and ranking systems — but the AI step adds retrieval, selection and generation on top.
- Google documents "query fan-out": one question can trigger several related searches behind the scenes before an answer is written.
- Engines publish some of this (crawler names, high-level architecture) and leave the rest undocumented. Treat anything not in official docs as inference, not fact.
- Because an answer is generated, not just ranked, the unit worth measuring shifts from position to how often you're named across many runs.
How does a traditional results page get built, and how is an AI answer different?
A traditional results page ranks pages against a query and shows a list — usually ten blue links — and leaves the choosing to the reader. The page that ranks first still has to be clicked to answer the question.
An AI-generated answer skips the list. It retrieves a set of candidate pages, decides which ones are relevant enough to use, and writes a short answer in sentences, naming a handful of brands or products directly. Google's own documentation says its AI features "rely on our core Search ranking systems to retrieve relevant, up-to-date web pages" before generating a response — so the same underlying index feeds both experiences, but only one of them turns the result into prose that names you or doesn't.
That's the core difference this post is about: ranking chooses an order; generation chooses what to say, and about whom. If any of the terms in this post are unfamiliar, the AI search glossary defines them in one place.
What actually happens between the question and the answer?
Simplified, and leaving out engine-specific detail that isn't public, both pipelines share early stages and diverge at the end:
| Stage | Traditional search (a ranked results page) | AI-generated answer |
|---|---|---|
| Crawl | A bot fetches and renders the page | Same underlying crawl in most cases (Google uses the same index for both) |
| Index | The page is stored and made searchable | Same index, or a separate retrieval index for engines without their own crawl (e.g., ChatGPT's search feature) |
| Retrieve | Pages matching the query are shortlisted | Pages matching the query — and its fan-out sub-queries — are shortlisted |
| Rank / rerank | Shortlisted pages are ordered for display | Shortlisted pages are reranked for relevance to the specific answer being written, not for display order |
| Generate | Not applicable — the ranked list is the output | A model writes an answer using the reranked pages as its source material, with citations where the engine shows them |
The step that doesn't exist in traditional search is query fan-out. Google describes it as the model issuing "concurrent, related queries ... to request more information and fetch additional relevant search results" — its own example is a search about lawn weeds spinning off related searches like "best herbicides for lawns" and "remove weeds without chemicals." One question becomes several searches, and the answer draws on all of them. We cover fan-out and what it means for content planning on its own in what is query fan-out.
What do engines actually document, and what has to stay an assumption?
Published, first-party detail is real but partial. Google documents RAG (retrieval-augmented generation) and fan-out at a conceptual level, and says plainly that "there's no requirement to break your content into tiny pieces for AI to better understand it" and that llms.txt files are ignored by Google Search. OpenAI documents its three bots by name and purpose: OAI-SearchBot crawls and indexes for ChatGPT's search feature, GPTBot is a separate training-only crawler, and ChatGPT-User fetches a single page live when someone asks about a specific URL — robots.txt rules "may not apply" to that last one because a person triggered it, not an automated crawl. Microsoft documents, via Bing Webmaster Tools' AI Performance report (released as a public preview on 10 February 2026), that citation counts shown there are "a sample of overall citation activity," and explicitly that citation frequency "does not indicate ranking, authority, or the role of any page within an individual answer."
What none of the engines document in public detail: the exact reranking model, how many candidate pages are considered before the cut, or why one source gets cited over another equally relevant one. Treat any claim about those internals — including claims in this post's own framing above — as a simplified model, not a specification. There is no single deterministic algorithm to reverse-engineer; each engine runs its own undisclosed process, and it can change without notice.
What does this change for measuring where you stand?
On a results page, position is the measurement: you rank third, or you don't rank at all, for a given keyword. In an AI answer, "ranking" has no equivalent — the output is one piece of generated text, not a sortable list, so there's nothing numbered to track from run to run.
What replaces it is how often your brand gets named, cited or recommended across repeated, independent runs of similar buyer questions — visibility rate, not rank. A single Ahrefs study of 15,000 long-tail queries found that links ChatGPT cites overlap with Google's own top 10 results only about 8% of the time, and Gemini and Copilot score similarly (8.6% and 8.2%); Perplexity was the outlier at roughly 28.6%, likely because it's built to always cite a source. Ranking well on Google, in other words, is only weakly correlated with being cited in most AI answers — which is why checking an AI answer directly matters, not just checking your SERP position. We go deeper on the four metrics that actually hold up for this in how to measure AI visibility.
What stays exactly the same as before?
Three things haven't changed. First, Google says explicitly that "the best practices for SEO continue to be relevant because our generative AI features on Google Search are rooted in our core Search ranking and quality systems" — crawlability, indexability and page quality still matter as a floor, at least for Google's own features. Second, a page still has to be found and understood before it can be cited by anyone — a page a crawler can't reach doesn't get into either pipeline. Third, measurement still has to account for how people actually ask — Pew Research found that Google users who saw an AI summary clicked a traditional result link in just 8% of visits, versus 15% without one (900 US adults, March 2025 data), a reminder that fewer clicks doesn't mean fewer questions being asked; it means more of the answering now happens inside the engine itself.
FAQ
Is an AI answer just a reordered version of Google's top 10? No. Google's own features draw on the same index, but generation adds a selection and writing step on top of ranking. Across other engines, the overlap with Google's top 10 is much lower — Ahrefs measured around 8% for ChatGPT, Gemini and Copilot, and about 28.6% for Perplexity.
Does ranking first on Google guarantee a citation in an AI answer? No. Google states there are "no additional requirements" to appear in AI Overviews or AI Mode beyond normal indexing, but nothing in its documentation promises inclusion, and it says nothing about how other engines, built on different indexes, choose sources.
What is query fan-out, briefly? A model splitting one question into several related searches before writing its answer, so the result reflects more than the literal words typed. See what is query fan-out for the full mechanics.
Can I tell which stage of the pipeline caused a brand to be missing from an answer? Not precisely, from the outside. You can tell whether a page was crawlable (robots.txt, server logs) and whether it's indexed, but the retrieval, rerank and generation steps aren't observable or documented in enough detail to diagnose exactly where an absence happened.
What to do next
- Check whether your pages are reachable by the crawlers that actually power citations — not just Googlebot — using the AI Citation Snapshot to see one live answer and its sources today.
- Stop tracking keyword rank as a stand-in for AI visibility; log named/cited/recommended across a small set of real buyer questions instead.
- Read how AI knows about my brand next — it separates what a model learned in training from what it retrieves live, which matters for deciding what you can actually influence this month.
ContextOwl sells one-time AI visibility reports. The AI Citation Snapshot is a free, single-question version of the same check.
Sources
- Google Search Central, "Optimizing your website for generative AI features on Google Search" (last updated 10 July 2026): https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
- Google Search Central, "AI features and your website" (last updated 10 December 2025): https://developers.google.com/search/docs/appearance/ai-features
- OpenAI, "Overview of OpenAI Crawlers": https://developers.openai.com/api/docs/bots
- Microsoft, "Introducing AI Performance in Bing Webmaster Tools Public Preview" (10 February 2026): https://blogs.bing.com/webmaster/February-2026/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview
- Ahrefs, Louise Linehan, "AI Search Overlap" study (11 August 2025; 15,000 long-tail queries): https://ahrefs.com/blog/ai-search-overlap/
- Pew Research Center, "Google users are less likely to click on links when an AI summary appears in the results" (22 July 2025; 900 US adults, March 2025 browsing data): https://www.pewresearch.org/short-reads/2025/07/22/google-users-are-less-likely-to-click-on-links-when-an-ai-summary-appears-in-the-results/
More in AI Search Basics
There's no single citation algorithm. Retrieval, relevance, freshness and source type each play a part — and some of them are yours to influence.
AI knows a brand from memory built during training, or from pages fetched live. You can influence the second one quickly and the first one only slowly.
Each engine documents a little about how it finds sources and leaves most of the rest unpublished. Here's exactly what's confirmed, by whom, and what still isn't.