Redirect Chain Checker (301, 302, 307, 308)
Redirect Chain Checker
Check where a URL redirects. See every hop with its status code, spot chains, loops and temporary redirects, and get the fix in plain words.
- Free, no sign-up
- 301, 302, 307, 308
- Up to 10 URLs
- CSV export
Redirect chain
Enter a URL and press Check. You will see every hop, its status code and where the chain ends.
Our server requests each URL the way a browser would and follows server redirects (301, 302, 303, 307, 308) for up to 10 hops. Meta refresh and JavaScript redirects are not followed.
Step by step
How to use the redirect checker
Enter a URL
Type or paste any address. If you leave out http or https, the checker starts with https. To test the http version, type it in full, for example http://example.com.
Read the chain
Every hop is listed in order with its status code and the address it points to, ending on the final page or the error that stopped it.
Act on the summary
The summary says whether the setup is good, can be better, or broken, and explains why. For chains, it shows the rule that points the first URL straight to the final one.
Check up to 10 at once
Switch to “Check several URLs” to test a list, for example after a site move. Copy the result or download it as a CSV.
Status codes
What each redirect status code means
| Code | Name | What it means |
|---|---|---|
| 301 | Moved permanently | Permanent. Google shows the new URL in search and treats it as the main version. |
| 308 | Permanent redirect | Permanent, like 301, and keeps the request method. |
| 302 | Found | Temporary. Google keeps showing the old URL in search. |
| 307 | Temporary redirect | Temporary, like 302, and keeps the request method. |
| 303 | See other | Temporary. Common after a form is submitted. |
| 200 | OK | The final page loaded. This is where every chain should end. |
| 404 / 410 | Not found / Gone | The page does not exist. Redirect to a relevant live page or fix the link. |
| 5xx | Server error | The server failed. Check again later; if it repeats, tell your host or developer. |
Google explains the difference between permanent and temporary redirects in its guide to redirects and Google Search. If a page has moved for good, use a 301 or 308. Use 302 or 307 only when the old URL will come back.
Redirect chains
Why redirect chains are worth fixing
A redirect chain is when one redirect leads to another before the visitor reaches the page, for example http://example.com/page to https://example.com/page to https://www.example.com/page/. Each hop is an extra request, so the page loads more slowly, and crawlers spend more time on every link.
Google says its crawlers follow up to 10 redirect hops (source). Most chains are far shorter, but they grow quietly: every site move, https switch or URL change adds a hop on top of the old ones. The fix is simple: change the first redirect so it points straight to the final URL, and update internal links to the final URL too.
Common causes the checker flags for you:
- http to https, then www. Two separate rules that should be one.
- Trailing slash. A redirect that only adds or removes the last slash, stacked on another redirect.
- Temporary redirects left in place. A 302 used for a move that turned out to be permanent.
- Old redirects pointing at redirected pages. After a second redesign, the first set of redirects lands on URLs that now redirect again.
What it checks
What the checker can and cannot see
The checker asks our server to request your URL and follow each server-side redirect, the same way a browser does before it shows a page. It reports the status code and destination of every hop, and stops after 10 hops or 8 seconds without an answer.
It does not run JavaScript or read meta refresh tags inside a page, so redirects done that way are not shown. Some sites also answer bots differently from people, or block unknown visitors, which can show up as a 403 here while the page works in your browser.
FAQ
Questions about the tool
How do I check if a redirect is working?
Enter the old URL and press Check. A working redirect shows a 301 or 308 hop and then the new page with a 200 status. If the chain ends on 404, 500 or an error, the redirect is broken.
What is the difference between a 301 and a 302 redirect?
A 301 is permanent: Google shows the new URL in search and treats it as the main version. A 302 is temporary: Google keeps showing the old URL. Use 301 when a page has moved for good.
How many redirects are too many?
One hop is ideal. Two still work, but each extra hop slows the page and should be cleaned up when you can. Google’s crawlers follow up to 10 hops, and the checker flags anything over one.
What is a redirect loop?
A loop is when URLs redirect to each other in a circle, for example A to B and B back to A. The page never loads, browsers show “too many redirects”, and search engines cannot index it. The checker marks loops in red.
Why does the checker show 403 when the page works for me?
Some sites block requests from servers or unknown visitors, or protect pages behind a firewall like Cloudflare. The checker sees what that protection returns. Test a few other URLs on the same site to confirm.
Does it detect meta refresh or JavaScript redirects?
No. It follows server-side redirects only, which covers 301, 302, 303, 307 and 308. Redirects done inside the page with a meta tag or JavaScript need a browser to see.
Can I check several URLs at once?
Yes, up to 10 at a time. Switch to “Check several URLs”, paste one per line, and download the result as a CSV when it finishes.
Is the redirect checker free?
Yes, with no sign-up. Each URL is sent to our server only to follow its redirects. Nothing is stored.