Redirect Chains: Why They Slow Your Site and How to Fix Them

A redirect chain occurs when following a URL requires multiple redirects before reaching the final destination. URL A redirects to URL B, which redirects to URL C. Users and search engines must follow each hop before reaching the actual content.

Chains form naturally over time. A site migrates from HTTP to HTTPS (adding one redirect). Later it moves from www to non-www (adding another redirect on top of the existing one). A page gets renamed. An old campaign URL redirects to a page that was later reorganized. Each change adds a hop, and without someone actively managing the redirect map, chains accumulate.

Google follows redirect chains, but each hop loses some PageRank. The commonly cited figure is that a single 301 redirect passes approximately 90–99% of link equity. A chain of 3 redirects might pass only 80–90% of the original equity to the final destination — less than a direct redirect would.

Crawl budget is the larger practical concern. Each redirect hop counts as a crawl. A page accessible only through a 3-hop redirect chain costs 3 crawl slots to reach. On large sites with many redirect chains, this meaningfully reduces how many unique pages Google can crawl in its allocated budget.

Each redirect adds latency — typically 50–150ms per hop, plus DNS resolution time. A chain of 3 redirects adds 150–450ms before the first byte of the destination page loads. On mobile connections, this compounds. For pages that are already borderline on Core Web Vitals, a redirect chain can push LCP from 'Needs Improvement' to 'Poor'.

Browsers also have a maximum redirect limit (typically 20 for Chrome) and will refuse to follow chains longer than this. While most chains don't reach this limit, they're still unnecessary performance overhead.

Finding redirect chains requires following every URL on your site and recording the full redirect path. This is impossible to do manually at scale. A crawl tool traces the redirect path for each URL and flags any chain longer than a single hop.

Fixing redirect chains means updating each redirect in the chain to point directly to the final destination. If A → B → C, update A's redirect to point directly to C and update B's redirect (if B is linked from anywhere) to also point directly to C. The chain collapses to a single hop from any starting point.

WebEnture's Redirect Mapper Agent crawls your site and traces every redirect path, identifying all chains and the specific hops involved. It prioritizes chains by the authority of the source URL (chains from high-authority URLs cause the most link equity loss) and provides the updated redirect mapping to collapse them.