Redirects Studio
HTTP redirect checker
Trace an HTTP redirect chain hop by hop: every status code, every Location, the timing of each step and the final URL — so you can catch loops, chains and the wrong status code.
Every hop, in order
Type a URL and Redirects Studio follows it the way a browser would — one hop at a time — showing each status code (301, 302, 307, 308…), the Location it points to, and how long the hop took, all the way to the final destination.
Why the status code matters
A 301 is a permanent redirect that passes on ranking signals and is cached hard by browsers; a 302 or 307 is temporary. Using the wrong one — a 302 where you meant a permanent move — quietly costs you SEO value and confuses caches. We label each hop so the intent is obvious.
Catch chains and loops
Redirect chains (http → https → www → final) add latency and can silently break; redirect loops fail outright. We flag long chains, mixed HTTP/HTTPS hops, and loops so you can collapse them into a single clean redirect.
Frequently asked
What is the difference between 301 and 302?
A 301 is a permanent redirect: search engines transfer ranking to the new URL and browsers cache it aggressively. A 302 (and 307) is temporary: the original URL keeps its ranking and the redirect is not cached the same way. Use 301 for permanent moves.
How many redirects is too many?
Aim for at most one or two hops. Each redirect adds a round trip; long chains slow the first load and risk breaking. A common clean pattern is a single hop from HTTP to the canonical HTTPS URL.
What causes a redirect loop?
Usually two rules that disagree — for example one forcing www and another forcing non-www, or an HTTP→HTTPS rule that also downgrades. The browser bounces between them until it gives up. The trace makes the loop visible so you can fix the conflicting rule.