Redirect Chain

What is a redirect chain?

A redirect chain happens when a URL does not go directly to its final destination. Instead, it bounces through one or more intermediate URLs before reaching the actual page. Each bounce is called a "hop." Every hop adds delay, increases server load, and creates another point where things can break.^[1]

Here is a simple example: /old-page -> 301 -> /intermediate-url -> 301 -> /final-page

That is a two-hop chain. Chains of three, four, or more hops are common on sites that have been through multiple redesigns.

How do redirect chains build up?

Redirect chains almost never happen on purpose. They build up over time through normal website changes.

Multiple site migrations. A URL moves from Platform A to Platform B. Later, Platform B moves to Platform C. Now there is a redirect from A to B, and another from B to C. Nobody set up a direct redirect from A to C.

HTTP-to-HTTPS upgrades. A site adds HTTPS. The redirect from http:// to https:// chains into a www to non-www redirect, or the other way around.

Trailing slash changes. A redirect from /page to /page/ combined with a later URL change creates a chain.

Marketing tracking URLs. Campaign links that pass through a tracking service add an extra hop before reaching the landing page.

CMS auto-redirects. Some content management systems create a new redirect every time a URL slug changes. They do not check if the old URL already had a redirect in place.

How do redirect chains affect page speed?

Each hop requires a full round trip between the browser and the server. On a typical connection, each hop adds 50 to 300 milliseconds of delay. That happens before the visitor sees any content.

This directly hurts Largest Contentful Paint (LCP), one of Google's Core Web Vitals. On mobile connections with higher latency, each extra hop has a proportionally larger impact.^[2]

For a government portal or banking site that serves millions of visitors per month, redirect chains on high-traffic URLs create a measurable drag on performance.

How do redirect chains affect SEO?

Crawl budget waste. Each URL in the chain uses crawl resources. Long chains mean the search engine makes multiple requests to index one piece of content. Over time, these accumulated redirects contribute to link rot if any hop in the chain breaks.

Link equity loss. Google says PageRank passes through redirects. But evidence suggests it weakens with each hop. The longer the chain, the less value reaches the final page.^[3]

Slower indexing. Pages at the end of long chains may get crawled less often and indexed more slowly.

For large organizations with thousands of pages and years of accumulated redirects, these effects add up across the entire site.

How do you find redirect chains?

Crawl tools like Screaming Frog, Ahrefs Site Audit, and Sitebulb follow all redirects and flag chains of two or more hops. These are the most efficient option for large sites.

Browser developer tools show the full sequence of requests in the Network tab. Content teams can use this for spot-checking individual URLs.

Server log analysis traces redirect paths from the server side. IT teams can use logs to find chains that crawl tools might miss.

How do you fix redirect chains?

The fix is straightforward: update each redirect at the start of the chain to point directly to the final destination.

1. Find the true final URL for each chain.
2. Update the first redirect to go straight to that URL with a single 301 Moved Permanently response.
3. Verify that no new chain was created in the process.

For CMS systems that auto-generate redirects on slug changes, IT teams should audit the redirect table regularly. Flattening chains before they grow keeps the site fast and crawlable.

How Askem Helps

Continuous quality assurance tools identify redirect chains as part of broken link scanning. When a crawler follows a link and encounters multiple hops, it flags the chain so IT teams can see which URLs need to be flattened. Tools like Askem scan the live site on a continuous schedule without installation, making it practical for large organizations to find and fix accumulated redirect chains without manually checking thousands of URLs.

Sources

1. MDN Web Docs — Redirections in HTTP: https://developer.mozilla.org/en-US/docs/Web/HTTP/Redirections
2. Google — Avoid multiple page redirects: https://web.dev/articles/redirects
3. Google Search Central — Redirects and Google Search: https://developers.google.com/search/docs/crawling-indexing/301-redirects