Your rankings dropped after a Google update — now what

Monday morning. You check Google Analytics. Traffic is down 40%. You check Search Console. Impressions dropped. You check your main keywords — you’ve gone from position 3 to position 19.

You didn’t change anything. You didn’t touch the site. Google did.

Welcome to the post-update panic. I’ve walked founders through this conversation dozens of times. Here’s the honest playbook.

That sinking feeling when you open your analytics and the graph points the wrong way. Before you react, you need to diagnose.

First: confirm it’s actually an algorithm update

Not every traffic drop is a Google update. Before you assume the worst, check:

1. Google Search Status Dashboard — Did Google confirm a core update, spam update, or helpful content update in the same timeframe? If yes, your timing matches.

2. Was it sudden or gradual? A core update impact shows up within 1–2 weeks of the rollout. If your traffic has been declining slowly over 3 months, that’s not an update — that’s a content or competitive problem.

3. Check for technical issues first. I’ve seen founders blame Google updates when the real cause was:

• A robots.txt change that blocked crawling
• An accidental noindex tag deployed with a code push
• The site went down for 48 hours and they didn’t notice
• SSL certificate expired
• A redirect chain broke after a plugin update

Run a crawl (Screaming Frog or Sitebulb). Check Search Console for coverage errors. Rule out the self-inflicted wounds before blaming Google.

Diagnosing which update hit you

Google runs several types of updates. The fix depends on which one affected you.

Core update

What it does: Re-evaluates overall content quality across the web. Winners and losers shift based on E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness).

Symptoms: Broad traffic decline across many pages, not just one section. Positions drop 5–20 spots on keywords you used to rank for.

Root causes:

• Thin content that satisfied queries in 2023 but doesn’t meet 2026 depth standards
• Lack of author credentials and trust signals
• Content generated at scale without editorial oversight (AI-spun or templated)
• Poor user experience metrics (high bounce rate, low time on page)

Spam update

What it does: Targets manipulative link building, cloaking, keyword stuffing, and other policy violations.

Symptoms: Dramatic drop — 70–90% traffic loss. Often accompanied by a manual action in Search Console.

Root causes:

• Paid links or PBN (private blog network) links
• Doorway pages or hidden text
• Cloaking (showing different content to Googlebot vs users)
• Link schemes your SEO agency built without telling you

Helpful Content update

What it does: Demotes sites with a high proportion of “search engine-first” content — pages written to rank, not to help.

Symptoms: Site-wide suppression, especially in informational queries. Your commercial pages might hold, but blog/resource content tanks.

Root causes:

• Large sections of generic, undifferentiated content
• Content that matches search intent superficially but doesn’t solve the problem
• “Programmatic” content at scale (city pages, product comparison templates)
• No first-hand experience or original insight

Recovery starts with diagnosis. The impulse to “just do something” after a ranking drop leads to more damage than the update itself.

What NOT to do (but everyone does)

Don’t panic-publish

Adding 20 thin blog posts to “increase freshness” doesn’t help. It often makes things worse because you’re adding more content that dilutes the quality signal Google is now paying more attention to.

Don’t disavow everything

The disavow tool is for specific, known toxic links — not a general “fix my rankings” button. Disavowing your entire backlink profile because you don’t understand it is like setting fire to your house because you found a spider.

Don’t redesign the site

A new theme doesn’t fix a content quality problem. And if the redesign introduces technical SEO issues (changed URLs without redirects, removed schema, broke internal links), you’ll have two problems instead of one.

Don’t fire your SEO person in week one

If they’ve been doing solid work and this is a core update, it may not be their fault. Core updates reshuffle rankings based on Google’s evolving standards. The right move is to assess together, not to start over with someone new who needs three months to understand your site.

The actual recovery playbook

Step 1: Map the damage

In Google Search Console, compare the 28 days before the update to the 28 days after:

• Which pages lost the most clicks?
• Which queries dropped?
• Are specific sections hit harder than others?

This tells you whether it’s site-wide (quality signal) or section-specific (content relevance).

Step 2: Audit the affected content

For every page that lost significant traffic, ask:

• Does this page answer the query better than the current #1 result? Be honest.
• Does it have original insight, data, or experience? Or could any freelancer have written it from Google’s page-one results?
• Is the author credible? Is there a real name, bio, LinkedIn, and evidence they’ve done the work?
• Is it up to date? Does it reference current tools, methods, and conditions?

Score each page honestly. The ones that fail these tests are the ones dragging your site down.

Step 3: Consolidate, don’t add

If you have 50 blog posts and 30 of them are thin, generic, or outdated:

• Merge related thin posts into comprehensive pillar pages
• Redirect the old URLs to the consolidated page
• Delete (and 410) content that serves no purpose

Fewer, better pages > more, mediocre pages. This is the single most effective recovery tactic I’ve seen work.

Step 4: Strengthen E-E-A-T

• Add real author bios with credentials and links to professional profiles
• Add “last updated” dates and actually update the content
• Add first-party data, screenshots, case studies — things a machine can’t fabricate
• Add schema markup (Person, Article, FAQ) so Google can parse your trust signals

Step 5: Fix technical debt

While you’re in there:

• Clean up your internal link structure (orphan pages, broken links)
• Ensure every page has proper schema
• Fix Core Web Vitals issues (they’re a ranking factor, even if a small one)
• Submit updated pages for reindexing in Search Console

Step 6: Wait — and measure

Core update recovery takes 3–6 months. Not because the work takes that long, but because Google needs to re-crawl, re-evaluate, and re-rank at its own pace. The next core update is usually when you see recovery reflected.

When you need outside help

You can diagnose yourself. The fix is harder.

Call in an SEO specialist when:

• You’ve lost more than 40% of organic traffic and can’t identify why
• Search Console shows a manual action
• You suspect your previous SEO built links that are now hurting you
• You need someone to run a content audit with an objective eye (you’re too close to your own content to be honest about quality)
• You need a technical SEO audit to identify crawl/indexation issues

The right specialist will start with a diagnostic — not a proposal. They’ll ask to see your Search Console, crawl your site, and tell you what they think happened before quoting a recovery engagement. Anyone who quotes a fixed price for “Google update recovery” without seeing your data first is selling a template, not a solution.

The uncomfortable truth

Some ranking drops are permanent. Not because the site can’t recover, but because the reason it ranked in the first place was a gap in Google’s quality assessment that the update closed.

If your site ranked because there were no better alternatives and now there are — the answer isn’t an SEO trick. It’s becoming the better alternative. Better content, better expertise, better user experience.

That’s slower. It’s also the only strategy that compounds.