Google's Search Console generative AI report, which launched on June 3, 2026, shows how often your pages appear inside AI Overviews and AI Mode — but only as impressions, with no clicks, no click-through rate, no average position, and none of the queries that triggered the answer. It tells you where you show up in AI search, not whether that visibility earns anything, so it is a presence signal you pair with other data, not a traffic report you read on its own.
We ran into that ceiling the week the report opened, while wiring Contexta — our WordPress and WooCommerce plugin — to reconcile Search Console numbers for our own users. The gen-AI report answers one question, "am I in the candidate pool AI pulls from?", and stops there. Every follow-up a store owner actually asks — which query, at what cost, worth fixing? — lives in a different dataset, and the useful move is learning to read the two together.
What does Search Console's generative AI report actually show?
It shows impressions — the number of times your URLs appeared in generative AI features — broken out by page, country, device and date, and nothing else. There are two views: a Search report covering AI Overviews and AI Mode, and a separate Discover report. Device data (desktop, mobile, tablet) exists only for the Search view.
- Impressions in AI Overviews & AI Mode
- Countries
- Devices, Search view only
- Date trends, hourly to monthly
- Clicks
- Click-through rate
- Average position
- The queries that triggered the AI answer
Two details matter for how much you can trust the numbers. The report is a separate, purpose-built view rather than a filter applied to your classic Search data, so it does not change your normal Performance totals. And within the Search view, AI Overviews and AI Mode sit together — you can't split the automatic Overview box from the opt-in conversational AI Mode surface, which matters because those two behave very differently. As of mid-2026 the report is still rolling out to a subset of sites, the United Kingdom first, pushed along by the UK Competition and Markets Authority and publisher feedback, with wider release to follow.
Why does it show impressions but no clicks?
Because inside AI Overviews and AI Mode a large share of answers resolve without a click — the user reads the synthesized response and moves on — so in many cases there is no click to count, and Google has chosen not to expose the click and query data it does hold. An impression here means your page was one of the sources the model drew on or displayed, not that a human read your headline and certainly not that anyone visited.
That gap is the zero-click pattern arriving inside your own reporting. A page can accumulate thousands of AI impressions and send you nobody, which is exactly the shift that is reshaping how a store earns from search. The trap to avoid is multiplying AI impressions by a familiar CTR-by-position curve to estimate "AI clicks" — those curves predate AI surfaces and badly overstate it. Treat the number as eligibility, not audience.
How do you use impressions-only data when you can't see clicks or queries?
Join the report to your classic Performance report by URL: the gen-AI report hands you the pages that appear in AI, and your ordinary Search Console report hands you the queries, clicks, CTR and position for those same URLs. Matching them on the address recovers the query and revenue context the AI report strips out.
The workflow is short. Export the gen-AI report's Pages list, take the URLs with the highest AI impressions, then open each one in your classic Performance report filtered to that single page and read its real query list and CTR. You now have a defensible map of which queries are likely pulling you into AI and whether those same queries still earn clicks in the blue links. It is the same import-and-segment discipline behind turning raw Search Console exports into ranked action lists — the AI report is just one more column to align by URL.
The pairing we run inside Contexta leans on its Problem Map, which imports your classic Search Console data and ranks every page by lost clicks per month. Laying the gen-AI report's high-impression URLs over that ranking surfaces the pages that are visible in AI and bleeding real clicks in ordinary search — the overlap is where a fix does double duty.
Which pages should you fix first from the report?
Fix the pages that appear in AI and still lose real clicks in ordinary search first — not the pages with the biggest AI impression counts. An AI impression with no click value behind it is a vanity metric; a page that surfaces in AI and also ranks fourth to eighth with a weak CTR is where a title or content rewrite recovers actual money.
Watch for a pattern we kept seeing when we cross-checked stores the week the report opened: the URLs with the most AI impressions were often how-to and informational pages, while the product pages that pay barely surfaced. The report flatters your content library and under-represents your catalog, so ranking fixes by AI impressions alone would send you polishing articles instead of the pages that convert. Rank by recoverable revenue per page instead, and let the AI report tell you which of those revenue pages already have an AI foothold worth defending. The threshold to keep in mind while you triage: earning a citation is worth roughly one extra click per 556 AI Overview impressions, so low-impression pages rarely repay the rewrite whatever the report shows.
Should you block AI Overviews and AI Mode to protect your clicks?
Almost never — Google does provide a way to opt content out of its AI features, but removing yourself from a growing surface does nothing to bring back the informational clicks AI is absorbing, and it forfeits the branded and agent-driven visits that citations seed later. It also overcorrects for a threat that lands unevenly: AI Overviews reach roughly a third of informational queries and almost no transactional ones, so a blanket block trades away visibility on pages that were never at risk. The more useful response to the report is to monitor the trend per page: rising AI impressions after a content change tell you the work moved your standing in the candidate pool, even when the click never shows up.
Keep the boring foundation that earns those impressions in the first place — pages a crawler can reach, read without JavaScript, and lift a self-contained answer from. The gen-AI report finally lets you watch that foundation pay off in AI visibility; it just can't, on its own, tell you what the visibility is worth.
FAQ
When did Google add AI Overviews and AI Mode data to Search Console?
Google announced the Search Console generative AI performance reports on June 3, 2026, giving site owners their first native view of impressions inside AI Overviews and AI Mode. The reports began rolling out to a subset of sites, starting in the United Kingdom under pressure from the Competition and Markets Authority and news publishers, with a wider global release to follow. As of mid-2026 not every property has the reports yet, so a missing tab means you are outside the current rollout, not that your pages never appear in AI.
Can I see clicks from AI Overviews in Search Console?
No — the generative AI report shows impressions only, with no clicks, no click-through rate, no average position and no query data. Google exposes how often your URLs appeared in AI features, broken down by page, country, device and date, but nothing about what that visibility earned. To measure real traffic from AI, count referrals from ChatGPT, Perplexity, Gemini and Copilot in your analytics instead of looking for a click figure the report doesn't contain.
Does an AI Overview impression mean someone saw my page?
Not exactly — an impression means your URL was one of the sources the AI feature drew on or displayed, not that a person read your page or clicked through to it. Because many AI answers resolve without a click, a page can log thousands of AI impressions and send you no visitors at all. Read the number as eligibility — proof you are in the pool AI pulls from — rather than as an audience you can bank on.
How do I find which queries triggered my AI impressions?
The generative AI report doesn't show queries, so recover them by joining its Pages list to your classic Performance report on the URL. Take the pages with the most AI impressions, open each one in the normal Search Console report filtered to that single page, and read the queries and CTR it already earns in ordinary search. That match gives you a defensible map of which searches are likely pulling each page into AI, since the AI report withholds the query data itself.