Free Redirect Checker
Follow a URL hop by hop and see each HTTP status, including 301, 302 and 404, plus http/https and www changes. No signup.
- ✓ 100% free
- ✓ No signup
- ✓ Works for any website
When a URL moves, the redirect is what takes people and search engines to the new address. If that path is wrong, or if it passes through several extra hops, visitors wait longer and crawlers waste time. This free redirect checker follows the chain and shows the HTTP status of each step, so you can see whether a link ends where you expect. There is no signup.
How to use the redirect checker
- Paste the full URL you want to test, including the protocol. If you are checking a canonicalisation rule, test http and https, and the www and non-www hosts, as separate lookups.
- Read the chain from the first request to the final URL. Note the status code at each hop, the destination, and whether the protocol or host changed.
- If the chain is longer than it needs to be, or if a hop uses the wrong status code, point the original URL at the final address in one step, then run the check again.
The tool is also useful after a site migration, a permalink change, or a move from HTTP to HTTPS.
What the tool checks
The checker reports the status code for each hop, including 301 (moved permanently), 302 (found / temporary redirect), and 404 (not found). It also surfaces other responses you may meet along the way, such as 307, 308, 410, or a 5xx error. For each step you can see whether the request stayed on the same host, switched between www and the apex domain, or moved between http and https.
A 404 is not a redirect. If the chain ends on a 404, the URL is not resolving to a useful page. A redirect loop, where URLs point back to each other, shows up as a chain that never lands on a stable final address.
Why redirect chains matter
A single, correct 301 is the usual way to tell search engines that a page has moved for good. Extra hops add delay and give you more places for a mistake to hide. A temporary 302 is appropriate when the change really is temporary, but it is the wrong choice for a URL that will not be coming back. HTTP to HTTPS and www to non-www (or the reverse) should be deliberate, and visitors should reach your preferred host in as few hops as possible, ideally one.
Tips from our team
Prefer a 301 for a permanent move, and point the old URL directly at the final URL. Keep redirect chains short. When several old addresses need to move, send each one to the right new page, not to the homepage by default. After you change a rule, test the exact links you have shared in emails, ads, sitemaps and internal navigation, not only the homepage.
If you would like help checking a migration plan or a set of legacy URLs, Technical Speaks offers a free website and SEO audit.
Want an expert to fix it for you?
Our team handles technical SEO, content and local SEO for businesses in India and worldwide. Send us a message and we'll reply with clear next steps.
More free SEO tools
View all SEO tools →Frequently asked questions
Is this redirect checker free?
Yes. You can follow a redirect chain and inspect HTTP status codes with no signup.
When should I use a 301 instead of a 302?
Use a 301 when the move is permanent, such as a new permalink, a domain change, or HTTP to HTTPS. Use a 302 only when the original URL is meant to come back, for example a short seasonal page.
How long can a redirect chain be?
As short as you can make it. One hop to the final URL is best. Search engines can follow more than one redirect, but each extra hop adds time and risk. If you already have a chain, flatten it so A goes straight to C.
Why do http and www need testing separately?
Because each host and protocol is a different starting URL. A site can handle https correctly and still leave http, or www, on a longer or broken path. Checking each variant is the only way to see the full picture.