# Query fan-out Query fan-out is how AI Mode expands one question into several sub-queries, reads them in parallel, then composes one answer with citations. It rewards pages that nail a narrow sub-question. If you run a small site, this explains why citations can come from pages that never ranked for the original query. Updated 2026-09-14 · Source: https://porteur.ai/glossary/query-fan-out ## What query fan-out is and why it matters Query fan-out is the method Google described for AI Mode, and used in AI Overviews: one question is expanded into several sub-queries, the results are read, then one answer is written with citations from across them. You do not need to win the head term to be cited. You need to answer a specific sub-question well, and be findable for that phrasing. A page on "/pricing" might earn a cite for "how long is the free trial" even if it never ranked for "yourproduct pricing". Fan-out explains odd citations. AI Mode may fan out "email warmup alternatives" into "does warming hurt deliverability", "how to ramp volume", "DKIM for new domains", and a comparison query. It cites the best source for each bit. Your "/guides/dkim-setup" can be cited even if it never ranked for the head term. A "query fan-out tool" is a third-party guess at likely sub-queries, useful for ideas, not as ground truth. ## How to spot fan-out in your data - Search Console, Performance: scan Queries for long-tail questions, modifiers and facets that match sections on your pages. - Open a page in the Performance report. Switch to Queries. Watch for new question-like queries after AI Overviews launched on your topic, as of 2026. - Compare queries to your headings. If "how to export to csv" starts showing for "/guides/getting-started", your page is findable for that sub-question. - Check People Also Ask and related searches on your head term. These often mirror the sub-queries assistants explore. - Watch for impressions without clicks on odd queries. That can be a cite inside an AI answer without a standard blue link click. A fixed page looks like clear sections that map to discoverable questions, with headings that match how users ask them, and internal links that name the facet in anchor text. ## What to do: write for sub-questions and make them findable 1. **List the likely sub-queries** Start from your head terms. Pull People Also Ask, support tickets and on-site search. Draft 10 to 20 precise questions users ask. 2. **Map each to a home** Decide which page should answer each one. Use existing pages where possible. Add a section or an FAQ block rather than a new thin page. 3. **Write the answer plainly** One question per section. Use the exact phrasing in the H2 or H3. Give the steps or facts first. Add a short example from your product. 4. **Name it in title and anchors** If a section earns traffic, consider a dedicated page. Use a title like "Export invoices to CSV". Link to it with the same words from relevant pages. 5. **Cover comparisons and qualifiers** Add "for X" and vs pages when users compare or filter, for example "/alternatives-pages/tool-a-vs-tool-b" or "pricing for nonprofits". Schema can help assistants understand scope. Mark up FAQs when you have real Q and A. Keep it accurate and on-page, not autogenerated filler. ## Traps to avoid - Chasing every variant as a new page. You create index bloat and dilute signals. Consolidate close variants into one strong page. - Writing vague catch-all posts. Fan-out rewards specificity. If a user asks "how to set DKIM in Postmark", answer that exact thing. - Overstuffing FAQs with fluff. Assistants can tell when you dodge the question. Keep each answer tight and useful. - Ignoring URL parameters. Multiple query parameters in URLs can spawn near-duplicates. Use consistent paths and document necessary parameters. - Treating tool output as certain. Sub-queries are guesses outside Google. Validate by user demand and your data before you commit. > If you want to be cited by assistants, do not block reputable AI crawlers in robots.txt. ## Questions ### What does query fan-out mean? It is how AI Mode expands one question into several related sub-queries, reads results for all of them, then writes one answer with citations. You can win a cite by answering a sub-question well, even if you never rank on the head term. ### How do I make my pages show up in AI Overviews? Target the precise sub-questions the overview must cover. Put clear, direct answers in scannable sections, and make those sections discoverable with matching headings and links. You cannot control when overviews appear, but you can be the best source for parts of the answer. ### What is a query fan-out tool? It is a third-party tool that guesses which sub-queries assistants might issue for a topic. Use it to brainstorm coverage and phrasing, then check the ideas against your users and Search Console. ### Why am I getting impressions for odd long questions with few clicks? That can be fan-out. Your page may be shown or cited for a sub-question inside an AI answer, which registers impressions without many traditional clicks. Check which page is matched and tighten that section. ### Is SEO for head terms dead now that AI writes answers? No. Head terms still matter for discovery and brand. Fan-out widens the surface area, so also focus on the specific questions people ask within that topic. ### How is this different from People Also Ask? People Also Ask shows follow-up questions on the results page. Fan-out is the assistant asking those and related questions behind the scenes to assemble an answer. Optimising for both often overlaps. ## Read next - [AI Overview](https://porteur.ai/glossary/ai-overview): AI Overviews are Google’s generated answers above results. See when they appear, what they cite, how to measure impact, and how to get cited. - [Google AI Mode: what it is and how a small site gets cited](https://porteur.ai/guides/google-ai-mode): What AI Mode is, how it picks citations, how clicks appear in Search Console, and the page changes that make a small site quotable. - [How to appear in Google’s AI Overviews](https://porteur.ai/guides/how-to-rank-in-ai-overviews): What overviews cite, which queries trigger them, and how to structure pages that get linked. Steps to find your openings and measure them. - [Generative engine optimization (GEO): how to be named by AI answers](https://porteur.ai/guides/generative-engine-optimization): How to get your site named in AI answers: sources, crawlers, lists, structure, llms.txt, comparisons, and how to measure by asking assistants. - [People also ask: turning Google’s questions into sections](https://porteur.ai/guides/people-also-ask): See what People also ask is, where questions come from, how to collect them, write two-sentence answers, add FAQ markup, and track results. - [Search intent: what the results page tells you to build](https://porteur.ai/guides/search-intent): Learn the four intents, read intent from the results page, and fix pages that will never rank by changing their kind, not just the words. Paste your URL to get, in about thirty seconds, three sub-question opportunities your site can win and the rival pages already cited on them. Free check: https://porteur.ai/