Redirect Checker for 301, 302 and redirect chains
Check any URL's full redirect path with status codes and timings. Spot temporary redirects that should be permanent, chains that should be one hop, loops, and broken destinations.
What this tool checks
Redirects are invisible to most visitors, but search engines and site speed tools notice every one. The Redirect Checker requests your URL from our server and records each response in turn:
- The status code of every step (301, 302, 307, 308, 200, 404 and so on).
- The number of hops and how long each one took.
- Loops, where URLs point back to each other.
- Meta refresh redirects, which search engines handle less reliably than server redirects.
- Whether the chain ends on a live page, an error, or plain HTTP.
Tick Also check http/https and www/non-www to test all four ways people can type your domain and confirm they reach one preferred address.
Redirect status codes at a glance
| Code | Meaning | Use it when |
|---|---|---|
| 301 | Moved permanently | A page or site has moved for good. The most common SEO redirect. |
| 308 | Permanent redirect | Like 301, but the request method (for example a form POST) must stay the same. |
| 302 | Found (temporary) | A short-term move, such as a seasonal page or A/B test. |
| 307 | Temporary redirect | Like 302, but keeps the request method. Browsers also show 307 for HSTS upgrades. |
| 303 | See other | Sending a visitor to a results page after a form is submitted. |
| 200 | OK | The final page loaded. Every chain should end here. |
| 404 / 410 | Not found / gone | Never as the end of a redirect. Point the redirect at a live, relevant page. |
Common problems and how to fix them
A 302 where you meant a 301
Many hosting panels and plugins default to 302. If the move is permanent, switch it to 301 so search engines show the new URL and consolidate signals onto it.
Redirect chains
A typical chain: http://example.com → https://example.com → https://www.example.com → https://www.example.com/home. Each hop adds delay. Update your rules so every old address points straight at the final one.
Redirect loops
Loops usually come from two rules fighting each other, such as a CDN forcing https while the server forces http, or a www rule and a non-www rule both active. Check your host, CDN (for example Cloudflare page rules or redirect rules) and site settings for conflicting rules.
Redirects to the homepage
Sending every old URL to your homepage confuses visitors, and Google may treat those as "soft 404s". Redirect each old page to its closest equivalent instead.
For a deeper explanation, read 301 vs 302 redirects explained.
Frequently asked questions
What's the difference between a 301 and a 302 redirect?
A 301 says a page has moved permanently, so search engines should index the new address. A 302 says the move is temporary, so search engines may keep showing the old address. Use 301 (or 308) for permanent moves such as a new domain, HTTPS or a renamed page.
How many redirects is too many?
Aim for one. Every extra hop adds a little delay for visitors and makes search engines do more work. Browsers give up after about 20 redirects and Google follows up to 10, but you should never come close to those limits.
Why check all four versions of my domain?
Your site can be reached at http or https, with or without www, which makes four addresses. They should all end on one preferred version with a single redirect. Otherwise search engines may treat them as duplicate sites, and visitors may hit errors or warnings.
Can this check pages behind a login or on my local network?
No. The checker only reaches public web addresses on standard ports. Local, private and intranet addresses are blocked for security.
Does the checker show JavaScript or meta refresh redirects?
Meta refresh redirects are detected and followed. JavaScript redirects can't be followed, but we flag pages that appear to use them.