What Is a Redirect Chain?
How It Kills SEO (And How to Fix It)

Here's a scenario that happens constantly: a site launches over HTTP. They move to HTTPS. They add www. They rename some URLs for a CMS migration. They do another redesign a year later. Each time, someone adds a redirect. Nobody ever goes back and collapses the chain. Five years later, their most important pages are sitting at the end of a five-hop redirect chain, and they have no idea why they keep losing PageRank they shouldn't be losing.

A redirect chain is exactly what it sounds like: a series of redirects where each URL in the sequence points to the next, rather than directly to the final destination. They accumulate naturally over time on any active website, and they're one of the most common technical SEO issues that goes unnoticed until something visible breaks.

1. How redirects work

When a browser or crawler requests a URL, the server responds with an HTTP status code. A 200 means success — here's the content. A 301 or 302 means “this URL has moved, try this other URL instead.” The browser then automatically makes a second request to the new URL.

A single redirect is completely normal and fine for SEO. Moving a page from its old URL to a new one with a 301 is the right thing to do — it tells search engines to transfer all the ranking signals (links, authority, relevance) from the old URL to the new one.

The problem starts when that new URL also redirects somewhere else.

2. What makes a chain

A chain is any sequence of two or more redirects before reaching the final destination. The most common three-hop chain on the internet today looks like this:

This particular chain forms almost automatically on sites that:

1. Started on HTTP (hop 1: HTTP → HTTPS)
2. Enforce www. canonicalization (hop 2: non-www → www)
3. Later moved the page to a new URL (hop 3: old slug → new slug)

The right fix at each step would have been to update all existing redirects to point directly to the current final destination. Instead, because each change was made independently, the chain grew one hop at a time.

3. How chains affect SEO and performance

PageRank dilution

Google hasn't published exact numbers on how much link equity passes through a 301 redirect, but the technical reality is that each hop introduces some loss. Google's own guidance says 301 redirects may not pass full PageRank — and longer chains compound this loss at each step.

The practical implication: if 10,000 external sites link to http://example.com/old and that URL goes through a three-hop chain before reaching the current canonical URL, the current URL is receiving less ranking signal from those 10,000 links than it would with a direct 301. This isn't theoretical — sites that flatten long redirect chains often see ranking improvements within weeks.

Performance impact

Every redirect hop is an additional HTTP round-trip. The browser sends a request, the server responds with a redirect, the browser sends another request to the new URL. On a typical server, this adds 100–300ms per hop. On mobile connections or slow networks, it can be significantly more.

Three hops = potentially 900ms of additional latency before the page even starts loading. For a page with a Largest Contentful Paint target of under 2.5 seconds, that's already a third of your budget burned before any content is delivered. Redirect chains are a straightforward contributor to poor Core Web Vitals scores.

Googlebot chain limits

Google's documentation says Googlebot will follow redirect chains “up to a certain limit” — estimated at around 5 hops in practice, though this isn't officially published. Chains longer than 5 hops may result in Googlebot stopping before reaching the destination, which means the final URL never gets crawled or indexed from that particular entry point.

4. How chains form on real sites

Understanding the common causes helps you prevent future chains after you fix the current ones.

5. Finding redirect chains on your site

You can't fix what you can't see. There are several ways to discover redirect chains:

For single URLs — SEOCheckPilot Redirect Tracer: The Redirect Tracer tool traces any URL up to 15 hops, showing the full chain with HTTP status codes and per-hop timing. Enter any URL you're concerned about and see the complete path immediately.

For entire sites — use curl or a crawler: To audit your whole site, you need to crawl it. Screaming Frog SEO Spider (free for up to 500 URLs) shows redirect chains in its “Response Codes” tab. SEOCheckPilot's site crawler runs the redirect module across every page and flags chains.

For individual URL testing — curl from the terminal:

# Follow all redirects and show each hop:
curl -Ls -o /dev/null -w "%{url_effective}\n" --max-redirs 15 http://example.com/old-page

# Show detailed headers for each hop:
curl -Lsv -o /dev/null http://example.com/old-page 2>&1 | grep -E "^[<>] (Location|HTTP)"

# Expected output:
> HTTP/1.1 301 Moved Permanently
> Location: https://example.com/old-page
> HTTP/2 301
> location: https://www.example.com/old-page
> HTTP/2 301
> location: https://www.example.com/new-page
> HTTP/2 200

6. Fixing redirect chains

The fix is conceptually simple: update every redirect that points to an intermediate URL so that it points directly to the final destination. The complication is doing this systematically and making sure you don't miss anything.

Step 1: Map the full chain for each problem URL

Before touching anything, document the complete chain: URL A → URL B → URL C → final URL D. You need to know all intermediate hops to know what you're changing.

Step 2: Update redirects from all intermediate points to the final destination

The goal: URL A → URL D (direct 301). URL B → URL D (direct 301). URL C → URL D (direct 301). Even URL B and C should be updated — they might still receive direct traffic from bookmarks or other links, and you want those to resolve directly too.

In Apache .htaccess

# Before (chain):
Redirect 301 /old-page /page-v2
Redirect 301 /page-v2 /page-final

# After (direct from both old URLs to final):
Redirect 301 /old-page /page-final
Redirect 301 /page-v2 /page-final

In Nginx

# Before (chain):
location = /old-page {
  return 301 /page-v2;
}
location = /page-v2 {
  return 301 /page-final;
}

# After (both redirect directly to final):
location = /old-page {
  return 301 /page-final;
}
location = /page-v2 {
  return 301 /page-final;
}

In Caddy

# Before:
redir /old-page /page-v2 301
redir /page-v2 /page-final 301

# After:
redir /old-page /page-final 301
redir /page-v2 /page-final 301

Step 3: Update internal links to point directly to the final URL

Redirect chains are often caused by links within your own site pointing to old URLs that then redirect. Even with the chain collapsed, you still have the overhead of the single redirect. Best practice: update all internal links to point directly to the current canonical URL with no redirect at all. Search engines crawl internal links frequently — the more you can make internal links resolve directly, the cleaner your crawl profile.

7. Redirect loops — a different but related problem

A redirect loop is when the chain circles back to a URL it already visited: A → B → C → A → B → C → .... Browsers detect this and show a “too many redirects” error (ERR_TOO_MANY_REDIRECTS in Chrome). The page is completely unreachable.

Common causes:

• Incomplete HTTPS migration: A rule redirects HTTP → HTTPS, but the HTTPS page also triggers a redirect back to HTTP (often a misconfigured load balancer that sees HTTP headers from the backend even though the frontend is HTTPS).
• Conflicting CMS and server rules: A WordPress redirect plugin and an .htaccess rule both trying to canonicalize the same URL, pointing at each other.
• Trailing slash rules: A rule adding trailing slashes and a rule removing them both applied to the same URL.

Diagnosing loops: the Redirect Tracer detects loops automatically and shows which URLs form the cycle. Once you know the loop, trace each URL's redirect rule back to its source (server config, CDN rules, CMS settings) and identify which rule is the rogue one.

8. HTTP status codes you should know

Frequently asked questions

The takeaway

Redirect chains are a background drain on your site's SEO performance — slow enough that you rarely notice the effect on any single page, but significant enough at scale to matter. The fix is straightforward once you've found them, and the audit process isn't complicated.

Audit your most important pages first — your homepage, your top-traffic product or category pages, any pages with significant external links. Fix the chains, update your internal links, and build a habit of updating existing redirects whenever you move a URL rather than just adding a new hop. Future you will thank present you.