Google's September spam update is over, and its official record is short enough to quote in full. The Search Status Dashboard lists the September 2026 spam update as starting on 24 September 2026 and running 13 days and 16 hours, which puts completion on 8 October 2026. Search Engine Journal ran a column the same day reporting the rollout finished. For scale, the same dashboard lists the August 2026 spam update at 2 days and 16 hours. The entry carries a title, "September 2026 spam update," and nothing else. It names no target, content type or region. This updates our 29 September brief, which said the rollout could run two weeks and named no target. It ran just under that and has now ended. The first clean read of any change comes only after a buffer period.
Credibility: HIGH. The dashboard entry is Google's own record, and anyone can open it. The completion date is computed from the listed start and duration, since the dashboard shows no explicit end date, and the SEJ column corroborates 8 October. The dashboard says nothing about what the update targets. The SEJ piece is an opinion column, so the buffer advice below is one practitioner's rule of thumb. Google has issued no such guidance.
- Start: 24 September 2026 (US/Pacific), per the Google Search Status Dashboard summary page.
- Listed duration: 13 days and 16 hours, which ends the rollout on 8 October 2026. The dashboard lists the August 2026 spam update at 2 days and 16 hours.
- The entry gives only the title, "September 2026 spam update"; it names no target, content type or region.
- Per the SEJ column, volatility peaked on the weekend of 26–27 September 2026, and its author, an SEJ enterprise-SEO contributor, recommends waiting 10–14 days after completion before judging losses.
Sources
Google Search Status Dashboard: September 2026 spam update (ranking incident, listed 24 Sep 2026, duration 13 days 16 hours) — https://status.search.google.com/summary
Search Engine Journal: Why Google Search Updates Cannot Be Judged During Early Rollout, Taylor Daniel (@TaylorDanRW), 8 Oct 2026 — https://www.searchenginejournal.com/why-google-search-updates-cannot-be-judged-during-early-rollout/591345/
Stay ahead of AI search
The changes that move your rankings and AI citations — and the exact move to make — before they cost you. Free, three times a week.
For business owners and marketing leads: Google has handed you a date range and no motive, and that decides how the next two weeks go. The window, 24 September to 8 October, is closed. A traffic or ranking drop that began inside it can now be measured. It cannot yet be read cleanly. The columnist's 10–14 day buffer lands between 18 and 22 October. Before that, a drop may still be settling; after it, a drop is a result to diagnose. Because the update names no target, a drop that lines up with the window is a candidate cause, not a verdict. The easy mistake this month is blaming the update for a fall that your own redesign caused the same week. So check the timing against your own content and template changes before concluding anything, and give a flat line the same scrutiny: no drop yet is not the same as no effect.
Actions this week
1. Ask your web team to schedule a Search Console performance export (clicks and impressions by page) for 9–22 October, to be pulled on 23 October and compared with 3–23 September.
2. Hold reactive site-wide content or template changes until after 22 October, and log the date of every change that does ship so it can be separated from the update's effect.
3. Keep your AI-visibility tracker running as the directional read and compare its movement with the Search Console export on 23 October; record the decision rationale for any client conversation before then.
Google Search Status Dashboard: September 2026 spam update, Google, listed 24 Sep 2026, duration 13 days 16 hours — https://status.search.google.com/summary
Search Engine Journal: Why Google Search Updates Cannot Be Judged During Early Rollout, Taylor Daniel (@TaylorDanRW), 8 Oct 2026 — https://www.searchenginejournal.com/why-google-search-updates-cannot-be-judged-during-early-rollout/591345/