Redirect checker
Show the full redirect chain of a URL.
How this tool works
The redirect checker shows the complete redirect chain of a URL — every hop with HTTP status code and Location header. This lets you spot redirect loops, unnecessary intermediate hops (e.g. HTTP→HTTPS→www→non-www) and verify SEO-relevant 301/302 decisions.
Typical use cases
- After migration, verify old URLs correctly redirect to new targets
- Debug redirect loops that cause browser errors
- Check if HTTP→HTTPS→www is correctly combined into one 301
- SEO: find redirect chains with more than 2 hops and shorten them
Frequently asked questions
How many hops are followed at maximum?
Maximum 10 hops. After that we abort — a redirect loop is likely.
What is the difference between 301 and 307?
301 = permanent, browsers may change method (POST→GET). 307 = temporary, method preserved. For SEO, 301 is almost always correct.
Does a redirect chain hurt SEO?
Yes — each additional hop delays crawling and may cost link equity. Google follows up to 10 hops but prefers direct redirects.
Are cookies or JavaScript considered?
No — we only follow HTTP Location headers. JavaScript redirects (window.location) or meta refresh are not detected.
Can I also test POST redirects?
No — the redirect checker sends GET requests. For POST tests, use the online cURL tool.
What happens with a redirect to a private IP?
Private IPs are not followed for security reasons. The chain ends at that point.
Related tools
Continuous monitoring vs. one-shot?
XICTRAQ monitors uptime, SSL, security headers, GDPR and performance 24/7. Free plan, no credit card.