Your website says Not secure because the browser could not set up a private, encrypted HTTPS connection to that page. The fix is almost always one of four things: turning on an SSL certificate, renewing or correcting one that has lapsed, cleaning up a stray http link inside the page, or sending the old http address to the secure version.
I hear about this warning most often right after an owner pulls up their own site on a phone and sees it sitting next to their business name. It looks alarming, and it does cost you trust, but it is usually a quick, one-time repair. Here is what it means, how to find the cause, and what to do today.
What does the Not secure warning actually mean?
It means information traveling between your visitor and your site is not private. Google's Chrome help page on checking whether a site connection is secure says that when a site does not use a private connection, someone may be able to view or change the information sent through it, and that the site owner has to fix this by securing the site with HTTPS.
For a customer, that warning shows up right where they decide whether to trust you. The same Chrome page advises people not to enter private or personal information on pages flagged as not secure, which is the opposite of what you want on a quote request or booking form.
Does it hurt my Google ranking?
It can play a part, but it is not the whole story. In its guide to page experience in Google Search, Google lists whether your pages are served securely as one of the self-assessment questions for a good page experience, alongside speed, mobile display and intrusive pop-ups.
Google also says it will still show the most relevant page even when the experience is not great, so HTTPS alone will not lift a thin page to the top. The bigger cost is people who land on your site, see the warning and leave. I covered the speed side of page experience in does website speed affect my Google ranking.
What causes the warning on a small business site?
Nearly every case I see falls into one of four buckets:
- HTTPS was never turned on. The site only loads at an address starting with http, with no certificate at all. This is common on older sites, or ones a friend or former employee built years ago.
- The certificate expired or does not match. Certificates have to be renewed, and each version of your address needs coverage. Google's web.dev guide to enabling HTTPS on your servers notes that if you have several hostnames or subdomains, each one needs the right certificate. A site that works with www but shows an error without it is the classic example.
- Mixed content. The page itself is secure, but an image, script or embedded widget still loads from an http address. Google's explainer on what mixed content is says most browsers mark the page as not secure in the address bar when this happens, even though the page loaded over HTTPS, and that most browsers now block insecure content, which can quietly break a form or booking widget.
- The old http address still works on its own. Someone types your address without https, follows an old directory link or scans a QR code on an old flyer, and lands on the unprotected version. The web.dev guide recommends a permanent 301 redirect from http to https so every visitor ends up on the secure page.
How do I check which one I have?
Start in the browser, then look at Google's view of your site. This takes about fifteen minutes:
- Load your homepage, contact page and booking page on a phone and a computer. Look at the icon to the left of the address, and select it to see Chrome's summary of the connection.
- Type your address four ways: with and without www, and with http and https. All four should end up on the same secure https address.
- Check the certificate renewal date in your hosting or website builder dashboard. If it has lapsed or is about to, renew it and switch on automatic renewal.
- Hunt for mixed content on any page that still shows the warning even though its address starts with https. Old images inserted years ago, embedded maps, chat widgets and review badges are the usual suspects.
- Open the HTTPS report in Google Search Console. Google's help page for the Search Console HTTPS report explains that it shows how many of your indexed pages are HTTP versus HTTPS, and lists reasons such as an invalid certificate, a sitemap pointing to HTTP addresses, or an HTTPS page that redirects back to HTTP. Google says it strongly recommends HTTPS and prefers to index the HTTPS version when both exist.
How do I fix it?
Match the fix to the cause. Most of these are a settings change or a phone call to your host, not a rebuild:
- No certificate: turn on SSL in your hosting or website builder settings. Many hosts and builders include a certificate at no extra cost, so ask before you assume you need a new site.
- Expired or mismatched certificate: renew it, turn on automatic renewal, and make sure it covers both the www and non-www versions of your address.
- Mixed content: change any http links to images, scripts and embeds to https versions, or re-upload old images so they load from your own secure site.
- Old http address: set a permanent 301 redirect from http to https, then update your sitemap, Google Business Profile, social profiles and directory listings so they all point to the https address.
If your site collects anything, such as quote requests, bookings or newsletter signups, this is also a good moment to check that your privacy policy matches what the site does. My guide on whether your website needs a privacy policy walks through it.
One caution from the same web.dev guide: an advanced setting called HSTS tells browsers to always use HTTPS for your site, and visitors can be locked out if your certificate ever has an error. Leave that one until HTTPS has been running cleanly for a while.
When does it make sense to hand this off?
When you have already called your host twice, when nobody remembers who set the site up, or when the warning is a symptom of a bigger problem, like an old site that also loads slowly and breaks on phones. In those cases a refresh can cost less than patching it piece by piece. Our small business website cost guide lays out what a fair rebuild includes.
Every site we build through our website work launches on HTTPS with automatic certificate renewal, every old address redirected, and no stray http links, so whether you run a bakery in Crozet or a contracting crew in Waynesboro, it is one less thing to think about. If you want a quick read on the rest of your online presence, the free local business growth scorecard takes a few minutes.
Common questions
Is an SSL certificate the same thing as HTTPS?
Close enough for most owners. The certificate is what lets your site set up an HTTPS connection. If your address starts with https and the browser shows no warning, the certificate is doing its job.
Does my site need HTTPS if I do not sell anything online?
Yes. Chrome flags any page that does not use a private connection, whether or not it takes payments, and contact forms carry names, phone numbers and email addresses that deserve the same protection.
I fixed it, but my phone still shows the warning. Why?
Close the tab and reload, since your browser may be showing an older copy. If the warning stays on just one page, look for mixed content there. Google can also take time to recrawl, and its HTTPS report help page notes that some errors correct themselves after a while.
Seeing Not secure next to your business name and not sure where to start? Book a free 15-minute call and I will look at your site with you and tell you plainly what is causing it.
