Google’s September 2026 spam update could take two weeks to roll out

Google began rolling out its September 2026 spam update on September 24, according to its Search Status Dashboard, which logged the release at 16:15 UTC. It’s the fourth spam update of the year, following similar passes in March, June, and August, and it applies globally across every language and region Google indexes.

What sets this one apart is the timeline. The three earlier 2026 updates each finished within days, the fastest wrapping in under 20 hours and the slowest, August’s, taking just over two and a half days. Google told Search Engine Roundtable this rollout will likely take longer, and the status dashboard itself lists a window of up to two weeks before the update is considered complete.

Google was specific about what the update doesn’t do. A spokesperson confirmed it isn’t targeting link spam specifically, and it doesn’t cover every spam policy the company enforces, which leaves publishers guessing at exactly which violations are in scope this time around. That’s a departure from how Google usually frames these releases, as broad, policy-wide sweeps rather than something narrower, and it comes at a time when the tactics being policed have gotten more inventive, from doorway pages to entire networks built around gaming search rankings.

For sites that do get hit, the guidance hasn’t changed. Google is telling affected publishers to review its spam policies, fix whatever’s out of line, and wait, because recovery isn’t immediate even after a site cleans up. The company has said it can take many months for its automated systems to relearn that a domain is compliant, since those systems tend to reassess sites gradually rather than flip a switch the moment a fix goes live. With the rollout itself stretched to two weeks and recovery measured in months rather than days, publishers caught in this update are looking at a longer road than the last three rounds combined, and there’s no new spam-policy changelog to check against, since Google hasn’t flagged any policy changes tied to this particular update.