A calm person's guide to Google core updates
Core updates now arrive several times a year. What they are, what actually recovers sites, and a checklist for the week one hits — panic not included.
Several times a year, Google ships a broad core update, SEO Twitter catches fire, and site owners everywhere discover urgent religion. Having watched a few of these cycles — 2024 managed four core updates, two of them back-to-back in November and December — here’s the calm version.
What a core update is (and isn’t)
A core update is a broad recalibration of how Google evaluates content — no single target, no specific penalty, just re-weighted judgments about quality, relevance, and trust applied to everything at once. Sites move because the grading changed, not because they broke a rule. That’s why there’s no “fix” to apply in the traditional sense: nothing specific was wrong on Tuesday that’s wrong on Thursday.
It also isn’t personal. Some fraction of the web moves in every core update; your slice of that is statistics, not judgment — until a pattern says otherwise.
The week one rolls out
- Don’t ship reactive changes mid-rollout. Rollouts take days to weeks, positions gyrate while they do, and changes you make mid-gyration are uninterpretable afterwards.
- Annotate the window on your ranking history. Future analysis depends on knowing which wobble was the update.
- Compare stable weeks — before rollout start vs. after confirmed completion. Weekly trend lines make this trivially easy; daily noise makes it a research project.
- Look for patterns, not casualties. One keyword down is noise. A whole page type down — every comparison page, every thin category — is the update telling you what it re-graded.
If you were genuinely hit
The honest playbook is unglamorous: make the affected pages genuinely better. More first-hand substance, clearer answers to the query’s intent, authorship and trust signals a stranger could verify, less padding. Google’s own guidance amounts to “be more helpful”, which is infuriating and true. Recovery, when it comes, often waits for a subsequent update — measured in months. Anyone selling a faster guarantee is selling.
Meanwhile, the boring fundamentals — clean technical foundations, honest titles, no self-cannibalization — don’t stop mattering during updates; they’re what keeps ordinary weeks stable so update weeks are readable at all.
The actual lesson
Sites that dread core updates usually have one thing in common: they only look at their data when something hurts. Continuous measurement plus annotations turns updates from emergencies into events — noted, measured, occasionally acted on, mostly survived.