Redirect chain
Every requested URL.
← Back to all tools
Redirect Checker
Follow URL redirects, inspect every response and find routing issues.
What we check
Status codes
Permanent and temporary redirects.
Final destination
Where the chain ends.
Redirect loops
Repeated URLs.
HTTPS downgrades
Secure to insecure transitions.
Response details
Location headers and available timings.
Understand the journey
- 1Enter a URLAdd the full URL you want to trace, including any path or query string.
- 2Review each hopSee every redirect in order with status codes and destination URLs.
- 3Fix unnecessary redirectsIdentify issues like redirect loops, long chains or incorrect status codes.
Results apply to the submitted URL. No redirect can be a valid result.
Frequently asked questions
What is a redirect chain?
A redirect chain is a series of HTTP responses where one URL returns a redirect status and a Location, and the next request goes to that URL. Two redirects followed by a final response are three responses.
How do permanent and temporary redirects differ?
301 and 308 tell clients the destination replaces the requested URL. 302, 303 and 307 say the routing is temporary. A temporary status is not automatically a mistake. Search engines decide how to treat link signals; this check does not measure link equity.
How many redirects should I use?
A short chain is easier to maintain. Zero redirects is a valid result when the first response is the page you wanted. Browsers and crawlers set their own limits, and those limits are not the same. This checker stops after 10 redirects and marks that result as partial.
What causes a redirect loop?
A loop sends the request back to a URL that was already requested. Conflicting server, CDN or application rules can cause it. The report stops at the repeated URL and does not present the loop as a completed destination.