Trace the full redirect path for any URL. See every hop, status code, and the final destination — instantly.
What it checks: every redirect hop from the starting URL to the final destination, including status codes (301, 302, 307, 308) at each step — useful for spotting redirect loops, chains that are too long, or a permanent move mistakenly using a temporary redirect.
An HTTP redirect chain is a series of redirects that a browser follows before reaching the final destination URL. For example, http://example.com might redirect to https://example.com, which redirects to https://www.example.com. Each hop adds latency and can affect SEO.
Yes — long redirect chains (3+ hops) can dilute PageRank, slow down crawling, and reduce page speed scores. Google recommends keeping redirect chains to a single hop where possible. Use our Redirect Checker to identify unnecessarily long chains.
A 301 redirect is permanent — it tells search engines to transfer all link equity to the new URL and update their index. A 302 redirect is temporary — search engines keep the original URL indexed. Use 301 for permanent moves and 302 for temporary ones.
A redirect loop occurs when URL A redirects to URL B, which redirects back to URL A (or through a chain that eventually returns to A). Browsers abort after detecting a loop and show an error. Our tool detects redirect loops and flags them immediately.