A redirect chain occurs when there are multiple redirects between the original URL and its final destination. Instead of URL A redirecting directly to URL C, it first redirects to URL B, which then redirects to URL C. Each extra hop adds load time, wastes crawl budget, and causes link equity to bleed away before reaching the final page.

How a Redirect Chain Works

A simple redirect looks like this:

  • Good (direct): old-page.html → new-page.html (1 hop)
  • Bad (chain): old-page.html → temp-page.html → new-page.html (2 hops)
  • Worse (long chain): URL A → URL B → URL C → URL D (3+ hops)

Redirect chains often build up over time as sites are redesigned, URLs are restructured, or old redirect rules are never cleaned up. Each migration that fails to update existing redirects adds another link to the chain.

Google's rule of thumb: Googlebot will follow up to 5 redirects in a chain. Beyond that it may stop crawling and the final URL may not get indexed. Even within 5 hops, every extra redirect hurts performance and PageRank flow.
/old-page Original URL → /temp-page Unnecessary hop → /middle-page Another wasted hop → /new-page Final destination Redirect Chain (BAD) - 3 hops, slow + link equity lost Fix: Point all old URLs directly to /new-page in one single 301 redirect

Why Redirect Chains Hurt SEO

  • Page speed: Every redirect adds an extra HTTP round-trip, increasing load time by 100-500ms per hop
  • Link equity loss: PageRank diminishes with each redirect hop. A chain of 3 redirects delivers less link juice to the final page than a single direct redirect
  • Crawl budget waste: Googlebot spends crawl budget following each hop instead of discovering new pages
  • Indexing risk: If Googlebot stops following the chain (after 5 hops), the final page may not be indexed at all
  • User experience: Slow redirect chains frustrate users, increasing bounce rate

Common Causes of Redirect Chains

  • Site redesigns where old redirect rules are not updated to point to the new URL
  • HTTP to HTTPS migration combined with a separate www to non-www redirect
  • Multiple CMS migrations over the years, each adding a new redirect layer
  • Temporary 302 redirects that were never cleaned up and later redirected again
  • Automated redirect plugins that stack on top of existing redirects

How to Find and Fix Redirect Chains

  • Audit tools: Use Screaming Frog, Ahrefs Site Audit, or Semrush to crawl your site and identify all redirect chains
  • Fix at the source: Update every redirect that points to an intermediate URL so it points directly to the final destination in one 301
  • Update internal links: Change internal links on your site to point to the final URL directly, avoiding any redirect
  • Update backlinks where possible: Contact referring sites to update links pointing to chained URLs
  • Check after migrations: Any time you restructure URLs, audit for new chains immediately
Quick fix rule: If URL A redirects to URL B and URL B redirects to URL C, update URL A to redirect directly to URL C. Repeat until every redirect in your site is a single-hop 301.

Redirect Chain vs Redirect Loop

A redirect chain has a final destination. A redirect loop has no exit: URL A redirects to URL B which redirects back to URL A, causing an infinite loop. Redirect loops cause a "Too many redirects" error in browsers and make the page completely inaccessible. Both are serious technical SEO problems that must be fixed promptly.