Redirect Checker
Follow the redirect chain and see every hop, status code and latency.
About the Redirect Checker
The Redirect Checker traces every HTTP redirect a URL follows before reaching its final destination. It shows each hop's status code (301, 302, 307, 308), the Location header, and any meta-refresh or JavaScript-based redirects. Redirect chains that look fine to a user can cause serious SEO issues (link equity loss, crawl budget waste) and performance problems (each hop adds a round trip).
SEO auditors use redirect checkers to spot 302s that should be 301s (temporary vs permanent), to catch redirect loops, to verify canonical URL enforcement, and to confirm that HTTP→HTTPS→www→apex chains resolve in as few hops as possible. Developers use them to debug OAuth callback flows, tracking-parameter passthroughs, and third-party integration redirects.
Google recommends keeping redirect chains to a maximum of 5 hops — beyond that, Googlebot may give up. Ideal is 1 hop. If a page has moved permanently, use a single 301 to the new URL, not a chain through intermediate hosts.
How to use this tool
- 1Enter the required value in the input field above (domain, IP, URL, or text depending on the tool).
- 2Click the action button to run the check — results are computed instantly from our edge network.
- 3Review the parsed output, key fields and any warnings shown in the result card.
- 4Copy the result, share the page URL, or jump to a related tool from the sidebar to continue debugging.
Key features
- Full redirect chain with status codes
- Detects redirect loops
- Handles meta-refresh and JS redirects (where possible)
- SEO-relevant timing per hop