What is a Redirect Chain?

Redirect chain: too many hops before the real page

A redirect chain is a sequence where URL A redirects to B, B redirects to C, and possibly more before a final 200 OK response. Each hop is a full HTTP round trip—browsers and crawlers follow Location headers until a non-redirect status or failure.

Chains are among the most common technical SEO debt items after migrations. They rarely break the homepage; they hide in legacy paths, parameter variants, and stacked infrastructure rules—silently consuming crawl budget and slowing 301 Redirect consolidation.

Chain visualization

Ideal:
/old-page ──301──► /final-page ──200──► content

Chain:
/old-page ──301──► /intermediate ──302──► /almost ──301──► /final-page ──200──► content
     hop 1              hop 2              hop 3              final

Four requests instead of one for every crawl and click that starts at /old-page.

How chains form

Layered migrations

2018: /article → /blog/article. 2022: /blog/article → /insights/article. Old links still hit two hops unless /article updated to point directly to /insights/article.

Protocol and host stacking

http://www.example.com/page
  → 301 https://www.example.com/page
  → 301 https://example.com/page
  → 301 https://example.com/page/
  → 200

Four hops from one bookmark—common when HTTP → HTTPS, www → apex, and trailing slash policies deploy separately without consolidation.

CMS + CDN duplicate rules

WordPress redirect plugin plus Cloudflare page rule plus origin nginx—each layer unaware of others.

Parameter normalization

/product?id=5 → /product/5 → /products/slug → canonical host—chains on legacy ecommerce patterns.

Mixed redirect types

302 Redirect hop followed by 301 Redirect followed by 307 Redirect—permanence signals conflict; crawlers may hesitate on consolidation.

SEO impact of redirect chains

Crawl budget waste

Googlebot fetching /old costs one queue slot; three hops consume three fetches before evaluating content. Million-URL sites with chains on templates multiply waste.

Signal dilution and delay

Link equity from external sites pointing at /old consolidates toward /final after processing each hop. Direct 301 from /old to /final is faster and clearer than hoping intermediate URLs pass signals cleanly.

Latency and Core Web Vitals

User clicks through hops—TTI delayed. Crawlers less sensitive to UX latency but still bounded by hop limits.

Indexing ambiguity

Intermediate URLs in chains may briefly appear in reports as "redirect" URLs. Long 302 Redirect intermediates may retain separate index entries longer than intended.

Failure amplification

If hop 3 returns 502 Bad Gateway, entire chain fails—even if hop 1 and 2 were healthy. More hops = more failure points.

Google's hop tolerance

Google follows multiple redirects in one crawl attempt but documents best practice: minimize chains. Extremely long chains risk aborted fetch—classified as crawl error. Do not treat "Google allows five" as target—target one.

Detecting redirect chains

curl trace

curl -sI -A "Googlebot" -w '%{url_effective}\n' -o /dev/null \
  -L --max-redirs 10 'http://www.example.com/old-path'

Count redirects in verbose mode:

curl -v -A "Googlebot" -o /dev/null -L 'http://www.example.com/old-path' 2>&1 | grep '< HTTP'

Crawl tools

Site crawlers record hop count per seed URL and per internal link target—surfaces chains users never see starting from homepage alone.

Log analysis

Sequential status 301/302 on same client request session—less common in logs than crawl tools.

Flattening redirect chains

Rule: one hop to final

# Before: /legacy → /temp → /current
# After:
Redirect 301 /legacy https://example.com/current
Redirect 301 /temp https://example.com/current

Update every legacy source—not only the first hop.

Consolidate infrastructure rules

Document single owner for redirects: CDN vs origin. Remove duplicate host/protocol rules after unified policy.

Update internal links

Internal links should point to final URLs—skip hops entirely:

<!-- Bad -->
<a href="/legacy">Article</a>

<!-- Good -->
<a href="/current">Article</a>

Sitemaps list only final 200 OK URLs.

Audit external backlink targets

Cannot edit third-party sites—but server-side flattening still reduces hop count from their entry point.

Chain vs redirect loop

Chains waste resources; loops block retrieval entirely. See Redirect Loop for cycle detection.

Example: SaaS docs rebrand

docs.oldsaas.com/path → 301 docs.newsaas.com/path → 302 www.newsaas.com/docs/path → 301 newsaas.com/docs/path → 200.

Three hops, mixed permanence, www correction last.

Flattened:

docs.oldsaas.com/* → 301 newsaas.com/docs/* (single hop)

Internal docs links updated; sitemap one host; HTTPS enforced in same rule set. Crawl requests per legacy URL dropped from 4 to 1; indexed doc URLs consolidated within one month.

How Crawlox helps with redirect chains

Crawlox builds redirect graphs across authorized crawls: start URL, each hop status (301, 302, 307, 308), and final response code. Filter URLs with hop count greater than one, export legacy paths for flattening rules, and verify internal links bypass chains by pointing directly at 200 OK destinations—cutting crawl waste and accelerating permanent redirect consolidation.