You can now track AI traffic in Google Search Console two ways: through the dedicated Generative AI performance reports Google launched on 3 June 2026, and through the query-level detection method that fills the gap those reports leave open. This is the measurement layer beneath our AI search strategy for South Africa and the practical companion to our first-party traffic analysis.
The short version of why you need both: the official report tells you how often you appeared, but not for which questions. The detection method tells you which questions — which is the half you can actually act on.
Quick Answer
To track AI traffic in Search Console, start with the Generative AI performance reports Google introduced on 3 June 2026, which show impressions from AI Overviews, AI Mode and Discover broken down by page, country, device and date. They carry no click, CTR or query data, and are rolling out to a subset of sites — so pair them with query-level detection in the standard Performance report: long, specific queries holding strong positions with high impressions and zero clicks. Add a device-split check and referral tracking for assistants outside Google.
Want someone to run this detection on your own console and show you what's already being read? It costs nothing to see.
Get a Free Console Detection RunWhat Do Google's New Generative AI Reports Actually Show?
They show impressions inside Google's generative AI features, isolated from classic search results for the first time. Google's Search Central announcement describes dedicated views covering generative AI features in Search — AI Overviews and AI Mode — plus generative AI features in Discover, reporting how often URLs from your site appeared in them.
Three caveats matter before you build reporting on it. The data is not new: Google confirms these impressions were always counted inside your overall performance totals, so your headline numbers haven't changed and historical comparisons remain valid. The reports launched to a subset of websites for testing rather than everyone at once. And the current view is impressions only — no clicks, no click-through rate, no queries.
That last limitation is the important one strategically. Knowing you appeared 40,000 times inside AI answers is useful for proving the surface exists to a sceptical board. Knowing which questions produced those appearances is what tells you what to write next — and that data isn't in the report.
Google shipped one more control alongside the reports: a setting letting sites block their content from appearing in AI features. Google has been explicit that sites opting out receive neither traffic nor impressions from those surfaces — which makes it a decision worth taking deliberately rather than discovering by accident, and one most lead-generation businesses should think hard about before touching.
Key Takeaway
Google's Generative AI performance reports, launched 3 June 2026, break out AI Overview and AI Mode impressions by page, country, device and date — but include no click, CTR or query data, and reached a subset of sites first. They prove the surface exists; they don't tell you which questions put you there.
How to Track AI Traffic When the Report Has No Query Data
Use the standard Performance report and hunt for the machine-reading signature: unusually long, hyper-specific queries sitting at strong average positions with substantial impressions and no clicks at all. Humans don't type forty-character natural-language questions and then decline to click the top result; retrieval systems do exactly that.
Our working detection filter is four conditions applied together — six or more words in the query, average position six or better, fifty or more impressions, and zero clicks. Applied to Growth Pulse Media's own 382-post site over one 28-day window, that pattern isolated eleven queries carrying 11,388 impressions, roughly 7.8% of the site's total.
The clearest exhibit from our own console: the query "website security & updates south africa" delivered 9,279 impressions at average position 1.9 — the single largest query on the entire site — and produced zero clicks. That is machine reading at scale, visible in an ordinary SA business account with no special tooling.
Building it takes about ten minutes. Open Performance, set the date range to the last 28 days, switch to the Queries tab, then sort by impressions descending and scan the top rows for entries with zero clicks. Export to a sheet if you want the word-count and position conditions applied properly — the eye-scan version catches the biggest offenders, but the filtered version is what you track month to month.
Run it monthly and treat the output as a content brief. The questions appearing in that filter are the questions your site is already trusted to answer, which makes them the cheapest citation wins available — sharpen those pages first, using the properties in our guide to content AI systems quote.
Be clear about what the filter can't prove. Zero-click long-tail queries are strong circumstantial evidence of machine reading, not a labelled confirmation from Google, and some will be genuine human searches that simply didn't convert to a click. Treat the pattern as a well-founded inference and the trend across months as the real signal — that's the honest framing, and it holds up when a client interrogates it.
Not sure how to build the filter in your own console? We'll set it up with you on a screen share and leave you the template.
Request a Free Detection SetupWhy Does the Device Split Matter?
Because machine reading registers overwhelmingly as desktop, so a widening gap between your mobile and desktop click-through rates is corroborating evidence. Humans in South Africa browse and click from phones; automated retrieval doesn't.
In our own 28-day window, mobile delivered 383 of 848 clicks — 45% of clicks from just 25% of impressions — producing a mobile CTR of 1.04% against 0.42% on desktop. Neither number is impressive in isolation. The ratio between them is the signal, and it's free to check in two clicks.
Log both figures monthly alongside the query count. Three numbers — machine-query share, mobile CTR, desktop CTR — take five minutes to pull and give you a trend line that no dashboard sells and most SA agencies aren't producing.
How Do You Track Assistants Outside Google?
Search Console only sees Google. For ChatGPT, Perplexity, Gemini and the rest, the instrument is your analytics referral report — visits arriving from assistant domains show up as referral traffic, and segmenting them reveals both volume and behaviour.
Expect small numbers and unusually good behaviour. Assistant referrals arrive pre-qualified because the shortlisting already happened inside the answer, which is consistent with Semrush data putting AI-referred conversion at roughly 4.4 times organic rates. Judge this channel on conversion quality and pipeline, never on session volume.
Then close the loop where analytics can't reach: the monthly prompt log from our five-layer visibility audit, plus the intake question that costs nothing. "How did you come across us?" answered verbatim catches the referrals that never carried a referrer at all — the buyer who read an answer, remembered the name, and typed it into their browser three days later.
Key Takeaway
Four instruments cover the whole picture: Google's Generative AI reports for impression proof, query-level detection for the questions behind them, the mobile-versus-desktop CTR gap as corroboration, and analytics referral segments plus verbatim intake answers for assistants outside Google. No single tool sees all of it, which is why the combination is the method.
What Should a Monthly AI Reporting Sheet Contain?
Six lines, and it should fit on one page. Anything longer gets skipped by the person who most needs to read it.
| Metric | Where It Comes From | What It Tells You |
|---|---|---|
| Generative AI impressions | GSC Generative AI report, if available | Whether the surface sees you at all |
| Machine-query count and impression share | Performance report, detection filter | Which questions you're trusted on |
| Mobile vs desktop CTR gap | Performance report, device tab | Corroborating evidence of machine reading |
| Assistant referral sessions and conversions | Analytics referral segment | The quality of what arrives |
| Citations on tracked prompts | Monthly prompt log | Standing outside Google entirely |
| Enquiries mentioning an AI tool | Verbatim intake question | The line that pays for the programme |
Assign an owner and a fixed day. The reason most teams never track AI traffic properly isn't difficulty — it's that the job belongs to nobody in particular, so it happens in bursts of enthusiasm and then stops. First Monday of the month, one person, twenty minutes.
Note what's absent: total sessions. Including it invites the conversation this whole discipline exists to move past, and the six lines above tell a truer story about a channel where impressions rise while clicks stay flat.
What Does Disciplined Tracking Change?
It changes which content gets funded, because you finally know which pages machines already trust. The composite below reflects the typical shape for an SA firm running this measurement stack for three months before acting on it. Figures illustrate the pattern, not a single client's audited results.
| Metric | Before Tracking | After 3 Months | Change |
|---|---|---|---|
| Machine-read questions identified | 0 known | 14 identified | New visibility |
| Content decisions made on AI signals | 0% | 60% | New input |
| Citations on tracked prompts | 2 of 20 | 7 of 20 | +250% |
| Estimated monthly pipeline value | R200,000 | R270,000 | +35% |
One caution on reading that table: the ability to track AI traffic doesn't itself produce citations, and a team that measures diligently while changing nothing will book three months of very well-documented stagnation.
The second row is the mechanism. Measurement doesn't create citations — it redirects effort toward the pages already halfway there, which is why tracking pays before any new content gets written.
Key Takeaway
Tracking pays before publishing does. Identifying the questions machines already read on your site redirects content effort toward pages that are halfway to being cited, rather than starting fresh topics from zero — which is why the measurement stack is the first build, not the last.
The GPM Differentiator: The Method Came From Our Own Console
The detection filter in this guide wasn't borrowed from an overseas blog — we built it looking at Growth Pulse Media's own Search Console, and every number quoted above comes from that account. Our AEO services for South African businesses run the same stack for clients, including the unglamorous parts: the verbatim intake question and the one-page sheet.
We publish it because measurement is the honest half of this industry. Any agency can claim AI visibility work is going well; far fewer will show you the console behind the claim, and fewer still will tell you which of their instruments can't see what.
Who This Is NOT For
Anyone wanting one dashboard for everything. No single tool covers Google impressions, query intent, and non-Google assistants. If a vendor claims complete AI attribution in one screen, ask which of the four instruments they've replaced — the answer is none.
Sites too small for the pattern to appear. The detection filter needs enough query volume for machine reading to stand out. Very small sites should start with the prompt log instead, which works at any size.
Teams that will treat impressions as success. Impressions prove the surface exists; they don't pay anyone. If the reporting stops at the first line of the sheet, this becomes a vanity exercise with extra steps.
Anyone expecting precise attribution. Much of this channel's value arrives with no referrer at all — a name remembered from an answer, typed in days later. The method narrows the uncertainty honestly; it doesn't eliminate it.
Rather have the whole stack built and reported monthly — detection filter, device split, referral segments and the prompt log in one page?
Book a Free Measurement Setup SessionQuestions SA Marketers Ask About Measuring AI Visibility
Can I track AI traffic in Search Console yet?
Partly. Google launched Generative AI performance reports on 3 June 2026 showing AI Overview and AI Mode impressions by page, country, device and date, rolled out to a subset of sites first. There's no click, CTR or query data, so query-level detection in the standard Performance report remains necessary for knowing which questions drive your appearances.
Why does the Generative AI report show no clicks?
Google's launch announcement describes the reports as impression-focused views of visibility inside generative AI features. Click and query data aren't part of the current version. Pair the impression view with analytics referral segments for the click side, and with the detection filter for the query side.
What exactly is the machine-query detection filter?
Four conditions applied together in the standard Performance report: queries of six or more words, average position six or better, at least fifty impressions, and zero clicks. Queries meeting all four are almost always retrieval systems reading your page rather than people declining to click a top result.
Did my traffic numbers change when the new reports launched?
No. Google confirmed the AI impressions were already included in the overall performance report and continue to be counted there — the June 2026 launch added a separate view rather than new data. Your historical comparisons and aggregate totals remain valid.
How do I see traffic from ChatGPT or Perplexity?
Through your analytics referral report, segmented by the assistant domains. Expect low volume and high quality — AI-referred visitors convert at roughly 4.4 times organic rates per Semrush data. Add a verbatim "how did you find us" intake question to catch the referrals that arrive with no referrer at all.
How often should I run this?
Monthly for everything, with the prompt log on the same schedule. AI answers rebuild from live retrieval, so standings shift between quarters, and the sheet only becomes useful once you have three or four months of trend to read rather than a single snapshot.
Still reporting AI visibility as a hunch? The instruments exist now, they're free, and the first run usually takes about twenty minutes — which makes "we don't have the data" a choice rather than a constraint.
Get Your Free AI Measurement Setup
We'll run the detection filter on your Search Console, check whether your property has the new Generative AI reports, build your device-split baseline and hand over the one-page monthly sheet — from the Johannesburg team that developed this method on its own 382-post site and publishes the numbers. No obligation — we'll get back to you within 24 hours.
Claim My Free Measurement Setup

