Redirect Checker
Follow the redirect chain and see every hop, status code and latency.
Ready to Analyze
Enter a target value above or click any sample preset chip to generate real-time diagnostic output.
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.
Enter the required value in the input field above (domain, IP, URL, or text depending on the tool).
Click the action button to run the check — results are computed instantly from our edge network.
Review the parsed output, key fields and any warnings shown in the result card.
Copy the result, share the page URL, or jump to a related tool from the sidebar to continue debugging.
- Full redirect chain with status codes
- Detects redirect loops
- Handles meta-refresh and JS redirects (where possible)
- SEO-relevant timing per hop
Frequently asked questions
Related reading
Related tools
Interactive 1xx–5xx codes & Cloudflare edge errors.
Response headers, status, TLS.
TLS cert issuer, validity, SANs.
Every TLS cert ever issued for a domain (crt.sh).
Grade HSTS, CSP, X-Frame-Options A–F.
Detect WordPress, Shopify, etc.