How Long Does a Google Spam Update Take?

What the dashboard is, and why we used it

When a ranking change lands on a client's site, the first question is always the same: is this an update, and when will it be over? The answer most people reach for is a recollection, or a figure from an SEO newsletter. There is a better source, and almost nobody reads it end to end.

Google runs a Search Status Dashboard. Its help page says the dashboard “shows the latest ranking updates made to Google Search that are relevant to website owners”, alongside outages and crawling incidents. Every ranking update gets an incident page with a start time, a short release note, usually a stated rollout window, and later a line saying when the rollout was complete. The history page for the Ranking product then prints a duration for each one.

That makes the dashboard the only public record of update timing that comes from the party that runs the updates. On 1 October 2026 we read the Ranking history page and opened every incident linked from it — 42 pages — and recorded the start, the stated window, the completion line and the posting timestamps. Everything below comes from those pages. Where we compare a stated window with an actual duration, both numbers are Google's.

The prompt was the September 2026 spam update, which Google posted on 24 September. It is a good moment to ask the question properly, because the answer people have been carrying around for spam updates — “they are quick” — is true for some years and wrong for others.

Spam updates and core updates are different instruments. Google's spam-updates page describes SpamBrain as an “AI-based spam-prevention system” that it improves “from time-to-time”, and says a site hit by one should review the spam policies. Core updates, which we cover in what happens in a Google core update, are broad re-weightings that Google says do not target specific sites. The policies the spam updates enforce — scaled content abuse, site reputation abuse, expired domain abuse — each have their own guide on this site. This one is only about time.

The first fifteen entries were written in a single morning

The first thing the incident pages show is that the dashboard is not, for its early years, a contemporaneous log.

Every incident page carries a table of updates with their own timestamps. For the November 2021 spam update, the release line and the completion line are both timestamped 22 March 2023, at 06:28 and 06:29 Pacific. The same is true of every entry after it up to and including the February 2023 product reviews update, which were posted in sequence between 06:28 and 06:52 that morning. The March 2023 core update, which began on 15 March, has its release line posted at 06:53 on 22 March too, and its completion posted live on 28 March.

So fifteen entries, covering sixteen months of updates, were entered retrospectively on one day. That does not make their dates wrong — the completion lines give specific “as of” dates, and the durations are calculated from them — but it does mean those entries had no stated window at the time, could not have been watched live by anyone, and show whole-day durations with no hours. For the timing analysis below we use the live record: the 25 named updates from the April 2023 reviews update to the September 2026 spam update, each posted on the day it began.

One more irregularity is worth recording. The March 2024 core update's completion line reads “The rollout was complete as of April 19, 2024”, but it was posted on 26 April. For a week, anyone watching the dashboard would have believed the update was still running. That is the only completion in the live record posted more than a day late.

How long spam updates actually took

The live record holds nine spam updates. Eight have finished. Their durations, in the dashboard's own figures, are below.

Two things stand out. The first is the range. A spam update in this record has taken less than a day and has taken nearly four weeks. There is no stable “spam update length” to carry around in your head, and the median of about seven days describes almost none of them: three finished in under three days and three took two weeks or more.

The second is the trend. The 2026 spam updates have been short. March 2026 finished in 19 and a half hours, June in two days and an hour, August in two days and sixteen hours. All three were announced as taking “a few days”, and all three did. The longest spam update in the record, August 2025, was announced as taking “a few weeks” and took 26.6 days. On this evidence the announcement wording has been a reasonable guide to spam update length since 2025, which is why the September 2026 wording matters: it says “up to two weeks”.

For core updates the picture is longer and steadier. The twelve core updates in the live record took 6.2, 11.9, 12.2, 13.9, 14.0, 16.1, 16.8, 18.1, 19.2, 23.5, 25.9 and 45 days. The median is 16.4 days. The February 2026 Discover update, which the dashboard lists under Ranking and which took 21.7 days, is not counted with them because it applied to Discover rather than to web results.

The stated window against what happened

Most live incident pages say how long the rollout should take: “may take up to 2 weeks to complete”, “up to 1 week”, “up to 3 weeks”, “up to a month”, or a vaguer “a few days” or “a few weeks”. Seventeen of the completed live updates gave a window in weeks or a month that can be checked against the result. We counted “up to a month” as 31 days, which is the generous reading.

Nine finished inside their window. Eight did not.

The honest summary is that the stated window is a planning estimate, not a ceiling. Three of the eight overruns were by less than a day, inside the precision of the record. Five were not: four core updates and the February 2026 Discover update ran between two and fourteen days long. The windows got more accurate in 2025 and 2026, when Google gave two core updates an “up to 3 weeks” window and both finished inside it, but the most recent overrun is February 2026.

For a spam update in particular, the practical rule from this record is to treat the window as the earliest point at which a recovery read is fair, not the point at which the system has settled. That matters for the September update. If it runs to its stated limit, it completes around 8 October 2026. If it behaves like the 2024 spam updates that overran by a day, the dashboard will say so a day later.

Four spam updates in nine months

The other change in 2026 is frequency. Counting named spam updates on the dashboard by the year they began: one in 2021, two in 2022 (including the December 2022 link spam update), one in 2023, three in 2024, one in 2025 and four in 2026 so far — March, June, August and September. 2026 has already had more spam updates than any other year on the record.

Shorter and more frequent spam updates is a pattern, not an explanation; the dashboard gives no reasons and we will not invent one. What it changes in practice is the odds of overlap. In March 2026 a spam update finished on the 25th and a core update began on the 27th. In March 2024 a core update and a spam update began within a minute of each other on the 5th, and the core update ran for 45 days. A site owner looking at a traffic line through either period has no way, from Google's record, to say which system moved them.

What a duration can and cannot tell you

A duration is the time between Google saying an update began and Google saying the rollout was complete. It is not the time it takes a site to be affected or to recover, and Google is explicit about the gap. Its spam-updates page says that “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”. For link spam it goes further: when the systems remove the effect of spammy links, “any ranking benefit the links may have previously generated” is lost, so changes “might not generate an improvement” at all.

So the dashboard answers a narrow question — when is the turbulence officially over — and that question has a practical use. Anyone diagnosing a drop needs to know whether they are looking at a site still inside an active rollout, and anyone being sold a fix needs to know that a recovery claimed inside the window is a claim about noise.

For companies whose visibility rests on coverage rather than on their own pages, the relevant spam policies are mostly about the host: a placement on a site later demoted for site reputation abuse loses its search value with the host's, which is covered in does site reputation abuse apply to placements. And the speed at which anything new is picked up in the first place is a separate measurement, set out in how long Google takes to index a new page.

Methodology and limitations

On 1 October 2026 we fetched the Google Search Status Dashboard's Ranking history page (status.search.google.com/products/rGHU1u87FJnkP6W2GwMi/history) and each of the 42 incident pages it links to, using curl with a standard browser user-agent string. From each incident page we took the incident title, the release text, the stated rollout window where one was given, the “rollout was complete as of” date, and the timestamp of each posted update. Durations are the dashboard's own figures from the history page, converted to days. We also read incidents.json, the dashboard's machine-readable feed, which covers only the ten most recent incidents and agreed with the HTML pages for all of them. The live record is defined as the named updates whose release line was posted on the day they began: the 25 updates from April 2023 to September 2026. A numeric window means “up to 1 week” (7 days), “up to 2 weeks” or “about two weeks” (14), “up to 3 weeks” (21) or “up to a month” (31); “a few days” and “a few weeks” were not scored. Five limitations apply. First, completion lines give a date without a time, so durations are precise to roughly a day, which is why we flag overruns of under a day as immaterial. Second, the dashboard records only what Google chose to announce; unannounced ranking changes are absent by design, and the November 2023 reviews update page itself says Google would stop posting future reviews-system changes. Third, the fifteen backfilled entries have no contemporaneous window and are excluded from the window analysis. Fourth, the dashboard says nothing about which sites were affected or by how much, so nothing here measures impact. Fifth, the September 2026 spam update was still open when we read it, and its duration is unknown.

Conclusion

Google's own dashboard is the only first-party record of how long its ranking updates take, and read end to end it says three useful things. Spam updates have no typical length: the live record runs from 19 hours to nearly four weeks, with a median of about a week that describes few of them. The stated window is an estimate rather than a ceiling, with eight of seventeen numeric windows exceeded and five of those by two days or more. And 2026 has been unusual on both counts, with four spam updates by September and the first three finishing in under three days as announced. The September 2026 spam update breaks that pattern on paper, announced as taking up to two weeks, and was still running when we read it. The practical use is narrow but real: before diagnosing a ranking change, check whether an update is open; do not read recovery into the days inside a window; and expect Google's own timeline to run long about half the time it gives one.

Frequently Asked Questions

Sources

1. live read Google, Google Search Status Dashboard: all incidents reported for Ranking. 42 incidents, November 2021 to September 2026, with durations. Read 1 October 2026.
2. live read Google, Search Status Dashboard incident pages, one per incident, linked from the history page; for example September 2026 spam update, August 2026 spam update, August 2025 spam update and March 2024 core update. Release text, stated windows, completion lines and posting timestamps. All 42 read 1 October 2026.
3. live read Google, incidents.json. Machine-readable feed of the ten most recent incidents; the September 2026 spam update listed with a begin time of 2026-09-24T16:15:00Z and no end. Read 1 October 2026.
4. documentation Google Search Central, Using the Google Search Status Dashboard. The dashboard “shows the latest ranking updates made to Google Search that are relevant to website owners”. Read 1 October 2026.
5. documentation Google Search Central, Google Search Spam Updates. SpamBrain as an “AI-based spam-prevention system”; improvement only if systems “learn over a period of months”; link spam changes “might not generate an improvement”. Read 1 October 2026.
6. trade press Semrush, Google September 2026 Spam Update: What to watch, and Search Engine Roundtable, Google September 2026 Spam Update Weekend Impact. Contemporary coverage of the update that prompted this report; no figures from either are used above.