A Google core update rolls out, and a week later your Search Console graph looks like a ski slope. Calls slow down. A service page that brought in steady leads is now on page two, and nobody on your team changed anything.
I have run this exact recovery for local service businesses many times, and the first thing I tell every owner is the same: a core update is not a penalty. Nothing is broken that a single setting can fix. Google re-ranked pages based on how helpful and trustworthy they look compared with everything else on the results page. Google core update recovery means making your affected pages clearly better, then waiting for Google to re-evaluate them.
This guide walks through the plan I use, in order. If you want a second pair of eyes on your data, our SEO recovery services cover the whole process.
What Is Google Core Update Recovery?
Google core update recovery is the process of regaining rankings and traffic lost during a broad core update by improving the helpfulness, depth and trust signals of the affected pages, so that Google ranks them higher when it re-assesses the web, usually at a later core update. It is different from penalty recovery: there is no manual action to remove and no reconsideration request to file.
Google releases several broad core updates a year and lists each one, with its start and end date, on the Google Search Status Dashboard. A rollout usually takes around two weeks, and rankings can move up and down during that time.
Step 1: Confirm the Core Update Actually Caused the Drop
Many owners blame the update when the real cause landed the same week: a plugin update that added noindex, a theme change that rewrote title tags, or a hosting outage. Rule those out first.
- Open Search Console, go to Performance, and set the date range to cover four weeks before and after the drop.
- Note the exact day clicks and impressions started falling.
- Compare that date with the rollout dates on the Google Search Status Dashboard.
- Check Manual Actions and Security Issues in Search Console. If either shows a notice, this is not a core update problem.
- Check your own change log for that week: plugin and theme updates, redirects, new pages, hosting changes.
If the drop started during the rollout window and nothing else changed on your site, you are almost certainly dealing with a core update.
Step 2: Find the Pages and Queries That Lost the Most
Core updates rarely hit every page equally. Use the Compare feature in Search Console (last 28 days vs the 28 days before the update) and sort by the clicks difference.
- Pages tab: list the 10 to 20 URLs with the biggest click losses. These are your recovery list.
- Queries tab: note which searches lost position. A cluster of related queries usually points to one weak page or two pages competing with each other.
- Position vs clicks: if position held but clicks fell, the cause may be a new AI Overview or more ads above you, not the update. Read our website rankings drop audit for that check.
Step 3: Look at What Google Now Prefers
For each page on your list, search its main keyword in a private window and read the top three results next to your page. Ask honest questions:
- Do they answer the searcher’s question faster and more completely?
- Do they show first-hand experience: real photos, real projects, named people, prices, process?
- Are they more current? An article that still says 2023 looks stale next to one updated this year.
- Do they match the intent better? A searcher who wants a local service wants a service page, not a long blog post.
Write down the gaps. This comparison tells you more than any SEO tool score.
Step 4: Improve the Affected Pages (In This Order)
| Fix | What to do | Why it matters after a core update |
|---|---|---|
| Answer first | Put a direct answer to the main question in the first 100 words. | Helps users and AI answers find the point quickly. |
| Add real experience | Add project photos, examples, numbers you can stand behind, and who did the work. | Core updates reward first-hand, trustworthy content. |
| Remove overlap | Merge pages that target the same query and 301-redirect the weaker one. | Two thin pages often lose to one strong page. |
| Update facts | Refresh prices, dates, screenshots, laws and steps that changed. | Outdated pages lose trust against current competitors. |
| Fix intent | Turn a blog post into a service page (or the reverse) if the results show a different page type. | Google ranks the page type searchers want. |
| Strengthen trust | Show reviews, licenses, team, address and clear contact details. | Trust signals separate local businesses from lead aggregators. |
Do not rewrite the whole website in one weekend. Improve the pages that lost the most traffic first, then the rest of their topic cluster. Changing everything at once makes it impossible to see what worked.
Step 5: Check Site-Wide Quality Signals
Core updates look at your site as a whole, not just single pages. A few site-wide issues can hold every page back:
- Large numbers of thin, near-duplicate pages such as city pages with only the city name changed.
- Old blog posts nobody reads and nobody would miss. Improve, merge or remove them.
- No clear information about who runs the business and why they are qualified.
- Aggressive pop-ups or ads that get in the way of the content on mobile.
How Long Does Core Update Recovery Take?
Be patient and plan for months, not days. Small improvements can show movement within a few weeks once Google recrawls the pages, but sites hit hard by a core update often recover at the next broad core update, when Google re-assesses the web. Some never fully return to old levels because competitors improved too, which is why the goal is to become the best result, not to undo the update.
Track recovery weekly in Search Console, by page, against the baseline you recorded in Step 2.
What Not to Do After a Core Update
- Do not file a disavow unless you have a manual action for unnatural links. Core updates are not link penalties.
- Do not buy backlinks to make up the difference. It adds risk and does not fix helpfulness.
- Do not delete large parts of the site in a panic. Remove only what is genuinely useless, and redirect what has value.
- Do not judge results daily. Rankings move a lot during and after a rollout.
When to Get Help
If you cannot find a pattern in the lost pages, or the drop is hurting calls and bookings right now, a structured audit saves months of guessing. Our team compares your before-and-after data, ranks every fix by impact and can implement it for you. Start with a free growth audit or see our SEO recovery services. If you work in the trades, our industry SEO pages show how we build pages that hold up through updates.
Frequently Asked Questions
Is a Google core update a penalty?
No. A core update re-ranks pages based on overall helpfulness and trust. There is no notice in Search Console and nothing to appeal. Penalties are manual actions, and they always show up in the Manual Actions report.
How do I know if a core update hit my website?
Compare the date your clicks and impressions fell in Search Console with the rollout dates on the Google Search Status Dashboard, and rule out technical changes made on your site the same week.
How long does it take to recover from a Google core update?
Small gains can appear within weeks after Google recrawls improved pages, but a full recovery often comes with the next broad core update, which can be several months later.
Should I delete content after a core update?
Only content that is thin, outdated and unhelpful, and only after checking it has no traffic or links. Improve or merge useful pages instead, and 301-redirect anything you remove that has value.
Can a small business website recover from a core update?
Yes. Small, focused sites often recover well because they can show real experience, local proof and fast, direct answers that large generic sites lack.
Do I need to change my whole website after a core update?
No. Start with the pages that lost the most traffic, improve them, and fix site-wide quality issues. A full redesign during a drop adds more variables and slows diagnosis.
