How a core update works
Google changes its ranking systems constantly, but a few times each year it makes a change broad enough to announce and name. During the rollout, which runs for days and sometimes weeks, results shift across many topics at once. Google publishes when each rollout starts and finishes, which is how you tell an update apart from something that happened on your own site.
What changes is the assessment, not a rule you broke. A core update reconsiders which pages best answer a query, across the whole index. Positions can fall because Google now reads the intent behind a search differently, because other pages became better answers, or because a signal that once counted heavily now counts for less. Nothing about your page needs to have changed at all.
Why core updates matter
For a business that depends on organic traffic, a core update is the largest single source of unplanned change in the year. Enquiries can fall within a week without anyone touching the website, and the first instinct — that something is broken — sends people hunting in entirely the wrong place.
Updates also expose concentration risk. A site whose traffic rests on a handful of pages feels one far more sharply than a site earning across many topics and several channels. The update does not create that fragility. It reveals it.
Common mistakes after a core update
Reacting during the rollout is the worst of them. Rankings move up and down while an update is still deploying, and edits made in that fog can never be evaluated afterwards — you will not know whether a recovery came from your change or from the rollout settling. Wait until Google confirms the update is complete.
The second is treating a drop as a punishment. A core update leaves no message in Search Console, because none is being sent, and that is exactly what separates it from a manual action. The third is buying a fix. There is no technical switch that reverses a core update, and any offer with a guaranteed recovery timeline is selling a certainty nobody has.
What to do about it
Start by establishing what actually moved. In Search Console, compare the weeks either side of the rollout page by page and query by query rather than by site total, because a headline drop often hides a small number of pages losing a great deal. Then look at what now ranks above you and ask, honestly, whether it answers the question better than your page does.
From there the work is editorial rather than technical. Google’s guidance around its helpful content system is essentially a set of questions: is this page written for the person who needs it, does it show real experience, does it say anything the existing results do not. Answering those properly is slow, and it is the only durable response. Where a whole section of a site has slipped, the answer is usually a review of content and search intent rather than page-by-page tinkering — and recovery, when it comes, often arrives alongside a later update rather than immediately.