Google Search Console Against an AI Visibility Tracker: What a UK Business Can Measure in 2026
One is a first party counter for Google's own AI features. The other samples assistant answers. Here is what each one is a record of, with Google's documentation read on 16 October 2026 and our own British reading of 3 citations in 420 readings.
Published by AI Knows Us · Updated 16 October 2026
These are two instruments, not two opinions, and they measure different things. Search Console is a census: Google's own count of what happened on Google's own results pages, AI Overviews and AI Mode included. A visibility tracker is a survey: it puts buying questions to named assistants on a schedule and writes down who was named and which sources carried the answer. A British business wants both, and the arguments start when somebody asks one of them to do the other's job. Google's documentation, read on 16 October 2026, places AI features "within the 'Web' search type" and inside the overall totals. Our own survey reading for the United Kingdom on the same date was 3 citations in 210 ChatGPT readings and none in 210 Gemini readings.
What Google's AI performance data is a record of
Verified ownership is the entry condition, and what you then see is Google's own record of its own results pages. For the AI features the qualifying test turns out to be the ordinary one. Indexing and snippet eligibility are all the Search Central guide asks of a page before it can serve as a supporting link, and the guide says in as many words that "there are no additional technical requirements". Three further documented behaviours shape how the report reads for a British site.
- AI features sit inside the Web search type. On 16 October 2026 that filter held Web text-based, Web multimodal, Image, Video and News. Clicks from AI features arrive inside the first of those, pooled with ordinary results.
- Overviews often do not appear. Google writes that they are "only shown when our systems determine that it is additive to classic Search, and as such, often don't trigger". An uneven month to month line is therefore the normal shape.
- The fan out changes what counts as one question. Google describes a "query fan-out" technique, issuing multiple related searches across subtopics, which is why one typed question can surface a wider set of links than a classic results page.
Aggregation is the other detail worth knowing before anybody builds a dashboard. The documentation states that data grouped by Queries, Countries, Devices or Dates is aggregated by property, while data grouped by Pages or Search appearance is aggregated by page. Two honest exports of the same week can therefore disagree, and the chart total can sit above or below the table total for the same reason. Data ages out of the interface as the window advances, so a monthly download saved somewhere permanent is the only history you will have. The rest of the reports are covered in our Google Search Console guide.
What a tracker is a record of
A tracker runs a frozen list of buyer questions in named assistants, several times each, and records four things per answer: whether the business was named, whether a page on its domain was credited as a source, where in the answer it appeared, and every other domain cited. It is a sample of the thing a buyer actually experienced. The denominator is yours, because you chose the questions, which is both its strength and the reason one supplier's figure is not comparable with another's. So the useful comparison is not which tool is better. It is which question each instrument answers.
| Question a British team asks | Instrument that answers it |
|---|---|
| Did somebody click through from an AI Overview or AI Mode last month? | Search Console, as a click inside the Web search type |
| Which pages are indexed and snippet eligible, the documented requirement for a supporting link? | Search Console, page indexing and URL inspection |
| When a buyer asks ChatGPT for a shortlist, are we one of the names? | A tracker, or the same questions run by hand |
| Which third party domains did the assistant reach for instead of us? | A tracker, from the cited source list |
| Did two assistants answer differently on the same day? | A tracker, reported per engine |
| How much of the organic trend is AI features rather than blue links? | Neither, as a precise split. Read the pooled Web trend and the tracker side by side |
The British numbers we hold, and the one we do not
The British questions in our 16 October 2026 survey numbered 210 per engine, drawn from a 630 question set covering three markets. Nothing came back unreadable, so the denominator is 1,260. Those readings held 20,143 citations across 4,947 distinct domains. Sorted by type, vendor and agency own sites took 82.0%, official platform documentation 12.3% and review directories 0.7%. Three of the 210 British ChatGPT readings carried our own domain as a source. None of the British Gemini readings did.
A survey taken the day before, from questions written independently of these, lands in the same place: 597 usable readings of 612 attempted, 10,652 citations, vendor and agency own sites at 85.6%, review directories at 0.8%, our own domain cited 3 times. What makes that quotable is the agreement, not either figure. The 597 reading benchmark of ChatGPT and Gemini in three markets carries it row by row, and the British slice has its own page, 420 British readings of ChatGPT and Gemini. Two domains showed up in the British answers and in no American one: gov.uk 57 times, ico.org.uk 28.
Here is the figure this page does not carry, said plainly because the alternative is inventing it. We have not surveyed a set of verified Search Console properties and counted how many returned usable AI feature data, so there is no proportion to quote for that. What we have is what Google documents about the counting and what our own sampler produced, both above. The property survey is next, and when it runs the numerator, the denominator and the dates get published with it.
When a separate tracker earns its place in a British budget
- Your buyers shortlist before they search. If the first three names reach a buyer inside an assistant, the sampler reading is the one that predicts your pipeline.
- You report to somebody who was not in the room. A figure with a question count, an engine name and a date survives a challenge. A blended score across engines does not, because the two engines we measured disagreed often.
- You need the citation list, not the score. The domains an assistant reaches for are a target list somebody else wrote for you, and they are the most actionable output of the exercise.
- Your organic trend is flat and your enquiry mix has changed. That is the pattern the pooled Web figure does not resolve on its own.
On cost, settle the VAT basis and the unit before the headline figure, because in this category the unit moves the invoice more than the sticker does. The lines to pin down are in what a UK buyer should settle before the pound price. Search Console costs nothing and needs verified ownership, so it goes in first whatever else you buy. None of this survives as a one off exercise, which is the argument in building a search programme that survives contact with a business, and it applies to the survey half exactly as it does to the census half.
Questions UK businesses ask about Search Console and AI visibility trackers
Does Search Console measure whether ChatGPT recommends us?
It measures Google's surfaces. The documentation covers AI Overviews and AI Mode, both inside the Web search type, and that is the boundary. For ChatGPT, Gemini, Perplexity or Claude, the reading comes from putting the questions to those assistants and recording the answers.
Can I see AI Overview clicks separately from blue link clicks?
The search type filter gave five values on 16 October 2026 and AI features are pooled inside Web text-based, so read the Web trend as one line. The per answer detail comes from a sampler, and the two readings are stronger together than either is alone.
Why do Search Console and a tracker show numbers that look unrelated?
They count different events. Search Console counts clicks and impressions on Google's results pages for your verified property. A tracker counts how often your business appears in answers to a question list you chose.
What should go in the monthly pack?
Three blocks. Search Console Web clicks and impressions with the date range. The tracker reading per engine, with the question count and the date. And the cited domain list, counted, which is the only one of the three that tells you what to do next week.
Two instruments, one British decision
The team that gets this right treats Search Console as its accounts: free, first party and authoritative about Google clicks. It treats the sampler as market research: a chosen sample, re-run on a fixed schedule, reporting each assistant on its own line. The mistake that costs a quarter is asking either one to answer the other's question and then concluding the data is broken. We build the survey half, which is the bias to read this page with. AI Knows Us puts buying questions to ChatGPT, Gemini, Perplexity, Claude and Google AI Overviews with your brand name absent from every one, and prints each rate beside the numerator and the date that produced it. Two of the five carry published measurements so far, and in Britain they left us at 3 citations out of 420 readings on 16 October 2026. A supplier prepared to print a figure like that has handed you something you can go and check.