Redirect tracer
Follow a URL's full redirect chain, hop by hop.
Long redirect chains slow pages and dilute SEO; loops break them entirely. Enter a URL and we follow every redirect one hop at a time, showing each URL, its status code (301, 302, 307, …), and where it points — so you can flatten chains and fix loops.
Frequently asked questions
301 vs 302 — which should I use?
Use 301 (permanent) when a page has moved for good; it passes SEO value. Use 302 (temporary) only for short-term redirects.
Why avoid long redirect chains?
Each hop adds latency and can lose link equity. Aim to redirect straight to the final URL in a single hop.
What causes a redirect loop?
A loop happens when URLs point back at each other — often http forcing https while a rule sends https back to http, or www and non-www each redirecting to the other. The tracer stops and flags the loop so you can find the conflicting rules.
What's the difference between a 301, 307, and 308?
A 301 is a permanent redirect that may let clients switch POST to GET; 308 is permanent but preserves the original method and body, and 307 is the temporary equivalent. Use 308/307 when the request method must be kept intact.
Do redirects hurt SEO?
A single clean 301 passes nearly all ranking signals, but chains and loops waste crawl budget and can lose equity at each hop. Redirecting straight to the final HTTPS URL is best.
Why does my redirect work in the browser but not here?
Browsers may have cached a permanent redirect, or the server redirects based on cookies, headers, or geography. This tracer follows the raw server responses, which is what search engines and API clients actually see.
More Website & HTTP tools tools
Want this checked automatically and around the clock? Create a free SJ Monitor account and we'll alert you the moment something changes.