Redirect Chains SEO Guide

Google recommends a maximum of one redirect hop from the original URL to the destination. Two hops are generally tolerated. Three or more hops are frequently abandoned by Googlebot — the crawler may not follow the full chain, meaning the destination URL receives no crawl credit from the original address. Browsers also add latency for each hop, degrading user experience.

Yes. Each redirect hop degrades the proportion of PageRank transferred to the final destination. A single 301 redirect passes approximately 99% of link equity. Each additional hop further reduces the amount transferred. In practice, the degradation per hop is small, but chains accumulated across thousands of URLs create a measurable drag on the authority of deep pages.

A redirect chain is a sequence of redirects leading to a final destination (A → B → C → 200). A redirect loop occurs when the chain circles back to a URL already in the sequence (A → B → C → A), preventing any final destination from being reached. Redirect loops always result in an error for users and crawlers. Both are harmful but loops are immediately critical — they make the URL completely inaccessible.

The most common source is layered migrations. When a site migrates from URL structure A to B, a set of redirects is created. When it later migrates from B to C, a new set is created — but if the original A→B redirects aren't updated to A→C, a chain forms. Any URL restructuring, CMS upgrade, or domain move that doesn't update all prior redirect rules will introduce new chains.

Yes — you can collapse the chain at the redirect rule level without updating source content. If A → B → C, you update the redirect rule for A to point directly to C, then remove or update the B→C rule if B is no longer needed. This is the fastest fix when chains exist in external backlinks or sitemaps that you cannot directly control.

Yes, significantly on large sites. Googlebot allocates crawl budget per domain, and each redirect hop consumes additional budget compared to a direct 200 response. Sites with thousands of chained redirects see slower content discovery, lower crawl frequency on deep pages, and delayed indexing of newly published content. For enterprise sites, crawl budget efficiency is a meaningful organic performance lever.

Both. Before a migration, audit existing chains and collapse them so you're not migrating additional complexity. During the migration, ensure all redirect rules point directly to the final post-migration URL — never redirect to an intermediate URL that itself redirects. After the migration, run a verification crawl to catch any newly introduced chains before they accumulate external links.

Use a site crawler configured to follow redirects and report the full redirect path for each URL. Screaming Frog, Ahrefs Site Audit, and Sitebulb all show redirect chain depth in their reports. Export all URLs with a chain length greater than 1 and prioritize collapsing chains on URLs with the most external inbound links — these have the greatest authority leakage.