---
title: "Your AI Visibility Tracker Sees the Prompt, Not the Searches Behind It"
description: "A buyer prompt can fan out into narrower searches before an AI assistant answers. Here’s why brand mentions fluctuate, what a useful tracker should show, and where to work instead."
url: "https://groas.com/post/the-prompt-you-track-isn-t-the-search-th"
image: "https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/7d88a9c7-4388-4964-b712-7e963ba48602.png"
published: "2026-10-26T05:42:32.206Z"
modified: "2026-10-26T05:42:32.262Z"
---

October 26, 2026 · 10 min read

# Your AI Visibility Tracker Sees the Prompt, Not the Searches Behind It

[Alexander PerelmanHead Of Product @ groas](https://groas.com/author/alexander-perelman)[LinkedIn](https://www.linkedin.com/in/alexander-433793253/)

![A tiny inspector tallies one parcel entering a model depot while, hidden behind its wall, three courier vans leave on different roads he never sees.](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/7d88a9c7-4388-4964-b712-7e963ba48602.png)

In this article

1. [The prompt is the keyword. The hidden searches are the search terms.](#the-prompt-is-the-keyword-the-hidden-searches-are-the-search-terms)
2. [Step 1: one buyer question becomes several narrower jobs](#step-1-one-buyer-question-becomes-several-narrower-jobs)
3. [Step 2: each sub-query creates a separate retrieval opportunity](#step-2-each-sub-query-creates-a-separate-retrieval-opportunity)
4. [Step 3: retrieval, citation, and recommendation split apart](#step-3-retrieval-citation-and-recommendation-split-apart)
5. [What your prompt list can—and cannot—tell you](#what-your-prompt-list-canand-cannottell-you)
6. [Demand a diagnosis, not another visibility percentage](#demand-a-diagnosis-not-another-visibility-percentage)
7. [Try the model on a prompt you have never tracked](#try-the-model-on-a-prompt-you-have-never-tracked)

## The prompt is the keyword. The hidden searches are the search terms.

Your AI visibility dashboard says your brand went from 80% visibility to zero on _“best fleet dispatch software for mid-sized couriers”_ between Tuesday and Thursday. Before you blame a competitor, look at what the dashboard measured: **the buyer prompt was not necessarily the search the assistant ran**.

If you have managed broad-match Google Ads, the distinction is familiar. You target `fleet dispatch software`, then open the search terms report and find `free dispatch app for single truck driver` or `how to start a courier service in Ohio`. The keyword triggered the opportunity. The search term tells you what actually happened. A buyer prompt can play the same triggering role in AI search, while the assistant’s narrower retrieval queries remain out of sight.

That process is called _query fan-out_. An assistant can rewrite one question into several synthetic sub-searches, retrieve material for each, and assemble an answer from what it finds. [Reverse-engineering ChatGPT search payloads](https://trevorfox.com/2025/11/chatgpts-shopping-feature-part-1-simple-search/) shows identical user prompts producing different internal searches across sessions. Your brand may get mentioned because it appeared in a useful result for one of those searches, not because your page matched the buyer’s original wording.

A tracker that replays the prompt and counts brand mentions can show you the outcome. It cannot, on that evidence alone, tell you which search produced it. That is reporting on the keyword while ignoring the search terms report.

## Step 1: one buyer question becomes several narrower jobs

An assistant answering a recommendation question needs more than pages that repeat the question’s words. A buyer asking for dispatch software may also need compliance information, a fleet-size fit, and pricing. A single lookup for the exact prompt could miss those distinctions. [Google patent US20240289407A1](https://querymint.com/blog/query-fan-out/) describes generating synthetic queries across intent dimensions such as comparisons, technical constraints, and pricing boundaries.

The number and wording of those queries can vary. An analysis examining [over 20 million fan-outs in ChatGPT](https://geosnap.ai/en/blog/quali-prompt-monitorare-risposte-ai-come-scegliere) reported an average of 2.3 to 2.8 internal web searches per prompt and found that average sub-query length grew from 6 to 12 words as rewrites became more specific. The important point is not that every prompt produces the same count. It is that **one prompt can open several different routes to an answer**.

![One buyer prompt splitting into several narrower search queries.](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/97afdff0-d282-4664-b8cf-31cda1569c26.png)

Consider the question I’ll use throughout: _“What is the best dispatch software for a 15-van medical courier business?”_ A prompt tracker records that one sentence. An assistant looking for an answer could instead pursue retrieval jobs like these:

1. `HIPAA compliant courier dispatch software requirements` — a compliance requirement.
2. `best dispatch routing platforms for fleets under 20 vehicles` — a fleet-size constraint.
3. `medical courier dispatch software reviews and pricing` — a buying comparison.

Those are **illustrative rewrites, not a transcript of an assistant’s hidden searches**. They show why a page targeting only `dispatch software` may miss the material the assistant needs to answer the narrower questions.

The rewrites are not just keyword variations. [Patent documentation on query fan-out](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQEL-Lmsy16TF8eG3jmoDlIG5N-vgP_q5bLH2bHBnnFinc3jO1KkruTF7axgmq3SOEubKWJJHCT4ZVdI4vtoEMH5XSLiHZkLEb89d1526oNMNojRncWGLxUV530wbe4yQzAyJwjC1pA==) describes operations including adding specifications, replacing buyer language with industry terms, checking dependencies, and clarifying intent. Engines do not use those operations with equal intensity. In a [Surfer benchmark of 10,000 queries](https://surfer.ai/blog/query-fan-out/), Gemini averaged 10.7 fan-out queries per prompt, ChatGPT roughly 2, and Perplexity 1.4.

For our courier buyer, location, recency, and the ambiguity of “best” may all affect the route. I would not try to write one page for every possible rewrite. I would first identify the distinct jobs the answer has to perform.

## Step 2: each sub-query creates a separate retrieval opportunity

Now the assistant has candidate searches. It needs material that answers them. A strong ranking for `courier dispatch software` does not guarantee that your page will serve a search about compliance or fleets under 20 vehicles. **Broad visibility does not automatically transfer to a narrow retrieval job.**

This is the part a familiar search ranking can obscure. You see your home page near the top for the broad phrase and assume the AI answer has to consider you. But the assistant can draw on passages returned for several narrower queries and combine their results. For a closer look at [how query fan-out, indexing, and passage selection gate AI citations](https://groas.com/post/how-chatgpt-and-perplexity-actually-choo), the useful unit to inspect is the passage that answers a particular need, not just the domain that owns it.

![Sub-queries feeding separate retrieval results into one answer.](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/1b7d6c75-4e1c-4913-aa2f-f172d6b641a1.png)

Back to the medical courier. A healthcare compliance guide might answer the HIPAA-related search. A software directory might answer the fleet-size search. A reviews page might supply pricing comparisons. The assistant can draw from those different results while writing one recommendation.

That creates a specific content problem. Suppose your landing page explains fleet routing but puts its compliance details behind a gated demo. The page may help with the fleet-size question while giving the assistant little accessible material for the compliance question. Practitioners discussing [query fan-out on r/bigseo](https://www.reddit.com/r/bigseo/comments/1uvtpce/how_do_you_optimize_for_qfo/) make the case for self-contained claim-and-evidence passages: material that can answer a narrow question without requiring the reader, or the retrieval system, to piece together a sales site. The practical move is to make the relevant answer findable where the question arises.

It also helps explain a volatile dashboard. In Surfer’s analysis, pages ranking for both a primary query and its fan-out sub-queries were [161% more likely to be cited in Google’s AI Overviews](https://surfer.ai/blog/query-fan-out/) than pages ranking for the primary query alone. The same analysis found that only 27% of fan-out queries repeated across runs of the exact same prompt, while 66% appeared once.

So a Tuesday mention followed by a Thursday absence does not, by itself, mean your content deteriorated overnight. Tuesday’s rewrite may have found your pricing passage. Thursday’s may have leaned toward a fleet-safety question you do not answer. **A mention trend shows what happened; the retrieval paths help explain why.**

## Step 3: retrieval, citation, and recommendation split apart

Finding your page is still not the same as recommending your product. After retrieval, the assistant has to assemble an answer. It can use one source to establish a fact and another to choose vendors. [Being retrieved, cited, and recommended are distinct events](https://www.richresults.ai/ai-visibility-chatgpt.html), even when a tracker compresses them into one visibility score.

Imagine your team publishes a useful breakdown of HIPAA cold-chain logistics. The assistant uses it to explain a requirement and cites the page. Then it names three dispatch vendors from a directory found through the reviews-and-pricing search. Your URL helped ground the answer. A competitor got the customer-facing recommendation.

![A compliance report earns a citation while a competitor receives the vendor recommendation.](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/8824a239-54b1-45dc-8e99-2daf86b1dbf7.png)

The reverse can happen, too. A competitor can appear in a recommendation because a forum discussion or third-party comparison names it, even if the competitor’s own site is not cited. Looking only at your domain’s citation count would miss the [retrieval event behind the citation](https://groas.com/post/why-chatgpt-cites-your-competitor-and-no) and the source behind the vendor mention.

This distinction gives me three diagnostic questions, in order:

1. Did material about my brand appear in a result for a relevant sub-query?
2. Did the assistant use or cite that material when explaining the answer?
3. Did it name my brand as a vendor that fits the buyer’s need?

A “no” at each stage calls for different work. More prompt replays will not tell you which stage failed.

## What your prompt list can—and cannot—tell you

A commercial tracker might run fifty buyer prompts across several assistants, parse the answers for your brand name, and report 64% visibility. That can be a useful record of its sampled answers. I would not treat it as a measure of underlying search authority. **The fixed prompt is an input, not a fixed retrieval path.** Repeated runs can take different routes and produce different answers.

My next instinct would be to check Search Console for the missing search terms. That runs into another familiar limit. As [Rheinwunder’s analysis of AI search tracking](https://rheinwunder.com/en/knowledge/query-fan-out/) notes, Search Console can show performance information associated with AI search experiences without revealing the synthetic sub-queries that led to a result. You can inspect the page and its ordinary search performance; you cannot simply download the assistant’s full search terms report.

That means working backward. [Before buying an AI visibility tool, audit your own prompts](https://groas.com/post/before-you-buy-an-ai-visibility-tool-run): compare the buyer questions you track with the long-tail searches and pages that already bring you high-intent traffic. Then ask which underlying needs those pages actually answer. Do they explain pricing boundaries, integration prerequisites, regulatory requirements, and operational constraints, or do they merely repeat a broad category phrase?

This is manageable without guessing every synthetic query. The Surfer dataset found that roughly 90% of fan-out queries clustered into four or fewer core topical intents. For the courier example, I would not write separate pages for `fleet routing software under 20 vans` and `dispatch tools for 15 vehicle courier fleet` just because the phrasing differs. I would make the fleet-size answer clear, then check whether the compliance and pricing answers are equally clear. **Cover the need, not every possible wording of the need.**

## Demand a diagnosis, not another visibility percentage

If an AI visibility platform only gives you an aggregate percentage for twenty fixed prompts, I would not buy it for search operations. The score may tell you when to investigate. It does not tell you what to fix.

A useful tool should make the stages of the problem visible:

- **Sub-query intent:** Show observed retrieval calls where available, or clearly label simulated fan-out. Group the searches by the distinct questions behind a buyer prompt rather than presenting guesses as captured payloads.
- **Separate outcomes:** Distinguish material that was fetched, a URL that was cited, and a brand that was explicitly recommended.
- **A specific content gap:** Point to the missing answer or passage attribute, such as an absent pricing boundary or an unaddressed compliance criterion, rather than telling you to “improve AI visibility.”

![A single visibility score beside separate streams for sub-query intent, citations, and recommendations.](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/178ba112-79d2-4b5a-9d4f-d16b4e333d81.png)

That is the difference between a dashboard and an operating instrument. The first says your number fell. The second gives you a plausible place to look before anyone starts rewriting the home page.

## Try the model on a prompt you have never tracked

Take a new buyer question: _“What warehouse inventory software integrates directly with Shopify and handles bonded customs reporting?”_ I would not start by drafting _“The Ultimate Guide to Bonded Warehouse Inventory Software for Shopify Brands.”_ A title that repeats the prompt does not answer all the retrieval jobs inside it.

I would break the buyer’s question into likely needs first. The assistant might search for Shopify inventory-sync constraints, bonded warehouse compliance requirements, and software comparisons covering customs reporting, integrations, and pricing. Those are predictions about the work required to answer the prompt, not claims that I have seen its hidden queries.

Now test the pages against those needs. If your product documentation explains Shopify webhooks on one page but buries customs reporting in an unindexed PDF brochure, the assistant has an accessible answer for one job and a weak path to the other. A competitor with clear, self-contained material on both dependencies has a better route into the final recommendation. A tracker replaying the original prompt might catch the lost mention. The retrieval model tells you what to inspect.

That is why I do not think prompt tracking is mainly a monitoring problem. A line chart can flag a change, but someone still has to connect the buyer’s question to the material an assistant can retrieve, then keep that material and the wider search program current. Periodic reviews leave too much of that work waiting in a queue.

At [groas](https://groas.com/), we built an autonomous growth engine for paid and organic search around continuous execution rather than another pile of recommendations. Specialized AI models work on content, technical adjustments, campaigns, and bids within client guardrails, while a dedicated human strategist owns direction and accountability. The operating principle is the same in the warehouse case as it was in the courier case: **stop treating the prompt as the whole search**. Find the narrower jobs behind it, give each one a clear answer, and measure whether that work reaches the recommendation.

## Frequently Asked Questions

### What is query fan-out in AI search?

Query fan-out is when an AI assistant rewrites one buyer prompt into several narrower synthetic sub-searches, retrieves material for each, and assembles an answer from what it finds. For example, a question about dispatch software can turn into separate searches about compliance requirements, fleet-size fit, and pricing.

### How many internal searches does an AI assistant run per prompt?

It varies by engine. A Surfer benchmark of 10,000 queries found Gemini averaged 10.7 fan-out queries per prompt, ChatGPT roughly 2, and Perplexity 1.4. An analysis of over 20 million ChatGPT fan-outs reported 2.3 to 2.8 internal web searches per prompt on average.

### Does ranking well for a broad keyword help my visibility in AI answers?

Not automatically for the narrower searches behind it. The assistant can draw on passages returned for several narrower queries and combine their results, so a top rank on the broad phrase does not guarantee your page serves a compliance, pricing, or fleet-size search. Pages ranking for both a primary query and its fan-out sub-queries were 161% more likely to be cited in Google's AI Overviews.

### Why did my brand disappear from an AI answer between two days?

A disappearing mention does not by itself mean your content deteriorated. Repeated runs of the same prompt can take different retrieval routes: one run may have found your pricing passage while another leaned toward a question your pages do not answer. Surfer's analysis found only 27% of fan-out queries repeated across runs of the exact same prompt.

### Is being cited by an AI assistant the same as being recommended?

No. An assistant can retrieve your page to ground a fact and cite it, then name competitor vendors from a different source in the customer-facing recommendation. A competitor can also be recommended because a forum post or third-party comparison names it, even if its own site is never cited.

### Can I see the actual sub-queries an AI assistant ran in Search Console?

No. Search Console can show performance information associated with AI search experiences without revealing the synthetic sub-queries that led to a result. You can inspect the page and its ordinary search performance, but you cannot download the assistant's full search terms report, which is why the article suggests working backward from the long-tail searches and pages already bringing high-intent traffic.

### Should I write a separate page for every possible AI query rewrite?

No. Roughly 90% of fan-out queries cluster into four or fewer core topical intents, so covering each distinct need clearly matters more than matching every phrasing. The article recommends identifying the distinct jobs behind a prompt, such as compliance, fleet size, and pricing, and making sure each one has a clear, self-contained answer.

### What should I look for in an AI visibility tracking tool?

The article argues a useful tool should show three things rather than one aggregate percentage: sub-query intent, with observed retrieval calls where available and simulated fan-out clearly labeled; separate outcomes that distinguish fetched material, cited URLs, and explicitly recommended brands; and a specific content gap, such as a missing pricing boundary or unaddressed compliance criterion, instead of a generic instruction to improve AI visibility.

## Paid Ads & SEO, Run For You

Businesses pay one flat monthly fee per service, agencies resell it under their own brand, and groas does the work either way.

[See Pricing](https://groas.com/pricing)

## Structured data

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://graph.groas.com/entity/groas","name":"groas","url":"https://groas.com/","description":"groas is a done-for-you marketing service, not software: elite people working with proprietary technology systems run search ads, Meta ads, SEO and AI search for businesses, and white label for agencies, with a dedicated senior strategist owning every account.","logo":{"@type":"ImageObject","url":"https://groas.com/icon-512.png","width":512,"height":512},"sameAs":["https://www.linkedin.com/company/groas/"]},{"@type":"WebSite","@id":"https://groas.com/#website","name":"groas","url":"https://groas.com/","inLanguage":"en-US","publisher":{"@id":"https://graph.groas.com/entity/groas"}},{"@type":"WebPage","@id":"https://groas.com/post/the-prompt-you-track-isn-t-the-search-th#webpage","url":"https://groas.com/post/the-prompt-you-track-isn-t-the-search-th","name":"Your AI Visibility Tracker Sees the Prompt, Not the Searches Behind It","description":"A buyer prompt can fan out into narrower searches before an AI assistant answers. Here’s why brand mentions fluctuate, what a useful tracker should show, and where to work instead.","inLanguage":"en-US","isPartOf":{"@id":"https://groas.com/#website"},"about":{"@id":"https://graph.groas.com/entity/groas"},"primaryImageOfPage":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/7d88a9c7-4388-4964-b712-7e963ba48602.png"},"breadcrumb":{"@id":"https://groas.com/post/the-prompt-you-track-isn-t-the-search-th#breadcrumb"},"dateModified":"2026-10-26T05:42:32.262Z","mainEntity":{"@id":"https://groas.com/post/the-prompt-you-track-isn-t-the-search-th#article"}},{"@type":"BreadcrumbList","@id":"https://groas.com/post/the-prompt-you-track-isn-t-the-search-th#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://groas.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://groas.com/blog"},{"@type":"ListItem","position":3,"name":"Your AI Visibility Tracker Sees the Prompt, Not the Searches Behind It","item":"https://groas.com/post/the-prompt-you-track-isn-t-the-search-th"}]},{"@type":"BlogPosting","@id":"https://groas.com/post/the-prompt-you-track-isn-t-the-search-th#article","url":"https://groas.com/post/the-prompt-you-track-isn-t-the-search-th","mainEntityOfPage":{"@id":"https://groas.com/post/the-prompt-you-track-isn-t-the-search-th#webpage"},"isPartOf":{"@id":"https://groas.com/blog#blog"},"headline":"Your AI Visibility Tracker Sees the Prompt, Not the Searches Behind It","description":"A buyer prompt can fan out into narrower searches before an AI assistant answers. Here’s why brand mentions fluctuate, what a useful tracker should show, and where to work instead.","datePublished":"2026-10-26T05:42:32.206Z","dateModified":"2026-10-26T05:42:32.262Z","image":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/7d88a9c7-4388-4964-b712-7e963ba48602.png"},"author":{"@id":"https://groas.com/author/alexander-perelman#person"},"publisher":{"@id":"https://graph.groas.com/entity/groas"},"keywords":"prompt, search, searches, visibility, answer, assistant, tracker, buyer","wordCount":2000,"inLanguage":"en-US"},{"@type":"Person","@id":"https://groas.com/author/alexander-perelman#person","name":"Alexander Perelman","jobTitle":"Head Of Product @ groas","description":"My background includes Goldman Sachs and Stanford Computer Science.","image":"https://groas.com/media/blog/4f17cac3a81acc224cc1b2cfab8f94bbc295a3089d13e8421125771ef8d4064f.jpg","worksFor":{"@id":"https://graph.groas.com/entity/groas"},"sameAs":["https://www.linkedin.com/in/alexander-433793253/"]},{"@type":"FAQPage","@id":"https://groas.com/post/the-prompt-you-track-isn-t-the-search-th#faq","mainEntity":[{"@type":"Question","name":"What is query fan-out in AI search?","acceptedAnswer":{"@type":"Answer","text":"Query fan-out is when an AI assistant rewrites one buyer prompt into several narrower synthetic sub-searches, retrieves material for each, and assembles an answer from what it finds. For example, a question about dispatch software can turn into separate searches about compliance requirements, fleet-size fit, and pricing."}},{"@type":"Question","name":"How many internal searches does an AI assistant run per prompt?","acceptedAnswer":{"@type":"Answer","text":"It varies by engine. A Surfer benchmark of 10,000 queries found Gemini averaged 10.7 fan-out queries per prompt, ChatGPT roughly 2, and Perplexity 1.4. An analysis of over 20 million ChatGPT fan-outs reported 2.3 to 2.8 internal web searches per prompt on average."}},{"@type":"Question","name":"Does ranking well for a broad keyword help my visibility in AI answers?","acceptedAnswer":{"@type":"Answer","text":"Not automatically for the narrower searches behind it. The assistant can draw on passages returned for several narrower queries and combine their results, so a top rank on the broad phrase does not guarantee your page serves a compliance, pricing, or fleet-size search. Pages ranking for both a primary query and its fan-out sub-queries were 161% more likely to be cited in Google's AI Overviews."}},{"@type":"Question","name":"Why did my brand disappear from an AI answer between two days?","acceptedAnswer":{"@type":"Answer","text":"A disappearing mention does not by itself mean your content deteriorated. Repeated runs of the same prompt can take different retrieval routes: one run may have found your pricing passage while another leaned toward a question your pages do not answer. Surfer's analysis found only 27% of fan-out queries repeated across runs of the exact same prompt."}},{"@type":"Question","name":"Is being cited by an AI assistant the same as being recommended?","acceptedAnswer":{"@type":"Answer","text":"No. An assistant can retrieve your page to ground a fact and cite it, then name competitor vendors from a different source in the customer-facing recommendation. A competitor can also be recommended because a forum post or third-party comparison names it, even if its own site is never cited."}},{"@type":"Question","name":"Can I see the actual sub-queries an AI assistant ran in Search Console?","acceptedAnswer":{"@type":"Answer","text":"No. Search Console can show performance information associated with AI search experiences without revealing the synthetic sub-queries that led to a result. You can inspect the page and its ordinary search performance, but you cannot download the assistant's full search terms report, which is why the article suggests working backward from the long-tail searches and pages already bringing high-intent traffic."}},{"@type":"Question","name":"Should I write a separate page for every possible AI query rewrite?","acceptedAnswer":{"@type":"Answer","text":"No. Roughly 90% of fan-out queries cluster into four or fewer core topical intents, so covering each distinct need clearly matters more than matching every phrasing. The article recommends identifying the distinct jobs behind a prompt, such as compliance, fleet size, and pricing, and making sure each one has a clear, self-contained answer."}},{"@type":"Question","name":"What should I look for in an AI visibility tracking tool?","acceptedAnswer":{"@type":"Answer","text":"The article argues a useful tool should show three things rather than one aggregate percentage: sub-query intent, with observed retrieval calls where available and simulated fan-out clearly labeled; separate outcomes that distinguish fetched material, cited URLs, and explicitly recommended brands; and a specific content gap, such as a missing pricing boundary or unaddressed compliance criterion, instead of a generic instruction to improve AI visibility."}}]}]}
```