Redirect Checker
Follow a URL through every redirect and see exactly where it ends up.
Every hop, explained
We follow the chain hop by hop — HTTP redirects and meta-refresh — showing each URL, status code, redirect type and timing. Each step is checked safely and independently.
Problems we flag
Long chains, temporary redirects that should be permanent, redirect loops, and HTTPS-to-HTTP downgrades that hurt security and SEO.
HTTP and meta-refresh redirects
Besides 301, 302, 303, 307 and 308 responses the tool follows meta-refresh redirects and reports each type, so you know exactly how a browser ends up on the final page.
Frequently asked questions
301 or 302 — which is better for SEO?
Use 301 (or 308) for permanent moves so search engines transfer ranking signals. 302 and 307 are meant for temporary redirects.
How many redirects are too many?
Keep chains to one hop where possible. Every extra redirect adds latency, and long chains can stop crawlers from following them.
What is a redirect loop?
A loop happens when URLs redirect to each other forever, so the page never loads. The checker stops after a safe number of hops and shows the cycle so you can fix the rule that causes it.
Does the checker follow JavaScript redirects?
No. It follows the HTTP and meta-refresh redirects that any client sees without running scripts. Redirects done in JavaScript need a real browser.