Google's September 2026 Spam Update Is Done: What to Check

Google marked its September 2026 spam update as complete on October 8, 2026. The rollout began on September 24 and lasted 13 days and 16 hours, according to Google's Search Status Dashboard. It applied globally and to all languages. With the rollout closed, it now makes sense to measure whether it touched your site.

What we know

End of the rollout: the Google Search Status Dashboard sets the end at 01:00 Pacific time on October 8, 2026. That is 08:00 UTC.
What the note says: the dashboard posted the notice at 01:37 Pacific time. In one sentence, it says the rollout was complete as of October 8.
Start: September 24, 2026, at 09:15 Pacific time, according to the same dashboard.
Duration: 13 days and 16 hours, according to the dashboard's history. At launch, Google had said it might take up to two weeks.
Scope: global and all languages, according to the launch note.
The other 2026 spam updates: the dashboard's history lists three more this year. March took 19 hours and 30 minutes; June, 2 days and 1 hour; August, 2 days and 16 hours. September is the fourth and the longest: about five times August, by this article's own math.
The last longer one: you have to go back to the August 2025 spam update, which ran 26 days and 15 hours according to that history.
What Google didn't say: the two dashboard notes don't detail which specific practices this update targets or how many searches changed.
What the tools saw: according to Search Engine Roundtable, movement clustered on September 25–27, September 30 and October 4–6. That is one outlet's reading of third-party tools, not Google data.

What changes and what doesn't

One thing changes: the rollout is no longer in progress. The ups and downs of the past two weeks stop being provisional and can be analyzed.

The rules don't change. Google's spam policies page shows a last-updated date of August 28, 2026: the update added nothing to that list.

Detection doesn't switch off. Google's guide to spam updates says its automated spam systems are "constantly operating". An update is an improvement to those systems, not a campaign with a start and an end.

There is no quick recovery. The same guide says changes may help if the systems learn "over a period of months" that the site complies. The guide adds one exception for updates that deal specifically with link spam: the benefit those links gave cannot be regained. The dashboard calls this one a "spam update", nothing more.

And it isn't a manual action. A spam update is automated: no notice arrives in Search Console.

How to tell if it hit you

Compare two equal windows. In Search Console, open Performance, click the date filter and choose "Compare" with custom dates: September 24 to October 7 against September 10 to 23. Each is 14 days and both start on a Thursday.
Look at pages, not the total. In the "Pages" tab, sort by click difference. A drop spread evenly across the site points to another cause. A drop concentrated in a group of similar pages is the signal to follow.
Rule out everything else. A public holiday, a migration, a stray noindex tag or server downtime in those days produce the same curve.
Open "Manual actions". It sits under "Security & Manual Actions". If the report is empty, there is no manual penalty: whatever happened is automated.
Check those pages against the spam policies. The ones a business site most often runs into: scaled content abuse, the site reputation policy, expired domain abuse, keyword stuffing, hidden text and link abuse, and link spam.
Don't mass-delete. Decide page by page: improve it, merge it or remove it. And count the timeline in months, not days.
Measure again. From October 24, compare October 8 to 21 against September 10 to 23. That window sits entirely after the rollout closed. Search Console warns that the newest data is preliminary.
If nothing moved, change nothing. A spam update that doesn't move you asks for no action.

Sources

Updates: if Google adds information about this update on its status dashboard or in Search Central, it will be noted here with its link.