Redirect checker & HTTP status tracer
Trace up to 10 URLs hop by hop. See every 301, 302, 307 and 308 with status codes and response times, and catch redirect chains, loops, temporary redirects and broken destinations.
Paste up to 10 URLs
One per line — old URLs, http:// versions, www and non-www variants, campaign links or anything you've migrated.
We follow every hop
Each redirect is requested individually (up to 10 hops), recording the status code, the Location header and the response time.
Fix what's flagged
Chains, loops, temporary redirects, HTTPS downgrades, www flips, meta refreshes and 4xx/5xx destinations are flagged with the fix.
Frequently asked questions
What's the difference between a 301 and a 302 redirect?
A 301 (and 308) tells search engines the move is permanent, so they replace the old URL with the new one in their index and consolidate ranking signals. A 302 (and 307) says the move is temporary, so the old URL may stay indexed. Use 301 or 308 for permanent moves like HTTPS migrations, URL changes and domain moves.
Are redirect chains bad for SEO?
Every extra hop adds latency and a chance for something to break. Google follows up to 10 hops but may defer crawling long chains, and other crawlers give up sooner. Best practice is to redirect every old URL straight to its final destination in a single hop.
What is a redirect loop?
A loop happens when a URL redirects to a URL that eventually redirects back to it — e.g. http → https → http. Browsers show “too many redirects” and search engines can't reach the page at all. It's usually caused by conflicting rules in the server config, CDN and CMS.
Why does my URL redirect from www to non-www (or back)?
Your site should pick one canonical host and redirect the other to it with a 301. If the chain switches between www and non-www more than once, two layers (for example your CDN and your CMS) disagree about the canonical host — fix one of them.
Is a meta refresh the same as a redirect?
No. A meta refresh is an HTML tag that tells the browser to load another page after it has loaded the first one. It's slower and a weaker signal for search engines than a server-side 301. The checker flags it on the final page.
Why do you send HEAD requests first?
HEAD requests return the status code and headers without downloading the page, which is faster and lighter on your server. If a server rejects HEAD or returns an error, we retry with a normal GET so the result matches what browsers and crawlers see.