A redirect chain occurs when a URL redirects to another URL that itself redirects to another URL — creating a chain of two or more hops before reaching the final destination. Instead of URL A pointing directly to URL C, you have A → B → C, or worse, A → B → C → D.

Redirect chains are a common technical SEO problem that accumulates quietly over time, usually from site migrations, CMS updates, or HTTPS migrations that were implemented in stages rather than all at once. They cause three specific problems that directly impact your rankings.

Why Redirect Chains Are an SEO Problem

Link equity loss. Each redirect hop passes slightly less equity than the previous one. A 301 redirect is not a perfect equity transfer — a small percentage is lost at each step. A two-hop chain loses twice that amount. A four-hop chain can lose a meaningful proportion of the equity that would otherwise reach the final destination page. As we covered in our guide to link equity, preserving every bit of authority is important for competitive rankings.

Crawl budget waste. When Googlebot follows a redirect chain, each hop counts as a separate crawl request. A three-hop chain uses three times the crawl budget of a single direct redirect. As we covered in our guide to crawl budget, wasting crawl slots on redirect chains means fewer slots available for indexing your actual content.

Increased page load time. Each redirect adds a network round-trip — typically 100–300ms per hop. A three-hop chain adds 300–900ms to the load time before the browser even starts downloading the final page. This directly impacts your Core Web Vitals and user experience.

How Redirect Chains Form

The most common cause is a staged migration. When a site moves from HTTP to HTTPS and also changes its URL structure at the same time, each change adds a hop:

  • Old URL: http://site.com/old-page/
  • HTTP to HTTPS redirect: https://site.com/old-page/
  • URL structure change: https://site.com/new-page/

What should be a single redirect from the original URL to the final URL has become a two-hop chain. Multiply this across hundreds of pages and you have a significant technical problem.

How to Find Redirect Chains

Use our site scanner to crawl your site and identify any URLs that are part of a redirect chain. The scanner follows redirects and reports chains — any URL that goes through more than one redirect before reaching its final destination is flagged.

Also check your internal links — links pointing to intermediate redirect URLs rather than final destinations are a common source of chains. Even if you fix the server-side redirects, internal links still pointing to the old redirected URLs create the same chain effect.

How to Fix Redirect Chains

The fix is straightforward: update each redirect in the chain to point directly to the final destination URL, bypassing all intermediate steps.

If you have: Old URL → Intermediate URL → Final URL

Change it to: Old URL → Final URL

In your .htaccess file or server redirect configuration, find the rule for the old URL and update its destination to the final URL directly. Remove or update any rules for intermediate URLs that no longer serve a purpose.

After fixing server-side redirects, update your internal links to point directly to final destination URLs. Use our internal link checker to find internal links that still point to intermediate redirect URLs.

Summary

Redirect chains waste link equity, crawl budget, and load time through unnecessary intermediate hops. Find them with our site scanner, fix them by updating each redirect to point directly to the final destination, and update internal links to skip intermediate URLs entirely. A site with clean, direct redirects performs better technically on every dimension that matters for SEO.

Missed the previous article? Read: Why HTTPS Is Important for SEO and How to Set It Up Correctly