Last Updated on August 25, 2026
If you opened Google Search Console in the middle of August and watched your impressions fall off a cliff, you were not imagining it. The chart really did drop.
The traffic did not.
Google has now recorded the whole thing on its own data anomalies page. Between 13 and 17 August 2026, a logging error cut the impressions shown in the Generative AI performance report. Google’s wording is short and unambiguous: “This issue affects data logging only.”
Translation: the number was wrong. Your visibility was not.
What actually broke
Three separate things went wrong in Search Console in the space of a fortnight.
| Dates | Report affected | Logged by Google? |
|---|---|---|
| 13 to 17 Aug | Generative AI in Search. Impressions under-reported. | Yes, on the anomalies page |
| 13 Aug | Discover and Generative AI in Discover. Clicks and impressions under-reported. | Yes, on the anomalies page |
| 15 and 16 Aug | Crawl Stats. Two days simply missing. | No. Reported by SEOs, patched 23 Aug |
John Mueller of Google put it plainly on Bluesky at the time. The drop was, in his words, “just a logging issue and not representative of visibility changes in Search.”
And a real algorithm update landed in the middle of it
Here is the part that turns an annoyance into an expensive mistake.
Google started rolling out the August 2026 spam update at 9:28 a.m. Pacific on 18 August and marked it complete at 1:49 a.m. Pacific on 21 August. Two days and sixteen hours, global, every language. Google published no new spam policies and no accompanying blog post.
So in one fortnight a UK business owner had two entirely different reasons for a wobbly chart, arriving days apart, with no label on either. One was a reporting fault that meant nothing. One was a live ranking change that might have meant a great deal.
13 to 17 August: your numbers were wrong.
18 to 21 August: your rankings may genuinely have moved.
Nothing in Search Console tells you which is which.
We covered the update itself in what we said when the spam update landed. The advice has not changed. What has changed is that the data you would use to check it was unreliable for part of the same month.
The mistake almost everyone makes
The mistake is not misreading a chart. The mistake is treating a dashboard as a result.
A dashboard is a report about a result. Reports break. Google’s own page proves it. Alongside the August entry sit a Discover logging error on 24 June and another on 21 May. Three recorded in 2026 so far, on the same page, in the same section.
If a single Google chart is the only place you find out how your business is doing online, then every reporting fault at Google becomes a strategy meeting at your business. That is not a measurement problem. That is a structure problem, and no amount of extra marketing spend fixes it.
What to do about it
One. Keep a second source. Search Console is Google’s account of Google. Your own analytics, your enquiry inbox, your phone log and your booking system all measure something Google cannot fake. When the two disagree, the one that pays your wages wins.
Two. Check the anomalies page before you react. It takes thirty seconds. Google records known reporting faults at the Search Console data anomalies page, with dates. If your dip matches an entry, you have your answer and you have saved yourself a fortnight of pointless rewriting.
Three. Know what normal looks like. Most owners cannot say whether last week was good, because they never wrote down what an average week is. Set a baseline. We publish our UK search engine statistics for exactly this reason, and the underlying mechanics are in how UK businesses actually get found online.
Four. Wait a fortnight before changing anything. The spam update finished on 21 August. Data from after that date reads cleanly. Data from during it does not. Compare like with like or do not compare at all.
The takeaway
Your enquiries are the result. Everything else is a report about the result, and reports break more often than most business owners assume.
If a five day logging error at Google could have changed what you do next quarter, the problem was never the logging error. It was that you had nothing else to look at. Fix that before you touch anything else, and if you want to see where the AI answers currently point in your sector, our UK AI visibility index is the place to start.
