WWW and HTTPS Redirect Checker
Check that http, https, www and non-www all end at one URL rather than four.
About this tool
Requests all four versions of your homepage — with and without `www`, over `http` and `https` — and reports where each one lands.
These are four distinct URLs. If more than one answers with a 200, the site is publishing its homepage several times over and splitting its signals between the copies, with nothing to say which is meant to be the real one.
It is the most common site-wide duplication problem there is, and it is invisible from a browser: the address bar hides `https://`, autocompletes `www`, and follows redirects without telling you. It is fixed once, with a server rule.
Common questions
Does it matter which version I choose?
Not really, as long as you pick one and every other version redirects to it. https is not optional; www versus non-www is a preference. Consistency is what matters, not the choice.
Why not just use a canonical tag?
A canonical is a hint that can be ignored, and it does nothing for visitors, who still land on whichever URL they typed. A 301 is an instruction, and it consolidates everything properly. Use the redirect; keep the canonical as reinforcement.
Why do I see two redirects instead of one?
Usually http://example.com going to https://example.com and then to https://www.example.com. It works, but every visitor pays two round trips. A single rule can go straight to the final URL.
Is this really a problem if the site works?
The site working is exactly why it goes unnoticed for years. Search engines see several copies of every page and have to guess which is canonical, and the guess can change.