Redirect Chain Checker
Follow a URL hop by hop and see every redirect between the start and the final page.
About this tool
Enter one URL and this follows it hop by hop, showing the status code and destination at each step, up to the point it stops redirecting.
Long chains are usually accidental — an http → https redirect, then a non-www → www redirect, then a trailing-slash redirect, each added by a different person at a different time. Every extra hop is another request before anyone sees the page.
Common questions
How many redirects is too many?
One is fine. Two is worth tidying. Three or more is worth fixing — search engines follow a limited number of hops, and every hop adds latency for real visitors.
What is the difference between 301 and 302?
A 301 says the move is permanent and the destination should replace the original. A 302 says it is temporary and the original should be kept. Using 302 for a permanent move is one of the most common migration mistakes.
Why does the chain stop before reaching a page?
The tool follows up to 8 hops. Beyond that a chain is almost certainly a loop, and following further would not tell you anything new.