Redirect CheckerAuditReady
Enter an address and we follow each redirect by hand, showing every hop with its status code, address and time, so chains, loops and mixed HTTP and HTTPS hops are easy to spot.
Up to 15 hops are followed. Add up to 10 more addresses under the address bar. No account needed. 6 of 6 checks left today.
How to use it
Four steps from an address to results you can act on.
The address is requested without following redirects.
Each Location header is followed one hop at a time.
Every hop is timed.
What each status code means and what to change.
What it brings you
Every result comes with the proof behind it, so you can check it yourself.
More than one hop before the final page.
Redirects that come back to an earlier address.
HTTPS pages sent back to HTTP.
301, 302, 307 and 308, and when each fits.
What the result looks like
Results are sorted so the most important rows come first. This example uses sample data to show the layout.
| Hop | Address | Code | Status |
|---|---|---|---|
| 1 | http://example.com/old | 301 | Redirect |
| 2 | https://example.com/old | 301 | Redirect |
| 3 | https://www.example.com/new | 200 | OK |
Questions
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.