Redirect Chain Checker
Follow a URL hop by hop and see every redirect on the way: the status code of each step, such as 301, 302, 307 or 308, the Location it points to and the final destination. Expand short links, find redirect chains and loops that slow down pages and waste crawl budget, and spot temporary redirects and HTTPS to HTTP downgrades that should be permanent.
Frequently asked questions
What does the checker do?
It requests the URL without following redirects, reads the status code and Location header, and repeats the request for the next address until a page answers without a redirect, for up to 10 redirects. Each step is listed with its status and target.
What is the difference between 301, 302, 307 and 308?
301 and 308 are permanent redirects, which search engines treat as a move of the page and its ranking signals to the new address. 302 and 307 are temporary, so the old address stays indexed. 307 and 308 also require the browser to keep the request method, for example POST.
Why are redirect chains a problem?
Every hop costs a round trip before the page starts loading, which hurts speed on mobile connections, and search engines follow only a limited number of hops. Point links and old redirects straight to the final URL so visitors reach it in one step.
Can I expand a short link before opening it?
Yes. Paste a link from bit.ly, t.co, tinyurl.com or any other shortener and the checker shows where it leads without you visiting the target in your browser.
What is a redirect loop?
A chain that returns to an address it already visited, so it never ends. Browsers stop with an error such as too many redirects. The checker stops at the repeated address and marks the loop.
Are JavaScript or meta refresh redirects followed?
No. The checker follows HTTP redirects only. Redirects done in a page's HTML with a meta refresh tag or in JavaScript appear as a final 200 page. Search engines handle those differently and less reliably than HTTP redirects.
Why is an HTTPS to HTTP step flagged?
A redirect from a secure address to an insecure one exposes the request and can trigger browser warnings. It usually comes from an old rule on the server. Make sure every hop stays on HTTPS.
Which addresses can be checked?
Public web addresses on the standard ports. Every hop is checked separately, and private, local and loopback addresses are refused, so a redirect cannot lead the checker into an internal network.
Does the checker send cookies or a browser user agent?
No. It sends a plain request without cookies. Sites that redirect based on cookies, location or device can therefore send you somewhere else than the checker.
Is there a limit?
A check follows at most 10 redirects, and each visitor can run a limited number of checks per minute.