Core Update vs Spam Update: Which One Hit You?

This is the most consequential distinction in algorithm recovery, and in 2026 it became more important than ever. Google confirmed four spam updates and only two core updates, the first year spam outnumbered core.

When updates overlap, as they often do, the dates alone will not tell you which one hit you. The signals below will.

The two side by side

	Core update	Spam update
What it judges	Overall quality and relevance	Specific published spam policies
Scope of loss	Broad, across templates	Concentrated on violating pages
Typical severity	Partial decline	Often near-total for affected pages
Median rollout	14 days	7 days
Reassessed when	Next core update only	Continuously
Recovery window	Months, gap-dependent	2 to 8 weeks after cleanup
The fix	Improve the site	Remove the violation

The reassessment row is the one that changes everything. A spam demotion can resolve in weeks. A core demotion waits, and in 2026 that wait passed 148 days by late October.

Signal one: does your site break a policy?

This is the fastest test and often the only one you need.

Spam updates enforce a written list. Check your site honestly against it.

• Scaled content abuse — many pages produced mainly to rank.
• Site reputation abuse — third-party content using your domain’s standing.
• Expired domain abuse — an aged domain repurposed for unrelated content.
• Cloaking, doorway pages, hacked or scraped content.
• Link spam — unmarked paid or manipulative links.

If none of these apply, a spam update almost certainly did not touch you, even if one ran the same week you dropped. Spam systems do not assess general quality.

Signal two: how much did you lose?

Severity separates them more reliably than dates.

• Specific pages to near zero while others held — points at spam enforcement.
• Most pages losing a similar share — points at a core reassessment.
• The whole domain to near zero — check Manual Actions first. That may be a penalty, not either update.

Signal three: which pages fell?

Scope is the strongest signal of all.

If the pages that fell are exactly the ones matching a policy — the hosted coupon section, the programmatic location pages, the scaled archive — that is spam. If clean, original pages fell too, that is core.

The page scope analyzer answers this from a Search Console comparison export in about a minute.

When they ran at the same time

This happens more than you would expect. Several pairs overlapped almost exactly:

• March 2024: core and spam began the same day, 5 March.
• October 2023: spam on 4 October, core on 5 October, plus a 26 day ranking incident.
• December 2024: core ended 18 December, spam began the next day.

In these windows the date is useless. Scope and severity are the only way to separate them, and you may need both fixes in sequence.

The fix order if it was both

1. Remove the spam violation first. It is faster, and it can cap everything else.
2. Wait for the spam reassessment, two to eight weeks.
3. Then address quality for the core side, and wait for the next core update.

Doing quality work while a spam violation is still live wastes it. The violation sets a ceiling the quality work cannot lift.

The most expensive mistake

Watching a spam update hoping it will reverse a core demotion.

It happened through the August 2025 rollout and it is happening again now. Different systems, different standards, separate clocks. A spam update reassesses spam. It does not re-score quality.

Rollout timing by type is measured in how long Google updates actually take. Spam recovery is in spam update recovery, and core recovery in core update recovery.

A worked example

Imagine a publisher with a strong editorial blog and a coupon section run by a partner company.

• The coupon section falls to almost nothing within days of a spam update.
• The blog loses about a quarter of its clicks across the following core update.

Those are two separate problems. The coupon section matches site reputation abuse. The blog decline is a quality reassessment.

1. Remove or noindex the partner section first. That recovery can begin within weeks.
2. Then improve the blog, and wait for the next core update to judge the result.

Treating it as one problem would have wasted months, either improving the blog while the violation stayed live, or waiting for a core update that the coupon section could never pass on its own.

Explaining which one hit you

Clients and managers usually want one sentence. Give them the cause, the response and the honest timeline.

• Spam: a specific part of the site breaks a named policy. Removing it can lead to recovery within weeks as the systems reassess.
• Core: the site as a whole was judged less helpful than competitors. Improvement is judged at the next core update, which can take months.

Say which it is before promising anything. The two need different budgets, different work and very different patience.

If you cannot tell yet, say so. An honest “we will know within two weeks” builds more trust than a confident guess that turns out wrong.

This is one of 16 Google spam policies. All of them, grouped and explained, are in every Google spam policy explained.