Back to Tools
Redirect Chain Analyzer
Follow URL redirect chains — status codes, SEO equity, latency per hop.
This tool is being set up. Backend processing coming soon. In the meantime, review the reference guide below and use the CLI equivalent.
HTTP Redirect Types: SEO & Performance Impact
| Status | Type | Link Equity | Use Case |
|---|---|---|---|
| 301 | Moved Permanently | ~90% passed | Permanent URL change, domain migration. Google recommends 301 for SEO. |
| 302 | Found (Temporary) | ~85% passed | Temporary redirect. Google may eventually treat long-standing 302s as 301s. |
| 307 | Temporary Redirect | ~85% passed | HTTP/1.1 replacement for 302. Preserves HTTP method (POST stays POST). |
| 308 | Permanent Redirect | ~90% passed | HTTP/1.1 replacement for 301. Preserves HTTP method. |
| Meta Refresh | HTML-level redirect | ~0% passed | Not recommended. Slow, bad UX, terrible for SEO. Avoid. |
Common Redirect Mistakes
1. Long redirect chains: Each hop adds latency and loses link equity. Google may stop following after 5 hops. Keep chains to 1-2 hops maximum.
2. Mixed HTTP/HTTPS in chain: Starting from HTTPS but redirecting through an HTTP hop exposes users to SSL stripping attacks. Use HSTS and all-HTTPS chains.
3. Non-www / www loops: example.com → www.example.com → example.com creates an infinite redirect loop. Pick one canonical version and redirect consistently.
4. Trailing slash inconsistency: /page → /page/ → /page creates unnecessary hops. Configure your web server to handle this with a single redirect.
CLI Equivalent
curl -sI -L https://example.com 2>&1 | grep -E "^(HTTP|Location:)"