About the Redirect Chain Checker
Each redirect costs time and can dilute signals. The checker follows the chain hop by hop (up to five) and flags chains, loops, 302s that should be 301s and moves from HTTPS to HTTP.
How it works
- We fetch the URL from our server like a crawler: redirects are followed (up to five), private and internal addresses are refused, and large pages are capped.
- The checks run on the live HTML and response headers. Nothing is guessed: every finding shows what we observed.
- Results are not stored unless you are signed in, in which case they appear in your dashboard history.
Frequently asked questions
301 or 308?
Both are permanent. 308 also guarantees the method is kept, which matters for forms and APIs; for pages either is fine.