September 2026 spam update

Four spam updates in one year is the fastest cadence Google has run. That alone is worth understanding before diagnosing anything.

The 2026 spam updates compared

Update	Dates	Rollout
March 2026 spam	24 to 25 March	19 hours 30 minutes
June 2026 spam	24 to 26 June	2 days 1 hour
August 2026 spam	18 to 21 August	2 days 16 hours
September 2026 spam	24 Sep to 8 Oct	13 days 16 hours

The jump in length is the story. Three updates under three days, then one taking nearly two weeks.

Length does not predict impact. The 19-hour March update moved rankings sharply. The 27-day August 2025 update moved them modestly. Rollout time reflects how Google deploys, not how much changes.

What it enforced

The existing published spam policies. No new ones were introduced.

• Scaled content abuse — many pages produced primarily to rank.
• Site reputation abuse — third-party content borrowing your domain’s standing.
• Expired domain abuse — an aged domain repurposed for unrelated content.
• Cloaking, hacked content, scraped content and doorway pages.

If your site engages none of these, this update almost certainly did not touch you. Spam systems enforce specific policies. They do not assess general content quality.

Two things that confuse this diagnosis

Both happened during or just after the rollout. Neither is a ranking change.

• Search Console reporting lagged roughly 60 hours over the weekend of 10 to 11 October, the longest delay since December 2025. If your data looked thin right after the update, this may explain it better than a real drop.
• Google updated its content guidance on 1 October, mid-rollout. That was a documentation change, not a ranking release, and the two get conflated constantly.

Diagnosing a drop in this window

1. Find the exact break date with the drop analyzer. A 14-day rollout gives plenty of room to be wrong by a week.
2. Measure after 8 October, not during. Rankings move both ways throughout.
3. Check scope. Loss concentrated on pages breaching a policy points here. Broad loss across clean templates does not.
4. Check severity. Near-total loss suggests a policy violation. A partial decline suggests something else.

The page scope analyzer settles the scope question from a comparison export.

This is not your cause if

• Nothing on your site breaches a published spam policy. A confirmed update in the same week is coincidence.
• Your decline began before 24 September. Check the break date.
• Impressions held and only clicks fell. That is displacement, not a demotion.
• Only your reported data dipped around 10 to 11 October. That was the Search Console delay.

Recovery timing

Spam systems reassess continuously. There is no scheduled update to wait for.

Removing the violation typically shows results in two to eight weeks, which makes this one of the faster recovery types. Provided the violation is genuinely removed rather than reduced.

A site that halves its scaled output while keeping the same production process gets caught again at the next enforcement. The method is in spam update recovery.

European stores that lost product traffic a week before this update began were probably hit by something else entirely: Google removed free product listings in Europe.

Worth knowing alongside this: no core update has been confirmed since May, which is covered in no core update since May 2026.