What is Redirect chain?

A redirect chain forms when a URL doesn’t point straight to its final destination but passes through one or more intermediate URLs first. A request for page A is sent to B, B sends it to C, and only C answers with 200 OK. Each step is a “hop”: a separate HTTP request and response that the browser or crawler has to complete before it sees any content.

Chains are rarely designed. They accumulate: an HTTP-to-HTTPS rule one year, a www consolidation the next, a new URL structure after a redesign. Each rule is fine in isolation; stacked together, they send everyone the long way round.

Why chains cost you

• Latency. Every hop is another round trip, and a new TLS handshake whenever the host changes. On a slow mobile connection, three hops can delay the first byte of the real page noticeably.
• Crawling. Google documents that Googlebot follows up to 10 redirect hops; past that, Search Console reports a redirect error and the content isn’t fetched (Google Search Central: HTTP and network errors). Well before that ceiling, each extra hop is a wasted request — a real cost on large sites with a tight crawl budget.
• Mixed signals. A permanent redirect is a strong canonical signal. A chain that mixes 301, 302 and a meta refresh blurs which URL you actually want indexed.
• Other bots. Not every crawler is as persistent as Googlebot. AI search bots and link-preview fetchers may stop after fewer hops, so a short path is the safe default if you want your text read and quoted.

Example: a three-hop chain

$ curl -sIL http://example.com/shoes/ | grep -iE "^(HTTP|location)"
HTTP/1.1 301 Moved Permanently
Location: https://example.com/shoes/
HTTP/2 301
location: https://www.example.com/shoes/
HTTP/2 301
location: https://www.example.com/running-shoes/
HTTP/2 200

Three separate rules fire in sequence: force HTTPS, add www, then map the old category to the new one. The fix is to resolve protocol and host in a single rule and point the old path directly at its final URL. In an Apache .htaccess file:

RewriteEngine On
# Old path straight to its final home (one hop)
RewriteRule ^shoes/$ https://www.example.com/running-shoes/ [R=301,L]
# Protocol + host together (one hop)
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L]

Order matters: specific path rules go first, so they don’t wait for the generic host rule to run.

Common mistakes

• Fixing the redirect but leaving internal links, canonical tags and the XML sitemap on the old URL, so every internal click still starts a chain.
• Adding a new redirect on top of the old one after each migration instead of updating the old rule’s target.
• Dropping a temporary 302 redirect into the middle of a series of 301 redirect hops.
• Creating loops (A → B → A) that never resolve and show users an error page.

How to find and fix chains

Paste a URL into the Redirect Checker to trace every hop with its status code, Location header and timing. It flags loops and long chains and shows whether the http/https and www/non-www variants consolidate in one step. Test the four variants of your home page, then the old URLs from past migrations. The goal: at most one hop from any legacy URL, and zero hops from your own internal links.

Frequently asked questions