On June 3, 2026, Google launched dedicated Search Generative AI performance reports inside Search Console. For the first time, you can see how often your URLs appear in AI Overviews, AI Mode, and generative AI features in Discover. As of June 23, John Mueller confirmed the rollout is expanding incrementally to more sites while Google reviews feedback.
The report sits alongside your existing Performance view. It doesn't replace anything. But what it shows (and what it doesn't) creates a real measurement problem for demand gen teams trying to connect AI visibility to pipeline.
What You Get: Impressions and Four Dimensions
The AI performance reports track impressions broken down by page (canonical URL), country, device, and date. That's it. No clicks. No CTR. No average position. No query data.
Read that again: no query data. You can't see which searches triggered your AI appearances. You can see that your pricing page showed up in AI Overviews in the UK on mobile last Tuesday, but you won't know whether the query was "[your product] pricing" or "best project management tools for mid-market." Two very different intent signals, zero differentiation in the report.
Data collection started May 18, 2026, with no historical backfill. If you haven't looked at the report yet, your baseline window is already ticking.
Why This Matters for B2B SaaS (and Where It Falls Short)
The value here is separation. Before this report, AI Overview appearances were lumped into your standard Search performance data. Now you can isolate AI visibility from traditional organic visibility. That's useful for diagnosing whether your content is being surfaced in AI features or just in blue links.
The limitation is equally clear. Impressions without clicks can't prove pipeline impact. An impression in an AI Overview where Google synthesizes your content and the user never visits your site is a brand exposure event, not a demand gen event. Treating rising AI impressions as a leading indicator of traffic or conversions would be a measurement mistake.
There's also scope to consider. These reports cover Google's AI surfaces only. Not the Gemini app. Not ChatGPT, Perplexity, Claude, or Copilot. So calling this an "AI visibility" measurement system overstates the coverage. It's one channel's partial view.
The Operational Workaround
Since the report has gaps, you need to pair it with other signals. Here's a practical framework:
- Search Console AI impressions — baseline by page type. Segment pricing pages, use case pages, implementation guides, and case studies separately. These content types tend to hold strong positions in AI features; generic comparison posts and thin "alternatives" content generally don't.
- GA4 traffic and conversion trends — overlay against the same page segments. If AI impressions rise but organic traffic to those pages drops, you might be getting cited without getting clicked. That's a signal worth understanding, not celebrating.
- External SERP feature monitoring — tools like Semrush or Ahrefs can track which queries trigger AI Overviews and whether your domain appears. This fills the query-data gap that Search Console leaves open.
The hypothesis (make it falsifiable): if we increase original data and implementation-focused content on pages already appearing in AI reports, then AI impressions will grow alongside organic traffic to those pages, because Google's AI features favor specificity and original sourcing over commodity content. Measure over 60 days. If impressions rise but traffic doesn't follow, the trade-off is brand exposure at the cost of referral traffic.
The Opt-Out Decision
Google also introduced a Search Console control letting publishers opt out of AI Overviews and AI Mode while staying indexed in standard results. It launched UK-first, mandated by the UK Competition and Markets Authority.
For most B2B SaaS companies, opting out is the wrong call. AI Overviews frequently appear on comparison and how-to queries where vendor content supports pipeline. Removing yourself from those surfaces trades brand exposure for a referral-protection benefit that's hard to quantify, especially when you can't measure AI-driven clicks in the first place.
When opting out might make sense: if you're a content publisher whose revenue depends on pageviews and you can demonstrate AI features are cannibalizing traffic. That's a different business model with different unit economics.
What to Do This Week
Check whether your Search Console properties have the AI performance report. Access is phased, so not every site has it yet. If you do have access, export impression data by page and establish your baseline from May 18 forward. Build a simple internal dashboard segmenting by page type and country. If you don't have access, set a calendar reminder to check weekly until rollout reaches your properties.
The broader point: SEO fundamentals still drive AI visibility. Google's own position is that optimizing for generative AI means optimizing for search. Pricing pages, use case pages, implementation guides, case studies, and original research are the content types that tend to surface. The new report doesn't change what to build. It changes what you can see after you've built it.
And right now, what you can see is half the picture with the click data blacked out. Useful? Yes. Sufficient? Not close. Build the baseline anyway, because when Google adds clicks and queries to these reports (and the pressure to do so will only grow), the teams that started measuring in May will have months of context the latecomers won't.
