Redirect chain: what it is, why it hurts and how to fix it

What is a redirect chain?

A redirect chain is a sequence of two or more redirects between the URL that was requested and the final page: URL A redirects to B, which redirects to C. A redirect loop is a chain that never ends because it points back to an earlier URL (A → B → A).

Chains usually build up over time: a site moves from HTTP to HTTPS, later adds or removes www, then restructures URLs, and each change adds a hop instead of updating the old rules.

What a chain looks like

Checking an old campaign link with curl -sIL (sample output, trimmed):

HTTP/1.1 301 Moved Permanently
Location: https://example.com/spring-sale

HTTP/2 301
location: https://www.example.com/spring-sale

HTTP/2 302
location: https://www.example.com/sale/spring/

HTTP/2 200

Three redirects before the page loads: HTTP → HTTPS, apex → www, old path → new path (as a temporary 302).

The visitor waited about 325 ms before the first byte of the real page. On a slow mobile network each hop can cost much more, because each may need a new DNS lookup, connection and TLS handshake.

Why redirect chains are a problem

• Slower pages. Every hop adds a round trip before content starts loading, which hurts time to first byte and LCP.
• Crawling waste. Search engines follow a limited number of hops; Google's documentation says Googlebot follows up to 10 redirect hops, then reports an error. Each hop also consumes crawl budget.
• Weaker signals. Long chains make it harder for search engines to consolidate signals onto the final URL, especially if a hop is a temporary 302.
• Lost tracking data. Some redirects drop the query string, so UTM parameters and ad click IDs disappear and the visit is counted as direct. Cross-domain hops can also strip the referrer.
• Fragility. Every extra rule is one more thing that can break into a loop.

How to find redirect chains

1. Crawl your site with an SEO crawler and export redirect chains; most tools list hops and final status.
2. Check important URLs manually with curl -sIL <url> or a browser extension that shows the redirect path.
3. Check your own links: navigation, sitemaps, canonical tags and hreflang should point straight to final URLs.
4. Check campaign links in ads, emails and QR codes; they are often years old.
5. Read server logs for 3xx responses served to crawlers; see log file analysis for SEO.

How to fix them

• Point every redirect directly at the final URL. Rewrite A → C instead of A → B → C, and keep B → C for anyone still linking to B.
• Combine protocol and host rules so http://example.com goes to https://www.example.com in one hop.
• Update internal links to the final URL, so internal traffic never hits a redirect.
• Use 301 or 308 for permanent moves, 302 or 307 only for genuinely temporary ones.
• Preserve query strings in redirect rules so campaign tags survive.
• Test for loops after every change to redirect rules.

In TapCub

Redirects happen before your analytics script loads, so TapCub records only the final page. Two symptoms point to redirect problems: a campaign whose clicks in the ad platform far exceed its sessions in TapCub, and a jump in direct traffic right after a URL migration, which usually means UTM parameters or the referrer were lost on the way. Check that redirect rules pass query strings through; see name UTM parameters and direct traffic. For crawler side effects, crawl health shows 3xx, 404 and 5xx responses per engine when server logs are imported.

Sources

• Google Search Central. Redirects and Google Search.
• Google Search Central. How HTTP status codes affect Google Search: 3xx redirection.
• MDN Web Docs. Redirections in HTTP.