Core Updates
Leafline's guides lost a fifth of their search clicks over two weeks. Asha reads that the search engine has just finished a "core update", and her first instinct is to rewrite everything that night. Knowing what a core update actually is will stop her making things worse.
The rule
A core update re-grades everyone; improve the work, not the trick.
Search engines change their ranking systems all the time, mostly in small ways nobody notices. A few times a year Google makes a larger, broad change to its core ranking systems and announces it publicly: a core update. Rolling one out takes anywhere from days to several weeks.
The key ideas:
- Not aimed at particular sites. A core update changes how the engine judges relevance and quality in general. Nobody is "penalised" in the manual-action sense.
- Relative, not absolute. Think of a teacher re-marking a whole class with an improved marking scheme. Some answers move up, so others must move down. A drop often means other pages are now judged to serve the search better, not that yours got worse.
- No quick fix. There is no single violation to remove, so recovery comes from genuinely improving the content and the site. It can take a long time to show, sometimes not until a later update.
- Movement during rollout is normal. Rankings can swing up and down while the update rolls out, before they settle.
Most changes to ranking systems are never announced; the announced core updates are simply the largest. That is one more reason not to read every wobble in traffic as an update.
So the right response is patient and diagnostic, not panicked.
The shortcut
Use four words, in order: wait, compare, learn, improve.
Wait
Asha changes nothing until the rollout is announced as complete, then waits another week so the data settles.
The trap: rewriting the whole site in a panic during the rollout, which makes it impossible to tell what the update did and what you did.
Drills
Answer fast — trust the rule.
What does a drop after a core update usually mean?
When should Leafline start analysing the impact of a core update?
Why is there no quick fix for a core update drop?
Which comparison fits a core update best?
Remember
- A core update re-grades everyone; improve the work, not the trick.
- Wait for the rollout to end, compare equal periods, learn from what now ranks, improve.
- The trap: rewriting everything mid-rollout, or hunting for a "penalty" that does not exist.