Your traffic dropped and you suspect Google changed something. Maybe it did. Google ships algorithm updates constantly, several core updates a year plus continuous smaller changes, and some of them reshuffle rankings hard. This guide walks through what to do, in order: confirm it was actually an update, work out what the update targeted, and recover without panicking yourself into making things worse.
Step 1: confirm it was actually an update
Most "the algorithm got us" stories turn out to be something else. Before anything, rule out the ordinary suspects:
- Technical accidents. A noindex tag shipped in a redesign, an expired domain or certificate, robots.txt blocking crawlers, the site simply being down. Check Search Console for coverage errors and manual actions first.
- Seasonality. Compare to the same weeks last year, not last month.
- Tracking breakage. Sometimes traffic did not drop; the analytics tag did.
- A competitor stepping up. Losing three positions because someone else improved is not an update, and the response is different.
Then check the timing. Google documents core updates publicly, and SEO trackers report volatility spikes. If your drop lines up with a confirmed update within a few days, and Search Console shows positions falling across many queries at once, you were probably affected.
Step 2: read what the drop is telling you
Updates are not random punishment; they are Google re-weighting what it values. Diagnose by looking at where you lost:
- Site-wide decline usually points at overall quality or trust: thin content across the site, aggressive ads, weak expertise signals.
- Specific pages or topics falling usually means those pages no longer match what Google considers the best answer, or better pages moved in.
- Rankings intact but clicks down can mean the results page itself changed: AI answers, more ads, a map pack where there was none. Your position held; the page around it moved.
Look at who replaced you. Search your lost terms and study the pages now ranking. They are the clearest available statement of what Google decided it wants for that query.
Step 3: recover methodically
Do not thrash
The worst response is rewriting everything in a panic the week after a drop. Rankings often keep shifting for weeks after an update, and some losses partially rebound on their own. Diagnose first, then work a plan.
Fix real quality gaps
Google's own guidance for core updates is consistent: make the content genuinely more helpful. Concretely, that means pages that answer the query fully, first-hand knowledge a template site could not fake, honest information about who you are, and no padding written to hit a word count. Compare your lost pages against the winners and close the specific gaps you can see.
Cut or consolidate dead weight
Sites carrying dozens of thin, outdated, or near-duplicate pages tend to fare worse in quality-focused updates. Merge overlapping pages, improve the ones worth keeping, and remove the rest properly. Our guide to duplicate content covers the mechanics.
Keep the technical house clean
Technical health does not usually cause update losses, but it compounds them, because a slow or messy site gives Google one more reason to prefer someone else. A technical SEO audit after a drop makes sure you are not fighting with a handbrake on.
Keep publishing and earning links
Recovery is rarely one fix. Sites that come back are usually the ones that keep demonstrating quality: fresh useful content, real links, active profiles. Momentum reads as health.
Know your update types
Not all updates target the same things, and the type shapes the response:
- Core updates re-weight quality and relevance broadly. Losses here are rarely one fixable defect; they mean Google now prefers a different overall answer. Respond with the quality work above, sitewide.
- Spam updates target manipulative tactics: bought links, scaled thin content, cloaking. If your drop matches one and you know which rule was bent (perhaps by a previous SEO provider), remove the offending tactic entirely before expecting anything to recover.
- Helpful content and review-focused changes (now folded into core updates) hit sites whose content exists for rankings rather than readers: mass-produced posts, affiliate boilerplate, pages that answer nothing. The test is uncomfortable but useful: would this page exist if search engines did not?
- Local ranking shifts reshuffle the map pack specifically. If your website traffic held but calls from your profile dropped, look at local signals rather than content: profile, reviews, and citations.
Google announces the big ones on its status dashboard. Match your drop date to a named update before diagnosing; the name narrows the search.
Realistic timelines
Here is the part nobody likes: recovery from a core update often is not visible until Google runs another one, which can be months. Improvements you make are reassessed over time, not instantly. Plan in quarters. If anyone promises to reverse an algorithm drop in two weeks, they are guessing or lying.
Reduce the damage next time
- Never depend on one traffic source. Email lists and repeat customers make updates survivable.
- Build pages for customers first, algorithms second. Sites that ride out updates are almost always the ones that would still make sense if Google vanished.
- Watch your data monthly so you notice changes early, when they are cheap to respond to.
If you want help diagnosing
Working out whether you were hit, and what to do about it, is exactly the kind of judgment call where experience pays. Send your site over for a free audit and we will tell you whether your drop looks like an update, a technical problem, or a competitor, and what we would fix first. Honest answer, no pressure.