Redirect chain

A redirect chain is a series of two or more redirects between the original URL and the final destination, for example A to B to C. Chains slow down users, waste crawl resources and can cause Google to stop before reaching the final page.

A redirect chain happens when a URL redirects to another URL that itself redirects again. Instead of going straight from the old page to the new one, browsers and crawlers have to make several requests in a row.

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/ with a trailing slash. Four requests for one page. Chains like this build up over the years as sites move to HTTPS, change hostnames, restructure categories and rename pages, each time adding a new redirect on top of the old ones.

A redirect loop is the broken version: A redirects to B and B redirects back to A. The page never loads and browsers show an error.

Why chains are a problem:

  • Speed. Every hop adds a full round trip to the server, which is noticeable on mobile connections.
  • Crawling. Googlebot follows up to 10 redirect hops; beyond that it gives up and the final page is not reached through that URL. Even shorter chains cost crawl resources on large sites.
  • Signals. Each extra step is another chance for something to go wrong: a temporary redirect in the middle, a hop to a page that later changes, or a misconfiguration that breaks the whole chain.
  • Other bots. Some crawlers, including link checkers and certain AI bots, follow fewer redirects than Google.

How to find them. SEO crawlers report redirect chains and loops in a dedicated report. For single URLs, the Network tab in browser developer tools shows every hop and its status code. Check especially the URLs that receive backlinks, because those are the ones that carry value into your site.

How to fix them:

  1. Update every redirect rule so the original URL points straight to the final destination in one hop.
  2. Update internal links, canonicals, hreflang annotations and sitemaps to the final URL, so your own site never triggers a redirect.
  3. Combine protocol and hostname rules: redirect http and non-www directly to https://www in a single step.
  4. Make sure every hop is a permanent redirect (301 or 308). A 302 in the middle sends a mixed signal.
  5. Keep a redirect map from each migration, so the next migration can build on it rather than stacking new redirects on old ones.

Backlinks and chains. If an important backlink points to an old URL at the start of a long chain, ask the linking site to update it to the current URL when possible. That removes the dependency on your redirects entirely. For sponsored articles, it is good practice to give publishers the final, canonical URL from the start, so the link points to the right page without any redirect.

Questions about Redirect chain

How many redirects does Googlebot follow?

Up to 10 hops in a chain. After that it stops, but aim for a single hop from any old URL to its final destination.

Do redirect chains lose link value?

Permanent redirects pass signals, but every extra hop adds risk and slows crawling. A single direct redirect is always the safer choice.

What is the difference between a redirect chain and a redirect loop?

A chain eventually reaches a final page after several hops. A loop sends the request back to an earlier URL, so the page never loads.

Related terms