Redirect Checker
Trace the full redirect chain for any URL — see each hop, status code, and the final destination.
Did this tool work for you?
How to use this calculator
- 1
Enter the URL you want to trace (including http:// or https://).
- 2
Click "Check Now" to follow all redirects step by step.
- 3
Each row in the chain shows the URL, HTTP status code, and where it redirects.
- 4
The final row shows the destination with its status code.
Frequently asked questions
What is a 301 vs 302 redirect?
A 301 is a permanent redirect — browsers and search engines update their records and transfer most of the link equity (PageRank) to the destination. A 302 is temporary — search engines continue indexing the original URL and may not pass link equity. Use 301 when permanently moving content.
How many redirects are too many?
Each redirect adds latency and a DNS lookup. Google recommends keeping redirect chains to 3 hops or fewer. Longer chains slow page load, may cause crawler budget waste, and some older browsers limit chains to 10. Ideally, redirect directly from old URL to final destination.
What is a redirect loop?
A redirect loop is when URL A redirects to URL B, which redirects back to URL A (or through a longer cycle). Browsers detect loops after 20–30 redirects and show an error. This tool detects loops by limiting to 15 hops.
Do redirects hurt SEO?
A single 301 redirect passes nearly all link equity and has minimal SEO impact. Redirect chains dilute the link equity at each hop. Unnecessary redirects slow down crawling and user experience. For large-scale site migrations, map old URLs directly to new URLs without intermediate redirects.
Redirect Checker — Trace URL redirect chains step by step
Why redirect chains matter
Every redirect in a chain adds an HTTP round trip, typically 50–300ms of additional latency. For mobile users on slow connections, a 3-hop redirect chain can add a full second to page load time. Search engine crawlers also have limited time budgets, so excessive redirects reduce crawl efficiency.
Common redirect patterns
HTTP → HTTPS (one hop, correct). www → non-www or vice versa (one hop, correct). /old-path → /new-path (one hop, correct). Problematic: HTTP → HTTP/www → HTTPS/www (three hops when it could be one). Always configure your web server to redirect directly to the canonical URL in a single hop.
Learn more from an authoritative source:
MDN Web DocsJSON Formatter & Validator
Format, validate, and minify JSON — with clear error messages for invalid input.
Base64 Encoder / Decoder
Encode plain text to Base64 or decode Base64 strings back to readable text.
URL Encoder / Decoder
Encode special characters in URLs (percent-encoding) or decode percent-encoded URLs.
UUID Generator
Generate UUID v4 (random) identifiers — one or in bulk.
Results are estimates for informational purposes only and do not constitute professional financial, medical, legal, or technical advice. Read full disclaimer →