Google has confirmed a reporting problem in Search Console that may make Google Discover performance look worse than it really was for two days in May. The issue affects the Discover performance report for 7 May and 8 May 2026, where clicks and impressions may show a drop because of a logging error.
For Bath and South West businesses that use Discover as part of their content reporting, this is a small but useful reminder: not every dip in a marketing dashboard means the audience disappeared, the content failed, or Google has suddenly changed its mind about your website.
Sometimes the first job is simply to check whether the data itself can be trusted.
What Google has confirmed
Google’s Search Console data anomalies page says a logging error caused a decrease in clicks and impressions for the Discover report from 7 May until 8 May 2026. Google describes it as affecting data logging only.
Search Engine Land also reported the issue on 12 May, noting that the bug does not mean a site’s position in Google Discover was affected. In other words, the report may show lower Discover activity for those dates, but that does not necessarily mean Google reduced the real visibility of your content.
That distinction matters. Search Console is often treated as the record of what happened, but it is still a reporting system. Like any reporting system, it can occasionally contain gaps, delays or corrections. When Google publishes an anomaly, it is worth recording it in your own reports so future comparisons do not tell the wrong story.
Why this matters for local businesses
Many local organisations will not rely heavily on Google Discover. It is more likely to matter for publishers, tourism and culture organisations, event-led businesses, charities, education providers, destination websites, and brands that publish timely articles or visual content.
Still, even a small Discover audience can influence how people interpret content performance. If an article about a local event, seasonal offer, venue, attraction, service launch or community story appears to lose visibility, it can lead to quick assumptions: perhaps the headline was wrong, the topic was weak, or the content calendar needs changing.
For dates affected by this bug, those assumptions would be risky. A Bath business looking at Discover clicks for 7-8 May should not treat a dip in Search Console as proof that its content underperformed. It should be treated as a known reporting caveat.
This is the kind of situation where good SEO support is not about overreacting to every graph. It is about knowing which signals are reliable, which need context, and which should be checked against other evidence.
What to do now
The sensible response is straightforward: annotate the affected dates in your reporting, then look for supporting signals before making decisions.
- Add a note to Search Console exports, dashboards, weekly reports or client reports covering 7-8 May 2026.
- Avoid comparing those two Discover dates directly with normal days as if the figures are clean.
- Check analytics data, enquiry patterns, sales, bookings, newsletter sign-ups or other on-site behaviour before concluding that real demand changed.
- If a report has already gone to a team, board or client, add a short clarification rather than rewriting the whole story around a data glitch.
For smaller organisations, this may only take a few minutes. The important part is to leave a trail. Six months from now, nobody wants to waste time explaining a mysterious May dip that was already known to be a reporting issue.
Do not mistake measurement noise for marketing strategy
One of the easiest mistakes in digital marketing is to treat every short-term movement as a strategic signal. A graph goes down, and the instinct is to change the page, rewrite the headline, alter the content plan, or blame a channel. Sometimes that is justified. Sometimes it is just noise.
For local businesses, the better habit is to ask three questions before reacting: is the data complete, is the time period long enough, and do other measures point in the same direction?
If Discover reporting dipped on 7-8 May but normal site visits, enquiries and customer activity did not, there may be nothing to fix. If other channels also changed, then it is worth looking more closely. The answer is rarely found in one isolated metric.
The same principle applies across search marketing, paid media and content reporting. Dashboards are useful, but they need human judgement around them.
What to watch next
Google’s data anomalies page is worth checking whenever Search Console shows an odd movement that does not match the rest of your marketing picture. It will not explain every change, but it can stop teams chasing the wrong problem.
For Bath, Bristol, Somerset, Wiltshire, Dorset and Gloucestershire businesses, the practical lesson is simple: keep reporting notes, compare several sources, and do not make content or SEO decisions from a single suspect graph. If the website is generating useful visits and enquiries, a two-day Discover reporting bug should be treated as context, not a crisis.
