Google Discover Performance Reporting Bug in Search Console

Why It Matters

Misleading Discover metrics can trigger unnecessary SEO adjustments and stakeholder alarm, so accurate reporting is critical for content strategy decisions.

Key Takeaways

• Bug impacted Discover clicks and impressions only on May 7‑8, 2026
• Google Search Console data logging error, not ranking algorithm, caused the dip
• Publishers should exclude the two‑day window from performance analyses
• Google has fixed the logging issue and updated the support article

Pulse Analysis

The recent Google Discover reporting bug underscores the fragility of third‑party analytics tools that many publishers rely on for traffic insights. While the underlying algorithm that surfaces content in Discover remained stable, a data‑logging flaw in Search Console temporarily erased clicks and impressions for a two‑day window. This discrepancy can mislead SEO teams into believing a content drop occurred, prompting hasty optimization moves that may not align with actual user behavior.

For marketers and site owners, the incident highlights the importance of cross‑checking data sources. Relying solely on Search Console for performance signals can be risky when anomalies arise; integrating server logs, Google Analytics, and third‑party dashboards provides a safety net. Moreover, transparent communication with stakeholders about data integrity issues preserves trust and prevents reactionary decisions based on faulty metrics.

Google’s swift acknowledgment and correction of the bug also reinforce its commitment to data accuracy, a cornerstone for the broader search ecosystem. As Discover continues to drive significant referral traffic for news and lifestyle sites, accurate reporting remains essential for budgeting, content planning, and ROI calculations. Going forward, publishers should monitor Google’s support channels for similar alerts and maintain a habit of annotating anomalous data periods in their reporting workflows.