How to Tell the Difference Between a Core Update and a Spam Update Impact

The core update vs spam update question comes down to cause. A core update is a broad re-evaluation of Google’s ranking systems that can move any site without a violation. A spam update is enforcement against sites that break Google’s spam policies. To tell which one hit you, match your traffic change to the dates on the Google Search Status Dashboard, read the pattern of the drop, and check your site against the spam policies.
In this article17 sections
The timing is relevant right now. Google began rolling out the November 2026 core update on 10 November, 33 days after the September 2026 spam update finished on 8 October. Google says a core update may take up to two weeks, so check the dashboard for its current status before analysing anything.
What Is the Difference Between a Core Update and a Spam Update?#
A core update changes how Google’s systems assess content overall, so sites can gain or lose without doing anything wrong. A spam update targets sites that violate Google’s spam policies and can demote them or remove them from results. Google describes core updates as “a regular update designed to better surface relevant, satisfying content”.
| Factor | Core update | Spam update |
| Purpose | Broad reassessment of ranking systems | Enforcement of spam policies |
| Violation required | No | Yes |
| Typical 2026 rollout | About 12 days (March, May) | Under 1 day to about 2 weeks |
| Who is affected | Any site, in either direction | Sites using spam techniques |
| Recovery | No guaranteed fix; may need the next core update | Fix violations, then wait months |
Note that a core update drop is not a penalty. That wording matters because it changes your response: you are improving relevance and quality, not cleaning up a violation.
What Did Google’s 2026 Update Timeline Look Like?#
Google’s 2026 ranking updates ran as follows. Dashboard times are in US Pacific time, so convert them to your own time zone before comparing with your data.
| Dates (2026) | Update | Type |
| 24-25 March | March spam update | Spam |
| 27 March – 8 April | March core update | Core |
| 21 May – 2 June | May core update | Core |
| 24-26 June | June spam update | Spam |
| 18-21 August | August spam update | Spam |
| 24 September – 8 October | September spam update | Spam |
| 10 November onward | November core update | Core |
This list comes from the Google Search Status Dashboard and news coverage of it. Treat the dashboard as the final authority and verify dates there. Search Savvy’s Google algorithm update tracker is a handy companion, and our complete history of Google algorithm updates adds context.
How Do You Cross-Reference Your Drop With the Update Timeline?#
Cross-referencing means placing your traffic change against the exact start and end of each update. This is the most reliable first step, and it often settles the question.
- Find the date of the change in Search Console, using daily data.
- Check it against the dashboard window for every update that was active.
- Look for overlaps. In March, the spam update ended on 25 March and the core update began on 27 March, so changes between 24 and 27 March could have come from either.
- Rule out your own changes. Migrations, redesigns, tracking edits and seasonal demand can mimic an update.
If your drop sits in a clean gap between updates, look for causes other than an update.
How Do You Diagnose the Ranking Volatility Pattern?#
Read the shape of the change. These signals are heuristics, not proof, since Google does not tell individual sites why they moved.
| Signal | Points more toward a core update | Points more toward a spam update |
| Timing | Changes during or after a rollout of up to two weeks | Sharp step change inside a short or specific window |
| Spread | Gradual shifts across many topics where competitors now look stronger | Concentrated on pages using a questionable tactic |
| Content type | Broad relevance or helpfulness gaps | Thin, scaled, scraped, doorway or hacked pages |
| Your history | No risky tactics in use | Tactics such as mass-produced pages or link schemes |
| Direction | Losses and gains are common | Usually a loss only |
Severity alone settles nothing. A steep drop can come from either, so combine pattern, timing and page-level evidence.
What Are the Signs of a Spam Policy Violation?#
Look for practices listed in Google’s spam policies. Common examples include scaled content abuse (many pages made with little effort or value), scraped or copied content, doorway pages, cloaking, sneaky redirects, hidden text, hacked content, expired domain abuse and site reputation abuse. Recent spam updates have not covered everything: Google told Search Engine Roundtable that the September update does not target link spam.
Also open the Manual Actions report in Search Console, because a manual action is a separate issue with its own process. Search Savvy’s recovery services cover both algorithmic and manual cases.
How Do You Assess the Impact Step by Step?#
- Confirm on the dashboard that the rollout has finished.
- Wait at least a full week after completion. Google’s core updates guidance recommends this before analysing Search Console data.
- Compare that week with the week before the rollout began. For the November update, the baseline week is the week before 10 November.
- Segment the data by page type, query group, country and device.
- Review your top pages and queries. Is the drop small or large?
- Check for competing explanations, including seasonality such as Black Friday, which falls on 27 November this year.
- Audit against the spam policies if the pattern points that way.
Our guide to handling a traffic drop after a core update walks through the Search Console side in more detail. To see how a past update played out, read our breakdown of the May 2026 core update.
What Is the Recovery Approach for Each Update Type?#
| Core update | Spam update | |
| First move | Assess before changing anything | Identify the specific violation |
| Main action | Improve helpfulness, accuracy and relevance on affected pages | Remove or fix the violating content and practices |
| Timeline | Often visible in a later core update; no guarantee | Google says automated systems learn over a period of months |
| Risk | Rash site-wide rewrites | Fixing superficially and expecting instant recovery |
For core updates, Google notes there is no guarantee that changes will produce a noticeable improvement. For spam updates, document what you fixed, keep the site compliant, and track progress month by month.
What Should You Do While the November Update Is Still Rolling Out?#
Treat the current rollout as a measurement exercise, not a repair job. Google’s window runs up to two weeks from 10 November, which puts the latest finish around 24 November, just before Black Friday. In the core update vs spam update debate, this matters because the last spam update ended on 8 October, so a November drop has a clean timeline pointing to the core update.
- Export your baseline now: the week of 3 to 9 November, before the rollout began.
- Log your own changes so you can rule them out later.
- Hold large rewrites until you can analyse a full post-update week.
- Separate seasonal demand from ranking movement, since shopping peaks inflate traffic and can hide real losses.
What Mistakes Should You Avoid?#
- Analysing data while a rollout is still active
- Blaming an update without checking your own site changes
- Treating a core update drop as a penalty
- Overlooking overlap between two updates
- Rewriting everything immediately after a drop
- Assuming a spam fix will recover rankings within days
Bottom Line#
Decide between the two using evidence in this order: dashboard dates, drop pattern, then a policy audit. If no violation turns up, treat it as a core update and work on quality and relevance. If a violation does turn up, fix it and plan for a long wait. Search Savvy’s technical guides cover the supporting analysis if you want to go deeper.
FAQ#
Can a site be affected by a core update and a spam update at once?#
Yes, particularly when the windows overlap, as in late March 2026. Separate the two by checking dates and page-level patterns.
Is a core update a penalty, and how does it differ from a spam update?#
No. In the core update vs spam update comparison, only the spam update enforces rules. A core update reassesses content across the index and does not require a violation. A drop means other pages were judged more relevant, not that you broke a rule.
How long should I wait before analysing a core update?#
Wait for the rollout to finish on the dashboard, then at least one more full week.
Do spam updates only hit obviously spammy sites?#
They target sites violating spam policies, but legitimate-looking sites can break them unintentionally, for example with scaled content or hacked pages.
Should I change my content during a rollout?#
Avoid large changes while rankings are still moving. Gather data first, then act once the picture is stable.
Where can I see official update dates?#
The Google Search Status Dashboard lists ranking updates with start and end times in US Pacific time.