Google has confirmed that the September 2026 Spam Update is now rolling out. The announcement names the rollout itself, but the company has not yet specified which spam systems the update targets, how long the rollout will take, or how it will interact with other spam policies currently in force.

This is a confirmed search-engine statement: Google says the update is rolling out. Everything below about likely impact, timing, and what to watch is analysis and tool-signal speculation, not confirmed by Google, and is labeled as such.

What we know from Google

The confirmed facts are narrow. The update is called the September 2026 Spam Update. It is rolling out now. Google has not published a percentage-of-queries impact figure, a rollout duration, or a list of targeted behaviors alongside the announcement.

That level of brevity is consistent with how Google has historically handled spam updates: short confirmations on its status dashboard, followed by a completion notice days or weeks later. Until Google posts that completion notice, the rollout remains open, and ranking volatility tied to it can continue accumulating.

What remains unconfirmed

Several practical questions lack answers in the announcement.

First, which enforcement layer does this update touch? Google operates distinct spam-fighting mechanisms, including SpamBrain, site reputation abuse enforcement, scaled content abuse policies, and link spam systems. The announcement does not say which of these the September 2026 update strengthens. Any claim about a specific system would be speculation.

Second, the rollout window. Google has not stated an expected completion date. Third, the magnitude. No percentage of affected queries or searches has been disclosed, so any volatility percentages circulating from third-party tools measure crawler-observed flux, not Google-confirmed impact.

How to read early volatility signals

Ranking trackers will likely show flux in the coming days. Treat those readings carefully. Tool-signal speculation, not Google statements: volatility spikes during a spam-update rollout often concentrate on sites with aggressive link patterns, thin or replicated content at scale, or sites previously flagged under Google's spam policies. Publishers in competitive verticals — health, finance, e-commerce aggregators, and coupon or deal sites — typically see the widest swings because spam pressure is highest there.

Flux in a tracker does not prove a penalty. Normal algorithmic churn overlaps with any multi-week rollout. Distinguish recovery patterns from demotion patterns: a site climbing during a spam update may be regaining positions lost to spam it previously competed against, not gaining from new tactics.

Practical guidance while the rollout is open

Site owners should avoid reactive changes mid-rollout. Google has long advised waiting until a rollout completes before diagnosing impact, because positions can shift repeatedly before the final state settles.

If a site drops sharply and stays down after Google posts the completion notice, review Google's spam policies directly rather than chasing tool scores. Spam updates enforce existing policies; they do not introduce new ranking factors. A sustained loss after completion usually points to a policy violation — link schemes, scaled abuse, or site reputation abuse — rather than a content-quality deficit that a core-update-style content overhaul would address.

Sites that rely on licensed or syndicated content should re-check compliance with the site reputation abuse policy, since that enforcement area has seen repeated tightening. Sites with historical link-building baggage should expect that spam updates revisit old link patterns.

What to monitor next

Watch Google's search status dashboard for the rollout-completion notice, which will define the window for impact analysis. After completion, compare pre-rollout and post-completion rankings by page type and vertical to separate spam-driven demotions from unrelated churn. If Google follows its recent pattern, the completion post may arrive within one to two weeks of the start; until then, treat all mid-rollout volatility readings as provisional.