What Steps Does an SEO Company Take to Recover Lost Rankings?

An SEO company recovers lost rankings in a set order: it dates the drop and lists the affected pages and queries, rules out reporting glitches and seasonal demand, checks the date against Google’s confirmed updates, looks for technical regressions, compares the affected pages with what ranks now, and reviews links last. Fixes follow the evidence, which is why disavows and site-wide rewrites come at the end.

Before Anything Else: Is There a Manual Action?

Open the Manual Actions report in Search Console. If it lists an action, the recovery runs through Google’s penalty process; follow how an SEO company identifies and fixes SEO penalties. The steps below assume the report shows no issues.

Step 1: Date the Drop and Measure Its Shape

The agency pins down when the drop started, using Search Console’s Performance report by date and a rank tracker for daily positions, and lists which pages and queries lost ground. The shape matters. A sudden drop across the site on one date points first to an algorithm update or a technical incident. A slow slide across many pages points more toward content that has aged or competitors that improved.

Google’s guide to debugging drops in Search traffic adds a second distinction, the size of the move:

• A small drop, such as position 2 to 4, can reverse on its own. Google recommends “avoiding making radical changes if your page is already performing well.”
• A large drop, such as falling out of the top 10 to position 29 across many terms, calls for a review of the whole site rather than individual pages.

Step 2: Rule Out a Reporting Glitch or Seasonal Demand

Two causes need no fix at all. Search Console’s data anomalies page lists known logging and processing problems that can look like a drop. And demand itself moves: Google’s guide suggests filtering the Performance report to one high-traffic query at a time and checking it in Google Trends, to see whether interest fell across the web or only for your site.

Step 3: Match the Date Against Confirmed Updates

Google lists confirmed ranking updates, with start dates and durations, in the ranking update history on its Search Status Dashboard. In 2025, core updates began on March 13, June 30 and December 11, each rolling out over about 14 to 18 days; in 2026, core updates began on March 27 and May 21. A drop that starts inside a rollout window is a different case from one with no matching update.

Timing your analysis matters too. Google’s core updates documentation recommends “waiting at least a full week after a core update completes before analyzing your site in Search Console.” For preparing before the next update lands, see how an SEO company handles Google algorithm updates.

Step 4: Look for Technical Regressions

Run the technical check even when the date matches an update, because two causes can overlap. A fresh crawl with Screaming Frog or Sitebulb, read alongside Search Console’s Page indexing, Crawl stats and Security Issues reports, can surface a regression unrelated to Google: a migration that broke redirects, a plugin update that added a noindex tag to a template, a new script that slowed every page, or a staging robots.txt file pushed to the live site. Google notes that a misplaced noindex tag produces a slower drop than a site outage, because it takes effect page by page as Google recrawls. The crawl and indexing checks are detailed in how an SEO company improves crawlability and indexing.

Step 5: Compare the Pages With What Ranks Now

Make this comparison whether or not the drop matches an update. A core update changes how Google assesses pages overall, so after an update-related drop, compare your pages with the results that replaced them. Look for a competitor’s more complete or more current page, data on your page that has gone stale (prices, statistics, product details), or a results page that has shifted toward a different type of page for the query. Writing to close that gap is content work, the subject of how an SEO company optimizes content for search engines.

Step 6: Check the Backlink Profile Before Any Disavow

Review inbound links for a sudden spike of spammy links, whether from negative SEO or an old guest-posting campaign on low-quality sites. Without a manual action, links are a precautionary check here, and a disavow filed on a guess can remove links that were helping. If the review finds a large spike that lines up with the drop, hold it against Google’s own test before acting: its disavow help page reserves the tool for a considerable number of spammy, artificial or low-quality links that have caused, or are likely to cause, a manual action, and says that in most cases Google can assess which links to trust without additional guidance. Short of that test, record the finding and keep working through the other causes.

Fixes That Follow From the Evidence

• Refresh an aged page with current data and examples, the subtopics the top-ranking pages cover, and a structure that answers the query early.
• Consolidate thin or overlapping pages that compete for the same intent into one stronger page, with 301 redirects from the old URLs.
• Relink a page that lost internal links when newer content was published without linking back to it, or when a redesign flattened the site’s hierarchy.

How Long Recovery Takes

Google gives ranges. Its traffic-drop guide says that “some changes can take effect in a few days, while others could take several months”. It suggests waiting a few weeks before analyzing the site in Search Console again. After a site move, “a medium-sized website can take a few weeks for Google to notice the change; larger sites can take longer.” For core-update drops, Google’s documentation adds that if a few months pass with no effect, recovery may wait for the next core update. Both pages state that there is “no guarantee” changes will produce a noticeable result.

Treat any recovery date an agency quotes as a planning estimate. Ask what it is based on.

Reading a Partial Recovery

Track the affected pages and queries in Search Console, not only the site-wide trend. A partial recovery, with some queries back and others still down, can point to a cause the first diagnosis did not cover, or to a change in the results for the queries still down; compare the two groups of queries before acting. Avoid stacking new changes on the same pages before the re-analysis window has passed, or you will not know which change worked.

What to Ask Before Approving a Recovery Plan

A recovery plan worth approving names three things: the date and the pages the drop is tied to, the evidence for the cause the agency chose (update timing, crawl data or a comparison with the pages that took your positions), and the metric and date at which it will judge whether the fix worked. A plan that opens with a disavow or a site-wide rewrite without that evidence is a guess.