Redirect Checker

This tool requests the address you enter and follows every redirect it returns, one hop at a time, up to a reasonable limit, recording the status code and destination at each step instead of only showing the final page. It then checks the full chain for the mistakes that actually hurt SEO and user experience: too many hops, loops that never resolve, drops from https back to http, and a broken status code at the end of the chain. Only the raw HTTP response at each hop is used, so a client-side JavaScript redirect that never reaches the server would not be seen here.

One common belief worth correcting: a 302 (temporary) redirect is not a weaker or "leakier" version of a 301 (permanent) for passing ranking credit. Google's own John Mueller and Gary Illyes have both said that for Google, the status code doesn't change how much link equity flows through the redirect, both 301s and 302s pass it. What the status code actually controls is which URL Google keeps in its index and treats as canonical: a 301 signals the move is permanent and Google typically drops the old URL right away, while a 302 signals it's temporary, though Google will eventually treat a 302 left in place for months as if it were permanent anyway. Use 301 for a genuine, permanent move, and 302 for something you expect to reverse, not because one passes more SEO value than the other.