Redirect Chain Analysis

Overview

Redirects are essential for managing URL changes, but poorly implemented redirects can hurt performance and SEO. SEO Crawler analyzes your redirect chains to identify loops, excessive hops, and suboptimal configurations.

Available on: All plans (Free, Solo, Pro, Agency)

What We Detect

Redirect Chains

A redirect chain occurs when a URL redirects to another URL, which then redirects again:

A → B → C → D (3-hop chain)

Each redirect hop adds latency and dilutes SEO value. Google recommends a maximum of 2 redirects in any chain.

Redirect Loops

A redirect loop occurs when redirects create a circular reference:

A → B → C → A (infinite loop)

Loops prevent pages from loading and cause browsers to display error messages.

Redirect Types

Code	Type	SEO Impact
301	Permanent Redirect	Passes full link equity (use for permanent moves)
302	Temporary Redirect	May not pass link equity (use for temporary changes)
303	See Other	Used after POST requests
307	Temporary Redirect	Strict HTTP method preservation
308	Permanent Redirect	Strict HTTP method preservation
Meta Refresh	HTML-based redirect	Slow, not recommended for SEO
JavaScript	Client-side redirect	Not followed by all crawlers

Why Redirect Issues Matter

Performance Impact

Each redirect adds:

DNS Lookup: ~20-120ms
TCP Connection: ~20-60ms
SSL Handshake: ~30-100ms (HTTPS)
Server Response: ~50-200ms

A 3-hop redirect chain can add 300-500ms+ to page load time.

SEO Impact

PageRank Dilution: Each redirect loses ~15% of link equity
Crawl Budget Waste: Search engines follow redirects, using crawl resources
Indexing Confusion: Too many redirects can prevent proper indexing

A page behind a 5-hop redirect chain may retain less than 50% of its original link equity.

Reading Redirect Analysis

After a crawl, the Redirects section shows:

Chain Summary

Metric	Description
Total Redirects	Number of URLs that redirect
Avg Chain Length	Mean number of hops
Loops Detected	Critical: redirect loops found
Long Chains	Chains with 3+ hops

Detailed Chain View

Click any redirect to see the full chain:

https://example.com/old-page
  ↓ 301
https://example.com/newer-page
  ↓ 301
https://example.com/newest-page
  ↓ 301
https://example.com/final-page ✓

Chain Length: 3 hops
Total Time: 847ms
Recommendation: Update original link to point directly to final destination

Common Issues and Fixes

Long Redirect Chains

Problem
Solution

Multiple URL changes over time have created accumulated redirects:

/product → /products/item → /shop/products/item → /store/item

Update all redirects to point directly to the final destination:

# Before (chained)
Redirect 301 /product /products/item
Redirect 301 /products/item /shop/products/item
Redirect 301 /shop/products/item /store/item

# After (direct)
Redirect 301 /product /store/item
Redirect 301 /products/item /store/item
Redirect 301 /shop/products/item /store/item

Redirect Loops

Problem
Solution

Conflicting redirect rules create infinite loops:

/page-a → /page-b → /page-a (loop!)

Map out all redirect rules
Identify the circular reference
Decide on the canonical destination
Update rules to eliminate the loop

# Remove conflicting rule
# Redirect 301 /page-b /page-a  ← DELETE THIS

# Keep intended direction
Redirect 301 /page-a /page-b

HTTP to HTTPS + www Redirects

Problem
Solution

Separate redirects for protocol and subdomain create unnecessary hops:

http://example.com → https://example.com → https://www.example.com

Combine into a single redirect:

# nginx configuration
server {
    listen 80;
    listen 443 ssl;
    server_name example.com;
    return 301 https://www.example.com$request_uri;
}

# .htaccess configuration
RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule ^ https://www.example.com%{REQUEST_URI} [L,R=301]

302 vs 301 Misuse

Problem
Solution

Using 302 (temporary) for permanent URL changes:

302 Redirect: /old-url → /new-url

This tells search engines to keep indexing the old URL.

Use 301 for permanent redirects:

# Correct: 301 for permanent moves
Redirect 301 /old-url /new-url

# Only use 302 for truly temporary redirects
# (e.g., A/B testing, maintenance pages)

Best Practices

Limit to 1-2 Hops

Always redirect directly to the final destination. Never chain redirects.

Use 301 for Permanent

Only use 302/307 when the redirect is genuinely temporary.

Update Internal Links

After setting up a redirect, update internal links to use the new URL directly.

Monitor Regularly

Redirect issues accumulate over time. Regular crawls catch problems early.

Redirect Audit Workflow

Run a Full Crawl

Enable redirect analysis to capture all redirect chains.

Fix Critical Issues First

Address redirect loops immediately—these completely break page access.

Flatten Long Chains

Update redirects to point directly to final destinations.

Update Internal Links

Change internal links to point to final URLs, eliminating redirect need.

Verify Fixes

Re-crawl to confirm all redirect issues are resolved.

Filtering Options

Filter	Description
Chain Length	Show chains with N+ hops
Has Loop	Only show redirect loops
Redirect Type	Filter by 301, 302, etc.
Source URL	Filter by URL pattern

Getting Started

Features

Domain Management

Crawling

Plans & Billing

Agency Features

Integrations

Redirect Chain Analysis

Overview

What We Detect

Redirect Chains

Redirect Loops

Redirect Types

Why Redirect Issues Matter

Performance Impact

SEO Impact

Reading Redirect Analysis

Chain Summary

Detailed Chain View

Common Issues and Fixes

Long Redirect Chains

Redirect Loops

HTTP to HTTPS + www Redirects

302 vs 301 Misuse

Best Practices

Limit to 1-2 Hops

Use 301 for Permanent

Update Internal Links

Monitor Regularly

Redirect Audit Workflow

Filtering Options

Export Options

Broken Link Detection

Response Time Tracking

​Overview

​What We Detect

​Redirect Chains

​Redirect Loops

​Redirect Types

​Why Redirect Issues Matter

​Performance Impact

​SEO Impact

​Reading Redirect Analysis

​Chain Summary

​Detailed Chain View

​Common Issues and Fixes

​Long Redirect Chains

​Redirect Loops

​HTTP to HTTPS + www Redirects

​302 vs 301 Misuse

​Best Practices

Limit to 1-2 Hops

Use 301 for Permanent

Update Internal Links

Monitor Regularly

​Redirect Audit Workflow

​Filtering Options

​Export Options

​Related Features

Broken Link Detection

Response Time Tracking

Overview

What We Detect

Redirect Chains

Redirect Loops

Redirect Types

Why Redirect Issues Matter

Performance Impact

SEO Impact

Reading Redirect Analysis

Chain Summary

Detailed Chain View

Common Issues and Fixes

Long Redirect Chains

Redirect Loops

HTTP to HTTPS + www Redirects

302 vs 301 Misuse

Best Practices

Redirect Audit Workflow

Filtering Options

Export Options

Related Features