What is a redirect chain? Definition, SEO impact and fixes

How does a redirect chain form?

A redirect chain forms when a redirect points to a URL that itself redirects, instead of pointing to the final page. Each step is an HTTP response from the 3xx class defined in RFC 9110, the IETF standard for HTTP semantics, with a Location header that names the next URL. Browsers and Googlebot request each URL in turn until they get a normal 200 response.

Chains rarely come from one decision. They build up over years through:

• Protocol changes: http to https.
• Host changes: non-www to www or the reverse.
• Formatting rules: trailing slash or lowercase normalisation.
• Site migrations: new URL structures, CMS changes or domain moves.
• Content updates: merged articles and discontinued products redirected again after an earlier redirect.

A typical example: http://example.com/shoes redirects to https://example.com/shoes, which redirects to https://www.example.com/shoes, which redirects to https://www.example.com/shoes/. That is 3 hops for one link.

Redirect chain vs redirect loop

A redirect loop is a chain that never ends because it returns to an earlier URL. MDN Web Docs notes that browsers detect such loops and show an error, for example Firefox’s message that the server is redirecting in a way that will never terminate. A chain eventually reaches a page, a loop never does.

How does Google treat redirect chains?

Google follows a chain up to a limit and indexes only the final target. Google Search Central states that its crawlers follow up to 10 redirect hops by default and ignore any content returned by the redirecting URLs. The Page indexing report in Search Console lists four redirect errors: a chain that was too long, a redirect loop, a redirect URL that exceeded the maximum URL length, and a bad or empty URL in the chain.

Chains also mix signals. A permanent 301 redirect or 308 redirect tells Google the target should be canonical, while a temporary 302 redirect keeps the source URL as a candidate. A chain that combines both sends a weaker, mixed signal than one direct permanent redirect. On large sites every extra hop is another request taken from the crawl budget.

How to find and fix redirect chains

Fixing a chain means pointing every old URL and every internal link straight at the final destination. I use this process in technical audits:

1. Crawl the site with a tool that reports redirect chains, such as Screaming Frog or Sitebulb.
2. Export old URLs from backlinks and Search Console to catch external links that start chains.
3. Update redirect rules so each old URL goes to the final URL in one hop.
4. Update internal links, canonical tags, hreflang and XML sitemaps to the final URL.
5. Recrawl and check that every redirect resolves in a single step.

Server examples as plain text. Nginx, one hop from any http or non-www request: return 301 https://www.example.com$request_uri; placed in the http and non-www server blocks. Apache, one rule instead of two: Redirect 301 /old-page https://www.example.com/new-page/ with the final URL, slash included. Google recommends keeping redirects for at least 1 year after a site move and, for users, ideally indefinitely.

Redirect chains are one of the first items I check in a technical SEO audit, especially before an international domain move, where http, host and language-folder redirects stack quickly. More on that in my technical SEO services.