Redirects are how you move a URL without losing its rankings, but done wrong, they leak the link equity you spent years building. Chains, loops, wrong status codes, and redirects to dead pages all cost you. Here's how to get them right.
Redirects accumulate. Every site migration, URL rename, and HTTPS move adds rules, and over time they tangle into chains and loops that quietly drain authority and crawl budget.
A redirect is a promise: this URL now lives somewhere else. Search engines honour that promise and transfer the old page's ranking signals to the new one, but only if the redirect is clean, permanent where it should be, and lands on a live page. Redirects are how you move or restructure URLs without losing years of accumulated authority, which makes them one of the highest-stakes parts of technical SEO. A botched redirect during a migration can erase rankings that took years to earn.
The trouble is that redirects pile up silently over a site's life. Each one looks harmless on its own, but together they tangle into the three failure modes below.
A redirects to B redirects to C. Each hop adds latency for users, wastes crawl budget, and risks leaking equity. There's no upside to a chain, only a hop to remove. Chains & loops →
A temporary 302 used for a permanent move keeps the old URL indexed and stalls the transfer of authority to the new page. 301 vs 302 →
A redirect that lands on a 404 or 5XX sends users and crawlers to a dead end, and any equity it carried evaporates. Always redirect to a live, relevant page, not a guess.
The redirect mistakes that cost the most ranking authority.
Why A to B to C leaks equity and wastes crawl budget, how loops break a page entirely, and how to collapse chains and update internal links to point at the final URL.
Permanent vs temporary, why using a 302 for a permanent move stalls the transfer of authority, and how to choose the right status code for migrations and campaigns.
Grounded in the real checks the crawler runs.
A redirect issue is often the visible symptom of an internal-linking problem too.
A single, correct 301 is fine and passes nearly all link equity to the new URL. Redirects hurt when they pile into chains, form loops, land on 404s, or use the wrong type (a 302 for a permanent move). The fix is to redirect directly to the final destination and update internal links to point there too, so no crawl or click wastes a hop.
Use a 301 for permanent moves: it transfers ranking signals and replaces the old URL in the index. Use a 302 only when the change is genuinely temporary and the original URL will return. Using a 302 for a permanent move is a common mistake that leaves the old URL indexed and slows the transfer of authority. See 301 vs 302.
When a URL redirects to another that itself redirects, e.g. A to B to C. Each hop adds latency, consumes crawl budget, and can dilute equity, and search engines may stop following long chains. Collapse it so the first URL goes straight to the final destination, and update internal links to point at that final URL.
Avoid it. Mass-redirecting dead URLs to the homepage is frequently treated by Google as a soft 404, so the equity doesn't transfer. Redirect each removed page to the most relevant live page instead; only if there's truly no relevant target should you let it return a clean 404.
Free to start. Find chains, loops and broken redirects across your whole site.
Start my free audit