Google Confirms Search Console AI Impressions Drop Is a Logging Issue

Google has confirmed that the sharp fall in Search Console Generative AI impressions in mid-August was a reporting fault rather than a real decline, and has since closed the incident at five days. The entry on its Data anomalies page now reads:

“A logging error caused a decrease in impressions on the Generative AI performance report in Search for data from August 13 - August 17, 2026. This issue affects data logging only.”

It first appeared with the run left open: “for data starting on August 13, 2026”, ending “and is ongoing”. A closed date range has replaced that, which is how every other entry on the page is worded once the fault is over, so impressions from 18 August onwards should be logged normally. There was no separate announcement. The change of wording is the only notice Google has given that the issue is fixed.

John Mueller gave the same account on 17 August while the run was still open, posting identical replies on LinkedIn and Bluesky to two site owners who had raised the pattern separately. Both, after the greeting, read:

“we’re aware of this issue and working on resolving it. This is just a logging issue and not representative of visibility changes in Search. We’re adding an annotation in Search Console to let folks know about this in the near future.”

Which dates are affected

Five days, 13 to 17 August inclusive. Google’s original entry gave only the first affected day, not the last good one: 12 August data is intact and the fall begins with 13 August. The closed range now supplies the other end. The early reports were describing the same boundary from the other side, which is why several of them refer to a drop “around August 12”. A thread on the Google Search Central Help forum is titled “Seeing a large (>50%) decrease in impressions from Generative AI Features”, and Pandita described “almost every client project” showing the same shape: weeks of growth, then a cliff-edge drop within a couple of days.

A second entry covers Discover

The anomalies page now lists two separate 13 August errors, and they are not the same fault. The Generative AI in Search entry is impressions only and now runs from 13 to 17 August. Directly above it sits an entry headed “Discover and Generative AI in Discover”:

“A logging error caused a decrease in clicks and impressions on the Discover performance report for data on August 13, 2026. For properties with access to Generative AI features in Discover, this error also caused a decrease in reported impressions. This issue affects data logging only.”

That one is a single day rather than a five-day run, and it covers clicks as well as impressions, so Discover reporting should be sound again from 14 August. Google has logged the same Discover pattern twice before this year, on 21 May and 24 June, both single days worded almost identically.

What the statements do not cover

Between them the two entries account for Generative AI in Search, Discover, and Generative AI in Discover. None of them covers the standard Search performance report. Glenn Gabe separately wrote on X that he was hearing from site owners about a drop in clicks from around 12 August, with third-party visibility tracking stable and analytics flat. The Discover entry now explains a one-day clicks dip for anyone whose traffic leans on Discover, but the Generative AI report in Search carries no clicks at all, so a Search clicks drop, or one running past 13 August, is still unaccounted for.

What the annotation does

The annotation Mueller mentions is now live. Search Console marks Thursday 13 August with a “Google Search Update” note reading “An event has occurred in Google Search that might affect your site’s data”, linking through to the Data anomalies page. It is a marker rather than a repair. Google defines system annotations as “automatically generated by Search Console to show issues with data processing and reporting”: they add context to a chart without changing the numbers under it. With the logging fixed, that distinction matters for the one question still open, which is whether the affected days are ever corrected. Google’s own log of past incidents is the best guide, and none of its 2026 entries says lost data was restored. The 50-week impression logging error was resolved going forward, and the visible result was a drop as reporting became accurate again. Two days missing from the Bulk data exports in February and March carry the flat note “This data won’t be recovered.”

What the logging gap means for your reporting

Do not read Generative AI impressions for 13 to 17 August as lost citations, and pause any week-on-week reporting that spans those dates. From 18 August the report should be counting properly again, so compare like for like by cutting the five days out of a range rather than writing off the month. Assume the gap itself is permanent, because on Google’s record that is the way to bet, and export or screenshot the period now if you need a version of it that survives. If you report on Discover, treat 13 August as one bad day for clicks and impressions and read the days either side normally.

Sources

• Data anomalies in Search Console (13 August, Discover and Generative AI in Discover), Search Console Help
• Data anomalies in Search Console (13 to 17 August, Generative AI in Search), Search Console Help
• Search Console annotations, Search Console Help
• John Mueller’s reply, Bluesky
• John Mueller’s reply on Meenka Pandita’s post, LinkedIn
• Seeing a large (>50%) decrease in impressions from Generative AI Features, Google Search Central Community
• Google Performance Reports Drop In Impressions/Clicks ~August 12, Search Engine Roundtable