A core update is a broad change to Google’s main ranking systems. Google announces them, names them (March 2026 core update, and so on), and posts rollout start and end dates on its status dashboard. They happen 2 or 3 times a year now, each rollout takes days to weeks, and they’re the updates most likely to visibly move your traffic. The full history lives on this site and gets updated every time a new one lands.
What a core update actually changes
Google’s own documentation describes core updates as improvements to how its systems assess content overall. Nothing is targeted at your site. The analogy Google has used is refreshing a ranked list of the best films: when the list changes, a film that slipped from 3rd to 8th didn’t get worse. The list got rebuilt with fresh eyes and new entries.
In practice that means relevance gets re-scored across the board. Pages that rose on signals that mattered more last year can fall when the weighting shifts. Sites also seem to be reassessed as a whole, which is why core update charts so often show a step change across an entire domain rather than a few pages drifting.
Since March 2024, core updates also carry the work of the retired standalone helpful content system, so sitewide quality classification is part of what gets refreshed when one rolls out.
During a rollout: sit on your hands
Rankings bounce while an update rolls out, sometimes reversing direction mid-way. Changing your site during that window buys you nothing and costs you a clean reading: you’ll never know whether the update or your panic edit caused what happened next. Note your dates, watch, and wait for the dashboard to say the rollout is complete before you draw any conclusion.
After: diagnose before you touch anything
Once it’s done, run the same workflow I keep with the update history: confirm the drop lines up with the rollout window, segment by page type and topic to find what actually fell, and check whether rankings dropped or the SERP changed shape around stable rankings. Those 3 checks kill most wrong theories before they cost you a rewrite.
If the update genuinely hit you, the road back is its own subject, covered honestly in core update recovery. The short version: recoveries mostly arrive at later core updates, so the work is real and the timeline is long.
What a core update can’t tell you
- It isn’t a penalty. Google says drops after a core update don’t signal a violation. Manual actions are a separate system with their own report in Search Console.
- It names no specific fix. Google points to its self-assessment questions about originality, expertise and reader satisfaction. Vague, yes, and also the only official guidance that exists.
- It won’t confirm your favourite theory. Every core update spawns confident explanations within 48 hours. Volatility data can’t separate them, which is why this site’s who to listen to page values people who publish their tests.
Sources
Google’s core updates documentation and the Search Status Dashboard. The observations about sitewide step changes and post-update theory-mongering are mine.