Chrome and other browsers show “Not secure” when a page loads without HTTPS, the encryption that stops anyone between your visitor and your website from reading or changing what’s sent. Google’s own help page puts it simply: the site isn’t using a private connection, and the fix is for the site owner to switch on HTTPS (Chrome Help). For most businesses that’s a quick, free fix. The good news from our research: almost every Utah trade website has the padlock. The bad news: most stop there.
What does “Not secure” actually mean?
It means the page wasn’t loaded over an encrypted connection. Anything a visitor types into it, like a name, phone number or address on your quote form, could in principle be read or changed on its way to you. On public Wi-Fi at a coffee shop, that isn’t just theory.
It doesn’t mean your site has been hacked. It’s a warning about the connection, not proof of a break-in. But your customers can’t tell the difference, and a warning next to your name in the address bar makes people hesitate right when you want them to call.
The four usual causes and how to fix each
| What’s wrong | How you’d notice | The fix |
|---|---|---|
| No certificate at all | Every page says Not secure | Turn on the free certificate in your host or builder settings |
| The certificate expired | A full-page warning, often “Your connection is not private” | Renew it, and turn on automatic renewal |
| The http:// version doesn’t forward | The warning shows only when someone types or clicks an old http:// link | Set every version of your address to forward to https:// |
| Mixed content | Only one page shows the warning, or the padlock has a warning sign | Change the image, script or form on that page from http:// to https:// |
Free certificates are normal now. Let’s Encrypt, a nonprofit, gives them away for free and serves more than 700 million websites (Let’s Encrypt). Most hosts and builders, including WordPress hosts, Wix, Squarespace and GoDaddy, include one and renew it for you.
Tip: type your address with http:// in front, then without www, then with it. Every version should land on the same https:// address. If any of them shows a warning or a different page, that’s the one to fix.
How many Utah trade websites get this right?
Almost all of them get the padlock. Far fewer get the rest. In October 2026 we checked the websites of 409 independent Utah trade businesses, taken from Google’s map results for 10 trades across Provo, Salt Lake City, Layton, Lehi and Sandy.
Most Utah trade sites have the padlock. Fewer have the rest.
Share of 409 independent Utah trade websites passing each security check.
Before that, some sites weren’t working at all. Google’s map results linked to 472 trade business websites. 24 of them, about 5%, had no working website behind the link: 12 had a domain that was gone or a certificate error, and 12 were parked, expired, broken or taken over by spam. Those businesses are sending customers from Google straight to an error page.
The padlock is nearly universal. 400 of the 409 working sites (98%) loaded over HTTPS with a valid certificate, and only 3 had a certificate within two weeks of expiring.
One address, many doors. 14% of sites didn’t send every version of their address (http, https, with and without www) to the same place. Usually that means one version shows a warning, an error or a duplicate copy of the site.
The protection most sites skip
A padlock protects the connection. A few more settings protect the page and your name.
Security settings sent with each page. Five settings, sent quietly with every page, tell the browser to always use HTTPS, not to let other sites frame your page, not to guess file types, what’s allowed to run, and how much to share when someone clicks away. The OWASP Foundation, the web’s best-known security nonprofit, recommends all of them (OWASP). Most Utah trade sites send almost none:
Most sites send few or none of the five basic security settings
Number of 409 Utah trade websites by how many of 5 settings they send (HSTS, CSP, nosniff, frame, referrer).
This depends heavily on the platform, because owners rarely set these themselves. Squarespace sent 3 or more on 14 of its 17 sites. WordPress did on 19% (28 of 148), GoHighLevel on 6 of 33, and Wix on 1 of 29.
Email protection records. Two short records on your domain, called SPF and DMARC, tell email providers which servers may send mail as [email protected]. Without them, it’s easier for a scammer to send an invoice that looks like it came from you, and your own quotes are more likely to land in spam. Gmail now requires these from bulk senders and expects at least SPF or DKIM from everyone (Google Workspace Admin Help). Only 38% of the Utah trade domains we checked had both SPF and DMARC.
Form spam protection. Of the 334 sites with a contact form, 40% had no spam protection we could detect. Unprotected forms fill up with junk, and real requests get buried or ignored.
Domain renewal. 19 of 399 domains we could check (5%) were within 60 days of expiring. An expired domain takes your website and your email down at the same time.
Does Not Secure hurt your Google ranking?
Slightly, and that’s not the main reason to fix it. Google announced HTTPS as a ranking signal in 2014, and said at the time it was “a very lightweight signal,” affecting fewer than 1% of searches (Google Search Central Blog). The bigger cost is trust. A visitor deciding between three roofers isn’t going to pick the one whose site carries a warning label.
What to do this week
- Check the padlock on your homepage, your contact page and one service page.
- Test every version of your address (with http://, without www) and make sure all of them end at the same https:// page.
- Turn on auto-renew for your domain and your certificate, and check the card on file hasn’t expired.
- Send yourself a test from your contact form, then ask your web person whether it has spam protection.
- Ask whoever handles your email whether your domain has SPF and DMARC records. It’s a ten-minute job for them.
- Ask when the site’s software was last updated. Out-of-date plugins and themes are a well-known weak spot.
If you’d like to see how your hosting choice plays into this, our guide on whether it matters where your site is hosted covers it, and does my website need a privacy policy? covers the forms side.
How we handle this for you
Every site we build is hosted on Amazon Web Services with HTTPS everywhere and security headers, the protective settings described above, kept up to date as part of Care, our $99-a-month plan. Forms have spam protection.
Your domain is registered in your name, in your own account, and you pay its yearly renewal, so turn on auto-renew there. The build is $5,000, one time, and you see your new site working before you pay anything. You can stop the monthly plan anytime and keep everything.
See what we build and what it costs, look at sites we’ve built, or apply in about two minutes.
How we measured
- Who: the websites of 409 independent Utah trade businesses, taken in order from Google’s local map results for 10 trades in Provo, Salt Lake City and Layton (plus Lehi and Sandy for some trades). 472 sites were linked from those results; broken, parked and blocked sites were counted separately and not scored; national franchise sites were left out.
- When: October 21, 2026.
- How: each site was loaded over https:// and http://, with and without www. We read the certificate, the security settings sent with the homepage, the visible software versions, the domain’s public DNS records (SPF, DMARC) and its registration expiry date. We didn’t test for break-ins or try to get past any protection, and we didn’t look at anything that isn’t public.
- Limits: a check from the outside can’t see everything; a site can pass all of these and still have weak passwords or an old plugin we can’t detect. These are a floor, not a full security audit.
- Who we are: we build websites for local businesses, so we have a stake in this topic. We don’t name any business.
Sites we've built
Five-minute security check
0 / 6
Tap to tick. Your ticks stay on this device.