GSC: Investigating the Generative AI Performance Data Bug

Impressions on your Generative AI performance report suddenly cratered on August 13. We dug into what Google confirmed, what it actually means, and what you should do about it.

By Snehal Singh | Published: August 20, 2026

AI Overview Summary

Google Search Console’s Generative AI performance report started showing a sharp, unexplained drop in impressions on August 13, 2026. After investigating, Google confirmed this was caused by a data logging error, not a real change in how often your pages appear inside Google’s AI Overviews and AI Mode. John Mueller confirmed the same on Bluesky, adding that Search Console will soon carry an annotation flagging the anomaly. The investigation matters less for the bug itself and more for what it reveals: a single alarming number inside a trusted dashboard can trigger unnecessary content rewrites and incorrect client reporting if nobody stops to verify it first. Cross-check this report against your regular Search performance data before treating any dip as real.

Table of Contents

• What Triggered the Investigation
• What Is the Generative AI Performance Report, Anyway?
• What We Found: Google and John Mueller’s Confirmations
• Why an Investigation Was Even Necessary
• Real Decay vs. This Reporting Bug
• What to Do While the Issue Is Under Investigation
• Mistakes That Look Like Strategy
• How Ad2Connect Approaches Search Console Monitoring for Clients
• Key Takeaways

What Triggered the Investigation

The trigger was simple: a lot of Search Console users noticed the same thing at once. Their Generative AI performance report showed impressions falling off a cliff, all starting on the exact same date, August 13, 2026.

That kind of pattern is exactly what makes something worth investigating. A gradual decline over weeks usually points to a real ranking or visibility problem. A sudden, identical drop across many different websites on the same day points somewhere else entirely, usually to Google’s own systems rather than anyone’s SEO.

That’s precisely what turned out to be the case here.

What Is the Generative AI Performance Report, Anyway?

Before getting into what went wrong, it helps to understand what this report actually does. It’s a specific section inside Google Search Console’s performance reports, separate from the regular blue-link data most SEOs check every day.

This report shows how your website performs specifically within Google’s AI Overviews and AI Mode results, the AI-generated summaries that now sit above traditional search listings for many queries. It’s a relatively new addition to Search Console, built for a search landscape that increasingly runs on AI-generated answers rather than a plain list of links.

Because it’s still new, a bug here is far easier to mistake for a genuine performance problem, especially for anyone who isn’t also checking their regular Search performance report side by side.

What We Found: Google and John Mueller’s Confirmations

Google addressed the issue directly on its official data anomalies page, confirming that a logging error caused the drop in impressions on the Generative AI performance report for data starting August 13, 2026, and noted the issue is ongoing.

Google’s John Mueller also responded on Bluesky, confirming the team is aware of the issue and working on a fix, and clarified that this only affects the report’s logging, not actual visibility changes in Search. He added that Search Console would soon include an annotation to flag this for anyone looking at the report.

Between the two confirmations, the investigation reaches a clear conclusion: this is a reporting problem inside Google’s own systems, not a signal about your website’s actual AI search performance.

Why an Investigation Was Even Necessary

Here’s the part worth sitting with for a moment. A logging bug on its own is a minor technical hiccup that Google will eventually fix, and on paper, nothing about your website actually changed. But the reason this was worth digging into at all is what business owners do in response to a chart that suddenly looks alarming, especially one living inside a tool most people already trust completely for tracking their SEO performance. Someone glancing at a sharp drop in impressions might reasonably assume their content stopped performing, panic-rewrite a page that was never actually broken, or worse, hand a client an incorrect explanation for a traffic change that never really happened. That’s the real cost of a reporting bug like this one: not the missing data itself, but the wrong decisions it can quietly trigger if nobody stops to verify the number against a second source first.

In short, investigating this bug is really a reminder that dashboards can lie, even Google’s own dashboards, and any single metric deserves a second look before it changes your strategy.

Real Decay vs. This Reporting Bug

It helps to know how to tell a genuine visibility problem apart from this specific bug. The table below breaks down the difference.

What to Do While the Issue Is Under Investigation

• Check your regular Search performance report alongside the Generative AI report. If only the AI report shows a drop, this bug is very likely the cause.
• Avoid making content changes based on this specific data until Google resolves the issue.
• Keep an eye out for the annotation Google said it would add to the report, confirming the anomaly.
• If you’re reporting on this data for a client or stakeholder, flag the known bug rather than presenting the dip as a real change.
• Revisit the report after Google confirms a fix, and compare it against the same period the following month for a clean read.

Mistakes That Look Like Strategy

• Rewriting or “refreshing” content because of a drop that was never real to begin with.
• Reporting a scary chart to a client or manager without checking Google’s official confirmation first.
• Treating every dashboard number as equally reliable, without cross-checking a second data source.
• Ignoring the regular Search performance report while overreacting to one newer, less battle-tested report.
• Assuming every visibility dip has a strategic explanation instead of first ruling out a technical or reporting issue.

How Ad2Connect Approaches Search Console Monitoring for Clients

At Ad2Connect, one of the Top SEO Company and Agency in Mumbai, India, we treat every Search Console alert as a starting point for investigation, not an automatic call to action. Before we ever recommend a content change, our team cross-checks the Generative AI performance report against regular Search performance data, so a logging bug like this one never gets mistaken for a real traffic drop.

This kind of careful monitoring is part of the broader professional SEO services we run for clients across SaaS, eCommerce, D2C, and local businesses, and it pairs closely with our performance marketing work, so budget and strategy decisions are never based on a single, unverified number.

As a boutique digital marketing agency in Malad, Mumbai, we know how easy it is for a small business owner without a dedicated analytics team to misread a dashboard and make an unnecessary change. If you’ve ever second-guessed a metric that didn’t add up, that’s exactly the kind of clarity our SEO and analytics team brings to client reporting.

Key Takeaways

• The investigation confirms this is a Google logging bug, not a real drop in your AI search visibility.
• The issue started on August 13, 2026, and only affects impressions inside the Generative AI performance report.
• Cross-check any alarming metric against your regular Search performance report before reacting to it.
• Don’t rewrite content based on this data until Google confirms the issue is resolved.
• Google plans to add an annotation to the report to flag this anomaly for everyone affected.

Ad2Connect is a digital marketing agency helping SaaS, eCommerce, D2C, and local businesses grow through data-driven SEO, performance marketing, and content strategy. If a Search Console metric ever looks off and you’re not sure whether it’s real, talk to our SEO team before making any changes to your site.