Something moved in the rankings on August 12th and 13th. You probably felt it before Google said a single word about it. That's not new, and it never really is. What might actually be new here is what this particular update is trying to clean up.
The update, on the record
Barry Schwartz called it on August 18th: Google unleashed the August 2026 spam update. No hedging, no "unconfirmed volatility," a straight confirmation from the one outlet whose job is tracking exactly this. Search Engine Roundtable's recap the next day added the part that matters if you were watching your own numbers move: the volatility had already spiked on August 12th and 13th, days before Google said anything.
That's the normal order of operations at this point, and if it still feels backwards, it's worth sitting with why. Independent SERP trackers, a dozen or more of them running in parallel, pick up movement within hours. Google's own confirmation, when it comes, lands on its own schedule, usually after the update is already most of the way through its rollout. You are never finding out about an update while it's happening. You're finding out after the fact that what you already noticed was, in fact, a thing.
| DATE | WHAT HAPPENED |
|---|---|
| Aug 12-13 | Independent SERP trackers flag a volatility spike, unconfirmed by Google |
| Aug 18 | Barry Schwartz/SE Roundtable confirms the August 2026 spam update is live |
| Aug 19 | SE Roundtable recap ties the Aug 12-13 spike to the now-confirmed update |
| Aug 19-20 | Glenn Gabe reports the update sounds nearly done, per a John Mueller comment |
The six-day gap nobody can close
Six days is actually fast, by the standard this year has set. A prior spike in July sat unconfirmed for longer, and the one before that too. Something in Google's own confirmation cadence has been consistently behind what the tracking tools already show, which is its own small story: the tools meant to give you an early warning are, at this point, more reliable than the source they're tracking.
Glenn Gabe, watching the same thread, said the update "sounds like it's pretty much done," citing a comment from John Mueller suggesting Google would likely mark it complete within a day of Gabe's post. If that held, the entire visible rollout, from the first tracker spike to a declared finish line, ran about a week. That's tight. It's also long enough that if you got hit on the 12th, you spent most of that week not knowing whether to panic, wait, or start rewriting things, which is its own kind of damage regardless of what the update was actually targeting.
I want to be honest about why this particular gap bugs me more than the usual version of it. Six days doesn't sound like much until you're the one living inside it. A site that lost real, meaningful traffic on the 12th spent the better part of a week getting conflicting advice: some corners of the industry insisting it was a core update, others calling it noise, a few treating it as a technical glitch worth filing a support ticket over. Nobody was wrong to guess. Nobody had the information to know. That's the actual cost of the confirmation lag, not the six days on a calendar, but the six days of a team making decisions blind.
And to be fair to Google here, near-real-time confirmation of a rolling algorithm change is a genuinely hard problem, not a communications failure they're choosing not to fix. Updates roll out gradually, region by region, query type by query type, and calling it "confirmed" before the rollout has enough signal behind it risks a false alarm that's arguably worse than a late one. The trackers don't have that constraint. They just report what they see, as soon as they see it, no reputational risk attached to being an hour early and slightly wrong.
Why Glenn Gabe is rooting for this one
Here's the part I actually want to talk about, because it's not about the update's speed. It's about what Gabe said he's hoping it does. He wants it to reduce GEO and AEO spam specifically: content built not to be good, not even to rank in the traditional sense, but to farm citations in AI Overviews and AI Mode.
That's a genuinely different target than a classic spam update. The old playbook was keyword stuffing, link schemes, doorway pages, the stuff built to trick a ranking algorithm into a position it hadn't earned. The new version of that same instinct, dressed up for the AI-search era, is content engineered to be extractable and quotable without actually being authoritative. Short, choppy, listicle-shaped pages that exist to get lifted into an AI answer, not to be read by a person who landed on them. You've seen these pages. They read like they were built for a bot's convenience, because they were.
Whether Google's spam systems can actually tell the difference between that and legitimate, well-structured GEO content is the real question, and it's not one Gabe's comment answers on its own. Structure for extractability is also what genuinely good, citation-worthy content looks like. Clear headings, direct answers, scannable format, that's the whole GEO playbook, and it's also exactly what a spam-farming page mimics on the surface. The difference has to live somewhere underneath the structure: whether there's a real point of view, real sourcing, a real reason the page exists beyond being quotable.
This is the part that should make anyone doing legitimate GEO work a little nervous, and I don't think that nervousness is misplaced. A classifier trained to catch AI-citation spam is, definitionally, being trained to catch content that's engineered for extractability. It has to be good enough to separate "engineered for extractability because that's a cheap way to farm citations" from "engineered for extractability because that's genuinely useful information delivered efficiently." Those two things do not look different in a crawl. They look different in whether the page holds up to a person actually reading it, whether the claims are sourced, whether the site behind it has any track record at all. That's a much harder signal to detect automatically than structure is, and it's the signal this update has to be getting right for Gabe's hope to actually pan out.
It's also worth saying plainly that we don't yet know if it does get that right. Nobody outside Google has visibility into the actual classifier, and Gabe himself framed this as a hope, not a confirmed outcome. The honest version of this story is: an update rolled out, it's aimed at least partly in the right direction according to someone whose read on these things has been reliable for years, and the real test is whether legitimate GEO content that happens to look extractable comes through the other side intact, or gets caught in the same net as the spam it was actually trying to catch.
What to actually do about it
Here's what I'd actually tell a client this week, in order, and none of it is complicated or clever.
Don't touch anything yet, and I mean that literally. If your rankings moved on the 12th or 13th, the instinct is to start editing pages immediately. Resist it for at least a week past whatever Google's official confirmation ends up being. A spam update finishing its rollout is not the moment to start making structural changes to pages that were fine; you'll just be introducing new variables into a system that's still settling.
Once it settles, do the actual audit, and be honest about it. Pull the pages that moved, and ask which category they fall into: genuinely thin content that was always vulnerable, or well-researched, well-sourced content that happens to also be structured for AI citation. If it's the first, fix it or retire it, that's overdue work regardless of this update. If it's the second and it still took a hit, that's the signal worth watching closely, because it means the update's targeting is catching real content alongside the spam, and that's a different problem than "we got caught doing something bad."
Separate the pages by more than just "did they lose traffic." Look at what each page is actually for. A comparison page built to answer a real buyer question, with a clear point of view and sourced claims, is a different animal from a five-hundred-word answer stub that exists purely to get lifted whole into an AI Overview. Both might be structured with short paragraphs, bolded key facts, and a scannable format, because that structure genuinely helps a reader too, not just a crawler. The audit has to go past structure and into substance: does this page say something, or does it just contain facts arranged conveniently.
Talk to whoever owns your content calendar about the incentive this creates, because it's a real one and it's worth naming out loud. If AI-citation volume has become a KPI somewhere in your org, and for a lot of teams it has, the fastest way to move that number is exactly the kind of thin, extraction-optimized page this update is reportedly trying to catch. That's not a hypothetical risk. It's the predictable result of measuring citation count without also measuring whether the citation is coming from something worth citing. Fix the incentive and the spam problem mostly fixes itself, on your own site at least.
The bigger habit worth building, past this one update, is separating the two things GEO content optimization is actually trying to do. One is making genuinely good content easier for a machine to parse and quote correctly. The other is manufacturing pages whose only job is to be quotable. They can look identical from the outside for a few months. Updates like this one are Google's periodic attempt to tell them apart, and the fact that Gabe is hoping it works, rather than assuming it already does, tells you the industry doesn't fully trust that distinction has been solved yet either. Keep technical SEO fundamentals in good shape regardless of which side of that line an update decides you're on this month, because that's the part that never stops mattering.
If you want to track this one as it finishes settling, Search Engine Roundtable's own recap of the August 2026 spam update is the most current record of what Google has and hasn't confirmed, and it's the source worth refreshing before you make any changes based on what you're seeing in your own numbers. Volatility settles, almost always. Panic edits made during the settling window tend to stick around a lot longer than the update that actually prompted them, and undoing a bad reaction takes longer than waiting a week ever would have.
See where you are cited today
A free snapshot audit of your rankings and AI citations before we ever talk.
Josh leads work at the intersection of SEO and generative engines at Something Inc., helping B2B brands get ranked and cited across every major AI engine.