Trace every redirect hop from a URL to its final destination, with the status code (301, 302, 307, 308) of each step.
How to use the Redirect checker
- Enter the starting URL.
- See each hop, its status code and where it points.
- Collapse chains into a single 301 to the final URL.
Why chains and the wrong codes hurt
Each extra hop slows the page and can lose a little link value. A 302 or 307 says the move is temporary, so search engines may keep the old URL indexed. For a permanent move, use one 301 or 308 straight to the final URL.
How to read the chain
The top row shows the number of redirects, the final status code, total time and whether you end on HTTPS. Each hop in the chain has a coloured code: blue for permanent redirects (301, 308), amber for temporary ones (302, 307), green for the 200 page at the end and red for errors. One redirect is normal, for example http to https. More than two is flagged, and so is any temporary redirect or a hop back to plain http. The final status should be 200; a 404 at the end means the redirect points to a page that no longer exists. We follow up to 15 hops.
Fixing what it finds
Chain of three or more: point every old URL straight at the final one, and update internal links so they skip the redirect entirely. 302 where you meant 301: in most frameworks it is a single setting, such as permanent: true in Next.js. Loop (A to B to A): the trace stops with an error; look for two rules that undo each other, often a trailing-slash rule fighting a CMS setting. A redirect to the home page for every old URL: map each one to its closest match instead.