How to Recover from a Google Core Update Drop
On this page
A drop during a core update isn’t a manual action. There’s no violation listed in Search Console and nothing to appeal. Google’s core updates documentation gives a specific way to read the drop before you change anything: confirm the timing, wait for the data to settle, measure how large the drop is, and only then decide whether to act. Recovery, when it’s needed, means making pages clearly better than what now ranks, and Google says there’s no guarantee that changes will produce a noticeable result.
Confirm the drop lines up with the update
Google’s documentation asks you to check the Search Status Dashboard and note the start and end date of the core update. It then recommends waiting at least a full week after the update completes before analyzing your site in Search Console, so you’re comparing settled data rather than the rollout itself.
If the drop doesn’t fall inside an update’s window, a core update is a weak explanation; look at changes on your own site and at competitors.
Measure how big the drop is
Review your top pages and queries in the Performance report and compare their positions before and after the update. Google’s documentation separates two cases:
| Drop | Google's example | What it recommends |
|---|---|---|
| Small | Position 2 to 4 | No need for drastic action; it recommends avoiding changes to content that's already performing well |
| Large | Position 4 to 29 | A deeper assessment |
It also suggests analyzing search types separately, so you can see whether the drop happened in Web Search, Google Images, Video mode or the News tab. A loss confined to one search type points somewhere different from a loss across all of them.
For a large drop, assess the site honestly
For a sustained, large drop across the site as a whole, the documentation points you to its self-assessment, to check whether the site overall, not just individual pages, is delivering content that’s helpful, reliable and people-first. Google’s guidance on creating helpful content supplies the questions, including warning signs such as content made primarily to attract visits from search engines, or content that mainly summarizes what others have to say without adding much value.
Then compare your dropped pages with the pages that rank now, query by query, and write down plainly what they offer that yours don’t: first-hand experience, depth, original information, a clearer answer. Sometimes the honest answer is that a larger, established site now owns a broad query. Knowing that early lets you put effort where you can still be the best answer.
Read the pages that held
Pages that held or gained through the update can point to the queries you can still win. Before rewriting anything, list them and look for what they share: a narrower topic, first-hand detail, a question they answer better than anyone else. Put new effort where those pages point, rather than spreading the same changes evenly across every page that fell.
Improve first, delete last
The core updates documentation warns against “quick fix” changes, such as removing a page element because you heard it was bad for SEO, and asks you to consider how to improve content in meaningful ways. It says deleting content is a last resort, only to be considered if you think the content can’t be salvaged.
For each page that fell, ask whether it can become the best answer for its query with real work. If it can, improve it. If several pages cover the same ground thinly, combine them into one strong page and redirect the others. Removal is for what can’t be salvaged.
Plan for months, not days
Google’s documentation says you don’t necessarily have to wait for a major core update to see the effect of improvements: smaller core updates happen without announcement, and they’re another way improved content can rise. It also says that if it’s been a few months without any effect, that could mean waiting until the next core update.
Measure against the baseline you took before the update, give changes time to be recrawled and reassessed, and keep in mind Google’s caveat that positions aren’t static and changes aren’t guaranteed to show a noticeable impact.
Frequently asked questions
Is a core update drop a penalty?
No. It isn’t a manual action and there’s nothing to appeal. Google’s documentation describes how to read the drop and assess your content instead.
Should I change pages that dropped only slightly?
Google’s documentation calls a drop like position 2 to 4 small, says there’s no need for drastic action, and recommends avoiding changes to content that’s already performing well.
Should I delete content to recover?
Improve it first. The core updates documentation calls deleting content a last resort, for content you think can’t be salvaged.