Anyone who watched impressions and clicks fall off a cliff in Search Console starting around August 12 or 13 is looking at a logging failure, not an actual loss of visibility. Google has confirmed the sudden decline, most visible inside the Generative AI performance report, comes from a bug in how the data gets recorded rather than any real change in how sites appear in Search. The timing makes the confusion worse.

This publication reported on August 12 that Google had rolled the Generative AI performance report out to every Search Console property. The same report readers were just told to start watching is now the one carrying corrupted numbers. Any baseline a team tried to build from that report’s first week has to be thrown out, since the underlying counts were broken almost from day one.

Several site owners flagged the pattern independently before Google acknowledged it. Glenn Gabe posted on X that site owners had told him about a strange drop in clicks beginning near August 12, and noted that visibility reporting stayed stable while third-party analytics showed no matching fall. On Bluesky, a user named Juan reported impressions sliding in the Generative AI report since August 13 or 14 and asked whether Google had changed something in AI Overviews without disclosing it. On LinkedIn, Meenka Pandita described nearly every client account she manages showing weeks of steady growth followed by a sudden, cliff-edge decline within a couple of days, a pattern too consistent across unrelated properties to be a coincidence. A thread on Google’s Webmaster Forums raised the identical complaint: a sharp two-day drop in the Generative AI Features report starting August 13. A participant identified as Dave Smart replied that he was noticing the same thing on several unrelated accounts, and guessed the cause was incomplete logging on certain dates rather than anything wrong with one specific site.

Google’s own response settled the question. John Mueller replied to Juan on Bluesky, writing that the team is aware of the issue and working on a fix. Mueller described it as strictly a logging issue, not a reflection of real visibility changes in Search, and said Search Console would get an annotation flagging the affected dates.

Google also logged the incident on its Data Anomalies page, the company’s own public record of measurement problems. The entry, dated August 13 under “Generative AI in Search,” attributes the impression drop in the Generative AI performance report to a logging error affecting data collection from that date forward. The page states the fault is limited to data logging. It lists the issue as ongoing, not resolved.

That last point matters most for anyone touching a report this week. Search teams should annotate the affected date range in their own dashboards before anyone presents these numbers as a real trend, and should hold off on any traffic-recovery or content decision tied to the dip until Google confirms the logging problem is actually fixed.

Search Engine Roundtable, reported by Barry Schwartz on August 17, 2026.