What does the Search Console generative AI report measure?
You get impressions, and nothing else. Google's help page defines them as "how many times links to your site were shown to a user in a generative AI feature on Google Search". It documents no clicks, position or click-through rate.
| Element | Measured | What the page says |
|---|---|---|
| Your impressions in AI Overviews and AI Mode | Yes | No per-feature split listed |
| Your clicks, CTR, average position | None documented | AI clicks sit inside the Web search type |
| Your pages, countries, dates, devices | Yes | Canonical URL; country of search; day, week or month |
| Your queries | No | No query dimension listed |
| Search type | Filter | "Web: text-based" and "Web: multimodal" (Lens, Circle to Search, Chrome image search) |
| Discover, Search Labs | Excluded | Discover has its own report; Labs is "still in active development" |
Google announced the report on 3 June 2026 for "a subset of websites". Now "As of August 31, 2026, we've rolled out these insights to all websites worldwide." You see it only with enough AI-feature impressions and no exclusion from Search generative AI features.
Our position: show your CFO a presence measure. The moment a slide calls it traffic, every other number on it loses credibility. In marketing analytics and insight work for insurers, banks and fintechs, the CFO objection is predictable: show me where the money touched this.
Why the generative AI impression is not a visit
An impression means your link was on screen inside an AI answer; it counts whether or not anyone clicked. In the chart total, two links from one site in one feature count once per property.
"This data is included in the overall performance report, where it will continue to be tracked"
Hillel Maoz, Search Ecosystem Engineering Manager, and Moshe Samet, Product Manager Lead, Search Console, in the Search Central blog, 3 June 2026
Google's AI features documentation says AI traffic is "included in the overall search traffic in Search Console", so you cannot pull out a separate AI click figure.
GA4's AI Assistant channel, live since 13 May 2026, covers "sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok" and "excludes Google's AI Overviews and AI Mode". Put the two side by side and you show presence on one set of engines next to visits from another. Google calls clicks from AI Overview pages "higher quality" without a number, so keep that line in your SEO programme review, out of your finance deck.
Five settings that change the number before the CFO sees it
Five settings move your number, and most are invisible in a screenshot.
| Setting | What happens | What you do |
|---|---|---|
| Time | "All dates are in Pacific Time Zone (PT)." Singapore and Kuala Lumpur: 15 or 16 hours ahead. Sydney: 17 to 19 | Label your row "Pacific Time"; compare trends, not days |
| Rows | "The usual data limitations (1,000 row limitation, time period, etc)" apply | Use your chart total; treat the page table as your top 1,000 rows |
| Freshness | "Preliminary data is indicated by a dotted line on the graph." | Never screenshot your range if it ends in the dotted line |
| Aggregation | Your chart: by property. Your page-grouped table: by page | Name your level; the totals can differ |
| Exports | Values you see as "~" or "-" export as zeros | Reconcile your zeros against the screen |
In Singapore or Kuala Lumpur, your Pacific Time month ends mid-afternoon on the 1st; in Sydney, in the evening. Finance closes on local months, so the periods never match.
A missing report is a finding, not a bug. The help page says you may lack enough AI impressions, or that "you've excluded your site from Search generative AI features". Google updated its "control what you share" documentation on 21 October 2026 to cover that site-wide control. Before you ask why the AI line is flat, check whether legal or compliance switched it off. For a regulated brand, that can be a legitimate choice, recorded as one.
What should sit next to the generative AI report in a board pack?
Three rows: GA4 AI Assistant sessions, a Clarity citation sample and assisted pipeline from your CRM. Each measures something different, so each label should say so.
| Row | What it counts | Where it stops |
|---|---|---|
| GA4 AI Assistant | Your visits: medium "ai-assistant", campaign "(ai-assistant)" | Misses Google AI and referrerless visits |
| Clarity Citations | Your citations, share of authority, grounding queries | A "representative view", a Bing-grounded sample |
| CRM assisted pipeline | Your opportunities with an AI-assistant touch | Shows a touch, not causation |
Google's release note of 13 May 2026 added the GA4 channel; its source list is Google's alone. Our GA4 board-grade reporting guide covers the cadence. Clarity Citations went generally available the same day, across "supported AI experiences" Microsoft does not name. Ihab Rizk, writing on the Microsoft Clarity blog on 17 February 2026, said grounding draws on Bing and set the limit: "The data provides a representative view of grounding and citation activity rather than a complete log of every reference." Use it as our Clarity citation share post describes.
Search Console covers the engine the other rows cannot see; without it, your Google AI presence is a blind spot. Report it by country and top pages (Singapore, Malaysia, Australia, the US, Canada). The prompt panel for the rest is in the share-of-authority measurement stack.
What does Bing Webmaster Tools' AI Performance report add?
Bing Webmaster Tools' AI Performance report shows you where Bing's AI answers cited your site. Microsoft opened it in public preview on 10 February 2026.
| Item | Detail |
|---|---|
| Counts your citations in | Microsoft Copilot, AI-generated summaries in Bing, "select partner integrations" |
| What you get | Total citations, average cited pages, grounding queries, page-level citations, trends |
| Sampling | "Represents a sample of overall citation activity" |
| Added 16 June 2026 | Citation Share (preview): your share of citations for the same grounding query |
| Our site, 28 days to 24 October 2026 | 7,088 citations (our daily citations export) |
Put it in your pack as the Copilot row beside the Search Console row. Label it citations, not visits: GA4 still decides what those citations were worth to you.
The CFO row set: what each number can and cannot prove
Five rows, five sources, and a "cannot prove" column you write before anyone asks. It is Leapbuzz's planning framework, not an industry standard.
| Row and source | Proves | Cannot prove | Slide |
|---|---|---|---|
| AI impressions by country (Search Console, monthly) | Your pages were shown in Google AI answers | Anyone read, clicked or bought | Visibility |
| AI presence share (impressions over Web impressions) | How often AI features showed your links; your counts overlap | Whether your ratio is good; no benchmark | Visibility |
| AI Assistant sessions and conversions (GA4) | Your visits and conversions from recognised assistants | Google AI features; referrerless visits | Finance |
| Citation share (Clarity, monthly trend) | Your citation share on overlapping queries, Bing-grounded | Other engines; exact counts | Visibility |
| Assisted pipeline (CRM, quarterly) | Your opportunities with an AI touch, in money | That the AI touch caused the deal | Finance |
A measure goes on your finance slide only when it is denominated in visits, conversions or money. Insurers and banks need one more "cannot prove" line: the report says nothing about what the AI answer said about you, and a page can earn an impression inside an answer that misstates a policy exclusion. We pair the row set with a monthly answer-accuracy review in AI visibility optimisation, with your compliance officer copied; the insurance marketing page sets out the pairing. This is marketing guidance, not legal or regulatory advice.
If your board pack calls a Search Console number traffic, Leapbuzz rebuilds your row set with a source and a cannot-prove line on every row. Send us the pack.
How to turn the search console generative AI report into three ratios
Divide it by something. Three ratios let you compare quarters without quoting raw counts, and you can compute them from three exports. This is our working assumption, not a Google method.
Presence share = AI impressions ÷ Web impressions × 100. Session share = AI Assistant sessions ÷ all sessions × 100. Opportunity rate = opportunities ÷ AI Assistant sessions × 1,000. Defaults are made-up round numbers; swap in yours.
AI features showed your links in the equivalent of 6.0% of Web impressions (the counts overlap, so read a trend, not a split). 2.0% of your sessions came from non-Google AI assistants, producing 6.7 assisted opportunities per 1,000.
Static version: two illustrative scenarios
| Input or ratio | Scenario A | Scenario B |
|---|---|---|
| Your generative AI impressions | 120,000 | 40,000 |
| Your Web impressions | 2,000,000 | 500,000 |
| AI presence share (trend ratio; counts overlap) | 6.0% | 8.0% |
| Your AI Assistant sessions | 1,800 | 600 |
| Your total sessions | 90,000 | 30,000 |
| Assistant session share | 2.0% | 2.0% |
| Your assisted opportunities | 12 | 3 |
| Opportunities per 1,000 assistant sessions | 6.7 | 5.0 |
Start comparing from the first full month after the 31 August 2026 rollout; earlier months are not comparable. Referrerless visits make your opportunity rate an upper bound, and your presence share is Google-only.
Do this before the next board pack
Rename the row: where your pack says "AI traffic" over a Search Console number, write "Links shown in Google AI answers (impressions, Pacific Time)". Then score your pack.
Not ready to draft: all three must-have items are missing.
If your CFO asks what AI visibility is worth, answer with assisted pipeline; AI marketing ROI the board will accept covers the proof. Leapbuzz builds this layer in marketing analytics and insights for insurers, banks and fintechs across Singapore, Malaysia, Australia, the US and Canada.
Today:
- Export your generative AI report by country for last month.
- Export your Web search type report for the same month.
- Save both with the export date in your filenames.
