Google today confirmed a data logging error in Search Console that caused clicks and impressions to disappear from the Discover performance report for May 21, 2026 - the third such incident affecting the same surface in under three weeks.

The problem is documented on Google's Data Anomalies in Search Console page, which serves as the company's official record of known reporting irregularities going back 3 to 16 months. According to Google, "A logging error caused a decrease in clicks and impressions on the Discover performance report for data on May 21, 2026." The company added that "this issue affects data logging only" - a phrase it has used consistently to clarify that the underlying traffic was not affected, only the system that records it.

For publishers relying on Search Console to measure Discover performance, the practical consequence is a gap in the data for that specific day. No correction or backfill is indicated.

What the anomaly page says

The May 21 entry is brief and contains no additional technical detail beyond what Google has disclosed publicly. The phrasing mirrors language used for a prior Discover logging error on May 7 and 8, 2026, when a separate incident caused a similarly described decrease in clicks and impressions over a two-day window. That earlier data is also described as permanently lost.

Both incidents are logged under the Performance reports section of the anomalies page, specifically under the Discover subsection, which sits alongside Search results and Google News within the broader performance reporting framework.

The distinction Google draws between "data logging" problems and actual traffic changes is significant. When a logging error is classified as affecting data logging only, it means the pages appeared in users' Discover feeds and were clicked on as normal. The failure occurred at the layer that records those events inside Search Console's reporting infrastructure - not at the serving layer that delivers content to users' devices.

A third incident in less than three weeks

What makes the May 21 event notable is the frequency of Discover-specific logging failures in May 2026. Google's anomalies page documents three separate entries for Discover within a 21-day span.

The first, covering May 7 and May 8, involved a logging error causing decreased clicks and impressions across two consecutive days. The second, confirmed today for May 21, follows the same pattern. Between those two events, a separate product-wide change took effect on May 7 when FAQ rich results were removed from Google Search entirely, producing a structural drop in FAQ impressions within the performance report that is distinct from a logging error.

Three anomalies in three weeks is unusual. Google's anomalies page is maintained as a rolling reference, but the concentration of Discover-specific entries in this period is higher than typical. Looking at the rest of 2026 entries, the next most recent Discover-specific logging entry before May was not present - earlier 2026 entries cover Job listing search appearances in April and a long-running impressions error that affected search results data from May 2025 until April 2026.

That earlier bug - a logging error that caused Search Console to inaccurately report impressions from May 13, 2025 until April 27, 2026 - is a separate and larger event. That error ran for nearly a year and inflated impression counts across the Performance report without affecting clicks. Google formally acknowledged it on April 3, 2026 and warned that impression counts would decrease as a fix rolled out. Clicks were not affected in that case either.

Why Discover data reliability matters now

Discover has become the dominant traffic source for news and media publishers. Research published in August 2025 analyzing 2,000 global news and media websites found that Discover accounted for two-thirds of all Google referrals to those properties - a proportion that has grown steadily as traditional search traffic declined. Traditional Google Search traffic dropped from approximately 16% to 10% of total referrals between 2023 and 2025, based on Chartbeat data.

When the reporting tool for a traffic source of that magnitude loses data, publishers lose the ability to make accurate comparisons against prior periods. A publisher reviewing May 2026 performance will see an artificial dip on May 21 that reflects nothing real about audience behavior. The same applies to May 7 and May 8. Three gaps within a single month compound each other when teams are trying to measure the impact of content decisions, publishing frequency, or algorithmic changes on Discover performance.

The stakes are especially high in 2026 because the Discover feed itself has been the subject of multiple algorithmic adjustments this year. Google released a February 2026 Discover core update targeting clickbait while prioritizing locally relevant and expert content. Any publisher trying to track whether their traffic recovered or shifted after that update will now contend with data gaps in the very metric they are monitoring.

Search Console is the primary - and in many cases only - tool publishers have for viewing Discover performance data. Unlike Google Analytics, which can capture referral traffic from Discover when pages are clicked through to a website, Search Console is where impression data for Discover lives. Impressions record how many times content appeared in a user's feed regardless of whether a click followed. That data does not exist outside of Search Console's reporting infrastructure, which means when logging fails, the record is gone.

The pattern of Search Console reliability issues

This is not the first time Search Console has experienced data accuracy problems affecting Discover or other performance surfaces. PPC Land has documented a series of reliability events in Search Console over the past two years.

In October 2024, Search Console showed near-zero traffic data for October 28, 2024 - a display bug that resolved by 1:00 PM Eastern Time that day. In October 2025, performance data froze across all Search Console profiles starting October 19, affecting reporting continuity for web operators globally. The April 2026 impressions correction added another data discontinuity at a structural level, requiring teams to treat May 13, 2025 as an annotation point in their historical trend lines.

The May 2026 Discover entries are smaller in absolute scope - each involves a single day or two-day window rather than months-long distortions. But the frequency of incidents specific to Discover within this compressed timeframe is a pattern worth noting.

There is also an open question about the Search Console link report, which according to reporting published by Search Engine Roundtable is currently non-functional - a separate issue from the Discover logging errors but another dimension of reduced reporting reliability within the same toolset.

What the data logging distinction means technically

Google's use of "data logging only" warrants some examination. Search Console's Discover performance data is generated through a pipeline that starts when Google's systems serve content to a user's device, records the impression event, processes that event through aggregation layers, and ultimately surfaces it in the reporting interface. A logging error at any point in that chain can suppress the data without any corresponding change to how content was served or how users interacted with it.

This is different from a serving error, which would reduce actual traffic, or an algorithm change, which would alter what content appeared. It is also different from a display error of the type seen in October 2024, where data existed in the back end but was not shown correctly in the interface. In the May 21 case, according to Google, the underlying events were not captured at the logging layer, meaning no retrospective correction is available.

The phrase "this issue affects data logging only" functions as both a technical clarification and a reassurance. It confirms the discrepancy between what publishers may have observed via other analytics tools - such as Google Analytics showing referrals from Discover.com on May 21 - and the empty or understated numbers inside Search Console for the same day.

Publishers who use Search Console data in downstream reporting systems, including dashboard tools, automated alerts, or performance benchmarks, should mark May 21 as an unreliable data point for Discover metrics. The same applies to May 7 and May 8 for anyone comparing weekly or month-over-month figures.

Broader context for Discover's role in publisher economics

The reliability of Discover data carries weight beyond internal reporting. Discover now serves more than 800 million monthly active users, a figure Google cited when launching the Discover report in Search Console. At that scale, the feed functions as a significant distribution channel, particularly for news and lifestyle publishers. For some, it represents a larger share of inbound traffic than traditional web search.

Publishers have faced persistent traffic instability from Discover since at least December 2025, when Google's third core update of that year caused severe drops - some operators reported 98% declines in Discover impressions within days. Recovery patterns were uneven and difficult to attribute, partly because of the compounding data quality issues inside Search Console during the same period.

When traffic drops sharply, publishers and their analytics teams rely on Search Console data to distinguish between an algorithm shift, a logging failure, and a genuine audience behavior change. Each of these requires a different response. A logging error warrants annotation and patience. An algorithm change may warrant a content audit. The two are very different diagnoses, and reaching the right one depends on the integrity of the data in the tool.

Google's anomalies page is the mechanism through which those distinctions are communicated. Its existence and regular updates represent a reasonable level of transparency. But for publishers tracking Discover as a primary traffic channel, three documented logging failures within 21 days in May 2026 add operational friction at a moment when the Discover ecosystem is already undergoing structural changes.

Timeline

Summary

Who: Google, as operator of Search Console and the Discover content feed; and publishers who use the Discover performance report to track traffic and content visibility

What: A logging error on May 21, 2026 caused clicks and impressions to be under-recorded in the Search Console Discover performance report for that day; Google confirmed the issue affects data logging only and does not reflect real traffic changes

When: The error affected data for May 21, 2026; Google disclosed it today, May 27, 2026, via its Data Anomalies in Search Console page

Where: Inside Google Search Console's Discover performance report, accessible to publishers and website operators globally; the underlying Discover feed itself was not affected

Why: A logging error at the data capture layer prevented accurate recording of impression and click events; no backfill or correction is indicated; the incident is the third Discover-specific logging failure documented within a 21-day window in May 2026, adding to a broader pattern of Search Console reliability issues that PPC Land has covered since 2024

Share this article
The link has been copied!