Google September 2026 Spam Update: What We Know

Google began rolling out the September 2026 spam update on 24 September at 9:15am PDT and says it may take up to two weeks to complete. That is the longest stated rollout window of any spam update this year. Google has not named the tactics it targets, which is normal for spam updates and unhelpful if you are trying to work out whether this week's traffic change is yours or theirs. Here is what is actually confirmed, and what a two week window means for reading your own numbers.

What is confirmed about the September 2026 spam update

Three things, and only three. The update exists and is listed as a ranking incident on Google's Search Status Dashboard. It started on 24 September. Google says the rollout may take up to two weeks.

Everything else circulating right now is inference. Google published no new spam policy alongside it and named no specific tactic, per Search Engine Journal's coverage of the announcement. The company's standing advice is the same as every spam update: if you see a ranking or traffic change, review the spam policies.

Worth noting for anyone who has been following the last few weeks of SEO commentary. Through most of September, aggregators were reporting an "August core update" finishing its rollout. That was never on Google's own dashboard. This one is. The dashboard is the thing to check.

What the spam policies actually say about volume

Since Google points at the spam policies rather than at the update, the policies are where to look. The one that matters most to anyone publishing at pace is scaled content abuse, which covers generating many pages primarily to manipulate rankings rather than to help people. The policy is written around purpose and value, not around word count, publishing frequency, or whether a machine was involved.

That distinction does real work. Google's documentation has been explicit for a while that AI assistance is not itself a violation. A hundred pages that each answer a question somebody actually has is not the same artefact as a hundred pages spun from a template to catch keyword variants, even though both are a hundred pages published quickly. We have written about where that line actually falls before, and nothing Google published this week moves it.

This blog publishes at volume, so the tension is ours too. Stating that plainly seems better than pretending otherwise.

Why a two week rollout wrecks your attribution

This is the practical part, and it gets less attention than it deserves. A rollout that takes two weeks means rankings move gradually and unevenly across queries and regions. For most of that window you cannot tell a spam update effect apart from ordinary volatility, a seasonal shift, or something you changed yourself.

Some concrete consequences:

• A drop on day three is not evidence. Partial rollouts routinely reverse before they finish.

• If you ship a site change during the rollout, you have permanently confounded the two. Freeze what you can.

• Search Console data lags by two to three days, so your last usable pre-update baseline is roughly 21 September.

• Comparing this week to last week measures the rollout midpoint against the rollout start, which is close to meaningless.

The useful move is to write down your pre-update baseline now, by query group rather than in aggregate, and then leave it alone until Google marks the rollout complete. Aggregate sessions hide the pattern that tells you whether a spam update touched you, which is a sharp move on a specific cluster of pages rather than a gentle site-wide slide.

What to do this week

1. Record the baseline. Export Search Console query and page data through 21 September before it rolls out of the window.

2. Freeze non-essential changes until the rollout completes, so that anything you do see is attributable.

3. Read the spam policies properly rather than the summaries of them. They are short.

4. If you do get hit, Google says compliance improvements can take months to register, so the recovery clock starts late. Plan accordingly.

One thing not to do: rewrite your content strategy on day two of a fourteen day rollout based on a dashboard wobble. That is how sites end up making a real change in response to noise. If you want a durable read on where search is heading for AI-assisted publishers, how citations work in AI Overviews has aged better than most update commentary, and keeping a sane AI news routine will save you from the next round of aggregator noise.