Follow a URL's full redirect chain, hop by hop, with every status code, so you can catch long chains, loops, and broken redirects.
We follow the redirects server-side through Numarr's own fetcher and report each hop's status code.
Long chains and stray 302s quietly cost you rankings and speed. Our team maps and fixes them site-wide.
Book a Free CallA redirect chain is when a URL redirects to another URL, which redirects to another, and so on before reaching the final page. Each hop has a status code, like 301 for a permanent redirect or 302 for a temporary one. This tool follows the whole chain so you can see exactly where a URL ends up and how many steps it takes.
Every extra redirect adds a little delay and can dilute the ranking signals passed to the final page. Ideally a URL redirects just once, straight to its destination. Long chains, temporary 302s used where a 301 belongs, and redirect loops are all worth catching and fixing.
A rule that sends one URL to a different URL. The most common types are 301 (permanent) and 302 (temporary).
A 301 is a permanent redirect that passes ranking signals; use it for moved pages. A 302 is temporary and is often used by mistake.
Each hop adds latency and can lose a little of the ranking signal passed along. Aim for a single redirect straight to the destination.
When URLs redirect back and forth endlessly, so the page never loads. It needs to be fixed at the server or CMS level.
Aim for zero or one. More than a couple of hops in a chain is worth simplifying.
A 301 passes most ranking signals to the destination. Long chains can lose some of that value along the way.
The site may block automated requests, or be temporarily unreachable. Try again in a moment, or check the URL.
Explore the rest of our toolkit or get a hand from our team:
See all free SEO tools →
