Skip to content

Playbooks

What query fan-out means for your pricing and comparison pages

Godfrey, lessClick

Query fan-out is when an AI assistant turns one buyer question into several smaller searches, reads the results of each, and writes one answer. For a software company, it means the answer to “which tool should I buy” is built from pages about pricing, features, fit and comparisons, so each of those needs its own clear page.

What is query fan-out?

Query fan-out is the step between the buyer’s question and the assistant’s answer. A buyer asks one broad question. The assistant breaks it into the narrower questions behind it, searches for each, and combines what it finds.

Google has described this technique for its AI Mode in search. Other assistants that search the web behave in a similar way, though they publish less about it.

In Google’s words, AI Mode “uses our query fan-out technique, breaking down your question into subtopics” (Google, May 2025). Google’s guidance for site owners says AI Overviews may use the same technique.

What does one buyer question turn into?

A single buyer question hides several smaller ones. Here is how a typical question might fan out, and which page would answer each part:

Part of the question Sub-question the assistant may search Page that answers it
“best contract software” What are the main contract software products? Category page, comparison articles
“for a 40-person company” Which ones suit small and mid-sized companies? A page on who the product is for
(implied) price How much does each one cost? Pricing page with prices in text
(implied) features Does it handle e-signature and renewals? Feature pages
(implied) risk What do customers say about it? Review sites, case studies
(implied) alternatives How does it compare with the leader? An honest comparison page

This table is illustrative. The exact sub-questions vary by assistant and by day.

Why does this matter for pricing pages?

Pricing pages matter because price is one of the sub-questions behind almost every buying question, even when the buyer never types the word. If an assistant cannot find your price, it has to describe you without it, or leave you out in favour of a product whose price it can state.

Three things help a pricing page answer that sub-question:

  1. Prices in text, not only in an image, a calculator or a “contact sales” form.
  2. Plain plan names with one line on who each plan is for.
  3. What is included, listed rather than hidden in a tooltip.

A company that does not publish prices can still say how pricing works: per seat, per month, a starting price, or the factors that set the quote.

Why does this matter for comparison pages?

Comparison pages matter because “alternatives to” and “X vs Y” are among the most common sub-questions. When an assistant searches for them, it finds whoever wrote the comparison. If you have not written one, a competitor or an affiliate site has, and they decide how you are described.

An honest comparison page says where your product is the better fit and where it is not. That honesty is what makes it quotable. A page that claims to win on every row reads as marketing and gives an assistant little it can repeat.

Which pages should you check first?

Start from your buyers’ questions, not from your sitemap. For each question, write down the sub-questions it hides, then check whether a page on your site answers each one in its first few lines.

lessClick’s own site follows the same rule: separate sections or pages for pricing, what is included, how long it takes, who it is for and how results are measured. The gaps are usually obvious once the sub-questions are written down.