Redirect Checker
Check where a URL redirects. Follows every 301, 302, 307 and 308 hop to the final destination, with the status code and timing of each. Catches redirect loops, mixed HTTP/HTTPS chains and redirect chains that slow the page down.
Frequently asked questions
How do I check where a URL redirects?
Paste the URL above. The redirect checker requests it without following redirects, reads the status code and Location header, and repeats on each new address until a page answers with a non-redirect status or 10 hops are reached. Every hop is shown with its code and timing.
What is the difference between a 301 and a 302 redirect?
301 (and 308) is permanent: search engines move ranking to the new URL and browsers cache it. 302 (and 307) is temporary: the old URL stays indexed. Use 301 for moved pages and domain changes; 302 for short-lived detours like a maintenance page.
What is a redirect chain and why does it matter?
Several redirects in a row, for example http://site.com to https://site.com to https://www.site.com/. Each hop adds a round trip (often 100-300 ms on mobile), and long chains dilute link signals. Point every old URL straight at its final address.
How many redirects are too many?
One is normal, two is acceptable. From four hops on, the checker warns: flatten them. Googlebot follows up to 10 hops per crawl and browsers give up on loops after about 20.
Does the redirect checker follow JavaScript or meta refresh redirects?
No. It follows HTTP redirects (301, 302, 303, 307, 308) only, the ones search engines treat as real redirects. A page that redirects with a meta refresh tag or JavaScript shows up as the final 200 response.