Google's New AI Visibility Report Has a Data Problem. Don't Mistake It for a Ranking Drop.
Google's newest AI-visibility report just broke. The fix is verify, don’t react.
A confirmed logging error is understating AI Overviews and AI Mode impressions in Search Console, starting August 13, 2026. It’s not a real drop in your visibility — but it’s worth checking the right way, not just glancing at a chart.
If your Generative AI performance report in Search Console just fell off a cliff, take a breath before you touch anything.
Google confirmed a logging error in that report on August 13, 2026. Impressions are showing lower than they really are, and that might cause a slight panic.
But when you look at the details (there’s always details, right?) it’s not because your content stopped getting surfaced in AI Overviews or AI Mode, but because the counting broke. As of this writing, it's still unresolved.
I already wrote the “verify before you react” post once this month — about the unconfirmed ranking volatility everyone was panicking over on August 5th and 6th.
This is the same kind of thing, but aimed at a narrower target. A single report. And this time, Google told us what happened.
- Google confirmed a logging error in Search Console’s Generative AI performance report, understating impressions for data starting August 13, 2026.
- John Mueller confirmed on Bluesky it’s “just a logging issue and not representative of visibility changes in Search.”
- The bug is scoped to the Generative AI report specifically — not standard Search rankings or traffic.
- This report was already a softer read before the bug: impressions-only, still in limited beta (launched June 2026), with “preliminary” data that can shift within hours under normal conditions.
- No resolution date has been announced. Google’s fix, for now, is a promised annotation.
Is there really a bug in Google's AI report?
Yes. Google's own Data Anomalies page in Search Console says it outright (nice of them, eh?):
“A logging error caused a decrease in impressions on the Generative AI performance report in Search for data starting on August 13, 2026. This issue affects data logging only and is ongoing.”
— Google, Search Console Help · Data Anomalies
Translate that out of Google-speak: the counting mechanism broke. Not your visibility.
There's a second, related wrinkle worth naming so you don't conflate the two.
A separate logging error is also hitting the Generative AI performance report inside Discover, starting the same day.
Two different reports, two different bugs, one shared cause window. So if you're checking your numbers, check them one at a time before you flip out.
What did Google say about it?
Not a forum rumor. Not a “sources say.” John Mueller, on Bluesky, on the record:
A practitioner flagged the exact pattern this post covers — impressions down in the Generative AI report since Aug 13–14, alongside a real citation drop — and John Mueller confirmed it directly: “This is just a logging issue and not representative of visibility changes in Search.” Full exchange: View on Bluesky →
That's about as close to a receipt as this business gets (reported by Search Engine Land). A named person at Google telling you, directly, that the number on your screen is wrong.
What it doesn't tell you: when it gets fixed. It’s mostly a recognition of the panic and a promise that Search Console will eventually flag the affected dates with an annotation, so you know to discount them.
Why was this report already a soft read to begin with?
Here's what most of the “Google's AI report broke!” posts this week won't tell you: this report was never as solid as the one you're used to.
The Generative AI performance report measures one thing — impressions. No clicks. No position. It's still in limited rollout, in Google's own words: “a subset of website owners… before rolling it further.”
And the chart itself can show “preliminary” results, marked with dotted lines, that shift within hours. That's not a bug. That's just what a brand-new report does.
Google launched this report in June 2026. It broke on August 13th.
weeks old when the counting broke
Google launched the Generative AI performance report in June 2026. It broke on August 13. You were never looking at a mature, stable number to begin with.
Do the math. That's roughly seven weeks old when the counting failed. You were never looking at a mature, stable number to begin with.
You were looking at a beta chart that just had a bad week — and now it's also broken.
What “a logging error” looks like on the chart
A stylized illustration of the pattern Google and site owners are describing — not a screenshot of real data. Pull up your own Generative AI performance report to compare against your own baseline.
This is the shape of the problem, not a claim about your specific numbers — the underlying counting broke, so the dotted segment reflects a data error, not fewer real citations.
Is my regular Search traffic affected too?
No — and this is the detail worth being precise about, because the first reports of this bug got it slightly wrong.
Search Engine Roundtable's initial coverage on August 12th described the drop hitting both standard Search performance reports and the Generative AI report — “weeks of growth, then a sudden cliff-edge drop within a couple of days.”
That's what several site owners were seeing and reporting in real time.
Once Google's own confirmation landed, the scope was narrower than that first alarm suggested: the confirmed bug is the Generative AI performance report in Search, plus that separate Discover-specific error.
Standard Search rankings and traffic aren't named as affected.
| Report / signal | Confirmed status |
|---|---|
| Generative AI performance report — Search | 🔴 Confirmed affected (Aug 13–) |
| Generative AI performance report — Discover | 🔴 Confirmed affected (separate bug, same day) |
| Standard Search performance report | 🟢 Not named as affected |
| Organic rankings / traffic | 🟢 Not named as affected |
That gap between the first alarm and the confirmed scope. It's the same pattern behind half the SEO panic cycles I write about — someone sees something break, says so accurately in the moment, and the story gets repeated a few times before anyone circles back with the precise, narrower version.
Neither report was wrong, exactly. One was just earlier than the facts.
What should you do while it's unresolved?
Three moves. All of them are boring - and that’s on purpose.
Leave your content alone. Nothing in the confirmed bug points to a real drop in AI visibility. Rewriting pages based on a broken chart fixes nothing and wastes a week.
Check your standard Search performance report on its own. It isn't confirmed affected — pull it up separately instead of reading it through the lens of the AI report's bad week.
Screenshot both, dated, right now. If this does turn out to matter later, or Google's eventual annotation doesn't cover the full window you care about, you'll want your own before-and-after.
Then wait for the annotation Google already promised, and don't make it your job to beat them to a fix they've already said is coming.
3 moves while it’s unresolved (all boring on purpose)
01
Leave your content alone
Nothing in the confirmed bug points to a real drop in AI visibility. Rewriting pages fixes nothing and wastes a week.
02
Check standard Search on its own
It isn’t confirmed affected — pull it up separately instead of reading it through the AI report’s bad week.
03
Screenshot both, dated, now
If this matters later, or the annotation doesn’t cover your full window, you’ll want your own before-and-after.
Haven't we been here before?
What do you expect from such a drastic shift in everything search has ever been known for?
I recently walked through the unconfirmed ranking volatility from August 5th and 6th: real movement across a dozen-plus rank trackers, nothing acknowledged by Google, and a four-step way to check your own data before reacting. This is the same argument, run through a cleaner example.
That story was murky — no confirmation, contested causes, real confounds stacked on top of each other.
This one is about as clean as this stuff gets: a named bug, a named date, a named person confirming it. If “verify before you react” holds up even here — on the easy case, where Google told you exactly what happened — it's worth trusting on the harder ones too.
But as always, remember: a chart dropping isn't the same thing as your visibility dropping.
That's especially true on a report that was still finding its footing before this week happened to it.
A broken chart is one thing. Knowing whether you’re really showing up is a different question.
Search Console, working or not, can only tell you what Google measured — not whether you’re actually cited in Google’s AI features, ChatGPT, or Perplexity. That’s a diagnosis question, not a chart-reading one.
Start with the free GEO Audit Checklist, or go straight to a full GEO Visibility Audit — I’ll show you where you’re cited, where you’re skipped, and what to fix first.
Get the free checklist → Book a GEO Visibility Audit →Fiverr Pro vetted · 4.9 stars · 1,600+ client reviews
Sound human. Get cited.
FAQ
Is there a bug in Google Search Console’s AI report right now?
Yes. Google has confirmed a logging error in the Generative AI performance report that understated impressions starting August 13, 2026. As of the most recent update checked, it was still unresolved.
Does this mean my AI Overviews or AI Mode visibility actually dropped?
Not necessarily. Google’s own statement, including a direct comment from John Mueller, describes this as a data-logging issue — not a real change in how often your content is being surfaced in AI features.
Is my regular Search ranking or traffic affected too?
Google’s official language scopes the confirmed bug to the Generative AI performance report, plus a separate error in the Discover version of the same report. It does not name standard Search rankings or traffic as affected.
What should I do while this is unresolved?
Don’t change anything based on this chart alone. Check your standard Search performance report separately, screenshot a dated baseline of both reports now, and wait for Google’s promised in-product annotation before drawing conclusions.
How is this different from the August ranking volatility you covered before?
That story was unconfirmed volatility across multiple independent rank trackers, with nothing acknowledged by Google. This one is the opposite case: Google has directly confirmed the cause, scope, and timeline — which makes it a faster, more straightforward one to verify.
Written by
Brad Bartlett
Brad is a copywriter and content strategist who helps creators, brands, and organizations build content that's actually worth reading — and built to be found. He specializes in conversion-focused copy, brand voice, and SEO and AI search optimization, with a straightforward philosophy: great content has to be authentic before it can perform. He works comfortably across the AI content space, helping clients use the tools without losing the voice. Fiverr Pro vetted, 4.9 stars out of 5 across 1,600+ clients.