1. What a redirect chain is
A redirect tells browsers and Google that a URL has moved. A single redirect is one hop: /old → /new. A chain is more than one hop in a row: /old → /newer → /newest. They usually build up innocently over years — you move a page, later move it again, switch from HTTP to HTTPS, drop the www, restructure a folder — and each change adds a link to the chain instead of replacing it.
A close cousin is the redirect loop, where URLs point back at each other and never resolve. Loops break the page entirely; chains merely degrade it. Both are worth cleaning up, but loops are emergencies.
2. Why chains hurt SEO
Google can follow a chain of a few hops, but it isn't free. There are three real costs. First, speed: every hop is another round trip before the page loads, which drags on your Core Web Vitals and frustrates users. Second, crawl efficiency: Googlebot spends requests walking the chain instead of crawling your actual content, which matters more the larger your site is. Third, signal dilution and risk — Google's guidance on redirects notes that rendering and following may fail, and Google will stop following after too many hops, at which point the destination may not be indexed as you intend.
3. How to find redirect chains
You can't fix what you can't see. There are a few practical ways to find chains. For a single URL, browser developer tools show the full request trail under the Network tab — you'll see each 301/302 hop before the final 200. To check many URLs at once, a redirect checker follows each URL through every hop and flags where there's more than one, plus any loops or mixed permanent/temporary redirects. Also watch Search Console's page indexing report for “Page with redirect” entries that shouldn't be there.
Pay special attention to the usual suspects: your HTTP-to-HTTPS and www/non-www rules (these often stack into two hops), old campaign URLs, and any page you've moved more than once.
4. How to fix them
Fixing a chain is conceptually simple: repoint the first URL straight to the last one. If /old → /newer → /newest, change the rule so /old → /newest directly, and make sure /newer also points straight to /newest. Work through it this way:
- Map the full chain first, so you know the true final destination (and that it returns a 200, not yet another redirect).
- Update each source to point directly at that final URL.
- Use permanent (301) redirects where the move is permanent, so Google treats the destination as canonical. Don't mix in 302s for moves that are really permanent.
- Fix internal links at the source — if your own pages link to
/old, update those links to/newestso you avoid the redirect entirely. - Re-test every fixed URL to confirm it's now a single hop.
That last point is the one people skip: a redirect you don't need to trigger at all is faster than even a perfect single redirect. Cleaning up internal links is half the job.
Trace every hop with the Redirect Checker
Enter a URL and see the full redirect path — every hop, status code, and the final destination — so you can spot chains and loops and flatten them to one clean redirect. Free, no signup.
5. Preventing new chains
Chains creep back if you let them. Two habits keep them away. First, whenever you add a new redirect, check whether the source is already a redirect target — if it is, update the existing rule to point at the new destination rather than stacking a fresh hop on top. Second, audit your redirects periodically, especially after a migration, a CMS change, or an HTTPS switch, which are the moments chains are born. A quick recheck of your key URLs a few times a year keeps the whole site loading in one hop.
Redirect chains rarely cause a dramatic ranking drop on their own, so they're easy to ignore — but they're equally easy to fix, and a clean redirect map is one of those quiet technical wins that makes everything else on your site a little faster and a little stronger.
