A Redirect Chain Cleanup That Recovered Lost Rankings

This client had been through two site migrations and one CMS replatform over two years, and nobody had ever gone back to clean up the redirects from the earlier moves. By the time we audited it, a meaningful chunk of their highest-value legacy URLs were redirecting three or four hops deep before landing on the current live page.

Each individual redirect was technically correct. The chain as a whole was the problem. Every additional hop dilutes the link equity being passed, slows the crawl, and increases the odds that Googlebot gives up following it before reaching the final destination, especially on a crawl-budget-constrained site.

What we found when we traced it

old-url-2022.html
  -> 301 -> migrated-url-2023.html
       -> 301 -> replatform-url-2024.html
            -> 301 -> current-live-url.html

3 hops, each one losing a bit more equity and crawl priority

Every redirect hop is correct on its own and still adds up to a slow leak nobody notices until the traffic's gone.

The fix

• Mapped every legacy URL directly to its final, current destination — flattening chains to a single hop regardless of how many migrations happened in between
• Prioritized the flattening work by historical backlink value, not by URL volume, since most of the chains carried negligible link equity anyway
• Set a policy going forward: every future migration updates the redirect map to point from the original URL, not from the most recent one

The top twenty flattened URLs by backlink value recovered an average of four ranking positions within two months, with a few recovering rankings they'd lost outright. The policy change mattered more than the cleanup itself — without it, the next migration would just add a fourth hop on top of the three we'd just removed.