Redirect Chain Checker
Follow the complete HTTP redirect chain for any URL. See each hop, status code, and final destination.
Checking…
What are HTTP redirects?
HTTP redirects tell the browser to load a different URL than the one originally requested. They are used for domain migrations, enforcing HTTPS, canonicalizing URLs (www vs non-www), and handling moved content.
What is the difference between 301 and 302 redirects?
A 301 redirect is permanent — it tells search engines to transfer all ranking authority to the new URL. A 302 is temporary — search engines keep the original URL indexed. Use 301 for permanent moves and 302 for temporary changes.
Frequently Asked Questions
A 301 redirect is permanent — it tells search engines to transfer all ranking authority (link equity) to the new URL. A 302 is temporary — search engines keep the original URL indexed. Use 301 for permanent moves (domain migration, URL restructuring) and 302 for temporary changes (maintenance, A/B testing).
Search engines treat www.example.com and example.com as different URLs. If both serve content, your page authority is split between them. Pick one as canonical and redirect the other with a 301. Most modern sites use the non-www version.
Each redirect adds latency (typically 50-200ms per hop). Google follows up to 10 redirects but recommends keeping chains short. Ideally, any URL should reach its final destination in 1 redirect (or 0). Chains of 3+ redirects indicate configuration problems.