TL;DR
| Step | What to do | Where to do it |
|---|---|---|
| Confirm the drop | Match your traffic cliff to Google’s update timeline | search.google.com/search/status |
| Find affected pages | 28-day comparison, sort by impressions drop | Search Console → Performance |
| Check indexing | Look for new “Crawled — not indexed” errors | Search Console → Pages |
| Diagnose root cause | Content thin? E-E-A-T weak? Technical failure? | See 4-question audit below |
| Fix highest-leverage first | Content → E-E-A-T → technical | In that order |
| Track week-over-week | Watch the 10–20 hardest-hit pages | Search Console, weekly |
Recovery timeline: 2–4 months for most sites with substantive improvements. 6–12 months for YMYL (health, finance, legal) topics.
Step 1 — Confirm It’s Actually an Algorithm Update
Not every traffic drop is an algorithm hit. Before you rewrite your entire site, verify the cause.
Check the official timeline first. Google publishes all confirmed updates at search.google.com/search/status. Match your traffic cliff to an update date. If your drop happened weeks before any announced update, a different cause is more likely: a competitor refreshed their top pages, a technical error broke crawling, or seasonal patterns shifted.
Updates worth knowing in the 2025–2026 cycle:
| Update | Dates | Primary focus |
|---|---|---|
| March 2025 Core | March 13–27, 2025 | Broad quality re-evaluation |
| June 2025 Core | June 30–July 17, 2025 | Content helpfulness |
| December 2025 Core | December 11–29, 2025 | E-E-A-T enforcement |
| March 2026 Core | March 27–April 8, 2026 | One of the most volatile core updates in years per industry trackers; thin AI-paraphrased content was widely reported as the hardest hit |
| May 2026 Core | May 21–June 2, 2026 | Broad quality re-evaluation; rolled out in under 12 days |
If your drop matches an update date, proceed to the diagnostic below. If not, run a technical SEO audit first — a crawl error or sitemap issue may be the simpler culprit.
Step 2 — Find Which Pages Were Affected
Open Google Search Console → Performance → Search Results. Set the date range to a comparison view: 28 days pre-update vs. 28 days post-update (use the exact update completion date as your split point).
Sort the Pages tab by Impressions (Difference), descending. Export this list. These are your recovery targets.
What you’re looking for:
- Pages that lost >40% of impressions — highest priority
- Clusters of pages on the same topic (signals a topical authority issue, not just a few thin pages)
- Your highest-revenue or highest-conversion pages regardless of percentage drop
Also check the Coverage report → Not Indexed section. New “Crawled — currently not indexed” URLs are a direct signal that Google visited a page after the update and decided it wasn’t indexable. This is distinct from crawl errors — it means Google made a quality judgment call against the page.
Step 3 — Diagnose the Root Cause
Google’s core updates re-evaluate the entire quality of a page against everything else that serves that query. A drop means one of four things:
- Thin or paraphrased content — Google assessed your page as less complete or original than competitors it now prefers
- Weak E-E-A-T — no demonstrated experience, expertise, or trust signals on the page or site
- A technical failure — Core Web Vitals or mobile usability degraded user experience enough to drag down the quality assessment
- Competitors improved — your content didn’t change, but the pages now outranking you did
For each of your top 10 impacted pages, run this four-question audit:
Q1. Does this page answer the searcher’s real question above the fold? Open the page on mobile. What does a first-time visitor see in the first 400px of screen? Is it a direct answer, or preamble and background? If the answer is buried, rewrite the lead.
Q2. Is the content original — or is it paraphrase? The March 2026 update was widely reported by industry trackers to hit AI-paraphrased content especially hard — sites that simply restated publicly available information in different words took the steepest losses. Original content means first-hand testing data, real client examples, specific numerical evidence, or a perspective genuinely not available elsewhere.
Q3. Is there a named author with verifiable credentials? Anonymous content or thin author bios are a trust deficit Google’s quality raters specifically flag. A named author with a linked bio, credentials, and real professional history repairs this. For YMYL topics (health, finance, law), this is non-negotiable.
Q4. Does the page have a Core Web Vitals failure? Check at PageSpeed Insights for the current Google thresholds:
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| LCP (load time) | < 2.5s | 2.5–4.0s | > 4.0s |
| INP (responsiveness) | < 200ms | 200–500ms | > 500ms |
| CLS (visual stability) | < 0.1 | 0.1–0.25 | > 0.25 |
Technical failures alone rarely cause a core-update drop, but they compound content quality signals. Fixing a 4-second LCP while also improving content depth produces faster recovery than either fix alone. See our Google PageSpeed improvement guide for specific implementation steps.
Step 4 — Fix in the Right Order
Content first. The most common reason for a core update drop is that Google now prefers a better answer to the same query. Fix this before anything else:
- Expand thin pages to genuinely answer every dimension of the searcher’s intent — not word-count padding, but missing sub-questions and nuance
- Add original observations: specific numbers, first-hand testing outcomes, real examples from your own work or clients
- Cut filler (“In today’s fast-paced world,” “Look no further”) that dilutes the signal-to-noise ratio
- Consolidate two overlapping thin pages into one comprehensive one — merged authority concentrates ranking signals
E-E-A-T second. Once content is solid:
- Add or upgrade author bios with named credentials, professional history, and a headshot
- Cite sources for factual claims — link to the primary source (a .gov page, a study, an official standard), not a blog post that cites it
- Add a “Last reviewed” date and who reviewed it — especially for YMYL content
- For health/finance topics: have a licensed professional review and byline the content
Technical third. Fix Core Web Vitals failures on impacted pages — particularly LCP and INP, which are the most common failures. See our guide to improving PageSpeed scores for a checklist. If mobile usability is broken, fix it before requesting re-indexing — Google indexes the mobile version.
Step 5 — What to Avoid After a Drop
Don’t make random “SEO fixes.” Adding keyword density, changing title tags, or rebuilding internal links without addressing the underlying content quality issue will not recover a core-update drop. Google’s own guidance is explicit: “There aren’t specific actions to take to recover. A negative rankings impact may not signal anything is wrong with your pages.”
Don’t delete content in bulk. Mass deletion as a “cleanup” strategy signals to Google that your site has contracted. Delete only content that genuinely cannot be improved and was created for search engines rather than humans.
Don’t evaluate results during rollout. Google core updates take 1–3 weeks to fully roll out. Search Console data also lags 48–72 hours. Wait until at least one full week after the update’s confirmed end date before drawing conclusions or making major changes.
How Long Does Recovery Actually Take?
This is the question nobody wants to give a straight answer to. Here’s the honest picture from the 2025–2026 update cycles:
| Content type | Typical recovery window |
|---|---|
| General informational content | 2–4 months |
| E-commerce / affiliate | 4–8 months |
| Health / finance / legal (YMYL) | 6–12 months |
| News and time-sensitive content | 2–4 months |
The pattern is consistent: sites that make substantive, not cosmetic improvements see partial recovery in the 60–90 days between core updates. More complete recovery — Google fully re-evaluating and re-ranking the improved content — typically arrives with the next core update cycle.
Google itself acknowledges there’s “no guarantee that changes you make to your website will result in noticeable impact.” Some ranking drops are comparative: your content didn’t decline, but the pages now above you improved.
The practical implication: the most important thing you can do is watch your impacted pages weekly and track direction of travel, not fixate on full recovery arriving on a specific date.
Monitoring So You Catch the Next Drop Early
Core updates now run every 3–4 months. The sites that recover fastest are the ones monitoring weekly — so a ranking shift triggers investigation within days, not months.
Google Search Console is the free baseline: a weekly check of the Performance report’s week-over-week position changes on your top 20 pages takes under 10 minutes and will surface meaningful drops before they compound. For a broader site health scan, run a free SEO audit to identify technical gaps that could amplify the next quality re-evaluation.
The core principle: an algorithm update doesn’t change what good content is — it changes how effectively Google can detect which content is good. The sites that consistently outperform through updates are the ones making content humans actually want to read, not the ones chasing the specific signals each update appears to reward.
Keep Reading
- Why Your Website Doesn’t Show Up on Google (And How to Fix It) — diagnose indexing blocks before assuming a ranking issue
- Google Search Console: A Practical Guide for Small Business Owners — how to read the reports that matter
- SEO Audit Checklist: 20-Point Verification — run this after making recovery changes to verify nothing else broke
- How Search Engines Actually Rank Websites — the underlying model that core updates are adjusting