Google's September 2026 spam update finished after 13 days and 16 hours
Google has confirmed on its Search Status Dashboard that the September 2026 spam update, which started on September 24, 2026, completed its rollout as of October 8. The update is global and covers every language. The dashboard puts the total duration at 13 days and 16 hours, longer than any of the three spam updates Google ran earlier this year.
Nearly the whole two-week window was used
According to the Google Search Status Dashboard, the update went live on September 24, 2026 at 09:15 US Pacific time. Google's note that day described it as global, said it covered all languages, and warned that the rollout could need as long as two weeks. A second note, added at 01:37 PDT on October 8, is a single line: "The rollout was complete as of October 8, 2026."
The dashboard records the incident as running from 09:15 on September 24 to 01:00 on October 8, both in US Pacific time, for a total of 13 days and 16 hours. Search Engine Journal gives the same 1:00 a.m. PDT end time and points out that Google used almost all of the two weeks it had announced. We covered the August spam update on August 20; this is a separate, newer update.
The longest spam rollout of the year
Search Engine Journal's comparison shows how much shorter Google's three earlier 2026 spam updates were. March's ran for 19 hours and 30 minutes, June's for 2 days and 1 hour, and August's for 2 days and 16 hours. The same outlet also recalls a longer precedent, the August 2025 spam update, which ran from August 26 to September 22, 2025, roughly 27 days. So the September rollout is the longest of 2026, but not a record among Google's spam updates.
Google's documentation frames spam updates as meaningful upgrades to the automated systems it uses to spot spam. Search Engine Journal reports that, at the time of its article, neither that page nor the two dashboard notes explained what the September update targeted or why it ran longer than the earlier 2026 updates. Some early data exists: according to Search Engine Journal, Diib published figures on September 29 from 32,569 sites with Google Analytics connected. Comparing September 24 to 26 with the same days one week before, the median share of visits from unpaid Google search fell from 34% to 31%, and the portion of sites whose share was cut in half or more rose from 5% to 10%. Diib called this an early read rather than a verdict and said the data cannot show which sites Google classed as spam.
There is now a fixed window to compare against
With the rollout finished, September 24 through October 8 gives site owners a clear period for comparing Search Console data before, during and after the update. Search Engine Journal stresses that a decline in that period should not be blamed on the update by default. There is a measurement caveat as well: SEOmonitor, also as cited by Search Engine Journal, says many industry rank trackers registered abrupt ranking swings from September 26 that real Google searchers never saw, and it traces this to Google serving incomplete and inaccurate results to automated queries.
That points to a simple order of operations: check Search Console first. In the same report, SEOmonitor notes that spam-related shifts usually hold for several days and are often reflected in Search Console impressions and clicks. For sites whose rankings moved, Google's documentation recommends going through its spam policies, and Search Engine Journal adds that fixes can help once Google's automated systems pick up on compliance, a process that can take months. Recovery should not be planned as a matter of days.
The sources say nothing about Türkiye, so this section is commentary
Neither source contains anything specific to Türkiye or to Turkish-language sites. The one relevant fact is that Google announced the update as global and applicable to all languages, which includes Turkish searches. Everything beyond that below is UNALSOFT commentary, not sourced fact.
Our view: Turkish businesses whose organic traffic moved between September 24 and October 8 can use that window as a reference point, but they should start from impression and click changes that last several days in Search Console, not from a single rank-tracker chart. To be explicit about the unknowns: the sources do not cover how many sites in Türkiye were affected, whether any particular kind of spam stood out in Turkish results, or whether Google will comment specifically on Turkish search.
UNALSOFT's take
After a spam update, the first move is not deleting pages in a hurry but reading the right measurement. If Search Console shows a lasting decline, the site should be reviewed against Google's spam policies across content, page structure and linking practices, with the expectation that any payoff can take months. When we build a new site or rebuild an existing one, we treat that review as part of the web design process: if thin template pages are never produced in the first place, there is nothing to defend at the next update.
Did the update cause your traffic drop, or was it something else?
A short conversation is enough to read your Search Console data against the September 24 to October 8 window and review your site against Google's spam policies.