Live diagnostic
Redirect Checker & Chain Mapper
Trace 301/302 redirect chains and spot loops. Free, no signup.
>
When a URL moves, the chain of redirects between the old address and the final page decides how fast users arrive and how much SEO value survives the trip. This redirect checker maps every hop — status code and target — so you can prove a 301 resolves cleanly, collapse needless chains into a single redirect, and catch loops before they break the page.
How it works
- 01
Enter a URL
Paste the starting URL — an old page, a shortened link, or any address you want to trace.
- 02
Trace the chain
Sitewell follows each redirect hop in order, recording the status code and target URL at every step.
- 03
Inspect the path
See the full chain, confirm the final destination, and get a warning if a redirect loop is detected.
Frequently asked questions
- What is the difference between a 301 and a 302 redirect?
- A 301 is a permanent redirect — it tells search engines the page has moved for good and passes ranking signals to the new URL. A 302 (or 307) is temporary and asks engines to keep the original URL indexed. Use 301 for moved or merged pages, 302 only for short-lived diversions.
- Why do redirect chains hurt SEO?
- Each extra hop adds latency and dilutes link equity, and long chains can exceed the limit crawlers will follow, leaving the final page undiscovered. Aim to point the original URL directly at the final destination in a single 301.
- What is a redirect loop?
- A redirect loop happens when URL A redirects to B and B redirects back to A (or any cycle), so the page never resolves. Browsers abort with a 'too many redirects' error. Sitewell flags loops automatically so you can break the cycle.
- Does this follow meta refresh and JavaScript redirects?
- It traces server-side HTTP redirects (301, 302, 307, 308) hop by hop and reports the status and target of each. Client-side meta refresh or JavaScript redirects are not part of the HTTP chain, so verify those in a browser.