Recovering From a Core Update: The 6-Week Plan

Lost rankings after a core update? Don’t panic. Don’t mass-rewrite. Run a 6-week triage plan instead.

The intuition that gets sites into deeper trouble is speed: the traffic graph just fell off a cliff, so the team rewrites the homepage, noindexes the blog, and disavows half the backlink profile by Friday. Every one of those moves destroys information the diagnosis needed. Recovery is possible and it is comparative — the pages that dropped lost to specific pages that won, and the gap between them is a checklist, not a mystery.

This is the plan we run on client sites the week after an update rolls out: document, audit the worst-hit pages, compare against the new winners, refresh, rebalance internal links, then measure — six weeks of work, then patience. The realistic odds — about 60% of dropped pages recover within 3 months of focused refresh — are in the final section, limitations stated plainly.

Key takeaways

• Diagnose before treating. Week one is screenshots and segmentation: page-level drops and site-wide drops mean different diseases.
• Focused beats broad. The audit is five URLs — the biggest losers — not a full-site rewrite panic.
• The fix is comparative. Study exactly what replaced you on each query — format, depth, schema, author signals, backlink profile — and close that gap.
• Recovery is slow by design. Give Google 4–8 weeks to re-evaluate after changes; don’t re-refresh inside the measurement window.
• Know the odds honestly: roughly 60% of dropped pages recover within 3 months of focused refresh, 30% recover partially, 10% never fully.

What a core update actually does to you

A broad core update is a recalibration of how Google’s systems assess helpfulness, expertise, and authority across the whole index — not a penalty and not a targeted attack. Pages that lost didn’t break a rule; pages that won better matched the new calibration. You cannot “fix a penalty,” only close a comparative gap.

Same logic applies across the three update types in the week-one triage. A broad core shift reshuffles relevance and E-E-A-T interpretation site-wide. A helpful-content-style classification event hits thin or unfocused pages hardest. A spam update targets specific manipulative patterns — links, cloaking, scaled abuse — and asks for removal, not a refresh. Treating a spam problem with the content plan below, or a core problem with a disavow campaign, wastes the recovery window. The E-E-A-T layer of the comparison work is unpacked in our E-E-A-T guide.

Week 1: Document the damage

Week one creates the record you measure against for the next six months. Nothing changes on the site.

• Screenshot your Search Console performance. Data decays and filters drift — capture impressions, clicks, and average position across the update window with date comparison set, on every property.
• Note every URL that lost traffic. Export by page, sort by lost clicks, and keep the file. This list is the work queue for weeks two through five and the scoreboard for week six.
• Categorize: page-level drop vs site-wide drop. Page-level losses on a handful of pages point at content or query-specific issues. A site-wide collapse across templates points at a domain-level trust or quality judgment — and each responds to different interventions.
• Identify the update type (broad core, helpful content, spam). The type determines whether you need a refresh plan or a compliance fix. Check the status page, the major trackers’ classifications, and whether the drop is gradual across the rollout or instantaneous at completion.

Segment before you judge: one export often contains both patterns layered. Directory slices drive week-two prioritization, and Search Console’s hidden reports hold the device, country, and query breakdowns that separate “our mobile pages tanked” from “everything tanked.”

Week 2: Audit your five hardest-hit pages

Pick the top 5 URLs that lost the most traffic and run the same interrogation on each. Five is deliberate: enough for a pattern, few enough to do properly in a week.

• Is the content fresh? When was it last updated? A page whose statistics predate the query’s current reality is an easy loss in any useful-content calibration. “Last touched 2023” is a data point, not a judgment — but it’s a data point.
• Is the content comprehensive vs the SERP? Open the live results for the target query and diff your page against what ranks: subtopics covered, questions answered, entities named, search intents satisfied.
• Does the page satisfy the E-E-A-T signals? Named author with verifiable credentials? First-hand experience markers — original numbers, named tools, screenshots of actual dashboards? Citations to credible sources? Transparency about the site and its authors?
• Are there obvious quality issues? Broken links, thin content, outdated screenshots, affiliate walls, intrusive layout elements — the unglamorous defects that make every other signal harder to believe.

The output of week two is a written diagnosis per URL: one or two sentences stating why this page lost, specific enough to be falsified. If you cannot name the gap, you cannot close it in week four.

Week 3: Compare against the pages that replaced you

For each lost URL, find the URLs that now rank in your spot. What changed? The five comparison questions:

• Format? Listicle vs guide vs tool page vs forum thread. Core updates routinely re-judge intent fit: an informational query that tolerated product pages for years may suddenly want a comparison article. Your format answers a different question than the index now believes the query asks.
• Depth? Surface coverage vs genuinely answering the follow-up questions searchers type next. Depth here is measurable — count the distinct subtopics and questions the winner covers that you don’t.
• Schema? Structured data the winners ship: FAQ, Article, Product, Organization, breadcrumbs. Markup doesn’t boost rankings directly, but it changes how confidently a page is understood and what it earns in the SERP. The Schema Generator gets you from gap to valid markup in minutes.
• Author signals? Named bylines, author pages, credentials, review stamps — the visible E-E-A-T layer. A verified byline is a trust asset the index can read; anonymous expertise gets discounted.
• Backlink profile? Compare the winners’ referring domains and anchor themes against yours. If every new winner has links from niche authority sites, the gap is editorial relationships, not content length.

Write the diff as a checklist per URL. Week four has nothing else to work from, and the discipline of a written diff is what separates a refresh from a rewrite-panic.

Week 4: Refresh with intent

Update your content to match — or beat — what now ranks. Add missing entities. Update stats. Tighten the structure. Before requesting a recrawl, verify how the refreshed pages look in SERPs with the SERP Preview tool — a clean title and meta description on a refreshed page is the signal that triggers Google’s re-evaluation.

Three rules keep this from becoming the mass-rewrite panic. One, refresh against the diff, not against a feeling — every edit traces back to a gap written in week three; the content strategy guide covers the editorial layer. Two, preserve what earned the page any authority — the original angles, the examples, the internal links other pages depend on; you are closing gaps, not starting from zero. Three, batch by template — if three losers share a diagnosis, fix the pattern once.

Keep a change log per URL — date, summary, before/after word count, schema added — so week six’s recovered impressions can be traced to specific interventions.

Week 5: Rebalance internal links

Re-balance your internal links. Make sure your refreshed pages get strong, contextual links from your top-performing pages.

The logic is crawl priority. After an update, Google revisits what you changed — but what it trusts most is how your own site ranks pages against each other. A refreshed page buried three clicks deep, linked only from the footer and its category listing, reads as a page its own publisher doesn’t believe in. A page that receives descriptive anchor links from your highest-authority pages inherits confidence.

The concrete moves: pull your top pages by link equity (crawl depth plus inbound contextual links), add one to three contextual links from winners to refreshed losers, with descriptive anchors matching the rebuilt-for query. Audit the reverse: link to winners where the reference helps readers — honest citation is E-E-A-T, not a leak. The mechanics live in internal linking algorithms.

Week 6: Wait and measure

Core update recovery is slow. Give Google 4–8 weeks to re-evaluate. Don’t re-refresh during this period. Track impressions and CTR in Search Console.

Why the wait is non-negotiable: every new edit resets the evaluation of the page. Re-refreshing mid-window means you never measure the effect of any single intervention — just motion, with impressions wobbling from your own changes. Freeze the content and run one ritual: same query, same filters, weekly, against the week-one screenshots.

Read impressions as the leading signal — they recover before clicks do, because position recovery starts at the impression layer — and check the live SERP before blaming snippets: a competitor’s new sitelinks or an AI Overview above you moves CTR without your page changing at all. A stable, improving trend sustained across two measurement cycles is a real recovery. A one-week blip is noise.

What doesn’t work

The plan above earns its credibility by what it refuses to do:

• Mass-rewriting every page. Destruction of the before/after record, a re-crawl of the entire site that resets evaluation on pages that were fine, and zero attribution when something improves.
• Disavowing every link. Core updates are not link penalties. A blanket disavow throws away equity on a bet that the problem is your links when week two said it wasn’t — and a wrongly disavowed strong link is a permanent self-inflicted loss.
• Changing the entire site architecture. URL migrations, template overhauls, and navigation resets during a recovery window stack a fresh crawl-and-trust problem on top of the existing one. Nothing from weeks two through five requires it.
• Panicking into a redesign. The most expensive non-intervention on the list: it ships URL changes, layout shifts, and template bugs while the site is under active re-evaluation, and it delays the real work: page-level, comparative, and boring.

All four share one root: they are responses to the feeling of the drop rather than the diagnosis of it. The six-week structure exists so diagnosis comes before treatment.

The realistic recovery odds

About 60% of pages that drop during a core update recover within 3 months of focused refresh. About 30% recover partially. About 10% never fully recover. Be honest with stakeholders about the odds.

Methodology and limitations, because this section cites numbers: these are our observed recovery rates across dropped pages worked on with focused refresh — not a controlled study, and not a law of physics. The window (3 months post-refresh against the update-start baseline) and the treatment (the six-week plan, not mass rewrites) both matter, and there is survivorship bias: sites that fired us aren’t in the denominator. Read 60/30/10 as “focused work on a core-update drop has strong odds of paying off, near-total failure is the minority case” — a planning frame, not a guarantee.

One more sentence on the split: partial recovery usually means the page comes back below its prior position but above its trough — a residual gap that is typically authority-level, not content-level. That is where the compounding strategy — building topical depth until the site earns durable trust — does the slow work the refresh can’t.

Recovery is a comparative act. The pages that replaced you told you what to build; the six weeks is the process of listening properly.

Frequently asked questions

How long does it take to recover from a core update?

Give Google 4–8 weeks after your changes to re-evaluate, and expect full recovery windows up to three months for pages that recover at all. Roughly 60% of dropped pages recover within 3 months of focused refresh, about 30% recover partially, and about 10% never fully. The first sign is impressions stabilizing; clicks and positions follow later.

Is a core update a penalty?

No. A core update recalibrates how the whole system assesses helpfulness and authority; your pages lost relative standing against a changed bar, not to a rule violation. That is why penalties get removed — with reconsideration requests or by fixing spam patterns — while core drops only get answered by closing the gap to the pages that now outrank you.

Should I update all my content after a core update?

No — that’s the single most expensive mistake in the recovery playbook. Start with the five hardest-hit URLs, run the comparative audit, and expand only as the pattern analysis justifies. Mass-rewriting destroys your before/after record, resets evaluation on pages that were fine, and tells you nothing about which intervention recovered what.

Can I recover before the next core update?

Yes. Recovery does not wait on the next broad rollout — re-evaluation happens continuously as Google re-crawls changed pages; many pages recrawl within days and months on average. The 4–8 week measurement window exists because the re-evaluation cycle is real but not instantaneous, and the next update may recalibrate again anyway.

Do I need to wait for a specific update to fix anything?

No. A spam-update-style drop needs the spam pattern removed now; a core-update drop needs the six-week plan now. Every week of drift is a week the index reinforces its new opinion of your site.

The bottom line

Don’t panic, don’t mass-rewrite, don’t redesign into a bigger problem. Document in week one, audit the five worst losers in week two, diff against the pages that replaced you in week three, refresh with intent in week four, rebalance internal links in week five, and let weeks six through fourteen do the waiting.

The odds, stated honestly, favor doing the work. Start the documentation pass today — and if you want the longer horizon where updates are blips instead of crises, the compounding model is covered in our pillar-cluster model and the measurement stack in our technical SEO guide.