Google confirmed and completed the August 2026 spam update between 18 and 21 August, its third spam-focused ranking adjustment of the year. Unlike a broad core update, this type of update specifically targets content that breaches Google’s spam policies rather than reassessing overall site quality, so most legitimate sites should see little to no change.
24 August 2026
Key insights
What was Announed
On 18 August 2026, Google’s Search Status Dashboard confirmed the rollout of the August 2026 spam update, applying globally and across all languages. Google didn’t publish a companion blog post or introduce any new spam policies alongside the announcement, and it specifically noted the update wasn’t targeting link spam or site reputation abuse, both of which are treated as their own distinct categories.
What this Update Targets
Spam updates are a different animal to the broad core updates most site owners are more familiar with. Where a core update reassesses the overall quality, relevance, and usefulness of content across the web, something we unpacked in our piece on Google’s AI Overview and E-E-A-T changes, a spam update is narrower and more punitive: it specifically demotes content that breaches Google’s published spam policies, things like scaled content abuse (mass-producing low-value pages), cloaking, and expired domain abuse (repurposing an old domain’s authority for unrelated spammy content). Sites operating within normal SEO practice generally see little movement from a spam update, even while trackers register a broad spike in change across the wider web.
Rollout Timeframe
The rollout began 18 August 2026 and completed 21 August 2026, running for roughly two days and sixteen hours, a relatively fast turnaround compared with a typical core update, which can run one to two weeks. This is the third spam update of 2026, following ones in March and June. It’s a smaller, more contained action than the broader volatility windows we tracked through July and early August, covered in our recap of July’s ranking volatility and our look at the July 18-19 spike specifically, both of which were never officially tied to a named Google update at all.
What We Know so Far
As of today, the update is complete and Google’s Search Status Dashboard shows the incident as closed. This follows a busy few months for Google Search: a Broad Core Update in May, a Spam Update in June, and then a run of five separate unconfirmed ranking-volatility spikes through July and the first half of August that trackers picked up but Google never officially named. The August spam update is the first update since June that Google has confirmed outright, rather than leaving it as an unconfirmed volatility pattern.
What We’re Monitoring
- Organic rankings and traffic in Google Search Console and GA4 for all client sites, cross-checked against each other.
- Any unexpected ranking or traffic drops that might indicate a site has been caught by the update, even unintentionally.
- Whether any client content resembles the patterns spam updates typically target (thin, scaled, or auto-generated pages).
- Continued monitoring of the Search Status Dashboard for any further updates in the weeks ahead.
What to Expect Next
Most sites following normal SEO practices, including anyone we manage, are unlikely to see any noticeable change from this update. If a drop does show up over the coming week or two, the first step is always to rule out anything else going on with the site itself before assuming the spam update is the cause. Reactive changes made in the days immediately after an update are rarely a good idea, since normal fluctuation can look alarming in isolation. We’d expect Google’s next confirmed update, whether spam-related or a broader core update, to land within the next month or two given the frequency we’ve seen so far this year.
Sources:
Author
Bee bowman
Bee is a digital strategist passionate about helping brands grow through thoughtful design and smart marketing. With a focus on websites, SEO, and paid media, they turn digital spaces into real business results.
Share this post