At some point in the next few weeks, you’ll sit in a monthly review and be shown a chart with a cliff in it. Reported impressions—the count of times Google showed your pages—fall away on the Generative AI in Search report on 13 August 2026. Five days later, Google announced a spam update. Both fall within the same thirty days, and they may get run together.
My experience says that many of the explanations given in September will be wrong because those two events aren’t the same. Even my own dated record of both was wrong until last week.
Three kinds of things move a Search Console line: reporting artefacts, ranking events and reclassifications. In a chart, they look identical. They have nothing else in common—not the cause, not the fix, not what they mean for your bottom line. August produced a confirmed example of each, eleven days apart.
So the question worth asking isn’t what your chart did. It’s which of the three it was—and that is a question with an answer, in Google’s own records and in what your own reports said at the time. And we’re actually dealing with three events in August, not two.
Dates from Google’s own records: the Search Console data-anomalies page, the Search Status Dashboard incident record for the August 2026 spam update, and the Merchant Center announcement of 11 August 2026. The thirty-day window is illustrative.
1. 13 to 17 August: the number moved, the world didn’t
Google’s Search Console data-anomalies page records a logging error that reduced reported impressions on the Generative AI in Search performance report for data from 13 to 17 August. Google states the issue affected data logging only. Your rankings, your pages and what searchers saw didn’t change.
There’s nothing to fix here, because nothing broke. And the data came back: on 21 August, Google updated the same page to say the missing data ‘has been restored’ and the Performance report ‘now shows complete metrics’. So annotating the window and leaving it out of your comparisons was right for about a week, and now it throws away good data. Only an export pulled before the restoration still has the gap. If a fall within those five days is identified as a performance problem with suggested remedial work, nobody checked.
But the logging error is the small artefact. Two bigger ones sit in the same report, and both are still running.
Look out for AI Mode conversations and AI Visibility tool polling
First, check your query table and scan for ‘yes’, ‘yes, go on’, and ‘yes, pricing’. Those aren’t queries. They’re follow-up turns in AI Mode conversations, logged as standalone queries with their own impressions and their own average position—the average rank your pages held when they were shown. Glenn Gabe has published a method for isolating them—export the query and landing-page pairs, then classify the conversational fragments—and found they carry almost no clicks.
Second, AI-visibility tools poll the AI surfaces automatically, over and over, to build their dashboards, and some of what Gabe surfaced was exactly that: impressions generated by vendors measuring visibility. If anyone in your market has bought one of those tools, part of the ‘demand’ in your report is robots checking whether you exist.
Putting those together, query count and average position are currently unreliable metrics for any site with meaningful AI Mode exposure. Neither number means anything until you filter the fragments out of the data.
2. 18 to 21 August: the world moved
Google’s Search Status Dashboard incident record shows the August 2026 spam update starting at 16:27 UTC on 18 August (09:27 Pacific, as the dashboard shows it) and ending at 08:49 UTC on 21 August (01:49 Pacific). This one is real. Rankings moved, and if your site moved with them, there are two quite different reasons why—and the chart won’t tell you which.
And anything that shipped on your site while the update was rolling out may be confounded, because nobody can separate what the change did from what the update did.
Beware: if your movement starts on 12 or 13 August, it predates the update—Google’s own record says nothing was rolling out then, and 13 August has a confirmed pattern of its own (see above).
3. 24 August: history restated back to 1 July
The third kind of thing is a reclassification. Nothing moved, and nothing failed—the metric changed its definition, and history was restated to match. These are the nastiest of the three, because there’s nothing in this month’s report to see. The defence against reclassification is dated exports—a saved copy of what the report said at the time, to hold against what the same report says today.
August’s example is in Merchant Center. Google’s announcement, dated 11 August 2026, says that from 24 August products eligible for YouTube affiliate commission are reported under a new ‘YouTube affiliate’ traffic value and excluded from the ‘Organic’ reporting value—’potentially causing a one-time significant drop in organic traffic’, in Google’s own words. The restatement also reaches back: the change applies to historical data from 1 July 2026. Six weeks of figures that merchants have already read, reported and made decisions on will no longer match what the same report shows. If September’s report disagrees with the numbers you quoted in July, you didn’t lose anything. The definition changed.
For a week, this change circulated as a vendor-blog claim with a date attached and nothing from Google behind it. I checked Google’s own pages, which turned it into the dated event above—and found what the vendor version missed: the restatement back to 1 July.
I made both of these mistakes myself
I keep a dated ledger of exactly these events—updates, anomalies, reclassifications—so that no client’s movement ever gets correlated against an undated rumour. Last week I audited it, every live entry, every source fetched again, and found the mistakes I’ve just described.
My entry for the logging error had the window still open—’ongoing’—when Google’s page states it closed on 17 August. It also cited a trade-press write-up as the primary source. An open window that should be shut is a false positive waiting to happen: every future movement gets a standing excuse.
Worse, an automated pass had taken the spam update and walked it backwards—from complete to still rolling out—because it read a news digest written mid-rollout. Any movement after 21 August could have been waved at an update that had already finished. I corrected both entries the same way: against Google’s own pages, as it should have been the first time.
The same morning, the discipline paid for itself. A set of page edits went out on a client site inside the update window. There’s no clean performance read on those pages for that week, and the record now says so.
What to look at, and in what order
Here’s what’s really going on
| Kind | What actually moved | What you see in the report | What you do |
|---|---|---|---|
| Reporting artefact | Nothing. Only the logging. | A fall in one report, usually with a stated window | Re-read the anomaly entry before you exclude anything—these get repaired, and the 13 to 17 August one was |
| Ranking event | Your positions, and what searchers saw | Clicks and impressions move together, and it persists | Read it as information about your site—but not for anything you shipped inside the window |
| Reclassification | Nothing. The definition. | Today’s pull of an old date range disagrees with what you reported at the time | Compare today’s pull against a saved export |
Here’s how to proceed
- Focus on the date, not the month. Daily data, filtered by search type. ‘Mid-August’ isn’t a date; 13 August is.
- Look at Google’s own records, before a cause gets named. Two apply to every site: the data-anomalies page and the Search Status Dashboard incident history—it’s headed History. It goes back to August 2025, so August incidents are in the default view without a click. If the movement is in Merchant Center reporting, the announcements on Google’s Merchant Center help pages count too. If Google has logged an event that matches your date, that gets ruled in or out before anything else.
- Determine which of the three kinds it is. An artefact usually hits one report, has a stated window and affects logging rather than reality. A ranking event moves clicks and impressions together and persists. For a reclassification, today’s version of an old date range won’t match a saved export.
- Examine the query table before quoting query count or average position anywhere. The conversational fragments—’yes’, ‘yes, go on’—have to come out of the data first. Until they do, both numbers are provisional.
- Be careful with everything that shipped inside a confirmed update window: the update can’t take the blame for a fall that week, and the week’s work can’t take the credit for a rise.
And one thing worth doing this week rather than in September: write down the three events against their dates—13 to 17 August, reporting error, data restored 21 August; 18 to 21 August, spam update; 24 August, Merchant Center reclassification, history restated to 1 July. The cliff will still be in the chart the next time you look. The reason won’t be.
If you want to talk about what your numbers actually did this summer, please get in touch with me at [email protected].
David Rosam has been working online for more than 25 years, after a career in direct marketing copywriting for the tech and financial services industries.
Today, he specialises in Content-Leveraged Search Engine Optimisation—from audits, through research and strategy to implementation.
He was probably the UK’s first SEO Copywriter.