Redirect checker
Enter a URL to trace its full redirect chain — every hop, each status code, and the final destination — so you can catch redirect loops, chains, and the wrong status type.
How it works
The checker requests your URL server-side without automatically following redirects, reads the status code and Location header, then repeats for each hop until it reaches a non-redirecting response or a loop. It reports the whole chain, not just the endpoint.
Each hop shows its status code: a 200 is the final page, a 301 is a permanent redirect, a 302 or 307 is temporary. The distinction matters for SEO — permanent redirects are the ones that consolidate ranking signals to the destination.
Requests run from the server with a short timeout and a hop limit, and only public URLs are allowed. Private and internal addresses are rejected.
Assumptions and limitations
- It follows only HTTP-level redirects (3xx responses). It cannot see JavaScript or meta-refresh redirects that happen after the page loads.
- Some servers respond differently to an automated request than to a browser — different geolocation, no cookies, a different user agent — so an occasional chain may not match exactly what a user sees.
- Only publicly reachable URLs work; pages behind authentication, private networks, or firewalls cannot be checked.
Frequently asked questions
What is the difference between a 301 and 302 redirect?
A 301 is a permanent redirect: it tells search engines the page has moved for good and ranking signals should transfer to the destination. A 302 (or 307) is temporary, signaling the original URL will return. Using a 302 where you meant a 301 can prevent the destination from consolidating the original's authority.
Why are redirect chains bad for SEO?
Each extra hop adds latency for users and consumes crawl budget, and long chains can dilute or delay how ranking signals pass through. Where possible, redirect straight to the final destination in a single hop rather than through a chain of intermediate URLs.
How do I find a redirect loop?
A redirect loop is a chain that never reaches a final page because URLs point back at each other. This checker stops after a hop limit and flags a likely loop, showing you the repeating URLs so you can break the cycle.
What is a redirect chain?
A redirect chain is when a URL redirects to another URL that itself redirects, and so on, before reaching the final page. This tool shows every step and status code so you can collapse multi-hop chains into a single redirect.
Does this store the URLs I check?
No. The URL is used only to perform the redirect trace for your request and is not stored or logged.
More free tools like this, by email
I publish new calculators and explainers regularly. Get them when they land — no spam, unsubscribe anytime.