Google's September 2026 Spam Update: How to Measure Its Real Impact on Your Traffic
In short: the update started on September 24 and ended on October 8, 2026. A verdict today would be premature. A reliable reading is possible from early November, once the stabilization period is over.
What the Search Status Dashboard confirms
The Google Search Status Dashboard lists the September 2026 spam update from September 24, with a duration of 13 days and 16 hours, which puts the end on October 8. Times on the dashboard are Pacific time. It is the fourth spam update of 2026, after March (19 hours), June (2 days) and August (2 days and 16 hours). The last core update started on May 21 and ran almost 12 days.
The dashboard gives dates, not a list of targeted tactics. Everything beyond those dates is interpretation, and I flag it as such below.
What sets this update apart
Its duration. The earlier spam updates of 2026 lasted from a few hours to under three days. This one ran for almost two weeks, a length closer to the March and May core updates. A long rollout means rankings moved gradually, so comparing two single days will mislead you.
A spam update is also not a core update. It enforces Google's spam policies, documented in Search Central, rather than reassessing overall content quality. Confusing the two leads to the wrong fix: rewriting pages when the real question is about practices such as scaled content, expired domain abuse or site reputation abuse. Check the current policy list before concluding anything.
A 5 step method to measure the impact
- Fix the window. Compare the 28 days before September 24 with the 28 days that follow a stabilization period of about a week after October 8. The first usable reading arrives in early November.
- Neutralize the noise. List your own changes over the period (migration, redesign, new templates), the seasonality of your sector and any overlap with other updates. The August update ended before the reference window, which helps.
- Segment before concluding. Split Search Console data by page type, query group, country and device. A loss concentrated on one section tells a very different story from a site wide loss.
- Confront the affected pages with the spam policies. Only when the loss is concentrated. Look for what those pages share: mass produced content, thin pages, third party content hosted on your domain.
- Decide. Three possible outcomes: nothing to do, a targeted fix, or waiting for the next core update before touching anything. A two week curve is never a reason to rewrite a whole site.
Three scenarios and the right reaction
- Drop concentrated on a section: audit that section against the spam policies, fix, then measure again after the next stabilization period.
- Stable traffic: keep your baseline and your change log. Stability is information too.
- Gain: document what you did before it and avoid new experiments on the pages that gained.
Should you expect a core update?
The last core update ended in early June. Nothing is announced and I would not treat a new one as scheduled. What helps is preparation: a clean before and after baseline and a log of every site change. The baseline you build now will serve for the next update as well.
Want to know where your site stands before then? Request the free flash test: 3 priority findings on up to 3 URLs of your site. For the ecommerce angle, read the May 2026 update article.
Do you manage client sites? I am piloting an update impact report delivered under your agency's brand. Write to me through the contact form and mention "Agency pilot diagnostic".
Frequently asked questions
Can I already tell if my site was hit?
Only partly. Until early November, a stabilized comparison is not available. You can still segment your data and spot a sharp, concentrated loss.
Should I rewrite my content now?
No. A spam update does not reassess overall content quality. Fix only what the spam policies clearly cover, and only after segmenting.
Does a small site need to worry?
The method is the same at any size. With low traffic, use longer windows, because daily variations are noisy.