A redirect checker follows your URL from start to finish and shows every hop it makes — each redirect, its status code, and the final destination — so you can spot chains, loops, and wrong turns before they cost you visitors and search rankings.
I learned how much this matters the hard way. A client once changed their site’s URL structure, and their most-shared blog post ended up bouncing through four redirects before landing anywhere. It still “worked” — the page eventually loaded — so nobody noticed for months. But the page’s search traffic had quietly dropped by half. One redirect checker test would have shown the problem in ten seconds: four hops where there should have been one.
What Is a Redirect Checker?
A redirect checker is a free tool that takes a URL and follows it the way a browser or search engine would, recording every step. You paste in a link, hit check, and it shows you the chain: the starting URL, each intermediate URL, the HTTP status code at each hop (301, 302, 307, 308), and the final page where the journey ends.
Think of it like tracking a parcel: you don’t just want to know that it arrived, you want to know every depot it passed through, because a parcel that took six stops to cross town has a problem even if it got there in the end.
Without a redirect checker, redirects are invisible. Click a shortened link and your browser silently follows each hop. The page loads, everything looks fine, and you have no idea whether it took one hop or five. The checker makes the invisible visible.
Why Should You Trace Your Redirects?
Because every redirect costs something. A browser has to make a separate request for each hop, and each request adds delay — usually 100 to 300 milliseconds per hop on a slow connection. Two hops is barely noticeable. Five hops is a full second of waiting before the page even starts loading, and on mobile that is enough to lose people.
Search engines pay attention too: Google passes less ranking value through each hop, so a chain of four leaks far more authority than a single clean 301.
There is a worse failure mode: the redirect loop. That is when URL A points to URL B, and URL B points back to URL A. The browser goes round in circles until it gives up. Visitors see a “too many redirects” message, Google drops the page, and the link is effectively dead — even though both URLs technically exist.
How to Use a Redirect Checker, Step by Step
Here is the whole process:
1. Find a redirect checker. Good free ones include httpstatus.io, redirect-checker.org, and the redirect tools in Screaming Frog and Ahrefs. Pick one that shows the full chain, not just the final status code. 2. Paste in the URL you want to test. Start with the links that matter most: your homepage’s old addresses, your most-shared posts, shortened links you use in social media or email, and any URL you changed during a redesign. 3. Run the check and read the chain. A healthy result is one line: your URL, a 301 or 308 status, and the final destination. Two hops is acceptable. Three or more means you have a chain worth fixing. 4. Check the status codes, not just the hops. A 301 means “moved permanently” — the right choice for a permanent change. A 302 means “moved temporarily” and tells search engines to keep ranking the old URL, which is wrong for a permanent move. If your permanent move shows up as a 302, fix it. 5. Test the destination too. The final URL should return a 200 status — the page actually exists and loads. If the chain ends in a 404, the redirect points at a dead page, and every link to the original URL is broken.
The whole test takes under a minute per URL — run it on your ten most important links once a quarter, and after every site change.
What Do the Redirect Results Mean?
The status code is the most important part of the result. Here is what each one says:
- 301 Moved Permanently. The page has moved for good. Search engines transfer the old page’s ranking to the new address. This is the code you want for almost every permanent redirect.
- 302 Found (temporary). The move is temporary. Search engines keep the old URL in their index and do not pass its ranking along. Use this only when the move really is temporary — a page down for maintenance, for example.
- 307 Temporary Redirect. The modern, stricter version of 302. Same idea: temporary.
- 308 Permanent Redirect. The modern, stricter version of 301. Same idea: permanent. Either 301 or 308 is fine for a permanent move.
- 200 OK. No redirect at all — the URL loads directly. If you expected a redirect and got a 200, the redirect is missing.
- 404 Not Found. The URL leads nowhere. If this appears at the end of a chain, the redirect is broken.
Watch the chain itself as well. A chain like old-url → new-url → newer-url means redirects were added on top of redirects over time instead of being updated. The fix is simple: point the original URL directly at the final destination, cutting out the middle hop.
How Many Redirect Hops Are Too Many?
One hop is ideal. Two is fine — it happens naturally when a site redirects http to https and then the non-www version to www, for example. Three is the point where you should start fixing things, because each extra hop adds delay and bleeds ranking value.
Google follows up to ten redirects in a chain, but that is a ceiling, not a target. In practice, chains longer than three or four are almost always accidents — old redirects that were never updated when the site changed again. I have seen chains of eight on sites that had been redesigned three times, with every redesign adding a new hop instead of updating the old ones.
The Five-Minute Redirect Audit You Can Run Today
Try this on your own site right now:
1. Pick five URLs: your homepage’s http version, your homepage without www, your most-shared blog post’s old address (if it ever moved), one shortened link from your social media, and one link from your oldest email newsletter. 2. Run each one through a redirect checker and write down the number of hops and the final status code. 3. Flag anything with three or more hops, anything ending in a 404, and any permanent move showing a 302 instead of a 301. 4. Fix the flagged ones by pointing the original URL directly at the final destination, then re-test to confirm one clean hop.
Once your redirects are clean, check how the final pages actually look to visitors — paste the destination URL into our free responsive preview tool and confirm it renders properly at phone, tablet, and desktop widths. A redirect that lands on a broken layout is barely better than one that lands nowhere.
FAQ
What is a redirect checker?
A redirect checker is a free tool that follows a URL and shows every hop it makes — each intermediate URL, its HTTP status code (301, 302, 307, 308), and the final destination. It reveals redirect chains, loops, and broken redirects that clicking the link hides.
How many redirects are too many?
One hop is ideal and two is fine. Three or more hops is worth fixing: each extra hop adds delay and passes less ranking value to the final page. Google follows up to about ten hops, but long chains are almost always accidental — old redirects never updated after a later site change.
What is the difference between a 301 and a 302 redirect?
A 301 means the page has moved permanently, and search engines transfer the old page’s ranking to the new address. A 302 means the move is temporary, so search engines keep ranking the old URL and do not pass its ranking along. Use 301 or 308 for permanent moves, 302 or 307 only when the move is genuinely temporary.
What is a redirect loop?
A redirect loop happens when URL A points to URL B and URL B points back to URL A. The browser goes round in circles until it gives up and shows a “too many redirects” error. A redirect checker shows the loop immediately, and the fix is to break the circle by pointing one of the URLs at the real final destination.