AI-powered
A redirect checker that follows every hop from an address to its final page, with each status code and time.
AvailableReady to use.
Open the tool| Hop | Address | Code |
|---|---|---|
| 1 | http://example.com/old | 301 |
| 2 | https://example.com/old | 301 |
| 3 | https://www.example.com/new | 200 |
AI explains the chain and suggests the shortest setup. The hops and codes come from our own requests.
The address is requested without following redirects.
Each Location header is followed one hop at a time.
Every hop is timed.
What each code means and what to change.
A redirect sends a visitor and a search engine from one address to another. A redirect checker follows those steps one at a time and shows every hop: the address, the status code and how long it took, until it reaches a page that answers.
It is the quickest way to check a site move, a new HTTPS setup or an old link that should land somewhere useful.
301 and 308 mean a permanent move: search engines move the old page's signals to the new address. 302 and 307 mean a temporary move: the old address is expected to come back. A meta refresh or a script can also redirect, but they are slower and less clear for search engines.
Chains of several hops slow every visit and waste crawl time. Loops never reach a page. Hops from HTTPS back to HTTP break security. A temporary code used for a permanent move can keep the old address in search for longer.
The fix is usually the same: send each old address straight to its final page with one permanent redirect, and update links to point at the final address.
This checker follows one address. Website Audit finds every redirect chain and loop across a site, along with the pages that link to them.
One redirect is fine. Chains slow pages down and waste crawl time, so point links straight at the final address.
Use 301 or 308 for a permanent move, and 302 or 307 when the old address will come back.
Up to 10. More than that is reported as a likely loop.