Google’s September 2026 Spam Update Is Done: Dates, Waves and What to Check

Google’s September 2026 spam update is finished. The Google Search Status Dashboard marked it complete on October 8, 2026, after 13 days and 16 hours. That is the longest rollout of Google’s four spam updates this year.

This piece covers when it started and ended, how long it took compared with recent spam updates, and when rankings moved, as tracked by Search Engine Roundtable. It also covers what Google said, and a separate author warning Google published the same week. It closes with a checklist for comparing your Search Console data against the dates.

The short version: the update ran from September 24 to October 8. Ranking tools showed movement in three stretches: September 25 to 27, around September 30, and October 4 to 6. Google named no target and announced no new policy. If your traffic dropped, compare your Search Console numbers against those dates before you change anything.

When the September 2026 spam update started and finished

The dates come from Google’s incident page for the update on the Search Status Dashboard. Times are Pacific.

The dashboard’s history page lists the duration as 13 days, 16 hours. Search Engine Land reported the finish the same morning and called it "almost 14 days." Both count the same window.

Google’s start note said the rollout "may take up to two weeks to complete." It came in just under that.

How 13 days compares with recent spam updates

Every spam update since 2024 is on the dashboard’s ranking updates history. Here is how long each one took.

The three spam updates earlier in 2026 each finished in under three days. September took five times as long as the slowest of them. Over a longer view it is ordinary. The March 2024 update took almost 15 days, and the August 2025 update took almost 27.

The length matters for one practical reason. A two-day update leaves a short window to look at. A two-week update spreads possible changes across a longer stretch, so other causes are more likely to overlap with it.

Google’s John Mueller had told Search Engine Roundtable at the start that this one would likely take longer than some of the previous ones. Google gave no reason for the longer rollout.

The three volatility waves, as tracked by Search Engine Roundtable

Google did not describe any phases. Search Engine Roundtable did, based on rank-tracking tools and site owner reports. Barry Schwartz listed the impact dates when the rollout ended:

• September 25 to 27. The first wave, starting the day after launch.
• September 30. On October 1, he said that day "may have been the second wave," possibly running into October 1.
• October 4 to 6. A third spike, which he expected to be the last.

Search Engine Land’s report gives the final stretch as October 4 to 7.

Schwartz notes these dates assume Google made no other ranking changes during the rollout. The tools he cites, including Semrush, Sistrix, Mozcast and AccuRanker, publish volatility charts. They show that rankings moved on those days. They do not show which sites moved or why.

Treat the waves as a guide for where to look in your own data. A drop that lines up with one of them is worth a closer look. A drop that started on September 15 is not this update.

Who moved: what named sources said

No tool or analyst has published a list of sites the September 2026 spam update hit, as far as we found. What exists is narrower.

Glenn Gabe, who tracks Google updates, posted on October 1 that he believed Google made "a specific change on 9/30," according to Search Engine Roundtable. He said site owners had emailed him about a "huge drop right on 9/30." He did not name them.

Gabe also reported that Reddit’s AI-translated pages were surging again in Italy, Germany, Brazil, France and other countries. He had earlier reported that they fell after the May 2026 core update and the June 2026 spam update. That is one analyst’s observation about one site, not a finding about the update as a whole.

Search Engine Roundtable also quoted forum posts about Google Discover and Google News traffic swinging. Those came from unnamed forum members, so we do not repeat them as findings.

What Google said about the September 2026 spam update

Google’s dashboard posts are short. In full, the start note said: "Released the September 2026 spam update, which applies globally and to all languages. The rollout may take up to two weeks to complete." The end note said: "The rollout was complete as of October 8, 2026."

Google also described it on LinkedIn as a normal spam update, according to Search Engine Roundtable.

What Google did not say is just as useful. It did not name a type of spam. It did not call it a link spam update. It did not announce a new or changed spam policy. It did not say what share of queries changed.

Google’s spam updates documentation still applies. Sites that break its spam policies "may rank lower in results or not appear in results at all." Recovery can come once "our automated systems learn over a period of months that the site complies with our spam policies." For how spam updates work in general, see our explainer on what a Google spam update is.

Google’s separate warning about fake author information

The same week, Google added a warning to its guidance on creating helpful content. The page shows it was last updated October 5, and Search Engine Roundtable reported the change on October 6.

The new text tells site owners to "avoid using deceptive authorship information." Its examples include "AI-generated headshots, made-up names, or false credentials." It adds: "Any form of deception makes a page untrustworthy to both users and our automated quality systems."

This is quality guidance, separate from the spam update. Google did not connect the two. It matters to small sites because bylines are often loose. A generic "staff" byline, a post credited to a leader who did not write it, or an invented persona for a content program all deserve a second look. We will cover the guidance in full in a separate post.

Before you open Search Console: the dates to compare

Write these down first. They frame every check of the September 2026 spam update.

• Before window: September 10 to 23, the two weeks before launch.
• Rollout: September 24 to October 8.
• Wave dates: September 25 to 27, September 30, and October 4 to 6 or 7.
• After window: October 9 to 22, once you have that data.

Google’s core updates guidance suggests waiting at least a week after an update finishes before judging the impact. The same patience makes sense here. Mid-rollout numbers move around.

Two weeks before and two weeks after keeps the same days of the week in each window. That matters for nonprofits and associations, whose traffic often dips on weekends.

A Search Console checklist for the September 2026 spam update

This is written for nonprofits, associations and small publishers. Work through it in order. Most steps take a few minutes.

1. Compare the windows. In the Performance report, open the date filter and choose Compare. Google’s help page on comparisons explains the steps. The results table then shows a Difference column.

2. Look at the daily line. A sudden step on a wave date points at the update. A slow slide over months points elsewhere.

3. Sort pages by the difference. A drop concentrated in one section, such as a sponsored area, an events directory or old blog archives, tells you where to look.

4. Split branded from unbranded queries. Add a query filter with your organization’s name. Branded searches rarely fall in a spam update.

5. Check Manual Actions and Security Issues. Both sit under Security and Manual Actions. Hacked pages are the most common way a legitimate site breaks a spam policy. Recent flaws like Click2Shell in WordPress are how that starts.

6. Check for borrowed authority. Third-party or partner pages can fall under the site reputation policy.

7. Rule out AI answers. If impressions held and clicks fell, look at Search Console’s generative AI performance report. The pattern we described in publisher traffic collapse at small scale is a slow slide, not a step.

8. Write it down. Note the dates, the sections affected and what you ruled out. If nothing lines up with the update, it is likely something else.

Frequently Asked Questions