ChatGPT site: Operator Share and Fanout Depth, August 2026
Promptwatch fanout data shows ChatGPT Search adopting the site: operator overnight on August 8, 2026, with searches per response nearly doubling at the same time.
On August 8, 2026, ChatGPT Search changed how it searches the web overnight. Fanout queries using the site: operator, searches scoped to a specific domain, jumped from 0.37 percent to 16.8 percent of all fanout queries in a single day. At the same time the average number of searches per response nearly doubled.
The site operator fanouts report and the query fanouts report, published August 10 and March 1, 2026, track the shift. For anyone who cares about showing up in ChatGPT answers, the practical question is what the methodology does and does not show.
What the sample does and does not show
Promptwatch's site operator report covers the percentage of all ChatGPT Search fanout queries that contain the site: operator, per day. The share hovered between 0.3 percent and 0.5 percent for weeks. It dipped briefly to 0.15 percent on August 3 to 5, which is consistent with a staged rollout or a pre launch experiment. Then it jumped to 16 to 17 percent on August 8. That is roughly a 46x increase in share within a single day.
The query fanouts report covers the average number of fanout queries per ChatGPT Search response, per day. On August 8 the average jumped from about 1.08 to about 1.83, the same day the site: usage surged. The timing is the key signal. The new domain scoped searches come on top of the generic web searches ChatGPT was already running, they do not replace them. If ChatGPT had swapped generic queries for site: queries, the average would have stayed flat.
The methodology is the part that decides what the number means. A fanout is a background web search ChatGPT runs to build an answer. A site: query is a fanout scoped to one domain. The share is site: fanouts divided by all fanouts, not by all queries. The average is fanouts per response, not per query. The two series measure different things, which is why the August 8 jump in both is a stronger signal than a jump in one.
What the sample cannot show is which domains ChatGPT targets with the site: operator. The data is aggregated and non identifiable. It shows the share of queries that are domain scoped, not which domains those queries target. For your own brand, the question is whether ChatGPT is running site:yourdomain.com against your topics, and that is a question only your own tracking answers.
What the sample does not tell you about your prompts
The reports are population level views. They tell you what ChatGPT is doing across the whole web. They do not tell you what ChatGPT is doing for your prompts. For that you need your own fanout data joined to your own visibility data.
That gap matters because the population share and your prompt share are not the same thing. ChatGPT can adopt the site: operator at the population level and never run a site: query for your prompts, or run them for your competitors. The 16.8 percent figure is a reason to check your own fanout depth, not a reason to assume your prompts were affected in proportion.
What to do about it
The first move is to treat your own domain as a retrieval surface. The pages ChatGPT can reach with a site: query are the pages it has indexed from your domain. Make sure your most important pages are crawlable and indexed. A site: scoped query can only surface what search engines have indexed from your domain, so gaps in coverage translate directly into gaps in AI answers.
The second move is to re run your fanout analysis for your tracked prompts. The queries ChatGPT generates from a prompt changed materially on August 8. Keyword mappings built before the shift are stale. A fanout you mapped in July no longer matches the fanout ChatGPT runs today, so the prompt to keyword map needs a refresh.
The third move is to watch fanout depth over time, not on a single day. The report shows the shift happened in a single day, but the population view does not tell you whether it held for your prompts. A sustained step in your own fanout depth is the signal, and a single day is a snapshot.
How to measure it properly
Population reports like Promptwatch's tell you what ChatGPT is doing across the whole web. The measurement that turns it into a prompt level decision is your own fanout data joined to your own visibility data. That join is the part most visibility tools skip.
Promptwatch publishes that data as query fanout tracking. The feature tracks query fanout volume, average queries per response, and query length trends over time, based on ChatGPT Search data. For a report that shows the site: shift at the population level, the matching move is to open the same fanout view for your own prompts and see whether the shift shows up in your fanout depth.
What the methodology cannot rule out
The report is careful about what it does not claim. It does not say why ChatGPT adopted the site: operator. A jump that fast, in lockstep across the fanout behavior, points to a model or system prompt rollout on OpenAI's side rather than a gradual behavior change. Platform controlled search behavior can change overnight, which is the part that makes one off audits unreliable and continuous monitoring necessary.
That restraint matters for how you read the number. A 16.8 percent share is evidence of a retrieval change, not evidence of a ranking change. The work that follows, watching whether your prompts now trigger site: queries and whether those queries surface your pages, is the work your own tracking does, not the work the population report does.
The broader pattern
The site: shift is one instance of a wider change in how AI search retrieves information. The average searches per response nearly doubling at the same time is the other half of the story. ChatGPT now searches both wider, more queries per answer, and deeper, queries scoped to specific domains, than it did before.
For visibility work, that means the retrieval surface is getting more granular. A year ago, the work was to be present in the open web results ChatGPT returned. Now the work is to be present in the open web results and in the domain scoped results. The practical response is to treat fanout depth as a first class signal, not an afterthought.
What to watch next
The reports are snapshots through August 17, 2026 for the site operator report and ongoing for the query fanouts report. The open questions are whether the site: share holds, whether the average searches per response keeps climbing, and whether the new domain scoped queries translate into different citation patterns. Those are exactly the questions a fanout view answers for your own prompts.
The dataset Promptwatch publishes is aggregated and non identifiable, and it is refreshed constantly. That makes it useful for spotting population level shifts. It does not replace the need to track your own brand, your own prompts, and your own fanout depth. The two work together: the public report tells you what is happening in the field, and your own tracking tells you whether it is happening to you.