Some Discover charts looked worse than reality this week.
Google has confirmed that a Search Console reporting issue caused clicks and impressions to appear lower than expected for Google Discover between May 7 and May 8, 2026.
The Dip Came From Logging, Not Discover Visibility
The issue affected the Discover performance report inside Google Search Console. According to Google’s Search Console data anomalies page, a logging error caused a decrease in reported clicks and impressions for the Discover report during the two-day window.
Google described the issue as data logging only.
That distinction matters. A reporting bug can make a publisher’s chart look like audience demand suddenly fell, even when the underlying Discover placement and user exposure did not change in the same way.
Publishers Saw the Wrong Signal at the Wrong Time
Discover traffic can already be volatile. A story may surge for a few hours, fade quickly, or reappear depending on user interest, topic freshness, and Google’s recommendation systems.
That volatility makes a reporting anomaly harder to read.
For publishers, media brands, and content teams that track Discover daily, the May 7–8 numbers should be treated as incomplete. The affected period may show lower clicks and impressions than actual performance.
Search Console Has Had a Busy Year for Data Notes
The Discover issue sits inside Google’s broader Search Console data anomalies record, where the company lists known reporting problems that can affect charts.
Google’s page also includes other 2026 reporting notes, including issues affecting job-related Search appearance types and a separate impressions reporting problem that ran from May 2025 to April 2026.
None of those notes should be interpreted as ranking updates on their own. They are reporting caveats, and they change how historical data should be read.
Don’t Rewrite the Discover Strategy Over Two Bad Dates
A two-day dip in Search Console Discover data can still create internal noise. Editors may question story selection. SEO teams may look for technical issues. Executives may assume Google Discover reach has weakened.
For May 7 and May 8, that reaction would be premature.
The cleaner approach is to annotate the reporting period, exclude those dates from short-term Discover comparisons where possible, and avoid using the affected data as evidence of a content, ranking, or distribution problem.
What Marketers and SEOs Should Do With the Data
For marketers and SEOs, the practical step is reporting hygiene. Dashboards, weekly reports, and month-over-month Discover comparisons should flag May 7–8, 2026 as affected by a Search Console logging issue. Teams relying on Discover for publisher traffic analysis should avoid drawing performance conclusions from those two days unless they can validate the trend against other analytics sources.
The Chart May Stay Broken Even After the Explanation
Google’s anomaly note gives teams the context they need, but it does not turn the affected numbers into clean performance data.
The safest reading is narrow: Search Console’s Discover clicks and impressions for May 7 and May 8 are unreliable. Any real Discover analysis should start outside that two-day gap.
