Search Console's AI Overviews Impressions Are Not a Traffic Forecast

Key Points

• Google's John Mueller confirmed that Search Console's generative AI performance report has structural limitations, and Google doesn't have a better approach yet.
• AI Overview impressions count when the overview renders, whether or not the user scrolled far enough to see your link.
• Links hidden behind "Show More" don't register at all until a user expands them, which understates your real presence.
• Position data reflects where the AI Overview block sat on the page, not where your link sat inside it.
• Publishers planning revenue against AI search visibility should treat these numbers as directional at best.

What Mueller Confirmed

Search Engine Journal reported on a Reddit exchange where Google's John Mueller agreed with a detailed critique of Search Console's AI search reporting. The critique argued that the generative AI performance report applies ten-blue-links logic to a surface that doesn't work that way.

Mueller's response was direct. "Position for these is hard to do in a way that makes it useful, so we're currently tracking it like we do for many search features (as a block), & it's not separated out in the Gen-AI performance report."

He went further and asked for input. "If any of you have thoughts on what would be useful in terms of tracking position, I'd love to hear & am happy to discuss with the team."

You can read the full Search Engine Journal breakdown of Mueller's comments for the full Reddit thread context.

Google announced the report in June 2026 and made it globally available on August 31, 2026. It shows impressions for URLs appearing in AI search surfaces, including AI Overviews and AI Mode.

The Four Measurement Gaps

The Reddit critique Mueller endorsed identified specific ways the report distorts what's happening. Each gap pushes your numbers in a different direction, which is what makes the aggregate so hard to reason about.

The overstating and understating cancel each other out in unknown proportions. You can't correct for the bias because you don't know its size.

Essential Background Reading:

• Google Search Console for Publishers Resource Center: A foundational overview of how Search Console reporting works for publisher sites.
• Google Search Console for Publishers: How to Use GSC to Protect Ad Revenue: Covers the core Search Console metrics publishers rely on to protect ad revenue.
• Google Search Console Analyzer Tool: A tool for reviewing your own Search Console data alongside the concepts covered here.
• AI Info: Background on how AI is reshaping ad tech and publisher measurement.

How This Distorts Revenue Planning

Publishers use search visibility data to forecast traffic, and traffic forecasts drive revenue forecasts. Corrupted inputs produce confident-looking projections built on numbers nobody can validate.

The problem compounds for publishers running session-based models. Revenue per session (RPS) assumes you know how many sessions you're getting and where they came from. AI Overview impressions that never converted to a scroll aren't sessions, and they aren't going to become sessions.

Attribution gets messier from here. A user who reads your content summarized in an AI Overview and never clicks generates an impression in your report and zero revenue in your ad stack.

Teams that treat AI Overview impressions as a leading indicator will forecast growth that never arrives. Ignoring the report entirely costs you real signal about which content AI surfaces are pulling from.

Related Content:

• AI Crawler Resource Center for Publishers: Technical options for managing AI crawler access to your site.
• AI Crawler Protection Grader: Check which AI crawlers are hitting your site and how your current setup handles them.
• Block AI: A breakdown of blocking configurations for publishers weighing that option.
• AI and Publishers Resource Center: A broader look at how AI is changing publisher strategy beyond search measurement.

What Publishers Should Do Now

Mueller's admission is useful information. Google telling you the data has known limitations beats Google letting you build a strategy on it silently.

Adjust your measurement practice accordingly:

• Segment AI surface data from your core reporting: Keep generative AI performance numbers in a separate view so they never get blended into traffic forecasts that feed revenue models.
• Never add the Gen-AI report to Web search type totals: The Gen-AI report is a filtered subset of data already counted in Web search. Summing them inflates everything downstream.
• Make clicks your primary AI search metric: Clicks land in your analytics and your ad server. Impressions in this report land nowhere you can monetize.
• Use your own server logs as a cross-check: Referral patterns from AI surfaces give you a ground truth that doesn't depend on Google's counting rules.
• Watch relative movement across URLs: Content-level patterns still tell you something useful even when the absolute values are unreliable.
• Submit feedback to Google: Mueller explicitly asked for input on position tracking. Publishers who understand the measurement problem should tell him what would help.

Focus your optimization effort on the traffic you can measure and monetize. Sessions that reach your site are the ones your ad stack can turn into revenue.

Next Steps:

• Reader Revenue Manager: The Complete Publisher's Guide: How identity and engagement data fill in the gaps that impression counts leave open.
• Google Ad Manager Training: Get your team up to speed on the platform where measurable sessions actually monetize.
• Google Ad Manager: A look at the ad serving platform tying your measurable traffic to revenue.
• Google AdSense Resources: Additional resources for publishers managing demand alongside Google's reporting tools.

The Broader Measurement Problem

Search Console isn't the only place where AI search creates a visibility gap. Publishers face a growing category of traffic that gets consumed, summarized, and never returned.

Our AI Crawler Protection Grader shows you which AI crawlers are accessing your site and how your current configuration handles them. The AI crawler resource center covers the technical options for controlling that access.

Blocking AI traffic is one choice. Optimizing for citation is another. The right answer depends on how much of your traffic comes from search, how much revenue each session generates, and what your content licensing position looks like.

Where We Come In

Measurement problems upstream make execution quality downstream more important. Every session that reaches your site has to work harder when acquisition is getting less predictable.

We run RAMP with three principles behind it: quality, performance, and transparency. Our Managed Service handles the full monetization stack for publishers who want their team focused elsewhere. Self-Service gives technical publishers direct control over floors, demand partners, and layout configuration, with visibility into what each change did.

Our reporting shows you which optimizations drove which results. No black box. You see the demand partners, the bids, and the yield math.

Google can't tell you what your AI search visibility is worth right now. We can tell you what your sessions are worth, down to the penny, and then help you make each one worth more.

Ready to see what your inventory is capable of earning? Let's look at your numbers together.