What does the Search Console AI performance report actually show?
The Search Console generative AI performance report shows how often links to your site appeared inside AI Overviews and AI Mode, and it counts impressions only. There are no clicks, no click-through rate and no query data. Google launched it for a subset of sites on June 3, 2026 and rolled it out to all websites worldwide on August 31, 2026. It is first-party data from Google, which makes it the only non-modeled measurement of generative search exposure most enterprises have ever had. Google's documentation does not describe a backfill before launch, so the historical series is short.
In practical terms you get one metric and four ways to group it. Google defines an impression as each time a link to your site was shown to a user in a generative AI feature on Google Search. You can group impressions by page (the final linked URL, mostly assigned to the canonical), country, date and device. The usual 1,000-row table limit from the Performance report applies, and the export turns values shown as unavailable into zeros. What you do not get is a split by feature. AI Mode and AI Overviews sit in one report rather than two channels you can trend against each other, and generative AI features in Discover have a separate report. Treat the numbers as directional volume rather than as a ledger you can reconcile line by line.
The most useful thing about the report is not any single metric. It is that AI exposure now lives inside the same tool your executive dashboards already pull from, which removes the credibility argument that has stalled AEO budget conversations for two years. When a VP of Marketing asks whether AI search matters to the business, a Google-owned number carries weight that a third-party estimate does not.
How should you read AI impressions against classic Search impressions?
Read AI impressions as a view inside your Search impressions, not as extra volume on top of them. Google says the generative AI report draws on data from the Web search type in the main Performance report, so adding the two totals together double counts. The behavior behind each number still differs. An AI impression means a link to your page was shown inside a generated answer, while a classic impression means your listing was present on a results page the user could scan. Report them as separate lines even though one sits inside the other.
The practical read is a ratio. Divide AI impressions by total Web search impressions for a given page group and track that share month over month. Most enterprise sites find AI share concentrated in a narrow set of explanatory and comparison pages rather than spread evenly. That concentration is the actionable finding, not the absolute count.
Also watch for divergence. When total Web search impressions are flat but AI impressions rise sharply for the same page cluster, Google is reusing that content in answers without giving it more room in the classic results. That pattern usually means the content is well structured for extraction and poorly positioned for ranking, which is a very different fix from the reverse case. Log the direction of each cluster every month so the pattern is visible before it becomes a traffic problem.
Why doesn't the report show AI clicks?
The report shows no AI clicks because Google has not added a click metric to it. Google's June 3 launch post lists impressions, pages, countries, devices and dates, and says Google is still working with site owners on which data would help, including more metrics over time. Clicks from AI Overviews and AI Mode are still counted, but Google reports them inside the Web search type of the main Performance report, blended with classic results. Any AI click-through rate attributed to Search Console today is an estimate built from other data, not a Google number.
For forecasting, this means impression growth on AI surfaces should not be modeled as traffic growth. Build two forecasts instead: a session forecast driven by Performance report clicks and GA4 sessions, and an exposure forecast driven by AI impressions that feeds brand and assisted-pipeline assumptions rather than sessions. If you fold AI impressions into a session model, you will overstate next quarter's traffic and lose credibility when the number misses. Keep the two lines separate in every board deck.
The visits that do arrive still matter, and you measure them in Google Analytics rather than Search Console. Clicks from AI surfaces tend to come from users who have already absorbed a summary and want depth, which is why many teams see stronger engagement per session even as raw volume falls. Pair that with pipeline data so a smaller session count is understood in context. A falling click count alongside rising qualified demand is not a failure.
What the Search Console AI performance report cannot tell you
The Search Console AI performance report covers Google surfaces only, so it contains no data from ChatGPT, Perplexity, Claude, or Copilot. That single limitation matters more than any other, because a Previsible referral-traffic study reported by Search Engine Land in July 2026 found ChatGPT accounts for roughly 92.4 percent of standalone AI referral traffic. If you plan from Search Console alone, you are planning around the smaller share of the visible AI referral market. Google reporting is necessary and nowhere near sufficient.
Inside Google, the report has no query dimension, so there is no query-level AI attribution. You cannot see which search produced a given AI impression, the citation text that accompanied your link, or where in the answer your reference appeared. Position inside a generated answer is not exposed, and neither are clicks or click-through rate, so there is no AI equivalent of average position or CTR that you can trend with confidence. Any vendor claiming to read those from Search Console is inferring rather than measuring.
Finally, the report says nothing about competitive context. It shows your exposure and never shows whose content was cited alongside yours or instead of yours. The Semrush AI Visibility Index, which analyzed roughly 126 million US AI search prompts from January to April 2026, found only 36 brands ranking in the top 100 across ChatGPT, Gemini, Google AI Mode, and Google AI Overviews. The absence of a competitive view is the gap third-party monitoring exists to fill.
How do you build a monthly reporting cadence off the new data?
Build a fixed monthly cadence with four steps and resist the urge to check daily, because AI surface data is noisy at short intervals. First, export AI impressions and total Web search impressions by page group. Second, calculate AI share of impressions for each group, and pull AI Assistant and Organic Search sessions and key events for the same pages from GA4. Third, flag every group whose AI share moved more than five points. Fourth, write two sentences of interpretation per flagged group before anyone opens a slide. The written interpretation is what turns an export into a decision.
Set the page group taxonomy once and keep it stable for at least two quarters. Group by buyer intent rather than by site section: category explainers, comparison and alternatives pages, pricing and packaging, documentation, and customer proof. A stable taxonomy is what makes month-three comparisons meaningful, and re-cutting the groups every month is the most common reason these reports never produce a decision. Most programs need eight to twelve groups, not fifty.
Give the cadence one owner and one standing slot. A reasonable planning range is four to six weeks before the report produces its first defensible trend, and a full quarter before it should influence roadmap decisions. Until then, treat the numbers as baseline collection and say so plainly. Teams that promise executives insight in week two usually end up defending noise, and that framing buys the patience the data needs. If no one on the team has the seniority to own that interpretation in front of leadership, a fractional CMO can hold the slot until the role is filled.
What does the Search generative AI control actually do?
The Search generative AI control is a Search Console setting that decides whether your site can appear in Google's generative AI features. Google rolled it out to all websites worldwide on August 31, 2026, after first releasing it to a subset of UK site owners alongside the report on June 3. You find it under Settings, then Search generative AI, and it has three values: include, which is the default, exclude, or inherit from a parent property.
Choosing exclude does two things across AI Overviews, AI Mode and generative AI features in Discover. Links to your site stop appearing, and content crawled from your site is no longer eligible to ground an AI response or preview. Google says you will receive no traffic or impressions from those features, and that content from other sites will still appear in them and may look similar to yours.
Four boundaries are worth knowing before anyone touches it. Google states the control is not used as a ranking or inclusion signal for other parts of Search. It does not affect AI training, which is still managed through Google-Extended. It does not remove you from Search, which still requires noindex. And it is not instant: Google says content is excluded within 1 to 2 days after the change goes live, though some content can take longer because of caching and propagation across its systems. Properties also inherit the setting from their closest configured parent, so a change on a domain property flows down to every subdomain and URL-prefix property beneath it unless one has been set separately.
Should enterprises use the opt-out control for AI responses?
For nearly all B2B vendors the answer is no, because excluding your site removes you from the AI answer without removing the answer. Google says content from other sites still appears after you opt out, and at I/O 2026 it reported more than 2.5 billion monthly users for AI Overviews and more than 1 billion for AI Mode, so buyers researching your category keep getting answers that now cite a competitor. The switch also does not stop Google using your content for model training, which is governed by Google-Extended, so opting out gives up visibility without buying the protection most teams assume it does.
There are narrow cases where restriction is defensible. Regulated claims, legal language, pricing that is contractually confidential, and unreleased product detail are all reasonable to withhold from generated summaries. The better move there is to restrict a specific section by setting the control on a child URL-prefix property, such as a single directory, tied to a documented policy, not a site-wide switch flipped in response to a traffic dip. Route the decision through legal and record the rationale, because the reasoning will be questioned in six months.
Before touching the control, model the downside honestly. Ask what share of your non-branded discovery already happens on AI surfaces, what your citation rate looks like across your top twenty commercial queries, and what a competitor gains if your content disappears from those answers. If you cannot answer those three questions with data, you are not ready to opt out of anything. Google documents how long exclusion takes but not how quickly citations return after you switch back, so treat the change as hard to reverse.
How do you connect AI impressions to pipeline?
Because Search Console stops at impressions, the path from AI exposure to pipeline runs through GA4 and your CRM. On May 13, 2026, Google Analytics added an AI Assistant channel to the default channel group. When a session's referrer matches Google's list of recognized AI assistants, GA4 sets the medium to ai-assistant and files the visit under AI Assistant. Google's channel definitions give ChatGPT, Gemini, Deepseek, Copilot and Grok as example sources, and its launch note names Claude.
Read the channel with two gaps in mind. First, clicks from AI Overviews and AI Mode are not in it. Google places them in Organic Search, so Search Console AI impressions and GA4 AI Assistant sessions describe different surfaces and should never be divided into each other. Second, Google has not published its full list of recognized assistants, and visits that arrive with no referrer, common from mobile apps and copied links, still land in Direct. If Perplexity or another assistant matters to your buyers, check where its sessions land in your Traffic acquisition report and keep a custom channel group as a backstop, as set out in our GA4 AI referral traffic setup guide.
Google Analytics added custom dashboards on September 9, 2026, which puts these numbers on one screen without Looker Studio. Editors and administrators create one under Reports, then Create, then Dashboard, drag cards onto a grid, and publish it to the left navigation, where anyone with access to the property can view it. A simple AI pipeline dashboard needs four cards:
- A scorecard for sessions in the AI Assistant channel.
- A scorecard for sessions in the Organic Search channel, which is where AI Overviews and AI Mode clicks land.
- A scorecard for your demo request or meeting booking key event.
- A table with Session default channel group as the dimension and sessions and key events as the metrics, so AI Assistant, Organic Search and Direct sit side by side.
Apply a date comparison so the scorecards show percentage change. Google's help page does not document card-level filters, segments are not supported, and standard properties are capped at 15 cards per dashboard, so if a scorecard cannot be limited to one channel, rely on the table and keep page-group analysis in Explorations. Then close the loop in the CRM by passing the session channel into a hidden form field and carrying it through to the opportunity, the method covered in AI search attribution. It is the same pipeline attribution discipline behind our IQLECT case study, where organic search and technical content built $6.4M in pipeline.
How does the Three-Layer AI Reporting Stack fit together?
The Three-Layer AI Reporting Stack organizes AI measurement into a first-party layer, an engine-monitoring layer, and a pipeline layer, each answering a question the others cannot. Layer one is Search Console: authoritative, Google-only, AI impressions without clicks or queries. Layer two is engine monitoring across ChatGPT, Gemini, Perplexity, and Claude, covering prompt-level citation presence, competitive share, and how your brand is described. Layer three is pipeline: GA4 AI Assistant and Organic Search sessions, self-reported attribution, assisted-conversion paths, and revenue tied to AI-influenced sessions.
The layers are read in order and never averaged. Layer one tells you whether Google is using your content. Layer two tells you whether the rest of the market is, and whether you are losing shortlist positions to a competitor. Layer three tells you whether any of it produced revenue. A program that reports only layer one will look healthy while losing the queries that actually convert, and a program that reports only layer three will never diagnose why. For the metrics that belong in each layer, see AEO metrics that matter, and for presenting them to leadership, see AI search board reporting.
Most enterprise teams now have layer one by default, and almost none have layer three connected. Lemniscate Growth builds the stack in that order through its AEO, GEO and SEO programs for clients across the US, Canada, and Dubai, and its GrowthGPT platform includes free AI Citation Checkers that cover the layer-two gap while a permanent monitoring process is stood up. The sequencing matters more than the tooling: exposure first, then competitive position, then pipeline.
