SourceCited / Surviving core updates
Strategy · Resilience
Don't panic-rewrite. Tell core updates, spam updates, and manual actions apart, diagnose the real cause (including AI-Overview click-loss), then rebuild quality and wait for the next assessment.
Three things move traffic: core updates (broad quality re-assessments, nothing is “penalized”), spam updates (targeting scaled low-value and, in 2026, scaled AI content), and manual actions (a human flag, shown in Search Console). Diagnose before reacting — losing clicks while keeping rank is often AI Overviews, not a quality hit — then recover by rebuilding information gain and E-E-A-T, not by panic-deleting.
Three different things move your traffic, and confusing them wastes weeks. Core updates are broad, roughly quarterly re-assessments of quality — nothing is “penalized,” the bar for what counts as helpful just moves. Spam updates (and the Helpful Content system, now folded into core) target specific abuse: scaled low-value content, and in 2026 specifically scaled AI content that adds nothing. Manual actions are different again — a human reviewer flagged you, and you will see it in Search Console with a defined path to reconsideration.
| Event | What it is | How you know |
|---|---|---|
| Core update | Broad quality re-assessment | Announced; a gradual site-wide shift over 1–2 weeks |
| Spam update | Targets scaled/abusive content | Announced; sharper drops on the affected content |
| Manual action | Human reviewer flag | A notice in Search Console with a reason and a reconsideration path |
The panic move — rewriting everything the week traffic falls — usually makes things worse. Diagnose first:
My traffic dropped. Help me diagnose before I react. I'll paste: the date it started, my Search Console data (queries/pages, before vs after), and whether there's a manual action notice. 1. Does the timing match a known core or spam update, or is it something else (AI Overview click-loss, seasonality, a technical break)? 2. Which pages/queries lost the most, and what do they have in common (thin, dated, AI-generated, duplicated)? 3. Is this likely a quality re-assessment, a spam-target, or clicks lost to AI Overviews while rank held? Give me the evidence for your call. 4. Rank the fixes by likely impact — and tell me what NOT to do.
Algorithmic recovery is not a switch; it is rebuilding quality and waiting for the next assessment. What actually works maps onto the rest of this site: raise information gain and first-hand experience on thin pages, fix or remove genuinely low-value content (consolidate or 410 what should not exist), strengthen E-E-A-T, and improve the technical foundation. Then wait — recovery typically lands on a later core update, not immediately.
Mass-deleting or mass-noindexing in a panic. Cutting pages that were fine loses the equity they held. Diagnose which pages actually underperform, improve what can be improved, and remove only what genuinely should not exist.
One thing worth naming directly, because this site is about using AI: Google's spam policy explicitly targets scaled content abuse — producing many pages with AI (or any method) that add no value. Using AI as a writing assistant is fine; using it as a mass content factory is exactly what the updates hunt. The line is information gain per page: if each page carries something original — a real test, a specific number, first-hand experience — scale is not the problem. If pages are interchangeable rephrasings of the consensus, volume is the liability. (More on doing this safely in the programmatic content guide, when you build it.)
Check three things in order: is there a manual action in Search Console (a human flag with a defined fix); does the drop's date match an announced core or spam update (an algorithmic quality shift); or did you keep your rankings but lose clicks (often AI Overviews eating the click, which is a different problem). Diagnose before rewriting anything.
A core update is a broad re-assessment of quality — nothing is penalized, the bar just moves, and pages can drop or rise. A penalty (manual action) is a human reviewer flagging your site for a specific violation, which appears in Search Console with a reconsideration path. They're diagnosed and fixed differently.
There's no instant switch: rebuild quality — raise information gain and first-hand experience on thin pages, strengthen E-E-A-T, consolidate or remove genuinely low-value pages, and fix the technical foundation — then wait for a later core update to re-assess. Panic-deleting pages that were fine usually loses equity and hurts.
Not for being AI-written per se. Google's spam policy targets scaled content abuse — many pages that add no value, however they're made. AI as a writing assistant is fine; AI as a mass content factory is the target. The dividing line is information gain per page: something original on every page keeps scale safe.