Redirect Checker
Trace what happens when a browser or crawler requests a URL. Find redirect chains, loops and temporary redirects that should be permanent.
Run a check
This tool isn’t available yet
Redirect Checker is still in development. The form below previews how it will work, but it can’t be submitted and no checks are run.
Results
Results aren’t available yet
Results will appear here once Redirect Checker launches.
How to use Redirect Checker
- Enter the URL you want to trace, including the protocol.
- Run the trace to follow each redirect in turn.
- Shorten chains so old URLs point straight to the final destination.
What it checks
- Each hop’s HTTP status code
- Location headers
- Final destination URL and status
- Redirect chains and loops
- HTTP-to-HTTPS and www redirects
- Permanent (301/308) versus temporary (302/307) redirects
Frequently asked questions
What is the difference between 301 and 302 redirects?
A 301 signals a permanent move and a 302 a temporary one. For permanent URL changes, use a 301 (or 308) so search engines consolidate signals on the new URL.
Why are redirect chains a problem?
Each extra hop adds latency for visitors and work for crawlers, and crawlers may stop following long chains. Point redirects straight to the final URL where possible.