Google released its September 2026 spam update on September 24, 2026 — a global update applied across all languages, with a rollout that unusually took two weeks, completing on October 8, 2026. The most defensible summary of the numbers available so far: a moderate median hit (−6% in the best available agency study), an uneven tail where some sites lost far more, and recently updated pages outperforming — with no evidence in any published dataset that AI-drafted content as such was targeted. A spam update is, in Google’s own spam updates documentation, a “notable improvement” to its automated spam detection — not a manual action, and not something Google pre-announces with a target list. Sites violating its policies “may rank lower in results or not appear in results at all,” and Google declined (per dated coverage, below) to say what share of queries were affected. Everything below separates the official record from the observational data, because the two are not the same thing.

What exactly did Google say about the September 2026 spam update?

Google’s official record is short, and it lives on its Search Status page (accessed 2026-10-29): an incident opened September 24, 2026 at 09:15 PDT stating, “Released the September 2026 spam update, which applies globally and to all languages. The rollout may take up to two weeks to complete,” closed on October 8, 2026 with, “The rollout was complete as of October 8, 2026.” Beyond that, the spam-updates doc supplies the standing mechanics: these updates improve automated spam detection, affected pages may rank lower or drop from results, and recovery is possible — “Making changes may help a site improve if our automated systems learn over a period of months that the site complies.”

The color around that comes from dated coverage, not Google itself. Seroundtable (Barry Schwartz) reported on October 8, 2026 that the rollout began September 24 around 12:00 pm ET and completed October 8 at 4:37 am ET — an unusually two-week rollout, where prior spam updates took about two days. It reported that Google told Schwartz via LinkedIn, “This is a normal spam update,” that the update does not target link spam, and that Google declined to say what percentage of queries are impacted. The same coverage identified September 25–27, September 30, and October 4–6 as observed volatility dates — treat those as reported volatility windows from coverage, not as dates Google published.

Two practical consequences of that official record. First, if you did not receive a spam-notification in Search Console, that tells you little either way — spam updates run automatically and most affected pages are never individually notified. Second, Google’s own language frames the aftermath in months, not days, which matters for how you plan recovery below.

What did the 100-site study find?

The most specific public dataset comes from an agency study published on r/SEO on October 23, 2026 by u/tjrobertson-seo: how roughly 100 SMB client sites, all with AI-drafted content, fared against the September 2026 spam update (the thread has since been removed by moderators; the findings below were verified against a snapshot of the post). The method: Google Search Console traffic for September 11–21, 2026 compared with October 9–19, 2026, plus the same weeks in 2025 and a pre-rollout control window (August 25–September 5 vs. September 15–20). It is an observational, self-selected portfolio study — no control group in the causal sense, no spam-notification data — so every number below is correlational, not causal.

MetricValue (Oct 9–19 vs. Sep 11–21, 2026)What it does and doesn’t show
Median traffic change vs. the site’s own fall pattern−6% (half of sites within −19% to +12%)A moderate median across ~100 AI-drafted SMB client sites; not causal, and not representative of all websites
Sites with big swings32% (vs. 48% for the same period in 2025)The update was calmer than the 2025 one for this portfolio; one self-selected sample
Pages shifting ≥3 positions27% (vs. 35% in quiet weeks)Rankings were comparatively stable — an update this quiet on position data is unusual; a GSC sample, not evidence about any individual page
Clicks on pages that held their rankings≈ −12%, driven by falling impressionsImpressions can fall even when positions hold; does not explain why the impressions fell
Timing of the impressions slideBegan before the Sep 24 rolloutSome of the decline pre-dates the update; no share of it can be cleanly attributed to the update
Worst-performing pagesTemplated location and program pagesAn observational pattern in this portfolio; not proof that templated pages are the update’s target
“Near me” queries−11%Query-family movement in the sample; consistent with query-distribution shift rather than demotion, but cannot prove it
8+ word queries−7%Same caveat as above
Clicks, pages updated in the last 30 days1,059 → 1,302 (+23%)Updated pages outperformed the portfolio median; observational, not a cause-and-effect guarantee
Clicks, new pages306 → 571 (+86%)Same as above

The author’s own read is worth quoting in full because it is more restrained than most of the commentary: “I don’t see anything that looks like Google penalizing content for being AI-drafted. What it looks like is Google going after the flood of low-value pages built to game search results.” We agree with that restraint, and we add ours: the study measured a portfolio of AI-drafted client sites, so it cannot isolate the cause of any site’s decline. AI-drafted content, templated pages, seasonal fall patterns and the update all moved at once in the same window. “Google is punishing AI content” is not a claim any published dataset supports.

What did Diib’s broader data show?

Diib, a website-reporting vendor, published early data on September 29, 2026 from 32,569 sites connected via Google Analytics: median search traffic share fell from 34% to 31%, and 10% of sites lost half or more of their search share, versus 5% the prior week. Diib called it “an early read, not a verdict,” and its data cannot show which sites Google flagged. That is vendor data with its own selection, not a Google statement — but it points in the same direction as the agency study: a moderate median dip, with a tail of much harder hits concentrated somewhere in that 10%.

Diib’s 2026 insights also contain a recovery datapoint relevant to planning: two in three websites that lost search traffic around a 2026 Google update were still down six weeks later. Again, vendor data, observational — but if it holds, “give it six weeks” is the wrong default. Expect the recovery horizon to be longer.

What should you do if your traffic fell?

Start with Google’s own recovery guidance from the spam-updates documentation, then layer on the moves that the observational data associates with better outcomes. None of this is a promise that traffic will return; the honest framing is what to review, what to fix, and how long to wait.

  • Review your site against Google’s spam policies. This update is a spam detection improvement, so the relevant audit is the spam-policy list, not a checklist of ranking tactics. Google says changes “may help a site improve if our automated systems learn over a period of months that the site complies” — months is the official unit of time.
  • Hunt for templated, thin pages. In the 100-site study, templated location and program pages fared worst — an observational pattern, but it matches Google’s long-standing position on scaled, low-value pages. Pages that differ only by a swapped city, product or keyword are the first candidates to prune, merge or redirect, with real unique detail added to what you keep.
  • Watch impressions, not just rankings. The study’s clearest mechanism was the one that surprises people: pages that held their rankings still lost about 12% of their clicks because impressions fell. A position-holding site can be bleeding traffic invisibly to a rank tracker. Check Search Console impressions by query family — the study’s −11% on “near me” and −7% on 8+ word queries are the kind of query-level shift worth separating from outright demotion. And keep the broader point in mind that ranking health and the traffic you actually receive are not the same metric — a divergence the ranking #1 but skipped by AI answers post works through for the AI side.
  • Update what you keep. Pages updated in the last 30 days (+23% clicks) and new pages (+86%) outperformed the portfolio median in the study. That is observational, not a guarantee — but refreshing genuinely stale or thin pages with specific, first-hand content is worth doing regardless of the update, and it costs nothing against the official recovery timeline. The mechanism worth understanding — which queries actually reward current content, and why a date bump is not one — is worked through in does content freshness affect SEO.
  • Don’t chase links as a rescue. Google’s coverage reporting says this update does not target link spam, and nothing in the data suggests buying a rescue-link package would move anything. Links matter — but as a slow, earned record, covered in how many backlinks you actually need — not as a post-update lever.
  • Set the patience budget in months. Google’s own language is “over a period of months,” spam updates are periodic, and Diib’s data says most losers were still down at six weeks. If you have made the compliance changes and the templated pages, log what you changed and when, then wait for impressions to move before concluding the work failed.

What the data does not show

Honest limits, stated once and clearly:

  • No causal proof. The agency study is a self-selected portfolio of ~100 AI-drafted SMB sites with comparison windows, not a controlled experiment. It can’t attribute any specific site’s change to the update, and it can’t isolate AI-drafted content as a variable. Diib’s numbers are vendor-collected and vendor-framed.
  • No notification data. Neither dataset includes Search Console spam-notification records, so no one can say what share of affected sites were flagged, or whether a specific page was.
  • No query-share figure from Google. Google declined to say how much of the query stream was impacted; any precise percentage you see quoted is not from Google.
  • Not representative of all websites. The study is one agency’s client portfolio. A site with a very different profile — strong local presence, no templated pages, no AI-drafted scale — may have seen nothing.
  • No verdict on AI content. The absence of evidence for an AI-content penalty is not evidence that no such system exists; it is evidence that none is visible in published data as of this writing.

Where to go from here

If your Search Console shows a step-change around the late-September volatility windows and you are not sure what to fix first, the order above is the order to run it: spam-policy review, templated-page audit, impressions-by-query-family, refresh the survivors, then wait in months not days. If you would rather have the audit done against our measurement baseline — the query mapping, the templated-page list, the impressions trend and a logged change record so you can tell afterward whether it worked — that is exactly what we run end to end, and the full process is in our methodology.