Google's scaled-content spam enforcement, 2026

Google’s spam policy has said the same thing since before 2026: scaled content abuse is about outcome, not tooling. What changed this year is the surface area the policy covers and how visibly Google enforced it. Between the March 2026 core update and the August 2026 spam update, the industry’s read on that enforcement came almost entirely from independent case-study work, because Google itself does not publish the numbers.

What the policy actually says#

Google’s spam-policies page defines scaled content abuse as “many pages… generated for the primary purpose of manipulating search rankings and not helping users,” and is explicit that the test is “no matter how it’s created.” Generative AI is listed as one method among several - alongside scraping, automated transformation, and stitching content together - not as a prohibited category on its own. A site can publish AI-written pages and stay clear of the policy; the policy is triggered by scale without editorial value, whatever produced it.

On 15 May 2026, Google revised the policy’s introductory line to add “attempting to manipulate generative AI responses in Google Search.” Search Engine Land read the change as a clarification that spam tactics aimed at AI Overviews, AI Mode and other AI-generated responses can be treated as spam under the existing policies. A page built to be cited in an AI answer through the same manipulative patterns Google already prohibited in classic rankings is now unambiguously in scope for the same enforcement.

What enforcement looked like#

Google’s Search Status Dashboard lists spam updates in 2026 in March, June and August. The August one started on 18 August and ran 2 days, 16 hours, completing on 21 August. Spam updates re-apply existing policy rather than re-scoring the index the way a core update does, so a site hit by one has a specific practice to point to, not a general quality verdict.

Analyst Glenn Gabe of GSQi published four blinded case studies from the August update, each tied to a scaled or AI-generated content pattern: a programmatic, AI-generated site in an ultra-YMYL niche; a thin Amazon affiliate site built substantially with AI-generated content; a site with over 1.5 million indexed URLs, about 85% of them programmatic pages, hit across sections; and a site combining scaled content abuse with redirects to other risky sites. Reported losses ranged from just over 14,000 queries on the affiliate site to more than 200,000 queries on the YMYL programmatic site. None of these figures come from Google; they are Gabe’s read of each site’s own visible query data, and he named them as such.

The limit of what can be said here#

Google has never released a page-count or site-count for spam enforcement, in 2026 or any other year. The Search Status Dashboard confirms that an update ran and for how long; it says nothing about how many URLs it touched. That gap is why this report leans on Gabe’s named, attributed case studies rather than an aggregate percentage: a range presented as “typical impact” without a named source and a stated sample is not a figure this site will publish, however often it circulates in search results and forum threads.

Why we care#

If a content programme on your site scales production - AI-written, scraped, or templated - the policy test that matters is whether a human reader would call an individual page worth publishing on its own, not whether the tooling that made it was AI. Before the next spam update lands, audit by practice rather than by page: identify anything published at a volume no editorial process reviewed, and decide whether it would exist if search traffic were removed from the calculation. That is the same question Gabe’s case studies answer for the sites he named, and it is the one Google’s own wording points to before any update arrives.