Google closed the September 2026 spam update after 13.7 days

Google closed the September 2026 spam update on 8 October. The entry on Google’s Search Status Dashboard now carries an end timestamp of 2026-10-08T08:00:00+00:00, and a status note posted 37 minutes after it reads: “The rollout was complete as of October 8, 2026.” The same entry began at 2026-09-24T16:15:00+00:00, so the rollout ran 13 days, 15 hours and 45 minutes.

That is the longest spam update rollout Google has published in 2026, by a distance. It is 5.1 times the next longest, 2.5 times all three earlier 2026 spam updates added together, and longer than either core update Google ran this year. Every figure in this article is arithmetic over two timestamps Google publishes itself, which means any reader can reproduce it from the same file.

What Google actually published

The Search Status Dashboard is the only place Google records a confirmed ranking update with machine-readable timestamps. Its entry for the September 2026 spam update, read live on 9 October 2026, contains two status notes and nothing else.

The first, timestamped 2026-09-24T16:15:47+00:00, says the update “applies globally and to all languages” and that “the rollout may take up to two weeks to complete”. The second, timestamped 2026-10-08T08:37:09+00:00, says the rollout “was complete as of October 8, 2026”. The incident’s own end field is 2026-10-08T08:00:00+00:00 — 37 minutes before the note that announces it, which is worth knowing if you are dating an impact to the minute.

Google named none of its sixteen spam policies in either note, gave no indication of which sites were affected, and published no measurement of any kind. Checked on 9 October 2026, the dashboard also carries no incident of any sort with a begin date in October 2026, so nothing else is confirmed as running right now.

The arithmetic: 13.7 days against 0.8, 2.0 and 2.7

Google publishes a begin and an end timestamp for every confirmed update. Subtracting one from the other gives the only duration figure in this story that anyone outside Google can verify. Here is every spam update and core update Google has confirmed in 2026.

The three earlier 2026 spam updates together account for 5 days 12 hours 52 minutes of rollout. The September one, on its own, took two and a half times that. No sample size applies to any of these numbers, because they are not a study: they are six pairs of timestamps on one page. PPC Land reached 13 days 16 hours and 19.5 hours for the same two updates on 8 October 2026, which corroborates the arithmetic independently.

Google said “up to two weeks”, and the window held

A fortnight from the 24 September begin timestamp lands at 2026-10-08T16:15 UTC. The rollout closed at 08:00 UTC the same day, 8 hours and 15 minutes inside the window Google published. That is a small thing and it is the only predictive claim in this story that has now been tested: Google gave a ceiling, and the ceiling held.

It is worth setting against where that figure came from. Google’s documentation page on spam updates, Google Search’s spam updates, carries a Last updated stamp of 2025-12-10 UTC and, checked twice on 9 October 2026, contains no rollout duration at all — the words “two weeks” and even “weeks” do not appear on it. The two-week ceiling existed only in a dashboard status note. If you watch Google’s documentation for timing guidance, there is none there to watch.

What the community measured, and what it did not

Third-party ranking trackers recorded movement in three bursts during the window. Barry Schwartz at Search Engine Roundtable described a first wave on 25–27 September, a second from 30 September, and a third over 4–6 October, which he published on 6 October 2026 under the heading of a possible final phase, writing: “I suspect this is it – we are pretty much done with this spam update.” He also reported Google telling him “the rollout will be around two weeks, versus the typical two-day rollout”.

Two things need separating here. The waves are real observations of tracker output; the word “phase” is a practitioner’s interpretation. Google confirmed no phases. It published a begin timestamp, an end timestamp and two sentences. The trackers that registered the movement publish no keyword set, no sample size and no methodology, so there is no way to test a wave against the update that was running at the time.

What this changes in practice

Three things change now that the entry is closed, and none of them is a ranking insight.

First, you have a boundary. Until 8 October there was no defensible end date for a before-and-after comparison, because the update was still running. There is one now, published by Google, to the minute.

Second, the rollout is no longer a reason to wait. Through late September the honest answer to “have we been hit?” was that the update had not finished and the data would move again. That answer has expired.

Third, a spam update is not a manual action. Spam updates are algorithmic and silent; manual actions appear in Search Console and come with a reconsideration request. Google’s spam updates documentation does not mention reconsideration at all — confirmed on two reads of the page on 9 October 2026 — because there is nothing to request. If you want the difference laid out properly, our course level on grey hat, black hat and parasite SEO covers which Google sanctions are visible and which are not.

What to do this week

A recipe, with the exact boundaries, so two people running it get the same answer.

• Mark two timestamps in your analytics: 24 September 2026 16:15 UTC and 8 October 2026 08:00 UTC. Everything between them is rollout and should not be averaged with either side.
• Compare equal-length windows that exclude the rollout: 10–24 September against 9–23 October. Comparing a fortnight of pre-update data against a fortnight that contains the rollout is the commonest way to manufacture a result that is not there.
• Segment before you conclude. Split clicks and impressions by query type and by page template. A sitewide dip and a dip confined to one template are different diagnoses with different fixes.
• Check Search Console for a manual action first. It takes thirty seconds and it rules out the one sanction that has an appeal route.
• Read the spam policies against your own site, which is precisely what Google’s own page tells you to do: “Sites that see a change after a spam update should review our spam policies to ensure they are complying with those.”
• Set expectations on recovery honestly. The same page says improvement comes only if “our automated systems learn over a period of months that the site complies with our spam policies”. Months, not days, and Google publishes no number at all.

If the answer to all of that is that nothing moved, the right conclusion is that nothing moved. Measuring that properly is its own skill, and our level on SEO analytics and measurement is built around not inventing a signal when the data does not carry one.

Where the industry genuinely disagrees

This story touches several questions on which practitioners split, and on which the evidence does not settle anything. We report the disagreement rather than pick a side.

Does the volatility belong to the update? One camp holds that the three waves inside a confirmed window are obviously the update arriving in stages, and that refusing to say so leaves readers mis-dating their own data. The other holds that trackers register movement almost continuously, that Google published no phases, and that attributing a particular day’s movement to a named update is unfalsifiable without a counterfactual. Nobody has published a paired series of tracker readings against confirmed rollout windows with sample sizes disclosed, so both camps argue from the same absence.

Does a rollout duration tell you when the effect shows? The only figure in circulation for how long a spam update takes to bite is Gary Illyes’s 1–2 weeks, stated at Search Central Live Deep Dive Europe in Barcelona on 2 October 2026 and reaching the trade press through one attendee’s LinkedIn recap, which blocks automated retrieval. It is also a different quantity from the one Google published: time for an effect to show is not time for a rollout to finish. One camp treats a named Google engineer’s figure as operational documentation; the other notes that an unpublished slide relayed by one attendee carries no sample size and no definition of “typical”, and cannot be re-read.

What does a spam update enforce? Google named none of its spam policies, so the update moves nothing in the long-running argument about where scaled content abuse begins. The policy text still defines it by purpose rather than by volume or production method, and still publishes no threshold.

Does a disavow file help after a spam update? Google’s position is that most sites never need one; a large part of the agency world disavows routinely anyway. No published study isolates a disavow file’s effect on recovery after a spam update, so the argument runs Google’s statements against uncontrolled case reports.

What I think

The duration is the only number in this story worth anything, and it is worth something precisely because it is checkable. Two timestamps, one subtraction, same answer for everyone. That is rarer in SEO reporting than it should be, and it is why it is the claim this article is built on rather than anything about what the update did.

What I will not do is read significance into the length. A 13.7-day rollout is not evidence that the update was bigger or more aggressive than the 19-hour one in March. It is evidence that it took longer, which could be scope, caution or infrastructure. Google published no measurement and I have none, so I will not supply a mechanism to fill the gap — that is the move that produces “Google is cracking down on X” coverage that ages badly.

The consequence I do hold is narrow: use the two timestamps as measurement boundaries, not as a diagnosis. A boundary is what Google gave you; the diagnosis is still your own work, and it is the part worth doing properly — which is what our advanced SEO strategy level spends its time on.

What is still unknown

Which spam policies this update enforced. How many sites were affected, in which markets and languages. Whether the three volatility waves were one system landing in stages or three unrelated things. Whether a longer rollout implies a wider one. How long recovery takes in anything more precise than “months”. Whether the next spam update returns to a two-day rollout — one data point is not a trend, and August, June and March all argue the other way.

The one thing that is now settled is the window, and a settled window is worth more than a theory. If you want the ground underneath all of this — how Google discovers, indexes and ranks before any update touches it — start with how Google works.

Sources

• Google Search Status Dashboard, incidents.json, read live three times on 9 October 2026 — begin, end and both status notes for the September 2026 spam update, and the begin and end timestamps for every 2026 spam and core update. All durations in this article are our own arithmetic over that file.
• Google Search Central, Google Search’s spam updates, Last updated 2025-12-10 UTC, read twice on 9 October 2026 — no rollout duration, no reconsideration, recovery stated only as “a period of months”.
• Barry Schwartz, Search Engine Roundtable, 6 October 2026, on the third volatility wave of 4–6 October, and 8 October 2026, “Google September 2026 Spam Update Has Finished Rolling Out”.
• Search Engine Journal, 8 October 2026, “Google Completes September 2026 Spam Update After Nearly 14 Days”.
• PPC Land, 8 October 2026, “Google’s spam update ends after nearly 14 days”, which reports 13 days 16 hours and 19.5 hours for the March update.
• Gary Illyes, Search Central Live Deep Dive Europe, Barcelona, 2 October 2026, as relayed by John Campbell’s recap on LinkedIn and rendered by PPC Land (3 October 2026) and Relevant Audience (4 October 2026). The original recap blocks automated retrieval and could not be read directly.