Query Fan-Out

How query fan-out works — the technique behind Google AI Overviews and AI Mode that decomposes one question into multiple concurrent sub-queries, retrieves across them, and synthesizes a single answer — and what it means for getting cited.

First published: Jul 3, 2026 · Last updated: Jul 22, 2026 · Advanced

Query fan-out is the retrieval technique behind Google AI Overviews and AI Mode: instead of running one search, the model decomposes a single question into multiple related sub-queries, runs them concurrently across the core Search index, and synthesizes the retrieved passages into one answer. Google confirms both AI Overviews and AI Mode 'may use a query fan-out technique — issuing multiple related searches across subtopics and data sources.' It's the retrieval step inside RAG/grounding — there's no separate AI index and no separate AI ranking system. The SEO consequence is concrete: your content has to be retrievable for the implied sub-questions a query spawns, not just the head query someone typed. Google's own explanation for why direct top-10 sourcing has fallen (roughly 76% of AI Overview citations in mid-2025 to about 38% in early 2026) is that fan-out matured. The popular '8–12 sub-queries' figure is industry estimation, not an official Google number.

TL;DR — Query fan-outQuery fan-out is the technique where an AI search system breaks a single user question into multiple related sub-queries, runs those searches concurrently, and synthesizes the retrieved results into one answer. Google confirms AI Overviews and AI Mode 'may use a query fan-out technique' issuing multiple related searches across subtopics. is the retrieval step inside RAGRAG is the retrieve-then-generate pattern behind AI search: the system retrieves relevant passages from an external index at query time, injects them into the model's context, and generates an answer grounded in those sources — without changing the model's weights./groundingGrounding is anchoring an AI model's answer to source documents it retrieves at the moment you ask — not to the patterns frozen into its weights during training. Retrieval-Augmented Generation (RAG) is the most common way to do it.: the model decomposes a single query into multiple related sub-queries, runs them concurrently across the core Search indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., and synthesizes the retrieved passages into one answer. Google confirms both AI OverviewsAI Overviews are the AI-generated summary box Google shows above or within its regular search results, written by Gemini models from pages retrieved out of Google's normal Search index. It's a Search feature, not a separate platform or index. and AI Mode “may use a ‘query fan-out’ technique — issuing multiple related searches across subtopics and data sources.” There’s no separate AI index and no separate AI ranking system — the same crawl → index → snippet-eligible gates apply. The SEO consequence is that content has to be retrievable for the implied sub-questions, not just the head query. Google’s own account is that fan-out maturing is why direct top-10 sourcing fell from roughly 76% (mid-2025) to about 38% (early 2026). The “8–12 sub-queries” figure is industry estimation, not an official Google number.

Where fan-out sits in the pipeline

Fan-out is a retrieval strategy within documented products, not a publisher-controlled ranking factor. Evidence for this claim Google describes AI Mode as using a query fan-out technique that issues multiple related searches across subtopics and data sources. Scope: Google AI Mode's documented behavior; exact orchestration, ranking, and generated queries are product-specific and can change. Confidence: high · Verified: Google: AI Mode in Search Exact generated queries, weights, and orchestration remain system-specific. Evidence for this claim Query fan-out is a retrieval-orchestration pattern that expands one request into multiple related searches before synthesis. Scope: Editorial abstraction from Google's product description, not a claim that every AI answer uses this pipeline. Confidence: medium · Verified: Google: AI Mode in Search

Query fan-out isn’t the whole system — it’s one step inside it. AI OverviewsAI Overviews are the AI-generated summary box Google shows above or within its regular search results, written by Gemini models from pages retrieved out of Google's normal Search index. It's a Search feature, not a separate platform or index. and AI Mode are powered by retrieval-augmented generation (RAG), which Google calls groundingGrounding is anchoring an AI model's answer to source documents it retrieves at the moment you ask — not to the patterns frozen into its weights during training. Retrieval-Augmented Generation (RAG) is the most common way to do it.: retrieve relevant passages from an index, inject them into the model’s context, and generate an answer grounded in them. Fan-out is what happens at the start of the retrieval phase — the decomposition of one user query into many.

The full loop, roughly: user query → fan-out into sub-queries → retrieve across the index → assemble the best passages → generate a synthesized, cited answer. If you want the retrieval mechanics in depth — chunkingChunking is splitting a document into smaller passages so AI systems can embed, index, and retrieve the single most relevant piece — not the whole page — in response to a query. It's a foundational step in RAG pipelines and the conceptual cousin of Google's passage ranking., embeddingsEmbeddings are dense numerical vectors — lists of floating-point numbers — that represent the meaning of text in a high-dimensional space. Semantically similar content lands close together, so search and AI systems can match by meaning, not just keywords., vector searchVector search finds content by comparing the meaning of a query against stored content as numerical vectors, retrieving the closest ones in a high-dimensional embedding space. At scale it uses approximate nearest neighbor (ANN) algorithms — not exact comparison — to search billions of vectors in milliseconds., re-rankingReranking is the second stage of a retrieval pipeline: after a cheap, broad first pass pulls a candidate set of documents or passages, a slower, more precise model re-scores and reorders that shortlist by true relevance before the results are served or handed to an LLM. — that’s the province of the retrieval and grounding topics in this cluster. This page is specifically about the fan-out step.

Fan-out widens one question into concurrent retrieval paths, then assembles the strongest evidence into one cited answer. Source: /ai-search/how-search-works/query-fan-out/

One user query branches into three illustrative related sub-queries labeled A, B, and C. Each branch retrieves and ranks passages from the core index, and the selected evidence is synthesized into one cited answer. The three branches illustrate the mechanism; Google does not publish a fixed number of generated queries.

© Patrick Stox LLC · CC BY 4.0 ·

What Google has actually confirmed (and what it hasn’t)

Be careful to separate the confirmed mechanism from the industry theory built on top of it. What Google states plainly:

  • Both AI Overviews and AI Mode “may use a ‘query fan-out’ technique — issuing multiple related searches across subtopics and data sources — to develop a response.”
  • The model issues “concurrent, related queries… to request more information and fetch additional relevant search results,” which Gemini then “analyzes… extracts the most relevant facts, and stitches them together into a single, comprehensive answer.”
  • It all runs over the core index: “our generative AI features on Google Search are rooted in our core Search ranking and quality systems.” There is no separate AI index or AI ranking algorithm.

What Google has not confirmed: any specific count of sub-queries. The widely repeated “8–12 sub-queries per prompt” figure is SEO-industry estimation, not an official Google number — I’d treat it as illustrative of “several, not one,” not as a hard fact. Google says multiple related searches; it doesn’t publish how many.

Grounding queries — the closest thing to seeing fan-out

You don’t get to see Google’s fan-out sub-queries. Google exposes nothing about them — its June 2026 Generative AI performance reportThe Google Search Console report that shows how your site actually performed in Google Search, built from real impressions and clicks. It reports four metrics — clicks, impressions, average CTR, and average position — and keeps the most recent 16 months of data. in Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. shows impressions only, broken out by Pages, Countries, Dates, and Devices, with no query dimension.

The one place the industry gets a peek at fan-out-style behavior is Bing/Microsoft. Bing’s AI Performance report in Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility. (public preview, February 2026) surfaces grounding queries — the actual retrieval-optimized query phrases that pulled your content into a Copilot or Bing AI answer. These are distinct from what a user typed: they’re simplified, machine-generated search terms. Microsoft Clarity added the same visibility. It’s the nearest thing anyone has to watching the fan-out fire — and notably, Google exposes no equivalent.

Why this is reshaping citations

Here’s the most concrete, measurable consequence of fan-out — and it’s from my own data at Ahrefs.

When we first studied how AI Overview citations line up with organic rankings, about 76% of cited pages also ranked in the traditional top 10 (mid-2025). By the March 2026 update — 863K keyword SERPs and 4M AI Overview URLs, twice the original sample — that number had fallen to about 38%. The rest split almost evenly between positions 11–100 and pages that didn’t rank in the top 100 at all.

The explanation, in our own words: “Google is selecting far fewer pages straight from the original SERP… AI Overviews are relying less on the direct search results and more on the sources showing up in fan out query SERPs.” As fan-out matured, sourcing moved off the head query’s top 10 and onto the SERPs of the sub-queries. Ranking #1 for the exact phrase someone typed is no longer the gate it used to be.

A related pattern from the same work: pages that rank across multiple fan-out queries are meaningfully more likely to be cited — a direct signal that breadth across the sub-topic space beats a single narrowly-optimized page. And YouTube is a disproportionate, ranking-independent citation source: 18.2% of AI Overview citations that don’t rank in Google’s top 100 for the query are YouTube URLs.

What fan-out means for your content

Strip away the mechanism and the playbook is straightforward:

  • Cover the sub-topics, not just the keyword. Fan-out retrieves for the questions around the question. Genuine topical depth — the kind that answers the obvious follow-ups on the same page or across a well-linked cluster — is what makes you retrievable across more of those sub-queries. Depth beats a page stuffed around one head term. Retrieval is a prerequisite, not a promise: being pulled into a sub-query’s candidate set doesn’t guarantee the model selects, cites, or accurately attributes your page in the final synthesized answer — treat broader coverage as improving your odds, not as a disclosed citation guarantee.
  • Being indexed is still the prerequisite. No separate AI index means the crawl → index → snippet-eligible chain has to be intact. A page that can’t be crawled and indexed can’t be retrieved for any sub-query. Google is explicit: to be shown as a supporting link “a page must be indexed and eligible to be shown in Google Search with a snippet… There are no additional technical requirements.”
  • Don’t over-optimize for the mechanism. Google directly rebuts the tactics the fan-out era has spawned: you don’t need llms.txtllms.txt is a proposed (not adopted) Markdown file at /llms.txt that gives AI systems a curated map of a site's most important pages. Proposed by Jeremy Howard in 2024, it's read mostly by coding agents like Claude Code — not search crawlers — and Google ignores it. or special AI markup (“Google Search itself doesn’t use them”), and “there’s no requirement to break your content into tiny pieces for AI to better understand it.” ChunkingChunking is splitting a document into smaller passages so AI systems can embed, index, and retrieve the single most relevant piece — not the whole page — in response to a query. It's a foundational step in RAG pipelines and the conceptual cousin of Google's passage ranking. your content into fragments to “match sub-queries” is exactly what Google says not to do — its systems already understand multiple topics on a page.
  • Structure for humans. Google’s actual guidance is deliberately minimal: organize content “by paragraphs and sections, along with headings that provide a clear structure.” Clear headings and self-contained sections happen to make individual passages easier to retrieve for a sub-query — but you write them for readers, not for a fan-out.
  • Off-site signals still dominate. In the broader research, branded web mentions correlate with AI Overview visibility more strongly than Domain Rating (0.664 vs. 0.326). Fan-out changes which SERP you need to show up on; it doesn’t change that authority and mentions drive citation.

The one-sentence version: fan-out didn’t invent a new optimization — it widened the target. You’re no longer optimizing one page for one query; you’re trying to be a credible answer across the whole neighborhood of sub-queries a topic generates.

TIP

Turn a research hypothesis into a reviewable coverage map with my free Query Fan-Out Simulator Free

  1. Start with one seed question and inspect the generated related branches.
  2. Compare a page or supplied copy against each branch; treat lexical and cosine coverage as directional, not as Google’s hidden queries.
  3. Strengthen genuinely missing answers or evidence, merge overlapping branches, and rerun the check.
A branch can be partially covered even when the head topic looks complete. This run is a planning aid, not a view of Google's hidden fan-out.

The result lists five modeled subqueries: technical SEO audit at 100 percent coverage; What is technical SEO audit at 100 percent; technical SEO audit benefits and limitations at 60 percent; technical SEO audit vs alternatives at 60 percent; and How to choose technical SEO audit at 75 percent. A note says the run used lexical BM25 and cosine coverage only and did not evaluate embeddings.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.