See the whole redirect path
Enter a URL and the checker follows it hop by hop, like a search engine crawler, showing each status code (301, 302, 303, 307, 308), the Location header it points to and how long each hop took, until it reaches the final page.
It warns about redirect chains (more than one hop wastes crawl budget and slows visitors), temporary redirects used where a permanent one belongs, and confirms when HTTP correctly redirects to HTTPS.
How to check redirects
- 1
Enter the URL
Try http://, www and non-www versions.
- 2
Read the chain
Each hop with its status code.
- 3
Fix chains
Redirect straight to the final URL.
Key features
Every hop shown
Up to 10 redirects.
Status and Location
Know which rule fired.
Chain warnings
Flags long chains.
Temporary-redirect alerts
302/307 where 301/308 is expected.
Common uses
- Domain moves: Verify old URLs reach the new site in one hop.
- HTTPS setup: Confirm http:// redirects to https://.
- Affiliate and short links: See the real destination.
Tips and good to know
- Meta refresh and JavaScript redirects aren't followed; use server-side 301s for SEO.
- For hundreds of URLs at once, use the HTTP Status Checker.
Frequently asked questions
What's the difference between 301 and 302?
A 301 is permanent and passes ranking signals to the new URL. A 302 is temporary, so search engines keep the original URL indexed.
Are redirect chains bad for SEO?
Google follows up to about 10 hops, but each one slows crawling and page loads. Keep redirects to a single hop.
What about 307 and 308?
They're the modern temporary and permanent redirects that also preserve the request method.