Redirect Checker
Trace the full redirect chain for any URL and see each HTTP status code.
Enter a URL above and click Check to trace the redirect chain.
Redirect chain is resolved server-side via GET /api/v1/seo/redirect-check to bypass browser CORS restrictions.
About this tool
Redirect Checker follows a URL through its complete redirect chain and shows you every hop — the intermediate URLs, their HTTP status codes (301, 302, 307, 308), and the final destination. Detecting long chains or redirect loops is critical for SEO because each redirect adds latency and potentially dilutes PageRank passing through it. Enter any URL and the tool fetches the chain server-side to bypass browser CORS restrictions, then visualises each step clearly.
How to use
- Paste the URL you want to check into the input field.
- Click Check Redirects to trace the full chain.
- Review each hop's URL and status code, and check the final destination.
Related Tools
Generate HTML meta tags including OpenGraph and Twitter Card markup.
Build a valid robots.txt file with allow, disallow, and sitemap rules.
Fetch any URL and verify the canonical tag — detect self-referential and cross-domain canonicals.
FAQ
What is the difference between a 301 and a 302 redirect?
A 301 is a permanent redirect telling search engines to transfer the ranking signals (PageRank) from the old URL to the new one and update their index. A 302 is temporary — search engines keep the original URL indexed and do not fully transfer ranking signals. Use 301 for permanent moves and 302 only for genuine temporary redirects.
How many redirects are too many?
Every hop in a redirect chain adds latency. Google recommends a maximum of 3–5 redirects in a chain. Long chains (6+) slow page load, may cause Googlebot to stop following, and each hop can dilute the PageRank passing through it. Consolidate chains where possible.
What is a redirect loop?
A redirect loop occurs when URL A redirects to URL B, which redirects back to URL A (or through a longer cycle). The browser stops and shows an 'ERR_TOO_MANY_REDIRECTS' error. The tool detects loops and flags them so you can identify and fix the circular rule.
Why does my browser show a different result than the checker?
Browsers cache redirects aggressively. If you recently changed a redirect, your browser may still serve the cached version. The checker makes a fresh server-side request so the result reflects the live redirect behaviour, bypassing your local browser cache.
Should I use 307 or 302 for temporary redirects?
307 (Temporary Redirect) is the HTTP/1.1 equivalent of 302 and guarantees the HTTP method (POST, GET) is preserved across the redirect. 302 technically should preserve the method but many browsers historically changed POST to GET. For modern applications use 307 for temporary redirects that need method preservation.