Tracing redirect chains…
Free SEO tool
Redirect chain checker
Paste one URL or a short list. We trace every redirect hop, flag loops, temporary redirects, long chains, and broken targets, then show the final canonical and noindex state.
What this checker reports
Redirect problems are common after site migrations, CMS changes, and URL restructures. This tool traces every hop so you can see the full path.
- Redirect chains. Two or more hops before the final destination. Each hop adds latency and wastes crawl budget.
- Redirect loops. URLs that redirect back to themselves, directly or through intermediate hops.
- Temporary redirects. 302 and 307 redirects that should usually be 301 for permanent moves.
- HTTPS downgrades. Redirects from HTTPS to HTTP that break the secure chain.
- Broken targets. Redirect chains that end in a 4xx or 5xx error.
- Final page context. Shows the canonical tag and noindex state on the destination page.
How a check works
Paste one URL or a short list. We fetch each URL without following redirects automatically, read the Location header, and repeat hop by hop up to 8 times. At the final destination we parse the HTML for canonical and noindex context.
Frequently asked questions
What does a redirect chain checker do?
It traces every redirect hop from the input URL to the final destination, showing the status code at each step and flagging loops, temporary redirects, and long chains.
Why are long redirect chains bad for SEO?
Each hop adds latency, and Google follows a limited number of redirects. Long chains waste crawl budget and can prevent pages from being indexed.
What is the difference between a 301 and a 302 redirect?
A 301 is permanent and passes full link equity to the new URL. A 302 is temporary and signals the original URL may return. Using 302 for permanent moves can hurt rankings.
What is a redirect loop?
A redirect loop occurs when URL A redirects to URL B, which redirects back to URL A (directly or through other hops). Browsers and crawlers give up after a few attempts.
Does this checker detect JavaScript or meta refresh redirects?
No. This tool traces HTTP-level redirects (301, 302, 307, 308) only. JavaScript and meta refresh redirects require a full browser rendering engine.
This tool is free and logs the requesting IP only to enforce the rate limit. URLs you submit are fetched so we can build the report. See the privacy policy.