Urgent.News

What's breaking now, across thousands of outlets.

AI

Query fan-out: why AI search never answers the question you typed

When you ask an AI assistant with web search something like "best CRM for a 5-person agency", it usually doesn't run that exact search. It quietly splits the question into several smaller ones, searches for each, reads the results, and writes one answer from all of them. This is called query fan-out , and if you care about showing up in AI answers, it changes how you should think about a page.…

When you pose a query to an AI assistant that incorporates web search, it typically does not conduct that specific search. Instead, it breaks down the question into several smaller inquiries, conducts searches for each one, peruses the outcomes, and then generates an answer from the amalgamation of results. This process is known as query fan-out, and it influences how one should approach content creation for AI visibility. Here's how it works:

The AI model rewrites your prompt into a series of search queries. It then retrieves each query from a search index, fetching the top results for every query. The model extracts relevant passages from those pages and synthesizes them into a single response, potentially citing the pages it utilized. For a query like 'best CRM for a 5-person agency', the fan-out could encompass queries such as 'best CRM for small agencies 2026', 'CRM pricing per user small team', 'CRM with client portal for agencies', 'CRM project management integration', and 'simple CRM setup time'.

The exact queries may vary between different AI products and can change with each query execution, although the general pattern remains consistent. This mechanism is publicly described by Google's AI Mode and other sources.

This concept of query fan-out challenges traditional SEO practices, which emphasize optimizing individual pages for specific keywords. Fan-out complicates this approach in two significant ways: you can achieve visibility without ranking for the primary keyword, and the unit of content that gets cited is a passage, not a full page.

To optimize for AI search, one should focus on creating concise, easily digestible sections that directly answer specific sub-questions related to the main query. For instance, if the main query is 'best CRM for a 5-person agency', identifying sub-questions like 'what is a CRM', 'CRM pricing per user', 'CRM with client portal', and 'how long does CRM setup take' can help structure the content more effectively.

A practical strategy involves drafting a list of main questions the page should answer, generating likely sub-questions, and mapping each sub-question to a corresponding section on the page or another page on the site. This ensures that the content is structured in a way that is easily accessible and usable by AI models, thus improving the likelihood of being cited in AI-generated responses.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

Is that really GPTBot? How to verify AI crawlers in your logs

Open any access log today and you'll see GPTBot, ClaudeBot, PerplexityBot and friends. The problem: a user agent is just a string.

  • Compare bot's IP address against OpenAI's published CIDR ranges
  • Use DNS reverse and forward lookups for Googlebot and Bingbot
  • Consult official bot documentation for accurate verification methods

Google Tabletop AI: Build Custom Collaboration Apps by Describing Them

Google Tabletop AI: Describe the App, Skip the Spreadsheet Google just admitted something the productivity industry has been dancing around for years: nobody actually wants to configure a…

  • Tabletop AI tool creates custom collaboration apps based on user descriptions.
  • Users can generate interactive tools like trip itineraries or expense splitters.
  • Currently an experimental service for adults in one country with age limit 18+.

How to review an AI-written pull request: a 10-point checklist

AI-written pull requests have a particular look. The code is tidy, the names are sensible, the description is confident, and the tests are green.

  • Read the task description to understand original intent
  • Compare diff against task to avoid extra changes
  • Examine tests to validate new functionality

More from Friday 13 November →