Google Confirms Search Console Bug: Discover Performance Data Glitch on May 21
Google Admits to Data Logging Error in Discover Reports
Google has officially confirmed a technical glitch affecting the Google Search Console (GSC) Discover performance reports. The bug, which occurred on May 21, 2026, resulted in a noticeable decrease in reported clicks and impressions for many website owners and digital marketers.
According to a statement from Google, the discrepancy was caused by a “logging error,” meaning the system failed to accurately record the traffic data for that specific date. For many SEOs, seeing a sudden drop in their Discover dashboard can be alarming, often signaling a manual penalty or a loss of visibility. However, Google was quick to clarify that this was an internal reporting issue rather than a problem with how content was being served.
Reporting Error vs. Traffic Loss
The most critical takeaway for publishers is that this issue affects data logging only. This means your website’s actual visibility and performance within the Google Discover feed were not negatively impacted. Users were still seeing your content and clicking through to your site; the Search Console simply failed to track and display those interactions correctly.
In short: your traffic didn’t actually vanish—the record of it did.
A Recurring Pattern of Search Console Instability
This latest incident is not an isolated event, contributing to a growing sense of frustration within the SEO community regarding the reliability of GSC data. This specific logging bug mirrors a previous issue encountered on May 7th and 8th, where data was similarly lost. In those instances, Google indicated that the missing data is lost permanently and cannot be recovered.
The Discover bug is part of a larger series of anomalies recently reported in Search Console, including:
- Broken Link Reports: Reports that the Search Console link report has been malfunctioning.
- Massive Data Loss: Previous admissions by Google regarding the loss of up to 50 weeks of historical data for some users.
How to Handle Data Anomalies in Your SEO Analysis
When dealing with these types of glitches, it is recommended that publishers correlate their Search Console data with third-party analytics tools (such as Google Analytics 4). If your internal analytics show steady traffic while GSC shows a crash, it is a strong indicator of a reporting bug rather than an algorithmic hit.
As Google continues to refine its AI-driven discovery and reporting tools, these “logging errors” serve as a reminder to diversify traffic sources and maintain a critical eye when analyzing single-day performance spikes or drops.