A core update hits, your traffic drops 40%, and the internet fills up with recovery advice written by people watching a rank tracker. Here is what works, and it starts with not touching anything for two weeks.
Step 1: wait for the rollout to finish
Core updates take two to three weeks to fully roll out. Traffic swings during that window and often partly corrects on its own. Judging your site on day three is like weighing yourself after one meal. Note the date, then wait.
Step 2: segment the drop
In Search Console and analytics, break the decline down before you touch anything. Look at it by folder first, because a drop concentrated in /blog/ or one category is a specific, fixable problem. Then by query type, since informational pages falling while commercial pages hold steady points at a content-quality or AI Overview issue. Then by page, because a handful of URLs losing most of the traffic is a very different situation from a smooth sitewide decline.
Step 3: fix the real problem
| Pattern | Likely cause | Fix |
|---|---|---|
| Thin or templated pages dropped | Helpful-content and quality signals | Improve, consolidate or remove them |
| Older content dropped, competitors newer | Freshness and depth gap | Refresh with real updates and first-hand detail |
| Sitewide, gradual decline | Site-wide quality and trust | Raise the floor: cut weak pages, strengthen E-E-A-T |
| YMYL pages hit hardest | Author and trust signals | Add credentials, review, sources, editorial process |
Keep a changelog. One shared doc: what you shipped, which pages, which date. When the next update lands, you will have cause and effect instead of a group chat full of guesses.
Step 4: wait for the next update
Core-update losses are usually re-evaluated at the next core update, which can be months away. You will not see a full recovery the week after you make changes. Ship the improvements, keep publishing well, and let the next update re-score the site.
Recovery checklist
- You waited for the rollout to finish before acting
- The drop is segmented by folder, query type and page
- Weak and thin pages are improved, merged or removed
- Trust signals are strengthened sitewide
- Every change is logged with a date
By the numbers
MD Saiful Islam · Founder & Head of SEO
Segment before you touch anything. A drop in one folder is a project. A smooth sitewide decline is a verdict on the whole site's quality, and the fix is raising the floor: cut or merge the weakest 20% of pages first.
Illustrative example
A B2B site down heavily after a core update
The loss is concentrated in an old, thin "resources" section. You wait out the rollout, confirm the pattern by segment, then consolidate the weak pages into a smaller set of strong ones, strengthen author bios and sourcing, and log every change with a date.
Some recovery often comes from the consolidation itself within weeks, and the next core update tends to restore most of what was lost once Google re-scores the improved pages.