SEO & webmaster
Redirect Checker
Follow every hop of a URL to its final destination, HTTP codes included.
Behind a single link there can be a whole obstacle course: http to https, old domain to new, non-www to www. Every extra redirect slows the page down, leaks link equity, and past two hops it starts wasting Google’s crawl budget. This checker follows a URL hop by hop, shows the HTTP code at each step (301 permanent, 302 temporary, 307 and friends), detects infinite loops and warns you when the chain is too long. In seconds you see the exact path both your visitors and search engines are forced to travel — and where to cut it short. Free, no account, unlimited checks.
How does it work?
- Paste the starting URL you want to check (an old address, for example).
- Click “Analyze” to follow the full chain.
- Read each hop with its HTTP code down to the final status.
- If the chain exceeds two hops, point the first URL straight at the final destination.
Frequently asked questions
What’s the difference between a 301 and a 302 redirect?
A 301 is permanent: it tells search engines the page has moved for good and passes the old URL’s authority to the new one. A 302 is temporary: the old URL stays canonical. Using a 302 for a permanent move is a classic SEO mistake.
Why are redirect chains bad?
Each hop adds a network round-trip — so load time — and Google only follows a limited number of consecutive redirects. Beyond two hops, link equity erodes and crawlers may give up before reaching the final page.
How do I fix a redirect loop?
A loop happens when two rules send visitors back and forth — usually a conflict between the server config, the CMS and the CDN. Find the URL in the chain that jumps backwards, then remove or fix the corresponding rule so everything points at a single destination.
My URL doesn’t redirect at all — is that a problem?
Quite the opposite: a URL answering directly with 200 is the ideal case. Just make sure all variants (http, https, www and non-www) end up on the same canonical version.