Every AI visibility tool on the market prices itself on data from Bing. Not because Bing is where the readers are. Because Bing is the only engine that will tell you it cited you.
The instrument
Bing Webmaster Tools publishes per-property AI citation counts. Nobody else does. Across fourteen live properties we run, summed from daily rows over the ninety days to 22 August 2026, that number is 768,234. Restricted to the eleven properties with a full window, the like-for-like figure is 735,780.
Before going further, the number argues with itself. Bing's own citationstats endpoint reports 768,234 for that window. Its per-URL pages/stats endpoint reports 737,197 for the same window, in the same session. The gap is 31,037, about four percent, and it runs in the same direction on all fourteen properties.
We publish the higher figure because it is what the tool's own chart shows a site owner, and we say the lower one exists rather than burying it. If a vendor quotes you a citation count without telling you which endpoint it came from, that is a four percent question they have not answered.
Then we went looking for the readers
Over twenty-eight days, GA4 recorded 2,605 sessions on the network that arrived from an AI assistant.
| engine | sessions | share |
|---|---|---|
| ChatGPT | 2,053 | 78.8% |
| Copilot | 387 | 14.9% |
| Claude | 123 | 4.7% |
| Perplexity | 42 | 1.6% |
| Gemini, DeepSeek, Grok | no matching source string | unmeasurable |
Copilot is the Bing surface. So the engine that publishes a citation count for us is the engine responsible for roughly one seventh of the AI readers who actually arrive. The engine responsible for nearly four fifths of them publishes nothing at all about who it cites.
The inversion
That is the whole finding, and it inverts what the category is sold on. Every dashboard, every AI-visibility score, every pitch deck with a citation chart in it is describing the small channel with confidence and the large one not at all.
We built our own measurement on the same foundation. This is a finding about our instrument before it is a finding about anyone else's.
The part that is genuinely unknown
Gemini, DeepSeek and Grok matched no source string in our data. Zero rows. The correct word for that is unmeasurable, not absent.
Gemini referrals in particular commonly arrive with no distinguishing referrer and land in organic or direct, which means a real reader gets filed as something else. Reporting those engines as zero would be the easy lie, and it is the specific lie this category is built to tell, because a zero looks like a measurement and an admission of blindness does not.
A hypothesis, offered as a hypothesis
Cloudflare per-bot logs show GPTBot, which crawls for training, at about 7,477 requests a day against OAI-SearchBot, which fetches for retrieval, at about 500. Roughly fifteen to one. Yet ChatGPT delivers 78.8% of the AI arrivals.
If the dominant channel is answering largely out of what it already absorbed rather than what it fetches live, then surviving in the training corpus is the lever on most of the traffic, and retrieval optimisation is the lever on the remainder. We are not claiming that is settled. We are saying the crawl ratio and the referral share point the same way and almost nobody is pricing on it.
The question
If the biggest channel is unmeasurable by construction, what is anyone actually selling: the placement, or the measurement of the one place that happens to report?
Figures: Bing Webmaster AI performance, fourteen properties, 23 May to 22 August 2026, summed from daily rows. GA4 Data API by session source, twenty-eight days to 20 August 2026. GA4 is JavaScript based, so ad blockers and privacy browsers are missed and every session figure here is a floor, not a ceiling.
Top comments (2)
The blindness vs absence distinction is the strongest part here. I would be cautious, though, about using GPTBot:OAI-SearchBot request counts to infer that training-corpus survival is the traffic lever. Requests are not successful fetches, unique content volume, or answer attribution. In a scan we ran across 284 Korean DTC brands and 50 AI shopping questions per brand, 65.5% had zero appearances and the mean was only 0.648 out of 50. That sparsity suggests crawl exposure alone may be a weak predictor of being selected. A cleaner next test might join OAI-SearchBot fetches by URL and time to repeated prompt-level citations and ChatGPT referral landing pages, while keeping GPTBot separate. Across the fourteen properties, does the property-level OAI-SearchBot share correlate with ChatGPT sessions at all?
wild that everyone is just relying on bing data for this stuff lol. wonder if there's a way to track this without a third party tool?