Google begins September spam update with global rollout

Google has begun rolling out its September 2026 spam update across all languages and regions. The Search Status Dashboard records the start at 9:15 a.m. Pacific on September 24 and says the rollout may take up to two weeks. Google Search Central said it will update the ranking release history when the rollout is complete.

Google has not identified a particular spam tactic this update targets. Calling it a link-spam update, an AI-content crackdown, or a change to one named policy would go beyond the announcement.

What has been confirmed

This is a Search ranking update, not a reported crawling or indexing outage. The dashboard lists its scope as global and all-language. It does not yet have a completion entry, so September 24 is the beginning of the observation window, not a before-and-after result.

It is the fourth spam update listed in Google’s 2026 dashboard history, after updates in March, June, and August. The August update finished in roughly two days and 16 hours; Google’s up-to-two-weeks estimate for September is a rollout allowance, not evidence that this update targets more sites or uses a different mechanism. Our August spam-update diagnosis shows why even a completed rollout needs careful traffic comparisons.

Google’s standing spam-update guidance says its automated spam-detection systems operate continuously and that it announces notable improvements. It advises sites that see a change after an update to review the spam policies. That is general guidance, not a disclosure of what changed in September.

A traffic drop is a question, not a verdict.

If your Search traffic shifts during the rollout, save the unedited baseline first: daily clicks and impressions for the affected pages and queries, with country, device, and search type held constant. Note the time of any site release, migration, analytics change, or indexing incident. Then compare the same segments after Google reports the rollout complete. Google’s traffic-drop guide treats algorithm changes as one possible cause alongside technical and demand changes.

A decline alone does not tell you which policy, if any, a page violates. Nor does it mean Google issued a manual action. Fix a verified problem that harms readers or blocks Google, regardless of the update. Avoid deleting or rewriting pages solely because a graph moved during an unfinished rollout. For a deeper diagnosis, our ranking-volatility guide shows how to preserve a fixed comparison segment before editing.

The next firm milestone is Google’s completion notice on the incident page. Until then, the confirmed story is the rollout’s start, scope, and estimated duration, not its measured effect on publishers.

A new SAFE paper does not identify this rollout’s mechanism

Google Research published a paper on SAFE, a multi-agent system for investigating coordinated synthetic-video channel clusters. Its public evaluation section does not report numerical effectiveness results, and neither the paper nor Google’s Search Status Dashboard says SAFE is part of this September Search spam update. The paper audit separates the architecture Google describes from a Search ranking claim. Do not treat publication of the paper as an explanation for a site’s traffic loss.

Separate a real traffic decline from its possible causes

The official incident record still has no completion entry at our September 30 check. A site-owner discussion about sudden losses is a useful diagnostic question, but an unverified report is not evidence that this rollout caused the loss or targeted a named tactic.

Start with the system closest to the observation. If an Analytics chart is empty but Search Console clicks and server requests remain normal, investigate reporting and collection before rewriting content. If Google clicks and search landing-page requests both decline, the loss is better corroborated, but its cause remains open. If important pages return errors or acquire a noindex directive, fix that concrete availability or indexing problem without waiting for the rollout to finish.

In a clearly hypothetical case, a daily page segment falls from 100 Google clicks to 5 while its corresponding server requests also fall and other channels remain stable. That supports a search-specific decline. It does not prove spam enforcement: query demand, ranking, result presentation, and indexing still need examination. Compare the same pages, queries, country, and device, and inspect affected URLs before choosing a remedy. Google’s traffic-drop guidance provides the broader diagnostic route.