Redirect checker
The redirect checker follows every hop a URL takes and lists each status code, so you can see redirect chains, loops, and the final destination.
- Free, no sign-up
- Results in seconds
- Checker · 35 free tools
This checks one page. The same problem usually repeats on every page built from the same template. Plans start at $14.99 a month.
How to use the redirect chain checker
- 1
Paste an address
A full URL or just a domain. We add https:// when it is missing.
- 2
We fetch it live
Our server requests the page now, the way a crawler would, and records what came back.
- 3
Read the evidence
Every result shows the value we read, so you can see why it passed or failed.
- 4
Fix and check again
Change the page, run it once more, and ship when the second run agrees.
What this does not measure
We would rather say what a tool cannot see than let a clean result mislead you.
- It caps the chain at six hops. A longer chain is reported as too long rather than followed indefinitely.
- It shows the status of each hop, not the reason somebody added it.
- It reads HTTP only. A client-side JavaScript redirect is invisible to it, and so is a meta refresh that the server never sees.
Want the full picture?
This tool answers one question. A full audit runs every check on a page, scores it, and gives you a short list of what to fix first.
Questions about the redirect chain checker
More in the guides.
Keep reading

Redirect chains and loops: 301 vs 302 vs 308, and how many hops is too many
Use 301 or 308 for permanent moves, redirect straight to the final URL, and keep any chain under five hops.

HTTP status codes for SEO: 404 vs 410, soft 404s, 5xx, and 429
Google treats 404 and 410 the same. 5xx and 429 slow crawling. A 200 error page is a soft 404.