See exactly where a URL really ends up
A redirect tells a browser or search engine that a page has moved and where to find it now. Done well, redirects keep old links working after a redesign, a domain change or a move to HTTPS. Done badly, they create long chains, loops and temporary redirects that were meant to be permanent, all of which slow pages down and can hold back SEO.
This checker requests your URL and follows each redirect one step at a time, recording the status code, the destination and how long each hop took. It stops at the final page, at a loop or after ten hops. A summary shows the number of redirects, the final status and the total time, and plain-language notes point out common problems.
The check runs on our server, which fetches only headers, not page content. For safety, addresses that point to private networks are refused, and a limit applies to how many checks each visitor can make in a short time.
Common status codes
| Code | Meaning | When to use it |
|---|---|---|
| 301 | Moved permanently | A page or site has moved for good. |
| 308 | Permanent redirect | Like 301, and the request method must stay the same. |
| 302 | Found (temporary) | A short-term move, such as a seasonal page. |
| 307 | Temporary redirect | Like 302, with the request method kept. |
| 200 | OK | The final page loaded successfully. |
How to use the Redirect Checker
- Type or paste the URL you want to trace. You can leave out http:// or https://.
- Choose how the request should identify itself: desktop browser, mobile browser or a generic crawler.
- Press Check redirects.
- Read the summary, then follow the numbered hops from the first URL to the last.
- Act on the notes underneath, such as shortening chains or replacing temporary redirects.
What you get
- Step-by-step trace with status code and timing for every hop.
- Detects redirect loops and stops safely after ten hops.
- Highlights temporary redirects, long chains and error endings.
- Option to request as a desktop browser, mobile browser or generic crawler.
- Shows whether an HTTP address is upgraded to HTTPS.
When it comes in handy
- Checking redirects after a site migration or domain change.
- Confirming that http:// and www versions point to a single preferred address.
- Finding redirect chains that slow landing pages for paid traffic.
- Verifying that old URLs send visitors and search engines to the right new page.
- Debugging a link that works in one browser and loops in another.
Tips for better results
- Aim for one hop at most between an old URL and its final destination.
- Use 301 or 308 for permanent moves and keep them in place for at least a year.
- Update internal links to point straight at final URLs so they do not rely on redirects.
- Test both the http:// and https:// versions, with and without www.
- Test with the mobile option if your site serves different content or redirects to a separate mobile address.
Redirect checks go hand in hand with a wider site audit. The SEO score checker and domain age checker on UseTools.in are useful companions.
Frequently asked questions
What is a redirect chain?
A chain is a series of redirects in a row, such as http to https and then non-www to www. Each hop adds delay, so it is better to send visitors straight to the final address.
What is the difference between a 301 and a 302 redirect?
A 301 says a page has moved permanently, so search engines transfer its signals to the new address. A 302 says the move is temporary, so the old address is expected to return.
Do redirects hurt SEO?
A single clean 301 is normally fine. Long chains, loops and wrongly used temporary redirects can waste crawl effort and slow pages, so they are worth fixing.
Why does the tool stop after ten redirects?
Browsers also give up after a limited number of hops, and a chain that long is almost certainly a mistake. The tool stops and reports it.
Does the tool download the whole page?
No. It reads the response headers and discards the body, so it is quick and light on the website being checked.
Why was my URL not allowed?
For security, the checker refuses addresses that resolve to private or internal networks, and ports other than 80 and 443.
Why is a check sometimes refused?
To prevent abuse, each visitor can only run a limited number of checks in a few minutes. Wait a moment and try again.