Redirect Checker
Check URL redirects and follow the full redirect chain. Detect redirect loops, excessive hops, HTTPS issues, and canonical problems affecting SEO. Verify HTTPS configuration with the SSL Checker.
Quick Guide
- Enter a URL or domain
- Click Check to follow redirects
- Review status codes (301/302/307/308)
- Fix loops and long chains (aim for 0–1 redirects)
Share
Actions
Run a check to enable actions.
What we check
- Full redirect chain with status codes
- HTTPS enforcement and canonicalization
- WWW/non-WWW and trailing slash consistency
- Response timing per hop and loop detection
Redirect Checker FAQ
What is a redirect chain?
A redirect chain is a sequence of HTTP redirects (301, 302, 307, 308) where one URL redirects to another, which may redirect again. Long chains can slow down page loads and dilute SEO value.
301 vs 302—what's the difference?
301 is a permanent redirect (use for domain moves, canonicalization). 302 is a temporary redirect (use for A/B tests, maintenance pages). Search engines treat 301s differently—they transfer link equity, while 302s do not.
How many redirects are OK?
Ideally, 0–1 redirects. One redirect (e.g., http → https or www → non-www) is fine. Chains of 2+ redirects add latency and should be consolidated. Browsers and crawlers typically stop following after 5–10 redirects.
Why do redirect loops happen?
Redirect loops occur when URL A redirects to URL B, and URL B redirects back to URL A (or through a longer cycle). Common causes include misconfigured server rules, conflicting CDN settings, or conflicting redirect rules in .htaccess/web.config.