Any address: your own old URLs, http:// or www versions, or a short link
How to use
Enter one URL or a list
Paste any address into the URL field. Without a scheme the check starts from http://, so you see how HTTP upgrades to HTTPS. For a migration, open Bulk and paste old URLs, each followed by its expected new URL.
Trace the redirects
Click Trace redirects. Our server follows each Location header, then reads the final page for meta refresh and JavaScript redirects if that option is ticked, recording every hop until the chain ends or hits 10 hops.
Read the verdicts and export
Check the verdicts for loops, long chains, temporary redirects and client-side hops, then walk the numbered chain. In Bulk, look for Wrong target badges and download the CSV for your fix list.
Why Redirect Checker
- Shows every hop with its exact status code and where it sends the visitor.
- Detects meta refresh and JavaScript redirects as well as HTTP ones.
- Flags loops, long chains, temporary redirects and merged-hop chances.
- Bulk migration check against expected URLs, with CSV export.
301 vs 302 vs 307 vs 308 redirects
All four send the visitor to a new URL. The differences are whether the move is permanent and whether the browser must repeat the same request method, which matters for forms and APIs. For search, Google treats 301 and 308 as strong signals that the target should be indexed, and 302 and 307 as weaker ones. If you are unsure which to use for a page that has moved for good, use 301.
| Code | Permanent? | Keeps the request method? | Typical use |
|---|---|---|---|
| 301 | Yes | Not guaranteed; browsers may turn POST into GET | Moved pages, domain moves, HTTPS |
| 302 | No | Not guaranteed | Short-term moves, tests, login redirects |
| 307 | No | Yes | Temporary moves where a form POST must stay a POST |
| 308 | Yes | Yes | Permanent moves for APIs and forms |