How many redirects stand between a link and its page?
Every redirect from an address to its final page, with status codes, loops and the HTTPS journey explained.
Your input is sent to our server to run the check. We don't log it. Public check targets and results may be cached temporarily to avoid repeating checks.
For example http://example.com/old-page. A bare name such as example.com is checked as https://.
Redirect chain
Ready to check
Enter an address and press Check.
- Final page
- Number of redirects
- HTTPS
Every redirect from an address to its final page, with status codes, loops and the HTTPS journey explained.
How to use
- Paste the web address you want to follow, such as http://example.com/old-page. A bare name like example.com is checked as https://.
- Press Check. The tool follows every redirect and shows the verdict, how many redirects there were and what to fix.
- Read the path below: each address that redirected, its status code and the page it finally reached.
How it works
A redirect is a server answering "not here, go there" instead of sending a page. The answer carries a status code and the new address, and the browser asks again. Codes 301 and 308 say the move is permanent, so search engines and bookmarks should switch to the new address; 302, 303 and 307 say it is temporary, so the old address stays the main one. The checker asks for the address the way a browser would, follows each answer and records the path.
Every redirect costs one more round trip before the page starts to load, so a path with three or more redirects is flagged. A path that returns to an address it already visited is a loop and never ends: a common cause is one rule sending http to https while another sends https back to http, or www and non-www pointing at each other. Example: http://example.com/ → 301 → https://example.com/ → 301 → https://www.example.com/ is two redirects, which one rule could do in one. Sources: MDN, Redirections in HTTP; Google Search Central, Redirects and Google Search.
The check runs once from our server and follows at most 5 redirects. Redirects done inside the page (a meta refresh or JavaScript) are not seen, and a site may treat our server differently from your browser, for example by country or by browser.
Sources
- Google Search Central: Redirects and Google SearchUsed for: rules
Frequently asked questions
What is the difference between 301 and 302?
301 means moved permanently: search engines should replace the old address with the new one. 302 means found elsewhere for now: the old address stays the main one. Use 301 or 308 for a permanent move.
What is the difference between 301 and 308?
Both are permanent. 308 guarantees the request method stays the same (a POST stays a POST), while old clients may turn a 301 into a GET. For ordinary page links the difference rarely matters.
How many redirects are too many?
Ideally one at most: the first address should go straight to the final one. This tool warns from three, and our checker gives up after 5.
Why does the browser say too many redirects?
The path is a loop. Check the rules that redirect http to https and www to non-www, and any CDN or proxy setting that does the opposite.
Do redirects hurt search rankings?
Google treats a permanent redirect as a signal that the new address is the canonical one, while a temporary redirect is not. Long chains also slow visitors down, so a single direct permanent redirect is the safe choice.
Why does it not follow my meta refresh?
A meta refresh or JavaScript redirect happens inside the page, after it has loaded. This tool follows only HTTP redirects, which the server sends before any page.





