Server & Network
Redirect Checker
Follow a redirect hop by hop: status codes, intermediate targets, loading time, chains, loops and meta refresh – and check with one click whether http, https, with and without www all lead to the same address.
- Processed on the server – Privacy
- No sign-up
- Free
Follow a redirect
Without a protocol it starts with http:// – just like someone who only types the domain. Each hop is fetched individually by my server (at most 10).
Hop by hop
Variants compared
Checks
Final page
Guide
How it works
- Enter an address
Enter the old address, e.g. example.com/old-page. Without http:// or https:// the check starts at http:// – which is also where visitors land who only type the domain.
- Choose options
With “Smartphone” you see whether mobile visitors are redirected differently, with “Googlebot” what the search engine sees. “Check all variants” compares http/https with and without www.
- Read the chain
Each hop shows the status code, address, response time and server. Ideally there is at most one permanent redirect (301 or 308) directly to the final page.
- Fix problems
The checks name chains, temporary redirects, fallbacks to HTTP, loops, meta refresh and deviating canonicals. You can create matching rules with the Redirect Generator.
FAQ
Frequently asked questions
How many redirects are too many?
Ideally exactly one. Google follows up to 10 redirects, but every hop costs time and can weaken signals. A typical and unnecessary chain is http:// → https:// → https://www. – better redirect http:// directly to the final address.
What is the difference between 301 and 302?
301 (and 308) means “moved permanently” – search engines adopt the new address. 302 (and 307) is only temporary, the old address stays in the index. So always use 301 for relaunches and domain moves.
What is a meta refresh redirect?
A redirect in the page’s HTML (<meta http-equiv="refresh">) instead of on the server. It works but is slower because the page has to load first. Google usually treats an immediate meta redirect like a 301, other search engines do not always.
Why should all variants lead to the same address?
Otherwise your website exists several times – with and without www, with http and https. Search engines then have to guess which version is the right one, and links are spread across several addresses.
Why do I see something different in my browser?
Browsers cache 301 redirects for a long time and switch to HTTPS themselves with HSTS. Servers may also redirect differently depending on device, language or location. The tool always checks fresh from the server.
Are JavaScript redirects detected?
Only as a hint: if the HTML contains a script that changes the address, the tool points it out. It is not executed – so whether and when it redirects cannot be said for sure.