Back to Glossary
SEO

Redirect Chain

A redirect chain occurs when two or more redirects are linked together, such as A→B→C, so a request passes through several intermediate URLs before reaching the final destination. Unlike a single redirect, the accumulated hops slow down page loads, waste crawl budget, and risk diluting link signals.

  • A redirect chain is a sequence of two or more linked redirects (A→B→C), distinct from a single redirect that makes just one hop (A→B).
  • Each extra hop adds a round trip that slows loading, and some browsers and user agents will not follow a long chain all the way to the end.
  • Google states that Googlebot follows up to 10 hops in a chain, but recommends redirecting straight to the final destination whenever possible.
  • When a chain is unavoidable, Google and Semrush both advise keeping it short — ideally three or fewer redirects, and under five.
  • The core fix is to update redirect rules and internal links so the starting URL points directly at the final URL, skipping every intermediate step.

Overview

A redirect chain happens when one URL redirects to another, that URL redirects to yet another, and so on — two or more redirects stacked back to back. For example, if example.com/page-a sends the request to /page-b and then on to /page-c, the request makes two hops before it reaches a final 200 response.

What matters most is the distinction from a single redirect. A single redirect such as A→B, which moves the request just once, is a normal and recommended way to handle a site move or a URL change. A chain, by contrast, is what you get when those redirects are linked across multiple steps and pile up. The more steps there are, the higher the cost to both users and crawlers.

Why It Is a Problem

  • Slower performance: Every hop adds another HTTP round trip, which slows page loading and hurts the user experience. Both Ahrefs and Semrush note that chains drag down load speed.
  • Compatibility limits: According to Google, not every user agent or browser supports long redirect chains, so in some environments the request may never reach the final page.
  • Wasted crawling: Chains complicate how search engines crawl a site and blur its internal link structure, which can affect indexing efficiency (Semrush, Ahrefs).
  • Risk of lost signals: The more hops there are, the greater the chance that ranking signals fail to pass cleanly through to the intended final URL.

Diagnosis

Redirect chains surface as a dedicated check in site-crawling tools. Ahrefs flags them as a "Redirect chain" issue in the Redirects section of Site Audit, while Semrush reports them under its "Redirect chains and loops" check on the Issues tab, listing the chain length together with the URLs involved. For individual URLs you can use the URL Inspection tool in Google Search Console; for bulk URLs, a command-line tool or script can read the hop sequence from the response headers.

The Fix: Shorten to a Direct Redirect

The guiding principle is to remove the intermediate steps and connect the starting URL straight to the final destination in a single hop.

  • Update redirect rules: Rewrite an A→B→C chain as a single A→C 301 (or 308) so the starting URL points directly at the final 200 page.
  • Replace internal links: Within the site, swap any links that point to an intermediate, redirected URL for links to the final URL. Ahrefs recommends pointing internal links directly at the final destination as the first remedy.
  • Break loops: A loop that circles back to the starting point is separate from a chain and must always be broken (Semrush).
  • Re-verify: After the fix, re-audit with the same crawling tool and manually check the affected URLs to confirm they reach the final destination without any unnecessary hops.

Google's Recommendations

Google Search Central states that Googlebot "follows up to 10 hops in a chain of linked redirects," while still recommending that you "redirect to the final destination directly." When a direct redirect is not possible, it advises keeping the chain short — "ideally three or fewer, and under five." The reasoning Google gives is that "chaining redirects adds latency for users, and not all user agents and browsers support long chains." Semrush likewise advises against using more than three redirects in a single chain.

Example: Collapsing a Chain to One Hop in .htaccess

# Bad: a chain that stacks two hops (A -> B -> C)
Redirect 301 /page-a /page-b
Redirect 301 /page-b /page-c

# Good: point each starting URL straight to the final destination (A -> C)
Redirect 301 /page-a /page-c
Redirect 301 /page-b /page-c

Implementation Checklist

  • Pull the "Redirect chain / chains and loops" issues from a crawling tool (Ahrefs Site Audit, Semrush Site Audit).
  • For each chain, identify the starting URL, the final 200 URL, and the intermediate hops in between.
  • Rewrite the redirect rules as a single A→final-URL 301/308.
  • Replace any internal links that pointed to an intermediate URL with links to the final URL.
  • If a loop exists, remove the redirect that circles back to break it.
  • Re-audit after the fix and manually check key URLs to confirm the chain is reduced to a single hop.
  • Keep valid redirects in place for the long term (typically at least one year).

References and Sources

Related terms