TL;DR
- Browsers show “Not secure” next to the address of a website that has no SSL certificate. The certificate is a small file on the computer that holds your site. The certificate makes everything sent between visitors and your site travel in scrambled form.
- The warning is there to protect visitors. Say your site has a contact form. Without a certificate, the name and phone number someone types into it could, in theory, be read by a stranger on the way.
- SSL certificates can be free (from Let’s Encrypt or Cloudflare, for example). There’s no reason to pay for a basic one in 2026.
- Most hosting companies (the companies that keep websites online) hand out free certificates. If yours does, the fix takes about ten minutes. It’s one setting, not a new website.
Someone searches Google for what you offer and finds your website. But next to the address, they see “Not secure.” They hesitate: is it safe to leave their phone number here? They go back to Google and open a competitor’s site instead. You never find out they were there.
What “Not secure” Actually Means
When you open a website, your browser (Chrome, Safari, Firefox) checks whether the connection between your phone or computer and the site is protected. On a protected connection, everything sent is encrypted: turned into a jumble of characters. A stranger can’t read it, even if they catch it on the way.
If the connection is protected, the browser shows a small padlock (🔒) next to the address. If it isn’t, it shows “Not secure.”
The encryption comes from an SSL certificate, a small file on the server, which is the computer where your website is stored. SSL is the name of the technology; its modern version is called TLS, but everyone still says “SSL”. The certificate is what tells the browser the connection is protected.
In plain English: without SSL, whatever a visitor types into your contact form — their name, email, phone number — travels across the internet as readable text. With SSL, it’s scrambled, so nobody can read it on the way.
Why Google Shows the Warning
Since 2018, Google’s Chrome browser has marked every website without a protected connection as “Not secure” (Chromium blog). Chrome is the most used browser: StatCounter counts about 69% of browsing worldwide (October 2026). Other browsers do the same.
Since autumn 2026, Chrome goes further. From version 154, it asks for permission by default before opening a site without a protected connection for the first time (Chrome 154 release notes). So visitors see a warning before they even see your site.
Google wants the whole web to use protected connections. It’s a safety measure, not a punishment, but that’s little comfort to a site owner with “Not secure” next to their address.
Google also gives sites with a protected connection a slight edge when it decides where to show them in search. But the edge is very slight. When Google announced it in 2014, the company said it affected fewer than 1% of searches. Don’t expect to climb in Google because of it. What it really changes is how much visitors trust you.
Why You Don’t Need to Pay for SSL
For years, SSL certificates cost money every year and were sold by hosting companies and security firms. They were hard to install and had to be renewed by hand.
Then a free project called Let’s Encrypt started giving certificates to everyone at no cost. Since then, most hosting companies, and the worldwide server networks that deliver websites faster (called CDNs), switch on free SSL by themselves.
If your hosting company charges for SSL, it’s either out of date or selling you something you don’t need. A free certificate from Let’s Encrypt or Cloudflare encrypts exactly as well as a paid one. The padlock looks the same. Google treats them the same.
The exception: some companies buy “extended validation” (EV) certificates, which also check the company behind the site more thoroughly. But browsers no longer show the company name next to the address. Chrome moved the company name into the site-information panel in version 77. So for most websites, the free certificate is all you need.
How to Get Rid of “Not secure”
Option 1: Your hosting company offers free SSL (most do)
- Log into your account on your hosting company’s website.
- Look for a section called “SSL”, “Let’s Encrypt” or “HTTPS”.
- Switch SSL on for your web address (your domain). It looks different with every host, but it’s usually one click.
- Wait 5–10 minutes for the certificate to be issued.
- Turn on the redirect to HTTPS, so that anyone who types your address with
http://lands on the protectedhttps://version automatically. Some hosts do this for you; with others it’s a separate setting. - Open your website and check: you should see the padlock.
Option 2: You use Cloudflare (recommended)
- Cloudflare provides free SSL automatically once your site is connected to its network.
- In your Cloudflare dashboard, set the SSL mode to “Full” or “Full (strict)”.
- Switch on “Always Use HTTPS” in the Cloudflare settings.
- Done — the connection to your site is now protected.
Related: Why Your Website Is Always Online — how Cloudflare keeps your site fast and available.
Option 3: You’d rather not touch the technical side
Ask whoever built your website, or your hosting company’s support, to switch on SSL. It takes them 5–10 minutes. If they charge more than €50 for it, find someone else — it should be free or close to free.
What Changes After You Add SSL
- “Not secure” disappears and the padlock appears. Visitors feel safe.
- Your site opens slightly faster: browsers only use modern ways of loading pages (such as HTTP/2) over a protected connection.
- Google may show your site a little higher in search (the very small effect mentioned above).
Common Problems After Switching On SSL
“Mixed content” warning: the page itself opens with https://, but some images or other files on it still load from old http:// addresses. Until that’s fixed, the padlock won’t appear. Fix: change http:// to https:// in the links to your images and in links between your own pages.
Certificate expired: certificates only last a limited time. Let’s Encrypt certificates last 90 days and renew themselves. And that time is getting shorter: Let’s Encrypt is moving to 45 days by 2028. If the automatic renewal fails, the warning comes back. Fix: check your hosting settings or ask whoever built your site.
The site stops opening: after switching on HTTPS, the browser says the page “redirected you too many times”. Two redirect settings are sending visitors back and forth in a circle. Fix: check the redirect settings at your hosting company or in Cloudflare. Their support can usually sort it out quickly.
FAQ
Is SSL the same as HTTPS?
Nearly. SSL is the certificate, the file that makes the encryption possible. HTTPS is the result: with SSL switched on, your address starts with https:// instead of http://, and the padlock appears. No SSL, no HTTPS. In conversation you can use the two words for the same thing — almost everyone does.
Do I need SSL if I don’t sell anything online?
Yes. Even without a shop or online payments, you probably have a contact form. Without SSL, whatever visitors type into it travels unencrypted. And “Not secure” puts visitors off whether you sell anything or not: Google shows it on every site without HTTPS. SSL is free, so there’s no reason to go without it.
Can I just ignore “Not secure”?
You can, but some visitors will leave when they see it. And since autumn 2026, Chrome even asks them whether to open such a site at all. Google also gives HTTPS a little weight when it decides which sites to show higher in search. Later you may want a booking link, a payment link or anything else where people leave their details. Then you’ll need HTTPS anyway. Fix it now; it’s free. Read about what happens when your site gets hacked →
Why does my website still say “Not secure” after I installed SSL?
The most common cause is “mixed content”: the page itself opens with https://, but some images or links on it still point to http://. The browser can’t show the padlock until everything uses https://. Check that all links to your images and between your pages start with https://. Another cause: the certificate is there, but the redirect from http:// to https:// isn’t switched on. Whoever built your site, or your host’s support, can fix both quickly.
Bottom Line
“Not secure” is free to fix, takes about ten minutes, and costs you visitors every day it stays. In 2026 there’s no reason for any website to show it.
Want SSL switched on from the start, free, with nothing for you to set up? Every site we build is hosted on Cloudflare, in an account in your name, with free SSL switched on at launch. The certificate usually renews itself, but not always. If renewal fails, “Not secure” comes back and stays until a new certificate is issued. Whoever looks after your site can do that in your Cloudflare account. See how the hosting works →