A spam update improves Google's automated detection of content and behaviours that break its spam policies; a core update is a broad change to how its systems assess helpful, relevant results. They can look identical in a traffic chart, but the diagnosis and the fix differ. As of 30 September 2026, Google's September spam update (started 24 September) is rolling out, so this question is live for many site owners.
Key Takeaways
- Spam updates are about policy violations: cloaking, link spam, scaled content abuse and similar. Core updates are broad reassessments of quality and relevance, and are not tied to violations.
- Match your drop date to Google's Search Status Dashboard before drawing conclusions. The September 2026 spam update began 24 September at 9:15am PT.
- Spam-update hits often show as sharp, sitewide or template-wide falls; core-update movement is usually more gradual and mixed. These are tendencies, not rules.
- Google says sites can improve after a spam update if its systems learn over months that they comply. Core updates have their own guidance about helpful content.
- Never treat a rank tracker as the only proof. Confirm in Search Console.
- Both can overlap with your own site changes, so keep a change log.
The short answer
Ask two questions. Did the drop start inside a confirmed update window? And does your site have anything that plausibly breaks one of Google's 16 spam policies? If yes to both, suspect spam. If the drop is broad across your niche and your content is honest but merely outclassed, suspect a core update or normal competition.
What each update is, in Google's words
Google's documentation describes a spam update as a notable improvement to its automated spam detection. Sites violating policies "may rank lower in results or not appear in results at all," and making changes "may help a site improve if our automated systems learn over a period of months that the site complies." Its guidance for affected sites is to review the spam policies.
Core updates are Google's periodic, broad changes to search systems. Google's ranking-systems documentation is where these are catalogued; I could not fetch that page today (it returned an error), so for core update history I am relying on secondary reports. As reported by trade press, the most recent confirmed core updates were in March and May 2026. Treat those dates as unverified by me.
| Spam update | Core update | |
|---|---|---|
| Purpose | Better detection of spam policy violations | Broad reassessment of results |
| Trigger for your drop | Something on your site (or links) breaks a policy | Others improved, or your content is judged less helpful |
| Typical rollout | Days to two weeks | Often longer, as reported |
| Google's advice | Review spam policies | Focus on helpful, people-first content |
| Recovery | Months of compliance, per Google | Usually needs a later update to reflect improvement, as widely reported |
| Manual action involved? | No (algorithmic) | No |
Step 1: date the drop
Open Search Console, Performance, daily view, and set the range to 90 days. Mark these:
- 18 to 21 August 2026: the August spam update, which Google's dashboard listed as lasting two days and 16 hours (per SEO Kreativ's summary).
- 24 September 2026, 9:15am PT: the September spam update start.
- Any core update dates you can verify on the Search Status Dashboard.
If your decline began the week before any of these, neither is the cause. If it began within a day or two after a start time, you have a candidate. If it began mid-rollout and gets worse, that fits an update, but wait for the rollout to finish before concluding.
Step 2: read the shape
Signs that lean spam
- A cliff over 24 to 72 hours rather than a slope.
- Entire sections or templates falling together: programmatic pages, a coupon subfolder, a guest-post area.
- Pages disappearing from the top 100 rather than dropping a few spots. SE Ranking's analysis of the August update, reported by Search Engine Land, measured this: 16.71% of previously top-10 URLs fell beyond position 100 in the window, versus 9.2% in a July baseline without a confirmed update (100,000 US keywords, 20 industries).
That data shows correlation, not causation. It cannot say why any individual page moved.
Signs that lean core
- Gradual erosion across many queries.
- Competitors with fuller, more original or more trusted content overtaking you.
- Losses spread across page types rather than concentrated in one template.
Signs that lean neither
- A drop confined to a single URL or query group.
- Impressions steady but clicks down, which points to SERP layout changes such as AI Overviews rather than ranking.
- Traffic down only in analytics, not Search Console.
Step 3: check the site against the spam policies
Google lists 16 categories: cloaking, doorway abuse, expired domain abuse, hacked content, hidden text and link abuse, keyword stuffing, link spam, machine-generated traffic, malicious practices, misleading functionality, scaled content abuse, scraping, site reputation abuse, sneaky redirects, thin affiliation and user-generated spam.
For each section of your site, ask whether anything fits. The usual suspects I see on small sites:
- Mass-produced pages built from a template with only the city or keyword swapped.
- Old paid links from a previous SEO vendor.
- Injected spam from a hacked plugin.
- Affiliate pages that repeat merchant copy.
If you find none, a spam update is a weaker explanation.
Step 4: pick the response
If it looks like spam
Fix the specific violation and document it. Do not expect a quick bounce. For link spam, Google warns that changes might not generate improvement, because the value of the links is already discounted. Post 335 covers recovery in more detail.
If it looks like core
Improve genuine usefulness: original experience, clearer answers, better sourcing, cleaner UX. Do not chase the update with mass edits. I audit the pages that lost the most, compare them to what now ranks, and ask what a searcher gets there that they do not get from me.
If it is mixed
Segment. Treat each page group separately and stagger changes so you can attribute results.
Common misreads
- Blaming AI content by default. Google's scaled content abuse policy concerns pages made mainly to manipulate rankings. The tool used is not the test.
- Trusting volatility trackers. They show industry-wide movement, not your cause.
- Using rank trackers only. Google's google.com/goto redirect change, as reported, may affect scrapers and trackers; verify with first-party data.
- Assuming both at once. Two updates rarely explain one drop, so look for the simplest fit first.
A worked example
Suppose a 300-page service site loses 35% of clicks starting 25 September. Search Console shows that 120 city-landing pages account for nearly all of the loss, while blog posts are flat. The city pages share one template with a swapped place name. That is a segment matching scaled content or doorway-style behaviour, and it started inside the September window. Compare that with a site whose clicks slide 15% across every section over six weeks with no date match: that fits competition or a core update far better. The evidence is different, and so is the plan.
What I would do this week
- Export baselines and annotate update dates.
- Segment losses by page group.
- Audit the biggest-loss group against the 16 policies.
- Write down a hypothesis and how you would disprove it.
- Wait for the rollout to end before large changes.
FAQ
What is the main difference between a spam update and a core update?
A spam update improves detection of policy violations; a core update is a broad change to how Google assesses results overall. Google frames spam updates around its spam policies and core updates around helpful, relevant content.
Can one update be both?
Google announces them separately, and each has its own entry on the Search Status Dashboard. Your site could, however, be affected by more than one change in a short period.
How do I tell which update hit me?
Match the date your drop began to the dashboard, then check the shape and the affected page groups. A sharp drop in a template that resembles a policy violation leans spam.
Is the September 2026 spam update finished?
Google said it may take up to two weeks from 24 September. Check the Search Status Dashboard for the completion entry before comparing final numbers.
Does removing content fix a spam hit?
Sometimes, if the content itself violates policy. Deleting good pages will not help and can hurt. Fix the actual violation.
How long does spam recovery take?
Google says improvement can follow if its systems learn over months that you comply. Plan in months, not days.
Will a core update fix a spam issue?
Not by itself. Spam detection and core ranking are different mechanisms, so a later core update will not reverse a policy problem you have not fixed.
Are there manual actions in either case?
Manual actions are separate and appear in Search Console's Manual Actions report. Algorithmic updates do not create one.
Should I hire someone to recover?
Be wary of certainty. Nobody outside Google can identify the exact trigger; a good consultant will show you evidence and a hypothesis, not guarantees.
CTA
If you are staring at a traffic chart and cannot tell what happened, I am happy to help you work it out. I bring 4+ years of marketing experience in organic growth, SEO and content strategy for edtech and startup teams. See my work and get in touch through the contact form at https://younusfardeen.in.
Verified as of 30 September 2026 against Google's Search Status Dashboard and spam update documentation; core update history is from secondary reports. Not legal or professional advice.