> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryprofound.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Query Fanout Estimator

> Predict how answer engines expand a single prompt into multiple web search queries

The **Query Fanout Estimator** node predicts how answer engines (like ChatGPT, Claude, Gemini, or Perplexity) are likely to expand a single user prompt into multiple **web search queries**. These expanded searches—called [**query fanouts**](https://www.tryprofound.com/blog/introducing-query-fanouts)—are what actually drive retrieval and citations in AI-generated answers.

This node helps you understand the search layer behind the answer: which queries an answer engine might run, what facets of intent it will explore, and where your content needs coverage to be cited more often.

<Tip>Check out [Getting started with Agents](/agents/getting-started) to learn how to add this node to an Agent.</Tip>

## When to use this node

Use the Query Fanout Estimator when you want to:

* See how a specific **user prompt** is likely to be decomposed into multiple web searches
* Identify the **high-intent queries** that matter most for a given prompt
* Plan content that covers the full **fanout space** behind important prompts
* Feed likely fanout queries into AEO data nodes, content briefs, or keyword clustering workflows
* Model how answer engines translate prompts into retrieval behavior for AEO strategy

## Node configuration

Selecting the Query Fanout Estimator node opens its configuration panel on the right side of the Agent builder.

### Target Prompt (required)

The user prompt that your content should optimize for, such as:

* “How do keyword hierarchies work in AI search?”
* “Best tools for monitoring AI citations for my brand”
* “How does query fan-out impact SEO strategy?”

The node will estimate which web search queries an answer engine is likely to run when answering this prompt.

### Output Label (required)

A descriptive name for the node’s output, for example:

* `query_fanout_estimate`
* `predicted_fanout_queries`

You will use this label to reference the fanout data in downstream steps (e.g., content briefs, research steps, reports).

## How the node works behind the scenes

This node runs a two-step pipeline:

### 1. Retrieve real query fanout examples

Profound maintains a knowledge base of **historical query fanouts**: real pairs of user prompts and web search queries that answer engines actually ran behind the scenes (the “fanout” set).

Given your **Target Prompt**, the node:

1. Performs a semantic search over this fanout dataset
2. Retrieves the most similar prompt–fanout examples
3. Passes those examples forward as in-context demonstrations

These examples are not restricted to the same topic; they illustrate how Answer Engines in general expand prompts into multiple searches.

### 2. Estimate fanout for your prompt using an LLM

Next, the node uses a model configured specifically to “think like” an Answer Engine’s retrieval layer:

* It receives:
  * Your **Target Prompt**
  * A set of historical prompt + fanout examples from Profound’s knowledge base
* It is instructed to:
  * Infer how an answer engine would break your prompt into multiple web search queries
  * Generate **realistic, high-intent, semantically diverse** search queries
  * Focus on **sub-queries** that would retrieve relevant sources (not just phrasing variants)
  * Capture different facets of the original intent (definitions, comparisons, how-to steps, evaluation, etc.) ([<u>Profound</u>](https://www.tryprofound.com/blog/expanding-analysis-for-query-fanouts-in-profound?utm_source=chatgpt.com))

The model returns a list of predicted web search queries—your **estimated query fanout**.

## Output

The node returns a structured text output containing likely search queries that answer engines would fan out from your prompt. For example:

```text wrap theme={null}
what is query fan-out in ai search, how do llms expand user prompts into multiple web searches, impact of query fan-out on brand visibility, examples of query fan-out in google ai overviews,how to optimize content for query fan-out
```

You can parse this text into a list in downstream steps or feed it directly to other nodes.

## Example workflow: Fanout-informed content planning

**Goal:** Build a content plan that covers the full set of queries an answer engine might run for a critical prompt.

**Steps:**

1. **Query Fanout Estimator**
   * Input: Target Prompt (e.g., “How do AI-generated answers choose citations?”)
   * Output: Predicted fanout queries
2. **Research and insights**
   * For each fanout query:
     * Use [Perplexity Search](/agents/nodes/perplexity-search) or [Web Page Scrape](/agents/nodes/web-page-scrape) to gather citations
     * Use [Research Snippets Generator](/agents/nodes/research/research-snippets-generator) to extract facts and quotes
3. **Create content brief**
   * Feed the fanout queries + research into the [Create Content Brief](/agents/nodes/content-creation/create-content-brief) node
   * Ensure the brief mandates coverage for each high-intent sub-query
4. **Generate article**
   * Use the brief to [Generate Article](/agents/nodes/content-creation/generate-article) that explicitly addresses the main prompt *and* its fanouts
5. Score the final article
   * Use [AEO Content Scorecard](/agents/nodes/content-optimization/aeo-content-scorecard) to checking whether the article covers enough of the fanout space implied by the prompt

This workflow ensures your content isn’t just optimized for a single phrasing—but for the **full set of searches** answer engines are likely to run behind that prompt.

## Best practices

* Use natural language prompts that mirror real user questions; the fanout will be more realistic.
* Store the fanout output in a reusable label (e.g., query\_fanout\_estimate) so it can power multiple downstream steps.
* Combine this node with Profound AEO data nodes to see how often your site appears across the predicted fanout queries.
* Use fanout results to design FAQs, headings, and section structure that map directly to the likely sub-queries answer engines care about.