Browsers hide "https://" and "www", so people type just mysite.com. Here is why that address needs HTTPS and a redirect, and how to check yours.
Look at your browser's address bar. Since 2019, Chrome hides https:// and www by default, and Safari shows only the domain. So even when your site lives at https://www.mysite.com, what visitors see is just mysite.com.
That is the address people remember, write on Instagram, print on business cards and say out loud. When they come back, they type mysite.com, without the www. If that address doesn't work, they reach an error, not your site.
Many hosting services and site builders only work on www (a CNAME record), and the root domain can't point to them. The result is a site that works at www.mysite.com and fails at mysite.com, which is exactly the address people type.
| How the root domain is set up | What the visitor gets |
|---|---|
| No record for the root | "This site can't be reached" |
| Registrar forwarding, HTTP only | A certificate error or a "not secure" warning, because the browser tries https:// first |
| 301 redirect with an SSL certificate | Goes straight to https://www.mysite.com |
The forwarding offered by many registrars only works over HTTP. Since browsers try HTTPS first, it usually fails exactly where you need it.
The root domain needs to answer over HTTPS, with its own valid certificate, and send the visitor to the main address with a 301 (permanent) redirect. That way:
mysite.com, with or without https://, ends up on your site.www.mysite.com as the main address and keeps all of its ranking.With Redirect-301 you point the root domain to our IP, and we issue the certificate and redirect to www automatically. The step-by-step is in the configuration guide. If you're not sure between 301 and 302, see 301 vs 302 redirect: which one to use?.
It's your call. Pick one main address, with or without www, and redirect the other to it with a 301. To Google the two are equal: what hurts SEO isn't choosing www or not, it's leaving both open separately and splitting your ranking across two addresses.
In practice, the domain without www is shorter to say and to print; www is sometimes easier on the technical side, because many hosts only let www (a CNAME) point at them, while the root domain is more limited, as explained above. If your host only accepts www, make www the main one. If you can point the root domain freely and prefer the short address, make the non-www domain the main one and redirect www to it. The rest of this article uses www as the main address, but it works the same both ways: whichever you pick, the other address needs a 301 over HTTPS.
Open a private window (so the browser doesn't use its cache) and try the four combinations. All of them should end up on the same address, with the padlock:
| You type | Should end up at |
|---|---|
http://mysite.com | https://www.mysite.com |
https://mysite.com | https://www.mysite.com |
http://www.mysite.com | https://www.mysite.com |
https://www.mysite.com | https://www.mysite.com |
In a terminal, curl -I shows each step:
$ curl -I https://mysite.com HTTP/2 301 location: https://www.mysite.com/
Neither. Google treats them as equal; what matters is picking one as the main address and redirecting the other, so your ranking isn't split across two addresses.
No. Browsers hide the www, so many people type the domain without it. Without a redirect, all of them reach an error.
It depends on where your site is hosted. Many platforms only work on www. In that case the root domain has to redirect to www.
Yes. The browser checks the certificate of the address you typed before following any redirect. Redirect-301 issues and renews it automatically.
No. A 301 from the root to www is exactly what Google recommends to have a single main address.
Feel free to reach out to us with any questions. We're here to help! Scan the QR code or click the button below to join our WhatsApp group.
Open WhatsApp →