How to recover rankings after a core update
Recovering from a core update drop starts with accepting what a core update is: Google reassessing which pages best answer queries, not a penalty for a specific error. Google's documentation on core updates says most sites do not need to worry about them, and compares a drop to a list of recommended restaurants being revised, where the ones that moved down are not necessarily bad. There is often nothing technical to fix.
What you can do is confirm the timing, find exactly which pages and queries lost, judge those pages honestly against Google's helpful content guidance, and improve or consolidate them. Google says some changes can take effect within days, but it can take several months for its systems to confirm that a site as a whole is producing helpful content.
Confirm it was the core update
Before changing anything, rule out other causes.
- Check the dates. The Google Search Status Dashboard lists when each core update started and finished. A drop that began a week before the rollout is something else.
- Check Manual actions and Security issues in Search Console. Anything listed there is not a core update effect and needs a different fix.
- Check the Pages report for a spike in excluded URLs. An accidental noindex, a broken canonical or a server outage in the same week can look like an algorithm hit.
- Check your analytics. A tracking change or a consent banner update can make traffic look lower than it is. Compare with Search Console clicks.
- Check seasonality. Compare with the same period last year.
- Check whether the results page changed shape. A new AI Overview, video carousel or forum block above your result can cut clicks while your position holds. That is a change in the results, not in how Google rates your page.
Google recommends waiting at least a full week after an update completes before analyzing the change in Search Console, so you are not reading a half-finished rollout.
A recovery plan, step by step
- Compare two periods. In the Performance report, compare the weeks after the update finished with an equal period before it began. Sort pages by the largest loss in clicks.
- Group the losers. Are they one section (all product reviews, all how-to posts) or scattered? A pattern points at a type of content Google now rates lower.
- Split position drops from demand drops. If impressions fell but position held, fewer people searched. If position fell, Google reassessed you.
- Look at who replaced you. Search the lost queries. Did forums, official sources or first-hand reviewers move up? That tells you what Google now prefers for those queries.
- Judge the pages against Google's questions. The helpful content guidance lists self-assessment questions about originality, expertise and whether readers leave satisfied. Answer them honestly, ideally with someone who did not write the page.
- Improve, merge or remove. Rewrite pages that can become the best answer. Merge overlapping pages into one and redirect the rest; Hydrogen SEO's Redirection Manager handles the 301s. The thin content pruning guide covers deciding which is which.
- Show who, how and why. Bylines linked to author pages, how you tested or researched, and a clear purpose for each page.
- Leave pages that did not drop alone. A site-wide rewrite puts working pages at risk.
When to expect movement
Google's core updates documentation says improvements do not have to wait for the next major core update, because smaller core updates and other changes happen continually. It is also clear that a full reassessment of a site can take several months.
As an experience-based range and nothing firmer: substantial improvements to a set of pages sometimes show partial movement within one to three months, while sites where much of the content was affected often wait until a later core update to see a clear change. Some sites never return to their old peak, because the results page itself changed and now favors a different kind of page.
Track the affected page group as a segment in Search Console, monthly, and annotate the dates of each update and each of your changes.
Reactions that make things worse
- Deleting large parts of the site in a panic. Pages with links and steady traffic may not have been the problem. Prune only after the analysis.
- Changing dates to look fresh. Google's helpful content guidance names this as a practice to avoid.
- Rewriting everything with an AI tool. Swapping one generic page for another generic page does not answer the helpful content questions.
- Disavowing links at random. Core updates are not link penalties. See disavow for when that tool is appropriate.
- Buying links to recover authority. It adds a spam risk on top of the drop.
- Judging recovery week to week. Rankings fluctuate after every update.
Recovery plan at a glance
- Drop dates line up with the update on the Search Status Dashboard.
- No manual action, security issue, indexing spike or tracking change explains it.
- Analysis done at least a week after the rollout finished.
- Lost pages grouped, with notes on who replaced them.
- Each affected page marked improve, merge or remove.
- Author and method visible on the pages you keep.
- Monthly tracking of the affected segment, annotated with update dates.
Common questions
Is a core update drop a penalty?
No. Core updates reassess content across the web. Penalties are manual actions, and those are listed in Search Console under Manual actions.
How long does recovery from a core update take?
Google says some changes can take effect in days, but it can take several months for its systems to confirm a site is producing helpful content overall. Some sites see the clearest change only at a later core update.
Should I delete the pages that lost traffic?
Not automatically. First find out why they lost. Improve pages that can become the best answer, merge overlapping ones with redirects, and remove only those with no value to readers.