Chrome now warns customers before opening your website: how to check yours in two minutes
Chrome no longer shows just a small label: it now asks customers whether they really want to open a site without HTTPS. Here's how to tell if yours is one, and what to ask whoever runs it.
You open your own website on your phone to check the hours, and instead of your page, Chrome shows a warning screen that says "Connection is not secure" and asks if you want to continue. That's what a new customer sees too. A website not secure warning doesn't mean you were hacked. Almost always, the site is missing HTTPS, the little security padlock, and since October Chrome takes that much more seriously.
It can be fixed, and often it's a small job. If you're building your site from scratch, the small business website guide covers the basics.
What changed in Chrome
For years, Chrome showed a small "Not secure" label next to the address. Most people never noticed it. In October 2026, Google announced that Chrome now asks for permission before opening any site without HTTPS, for everyone, with nothing to turn on. Earlier in the year it only did this for people who had Enhanced Protection switched on.
In practice, someone looking for your business sees a warning screen first, and your site second. Google explains it on its help page about how to check if a connection is secure. The customer can choose to continue, but they have to make that call. And someone who doesn't know you yet has little reason to take the chance.
Chrome only asks the first time. If the person says yes, it won't warn them again until they go two weeks without visiting your site. So your regulars might see it once. The one it hurts most is the new customer, the person who just found you on Google Maps and has never been to your site.
Why does my website say "not secure"?
HTTPS is the secure way to connect a customer's phone to your website: whatever gets sent is protected, so nobody along the way can read it or change it. To have it, your site needs a security certificate (often called an SSL certificate) set up on your hosting, which is where the site is stored.
Google's help page says it plainly: the site owner has to secure the site with HTTPS. Your customers can't do anything about it on their end.
The usual causes:
- The site never had a certificate. This is common with sites built years ago, or ones a friend or relative made that nobody has touched since.
- The certificate covers only one version of the address, for example yourbusiness.com but not www.yourbusiness.com.
- The certificate expired and nobody renewed it. That one shows a different warning that says "Your connection is not private." The fix is the same: talk to whoever runs your hosting.
How to check your site in two minutes
You don't need to know anything technical. Just your phone.
- Open Chrome on your phone.
- Type your full address starting with http:// (no s), for example http://yourbusiness.com, and tap go.
- If your site opens and the address changes to https:// on its own, you're fine.
- Do the same with www in front: http://www.yourbusiness.com.
- If either one shows the "Connection is not secure" screen, that's exactly what a new customer is seeing.
If you've visited before If you ever tapped to continue, Chrome won't ask you again for a while. To see what a new visitor sees, ask someone who has never opened your site to try it on their phone.
Check the links to your site too
Your address shows up in a lot of places: your Google profile, your Instagram bio, your Facebook page, your printed menu and the QR code on the table. Once your site has HTTPS, change any that still say http:// to https://. If your site sends http:// to https:// on its own, customers get there either way, but it's better when everything points to the right address.
On your Google profile, the website address is in your business information. The Google Business Profile guide shows you where everything is.
A printed QR code can't be edited. If the site has HTTPS, it works fine. If it doesn't, what needs fixing is the site, not the menu.
Who fixes it and what to ask for
Whoever has access to your hosting fixes it: the company where your site is stored, the person who built it, or the website builder you used. Many hosting services include the certificate at no extra cost, so sometimes it's just a matter of turning it on.
You can send them something like this:
A message for whoever runs your site Hi, Chrome is warning people that my website isn't secure. Can you turn on HTTPS for yourbusiness.com and www.yourbusiness.com, and make the http:// version send people to https:// automatically? Let me know when it's done so I can test it.
If you don't know who has the hosting password, or the person who built your site doesn't answer anymore, that's the real problem. Before you pay anyone, find out whose name the domain is in and where the site is stored. Our post on what a domain, hosting and business email cost explains what each piece is.
If you'd rather we handle it
On the sites we build, the security padlock (HTTPS) is set up from day one, and the site opens with and without www. It's part of what our domain registration includes. If you're thinking about a new site, see how we do website design in Puerto Rico for small businesses, like our websites for restaurants and cafés. See plans and prices or book a free 30-minute call, in English or Spanish.
Questions
Can customers still get into my site?
Yes. The screen has an option to continue. But the customer has to decide to take the risk, and a security warning is a poor way to welcome someone.
Is it dangerous for my customers?
Without HTTPS, what someone types on your site, like their name or phone number in a booking form, could be seen or changed along the way, for example on public Wi-Fi. That's why Chrome warns them.
My site only has information, no forms. Does this affect me?
Yes. Chrome doesn't look at what's on the page, only at whether it opens with HTTPS. A site with just your menu and hours gets the same warning.
Does fixing it cost money?
Often not, as we explain above. If someone wants to charge you for it separately, ask whether the certificate renews on its own, so you don't get a different warning when it expires.