Google began rolling out its September 2026 spam update at 09:15 Pacific time on September 24, according to the Search Status Dashboard. The entry says the update “applies globally and to all languages” and that the rollout “may take up to two weeks to complete.” Google named no target, and the same dashboard shows the three earlier 2026 spam updates all closing out in under three days.
Three Rollouts, One Outer Limit
The dashboard’s summary page lists every 2026 spam update by start date and duration. Here is how September’s stated ceiling compares with the year’s actual record:
| Update | Started | Duration |
|---|---|---|
| March 2026 spam update | Mar 24 | 19 hours, 30 minutes |
| June 2026 spam update | Jun 24 | 2 days, 1 hour |
| August 2026 spam update | Aug 18 | 2 days, 16 hours |
| September 2026 spam update | Sep 24, 16:15 UTC | Not yet completed |
September’s is the fourth spam update of the year, and the only one still open; the dashboard carries a single entry for it, with no completion time logged as of this writing. Search Engine Journal noted that Google gave each of the previous three spam updates a rollout window of “a few days.” This time the stated window is two weeks.
What Is the September Spam Update?
The September 2026 spam update is a global ranking update that the Search Status Dashboard says started at 16:15 UTC on September 24 and “applies globally and to all languages.” Google has not said what the update targets. Its own “up to two weeks” estimate is an outer limit, not a track record — the three prior 2026 spam updates each finished in under three days.
Tracker Volatility Predates the Official Start
Search Engine Roundtable’s Barry Schwartz clocked ranking swings before Google’s own start time. On September 24 he wrote: “We are seeing significant volatility again within the Google Search rankings again, this time starting around September 23rd (maybe the 22nd) and throughout today.” He listed Semrush, Mozcast, Sistrix, Similarweb, AccuRanker, Wincher, AWR and Algoroo, among others, as trackers showing it, then updated the post once Google confirmed the update had started rolling out that day.
The gap matters for attribution. Google’s rollout clock starts at 16:15 UTC on September 24. A ranking move logged on September 22 or 23 predates that clock. Google has offered no explanation for what the trackers picked up beforehand.
No Target Named, and Recovery Runs on Google’s Clock
Google’s spam-updates documentation, last updated in December, tells site owners who see a change to “review our spam policies to ensure they are complying with those.” Recognition, it adds, is slow: “Making changes may help a site improve if our automated systems learn over a period of months that the site complies with our spam policies.” Months, not the two-week rollout window, is the unit Google uses for recovery.
The same page adds a narrower rule for a specific kind of update. “In the case of a link spam update (an update that specifically deals with link spam), making changes might not generate an improvement,” Google writes, because once its systems remove the effects of spammy links, “any ranking benefit the links may have previously generated for your site is lost.” Google has not said whether September’s update deals with links at all, so that rule describes link spam updates in general, not this one.
The August update followed a similar pattern: in August, Google also named no target for its spam update. The dashboard’s durations for June’s spam update, which closed in two days and one hour, and the other two finished rollouts are the only completed benchmarks for this year so far.
What to Log Before Drawing Conclusions
The dashboard has not posted a completion entry for September’s update, so the window stays open. Site owners tracking it should note the 16:15 UTC, September 24 start time and measure drops against that timestamp, not against whatever a rank tracker showed on the 22nd or 23rd. Past entries on the same dashboard show Google does log a duration once a rollout ends, so a completion entry should eventually follow. Until then, the responsible read is to treat the whole window as unsettled and wait for that entry before deciding whether the update touched a site at all.
