Redirect Checker
Trace every redirect hop for any URL — see 301, 302, 307 chains, response codes and final destination instantly.
Frequently Asked Questions
What is a redirect chain?
A redirect chain occurs when a URL redirects to another URL which then redirects again — sometimes multiple times before reaching the final destination. Each extra hop adds latency, dilutes PageRank and can cause SEO issues. The ideal is 0 or 1 redirect per URL.
What is the difference between 301 and 302 redirects?
A 301 redirect is permanent — it tells browsers and search engines the content has moved forever. PageRank is passed to the new URL. A 302 redirect is temporary — search engines keep the original URL indexed. Use 301 for moved content and 302 for temporary changes.
How many redirects are too many?
More than 2 redirects in a chain is considered excessive. Each redirect adds 100-300ms of latency and Google has stated that too many hops can dilute PageRank. Ideally your URLs should resolve in 0 redirects (direct) or 1 redirect maximum.
Why does my URL show a different final destination than expected?
Some servers use JavaScript redirects, meta refreshes or conditional redirects based on User-Agent or cookies. This tool only follows HTTP-level (header) redirects. Client-side redirects will not be detected — the final URL shown is the last HTTP response URL.