IN THIS ARTICLE · 8 PARTS
"Not secure" next to your address, or a full-page "Your connection is not private" warning, means the browser cannot confirm that the connection to your site is encrypted and really yours. For a small business this is expensive: visitors turn back, and almost nobody fills in a form on a page the browser has just called unsafe. The good news is that the cause is almost always one of six things, and you can find which one in five minutes.
If you are not sure what a certificate is in the first place, start with what an SSL certificate is and why you need one.
Which warning do you see?
Chrome shows different warnings for different problems [1]:
| What you see | What it usually means |
|---|---|
| "Not secure" in grey next to the address | The page is loaded over http://, with no encryption |
"Not secure" in red, or a crossed-out https | There is a certificate, but something is wrong with it or with the page |
| Full page: "Your connection is not private" | The certificate is expired, for another address, or not trusted |
| Full page in red: "Dangerous" | A different problem: Google Safe Browsing has flagged the site as unsafe, often after a hack |
The last one has nothing to do with the certificate. If you see it, open Search Console and check the Security issues report, because your site has most likely been hacked.
Why it matters more since October 2026
For years Chrome only labelled http:// sites "Not secure" quietly next to the address. That changed. Google announced that from Chrome 154, in October 2026, the "Always use secure connections" setting is on by default: Chrome asks the visitor for permission before it opens a public site without HTTPS, and shows a warning they have to click through [2].
So a site without HTTPS no longer just looks a little worse. A visitor coming from Google or from your Facebook page now meets a warning before they see anything.
The six common causes
1. There is no certificate at all
The address starts with http://. This is common with old sites and cheap hosting where nobody switched HTTPS on. Today certificates are free: Let's Encrypt does not charge for them [3], and most hosts install them with one click.
2. The certificate has expired
The site worked yesterday and today shows a full-page warning. Certificates are valid for a limited time, and that time is getting shorter: the industry has agreed to cut the maximum from 398 days down to 47 days, in steps from March 2026 to March 2029 [4]. Let's Encrypt certificates last 90 days, and it recommends renewing them every 60 [3].
In other words, renewing a certificate by hand once a year no longer works. Renewal has to be automatic, and someone has to notice when the automation fails.
3. The certificate is for a different address
The certificate covers example.com but not www.example.com, or the other way round. The site opens fine one way and shows a warning the other way. Chrome reports it as an invalid name error (ERR_CERT_COMMON_NAME_INVALID). The fix: a certificate that covers both versions, and a redirect from one to the other.
4. Mixed content
The page is on https://, but it loads something from http://: an old image, a script, a font, an embedded map. Modern browsers upgrade images, video and audio to HTTPS automatically, but they block insecure scripts, stylesheets, iframes and fonts [5]. The result is a page that looks half broken: a missing map, a booking widget that does not load, a different font. This usually happens after a move to HTTPS where old addresses stayed in the content.
5. No redirect from http to https
The certificate is fine, but old links, old business cards and people typing the address by hand still land on http://. The site has to send every http:// address to its https:// version with a permanent (301) redirect. Google confirms that 301 redirects do not lose ranking strength, and recommends keeping them for at least a year [6].
6. A form that sends over http
Everything looks fine until someone starts typing in the contact form and the browser warns them. Usually the form sends its data to an old http:// address or to an outside service without HTTPS. This is the worst place for a warning, because it is exactly where the enquiry happens.
When the problem is on the visitor's side
Sometimes the site is fine and only one person sees a warning. The most common reason: the date and time on their device are wrong. Chrome then shows NET::ERR_CERT_DATE_INVALID or "Your clock is behind", and the fix is to set the correct date and time [7]. Antivirus programs that "scan HTTPS" and company networks can cause similar errors [7]. If the warning appears for everyone, on every device, the problem is the site.
Find the cause in five minutes
- Open the site in a private window, both as
example.comand aswww.example.com, withhttp://and withhttps://. All four should end up on the samehttps://address, without a warning. - Click the icon to the left of the address. Chrome shows whether the connection is secure and whether the certificate is valid [1].
- Check the certificate date. In the same window: "Connection is secure" > "Certificate is valid". Look at "Expires on".
- Look for mixed content. Right click > Inspect > Console. Warnings that mention "Mixed Content" list exactly which file is loaded over
http://[5]. - Send yourself a test enquiry from the contact form, and watch for a warning while you type and send.
- Run a free external test such as SSL Labs (ssllabs.com/ssltest). It checks the certificate, the chain and the settings, and explains what is wrong in plain terms.
| Error or symptom | Most likely cause | Fix |
|---|---|---|
Grey "Not secure", address with http:// | No HTTPS or no redirect | Install a certificate, add a 301 redirect to https |
NET::ERR_CERT_DATE_INVALID for everyone | Expired certificate | Renew it and set up automatic renewal |
NET::ERR_CERT_DATE_INVALID for one person | Wrong clock on their device | Correct date and time on the device |
ERR_CERT_COMMON_NAME_INVALID | Certificate for another address (www or without) | Certificate for both versions |
| Page half broken, warning in the console | Mixed content | Change the http:// addresses in the content to https:// |
| Warning when sending the form | Form sends to an http:// address | Point the form to an https:// address |
Does "Not secure" hurt your Google ranking?
Indirectly, yes. Google says that among the page experience aspects only Core Web Vitals are used directly in ranking, and that the rest, including whether a page is served securely, do not directly help a site rank higher [8]. But a visitor who meets a warning and goes back to the results is a visitor you lost, and Google's systems aim to reward pages people are satisfied with [8]. HTTPS is also a basic part of SEO for a business website, so there is no reason to go without it.
How to make sure it does not come back
- Automatic renewal. The certificate renews itself well before it expires. With hosting like Cloudflare this happens without anyone touching it.
- One main address. Choose
https://with or withoutwww, and send every other version there with a 301. - Only
https://in the content. When you add a video, a map or a widget, take thehttps://version of the code. - Someone who notices. A check that sends an alert when the certificate is close to expiring or the site is down. That is a big part of what website maintenance is for.
When you move a site to a new host or a new address, the risk of all six causes is at its highest. Before moving, read how to move your domain to a new website, and for the full picture of domains, DNS and hosting, see domains and hosting: a complete guide.
Sources
- Google Chrome Help. "Check if a site's connection is secure." support.google.com/chrome
- Google. "HTTPS by default" (October 2025). blog.google
- Let's Encrypt. "FAQ." letsencrypt.org
- CA/Browser Forum. "Ballot SC-081v3: Introduce Schedule of Reducing Validity and Data Reuse Periods." cabforum.org
- MDN Web Docs (Mozilla). "Mixed content." developer.mozilla.org
- Google Search Central. "Site moves with URL changes." developers.google.com/search
- Google Chrome Help. "Fix common error messages in Chrome." support.google.com/chrome
- Google Search Central. "Understanding page experience in Google Search results." developers.google.com/search

