A redirect chain is a sequence of URL redirects where the browser or crawler must follow multiple hops before reaching a final destination that returns a 200 OK. Instead of URL A redirecting directly to the final destination, URL A redirects to URL B, which redirects to URL C, which finally returns the page. Each intermediate redirect in the sequence is a hop. The total number of hops from the original URL to the final destination defines the length of the chain.

A single redirect hop, URL A redirecting directly to the final destination, is the correct and expected behaviour for any redirect. A redirect chain begins the moment a redirect destination itself returns another redirect rather than the final content. Two hops, three hops, five hops: all are redirect chains, and all carry costs in performance, SEO equity, and crawl budget that compound with every additional hop.

Redirect chains are one of the most common technical issues found during SEO audits and site migrations. They accumulate gradually and silently, each one typically created by a well-intentioned redirect that did not account for an existing redirect already in place at the destination. Left unaddressed, they degrade site performance and leak SEO value in ways that are invisible to casual inspection but measurable in crawl data and ranking signals over time.

How a redirect chain forms

Understanding how redirect chains form helps explain why they are so common and why they are easy to miss until a systematic audit surfaces them.

The most typical chain formation scenario involves sequential redirects added over time without updating earlier ones.

A site migrates from HTTP to HTTPS. Every HTTP URL gets a 301 redirect to its HTTPS equivalent. At this point every HTTP URL is one hop from its HTTPS destination, correct and clean.

Six months later the site moves from www to non-www. Every www URL gets a 301 redirect to the non-www equivalent. Now http://www.example.com/page redirects to https://www.example.com/page which redirects to https://example.com/page. Two hops.

A year after that, a URL restructure renames /page to /new-page. A 301 redirect is added from /page to /new-page. Now http://www.example.com/page goes through three hops before reaching https://example.com/new-page.

At no point was anything configured incorrectly in isolation. Each redirect was added correctly for its specific purpose. But the cumulative effect is a chain that grows longer with every infrastructure change, because earlier redirects were never updated to point directly to the current final destination.

The costs of redirect chains

Redirect chains impose costs at multiple levels: performance, SEO equity, crawl budget, and user experience. Each cost compounds with chain length.

Performance and latency: every hop in a redirect chain requires a complete round trip between the browser and a server. The browser sends a request, receives a redirect response, sends a new request to the next URL, receives another redirect response, and so on until it reaches the final destination. Each round trip adds latency, typically tens to hundreds of milliseconds depending on the server response time and network conditions.

For visitors on fast connections this may be imperceptible for short chains. For visitors on slow connections, mobile networks, or high-latency connections, a three or four hop chain adds a noticeable delay before the page begins loading. This directly impacts page speed, Core Web Vitals metrics, and the overall experience of visiting the site.

SEO equity dilution: each hop in a redirect chain marginally dilutes the SEO equity and link juice being passed from the original URL to the final destination. A 301 redirect passes the vast majority of equity from source to destination, but not necessarily 100%. With each additional hop, a small amount of equity is lost. A two-hop chain loses a little. A five-hop chain loses measurably more. For URLs with significant backlink profiles, this equity dilution has a real impact on the rankings the final destination achieves.

Crawl budget waste: Googlebot and other web crawlers follow redirect chains hop by hop. Each hop consumes crawl budget, the finite amount of crawling activity search engines allocate to a site. On large sites with many redirect chains, a significant portion of crawl budget is spent following intermediate redirects rather than crawling live indexable content. This slows the discovery and indexing of new and updated pages.

Crawler chain limits: search engines follow redirect chains up to a maximum number of hops: Googlebot follows up to five hops before stopping. A chain longer than the crawler’s limit means the final destination is never reached. The crawler stops at its limit and treats the last URL it reached as the destination, which may be an intermediate redirect URL rather than the intended final page.

Browser chain limits: browsers similarly limit the number of redirects they will follow for a single request. Most browsers stop after 20 hops and display an ERR_TOO_MANY_REDIRECTS error. A chain approaching this limit is effectively a usability failure.

Redirect chains and SEO

The cumulative SEO impact of redirect chains is one of the primary reasons auditing and collapsing them is a standard recommendation in technical SEO.

Link juice leakage: backlinks pointing to URL A pass their equity through the chain to the final destination. With each hop, a small percentage of that equity is lost. The more hops, the more equity is lost before reaching the final destination. For important pages with strong backlink profiles, collapsing chains to a single hop maximises the equity reaching the final destination.

Index consolidation delays: when Googlebot follows a redirect chain, it needs to process each hop before reaching the final destination and updating its index. Longer chains mean slower index updates after URL changes, the chain takes more processing to resolve and the signals take longer to consolidate at the final destination URL.

Canonical URL ambiguity: intermediate URLs in a redirect chain can create confusion about which URL is canonical. If an intermediate URL has been indexed at some point, there may be competing canonical signals between the intermediate and final destination URLs. Collapsing the chain removes the intermediate URLs from the picture entirely.

Soft 404 risk: if an intermediate URL in a chain was previously indexed and the chain changes so that URL now returns a different response, search engines may treat it as a soft 404 rather than a redirect. Regular chain audits prevent these ambiguous states from developing.

Common causes of redirect chains

Sequential infrastructure changes: as described above, the most common cause. HTTP to HTTPS, then www to non-www, then URL restructuring: each change adds a hop without updating the previous ones.

CMS and platform migrations: migrating from one content management system or platform to another often involves a new URL structure. If the old platform’s redirects are preserved as-is and new redirects are added on top, chains form where old platform URLs redirect to intermediate platform URLs that redirect to new platform URLs.

Domain migrations with existing redirects: when a domain with existing internal redirects is migrated to a new domain, the existing redirects add hops on top of the domain-level migration redirects.

Redirect management across multiple systems: redirects configured at multiple layers, .htaccess files, application code, CDN rules, redirect management tools, can create chains where a URL is redirected at one layer and the destination is redirected again at another layer without either layer being aware of the other.

www and non-www combined with HTTP to HTTPS: one of the most universal sources of redirect chains. A visitor arriving at http://www.example.com/page may be redirected to https://www.example.com/page and then to https://example.com/page, two hops that could easily be collapsed to one.

Outdated internal links: internal links pointing to URLs that have been redirected once create single-hop chains. Links pointing to URLs that have been redirected multiple times create longer chains. Keeping internal links updated to point directly to current canonical URLs prevents chain accumulation from internal navigation.

How to find redirect chains

Redirect chains are invisible during normal browsing, the browser follows them automatically and the visitor sees only the final destination. Discovering them requires systematic checking.

Redirect checking tools: dedicated redirect checker and site auditing tools follow the full chain for any URL, showing every hop, its HTTP status code, and Location header. Most SEO crawl tools identify redirect chains automatically as part of a full site audit.

curl command line: curl -IL https://example.com/url with the -I flag for headers only and -L to follow redirects shows every hop in the chain including status codes and Location headers. This is a quick way to check individual URLs.

Google Search Console: the Coverage report surfaces redirect issues that Googlebot has encountered, including chains that may be affecting crawl efficiency.

Server logs: analysing server logs reveals patterns of redirect activity including chains where intermediate URLs appear as both redirect sources and redirect destinations.

How to fix redirect chains

Fixing a redirect chain means updating redirect rules so that every source URL points directly to the final destination in a single hop, eliminating all intermediate redirects.

Update the source redirect: the most direct fix. For each chain, identify the original source URL and update its redirect rule to point directly to the final destination rather than to the next intermediate URL. For a chain of A → B → C, update A’s redirect to point directly to C. The intermediate URL B no longer needs to exist as a redirect destination for this chain.

Batch updates for large chains: on sites with many redirect chains, updating each one individually is impractical. A systematic approach involves exporting all current redirect rules, identifying chains by tracing each destination through all existing rules to find the final destination, updating all sources to point directly to their final destinations, and reimporting the updated rules.

Update internal links simultaneously: collapsing redirect chains in the redirect rules is the immediate fix but does not address the root cause of chains caused by outdated internal links. Updating internal links to point directly to current canonical URLs prevents the same chains from reforming as redirect rules are added in the future.

Prevent chains at the point of creation: the most effective long-term fix is a process that prevents chains from forming. When adding a new redirect, check whether the source URL or destination URL is already involved in an existing redirect. If the destination already redirects, update the new rule to point directly to the final destination rather than the intermediate one.

Redirect chains vs redirect loops

Redirect chains and redirect loops are related but distinct problems.

A redirect chain has a definitive final destination, a URL that eventually returns a 200 OK. The chain adds unnecessary hops but does resolve. A redirect loop has no exit: the chain of redirects circles back to an earlier URL and continues indefinitely, never reaching a final destination. Loops result in ERR_TOO_MANY_REDIRECTS errors and make the URL completely inaccessible. Chains degrade performance and SEO. Loops break access entirely.

Both are identified through the same diagnostic tools and both are resolved by correcting the underlying redirect rules, but the urgency differs. A redirect loop is an outage requiring immediate attention. A redirect chain is a performance and SEO issue that should be addressed systematically but does not cause immediate access failure.