Google has logged the September 2026 spam update on its Search Status Dashboard: it started on September 24, 2026 at 9:15 a.m. PDT, and Google says it "applies globally and to all languages. The rollout may take up to two weeks to complete." When we checked on October 8, the dashboard entry still had no end time.

The Year's Fourth Spam Update, on a Different Clock

The three earlier spam updates of 2026 were all short on the official dashboard: March (from March 24) ran 19 hours 30 minutes, June (from June 24) ran 2 days 1 hour, and August (from August 18) ran 2 days 16 hours — the one we covered in our August report. Each of those was announced as taking "a few days". This one was announced as taking up to two weeks, which puts it in the same range as 2026's two core updates (March, 12 days 4 hours; May, 11 days 21 hours).

Google has not said which kind of spam this update targets, so any claim that it "hits tactic X" is speculation for now.

A Longer Window Changes How You Diagnose

  • Don't draw conclusions from data between September 24 and the day the dashboard marks it complete. A two-week rollout spreads volatility across the whole window, distorting both day-over-day and week-over-week comparisons.
  • If your traffic dropped before September 24, it wasn't this update. The official dashboard shows no ranking event at all between September 1 and September 23.
  • Compare only after the rollout finishes: take a block after completion against the stable September 10 to 23 period, with equal lengths and the same mix of weekdays and weekends.

Spam Updates and Core Updates Recover Differently

A core update re-evaluates what counts as helpful content; a spam update targets specific behaviour that breaks the spam policies, such as mass-generated low-quality pages, parasite hosting or expired-domain abuse. If a spam update hits you, the useful move is to find and remove that specific behaviour, not to launch a vague "site-wide content refresh". As we argued in our August 26 piece, third-party volatility indexes are no substitute for the official dashboard: check that the dates line up before you look for causes.

Rule Out Technical Noise First

The longer the rollout, the more likely it overlaps with your own changes. If you moved servers, switched CDN, or touched robots.txt or canonicals in the same period, eliminate those first. Server location affects SEO mainly through TTFB, and if you run crawlers or rank tracking on a VPS, choosing a VPS for SEO tools lists resource needs by tool type so an underpowered monitor doesn't invent volatility of its own.