Query fan-out
Also known as: query rewriting, multi-query retrieval
One question typed by a person becomes several different searches run by the machine — so you compete for questions nobody ever typed.
Last revised 2026-09-07. Also available as markdown — request this URL with Accept: text/markdown.
In plain English
Ask an assistant "which accounting software should a UK sole trader use?" and it will not run that as one search. It breaks the question into pieces: making tax digital requirements, software comparisons, pricing, reviews from sole traders. Each piece is its own retrieval, and each pulls different pages.
The practical consequence is that optimising for the exact phrase a customer would type is no longer enough. Your page has to be findable for the sub-questions the machine invents on the way to answering it.
How to fix / set it up
- List the sub-questions inside each buying question, and check something on your site answers each one.
- Give each sub-answer its own heading, or its own page when the answer is substantial.
- Link the cluster together so the pieces are reachable from each other.
The technical detail
Fan-out is why coverage beats keyword density. A cluster of pages that each answer one sub-question thoroughly tends to be retrieved more often than one long page that mentions everything shallowly.
It also explains a common surprise in tracking: your brand appears in answers to questions that never mention your category, because a sub-query about a narrow requirement matched your page.
Internal linking matters more than under classical SEO, because it is how a retriever moves from the sub-question page it found to the page that names you.
FAQ
Should I make one big page or several small ones?
Several, when each genuinely answers a distinct question. One page per keyword variation is the old mistake; one page per real question is the new discipline.