What the Not Secure warning on your website means
If your browser shows Not Secure in the address bar, your site is sending data in the open. Here is what that means, what causes it, and how to get it sorted.


Your browser is telling you, and every one of your visitors, that the connection to your site is not secure.
The connection between a visitor’s browser and your server is unencrypted: data travels in the open, readable by anyone sitting between them. A free certificate fixes most small business sites in under an hour. The tricky part is knowing what to check afterwards.
This guide covers what SSL actually does, why browsers and Google care, the difference between free and paid certificates, and the two or three things that often go wrong even after a certificate is installed.
What SSL actually does
When someone visits your site over plain HTTP, the data moving between their browser and your server travels as plain text. Your internet provider can read it. So can a dodgy public wi-fi router, or any piece of software inserted somewhere along the route.
HTTPS wraps that connection in encryption. The browser and server agree on a private key before any real data moves. From that point, everything passing between them looks like scrambled noise to anyone intercepting it.
- Encrypted connection (HTTPS)Data scrambled in transit; only browser and server can read it
- CertificateProves the server is who it claims to be; issued by a trusted authority
- Your web serverSends pages, receives form submissions
The certificate does two jobs: it holds the encryption keys, and it proves your domain is operated by whoever installed it. When a browser opens your site, it checks the certificate was issued by a trusted authority and has not expired. If both pass, the connection proceeds and no warning shows.
Google’s own guidance on web security puts it plainly: HTTPS prevents intruders from tampering with communications between your site and your users. Those intruders range from malicious attackers to companies that inject ads into unprotected pages.
What the padlock actually meant, and what Chrome changed
For years, a padlock in the address bar meant HTTPS was active. Chrome replaced it with a neutral settings-like icon a couple of years ago. The reason, according to the Chromium team’s explanation, is that research found most people misread the padlock as a sign the site itself was trustworthy, rather than just that the connection was encrypted.
The warning side stayed the same. A site on plain HTTP still gets “Not secure” in the address bar, in plain text, before any content loads.
- "Not secure" shown in the address bar
- Any form data sent as plain text
- Modern browsers may refuse to load it at all
- Google treats it as a weaker signal than HTTPS
- Neutral icon, no warning shown
- Connection encrypted end to end
- Eligible for modern browser features
- Meets Google's baseline expectation
A first-time visitor who sees “Not secure” before they have read a single word about your business has already been given a reason to leave. That is a hard first impression to recover from.
Why Google cares about HTTPS
Google confirmed HTTPS as a positive ranking signal some years ago, and it remains one. The effect on any individual site is modest. But on a competitive local search, where a dozen similar businesses are trying to rank for the same suburb and service, modest disadvantages add up.
Google’s crawler also prefers HTTPS and will index that version of a page over the HTTP version when both exist. If your site runs on both without a redirect, you end up with two versions of every page competing in the index. That dilutes whatever authority the page had built up.
Free versus paid certificates
Let’s Encrypt is a free, automated Certificate Authority run by a nonprofit called the Internet Security Research Group. Their own about page describes it plainly: anyone who owns a domain can get a trusted certificate at zero cost. The encryption it provides is identical to a paid certificate.
Paid certificates add layers of validation that go beyond proving you control the domain. The comparison below shows what the main types actually check.
| Certificate type | What it verifies | Who needs it |
|---|---|---|
| Domain Validation (DV) | You control the domain | Most small business sites, including Let’s Encrypt |
| Organisation Validation (OV) | Domain plus your business details | Businesses wanting the company name visible in cert details |
| Extended Validation (EV) | Domain plus legal and operational checks | Banks, payment processors, large e-commerce |
For a local trades or service business, a free DV certificate is the right tool. The encryption is identical to a paid one; the only difference is how thoroughly the Certificate Authority checked the business behind the domain, and most visitors never see that detail.
Most reputable hosting providers install Let’s Encrypt automatically and renew it every 90 days without you touching anything. If yours does not, it is worth asking why.
How to tell if your site has one
You can check in about 30 seconds:
- Type https:// followed by your domain into a browser address bar and press enter. If no warning appears, the certificate is working.
- Now type http:// followed by the same domain. You should be redirected to the HTTPS version automatically. If you land on the HTTP version with no redirect, that is a gap to fix.
- Check a few internal pages beyond the homepage. A certificate that only covers one page is not a complete setup.
- If you have a contact form, submit a test enquiry over HTTPS and confirm it arrives. Forms on a secure page sending data to an insecure endpoint are a common misconfiguration.
For a more detailed check, the SSL Labs server test at ssllabs.com grades your certificate and flags technical problems. An A or A+ means the setup is clean.
What mixed content is and why it keeps showing a warning
Installing the certificate but still seeing warnings is almost always mixed content. That is when your page loads over HTTPS but one or more elements, an image, a script, an embedded map, still load over plain HTTP.
Browsers treat these two types differently:
- Passive mixed content is things like images and video. Modern browsers will often upgrade these silently, but you may still see a warning in the browser console.
- Active mixed content is scripts and stylesheets. These get blocked entirely, because a script loaded over an insecure connection could be altered in transit to do anything.
Mixed content often comes from an old image URL hardcoded as http:// in your CMS, or from a third-party plugin or widget that has not been updated. Search your page source for http:// and check each one. Changing them to https:// or to a protocol-relative URL fixes most cases.
The other common culprit is a WordPress site where the general settings still show http:// as the site address. Updating those two URL fields in Settings > General, then running a search-and-replace on the database for old HTTP URLs, is usually the full fix.
What to do if you see the Not Secure warning on your site
Work through these in order. A hosting control panel with SSL settings means you can do most of this yourself.
- Check if a certificate is installedGo to your hosting control panel and look for an SSL or HTTPS section. If no certificate is listed, install one. Most panels offer a free Let's Encrypt option with one click.
- Set up the HTTP to HTTPS redirectThis is usually a setting in your hosting panel or a line added to your .htaccess file. Once set, http:// automatically sends visitors to https://.
- Update your CMS site URLIn WordPress, go to Settings > General and change both the WordPress Address and Site Address to start with https://. Save, then log out and back in.
- Fix mixed contentLoad your site and open the browser developer console. Any mixed content warnings will show as errors listing the http:// URL causing them. Update each one to HTTPS.
- Verify and testGo through the checklist above: HTTPS loads cleanly, HTTP redirects, internal pages work, form submissions arrive. Done.
If the warning came back after a site migration, run through this list:
- No HTTP to HTTPS redirect. The certificate is working but http:// still serves the unencrypted version. Visitors who type your address without https:// never reach the secure site.
- CMS still set to HTTP internally. WordPress has a site URL setting. If it still reads http://, internal links and form submissions go to the wrong place.
- Certificate covers only one subdomain. Some setups issue a certificate for www but not the bare domain. Both versions need covering.
- Expired certificate. Let’s Encrypt runs for 90 days and needs renewing. Most hosting setups do this automatically, but if auto-renew breaks, the warning returns. Your hosting panel will show the expiry date.
- Mixed content remaining. Covered in the section above.
Migrations often copy across the old HTTP site settings unchanged. If everything was fine before the move and broken after it, start with the CMS URL setting and the redirect.
Getting it right from the start
The cleanest outcome is a hosting setup where this is already handled: certificate installed, auto-renew on, HTTPS forced, CMS pre-configured. The warning never appears and you never have to run a checklist.
If your current website has this problem, fix it before a customer has to mention it. Use the traffic lights below as a quick triage.
- Fix nowHTTP site with no certificate. The warning shows to every visitor on every page.
- Fix soonCertificate installed but no HTTP to HTTPS redirect, or mixed content warnings still showing.
- FineHTTPS loads cleanly, HTTP redirects automatically, certificate renews on its own.
Crsp Digital installs, configures and auto-renews SSL as part of every plan. The Get Found plan covers the full setup, including the site, your Google listing and email.
Frequently asked questions
What does Not Secure mean on a website?
It means the connection between the visitor's browser and your web server is unencrypted. Any data sent over that connection, including form details and contact information, travels as plain text that can be read or altered in transit.
Do I need an SSL certificate if I don't take payments?
Yes. The warning shows on any page that asks for data, including a simple contact form or even just a search box. Browsers also use HTTPS as a signal that the site is maintained, so even a brochure site benefits from having one.
Will not having SSL hurt my Google rankings?
Google has confirmed it uses HTTPS as a positive ranking signal. The effect on any individual site varies, but a site without HTTPS is at a disadvantage compared to an otherwise similar one that does have it.
What is the difference between SSL and TLS?
TLS is the current version of the protocol; SSL is the older name that mostly stuck. When someone says SSL certificate they usually mean a TLS certificate. The practical difference for a website owner is nothing.
Is a free Let's Encrypt certificate as good as a paid one?
For most small business websites, yes. The encryption is the same. Paid certificates add things like organisation validation or a warranty, which matter for banks and large e-commerce sites but are not meaningful for a local business site.
What is mixed content and why is it still showing a warning?
Mixed content is when a page loads over HTTPS but some elements on it, like an old image or a third-party script, still load over plain HTTP. Browsers block or warn on this even though the main page is secure. It is usually fixed by updating the affected URLs.
How do I check if my website has SSL set up correctly?
Type your domain into a browser with https:// at the front and look at the address bar. If you see a padlock or a neutral icon and no warning, the certificate is working. Also check that http:// redirects to https://, because if it does not, visitors who type the short version land on the insecure copy.
My hosting provider says SSL is free. Do I need to do anything?
Possibly. Many hosts install a Let's Encrypt certificate automatically, but you still need to confirm that HTTP redirects to HTTPS, that your CMS is set to use HTTPS for internal links, and that no mixed content remains. Installation and correct configuration are two different jobs.
The SSL and Not Secure checklist.
Check, fix and verify your SSL setup, on one page.


