What the warning is telling you

"Not secure" is about the connection, not your content. It means the browser couldn't load the page entirely over HTTPS, the encrypted version of the web. Click the icon to the left of the address to see the details: Google's guide to checking if a site's connection is secure explains what each symbol means in Chrome.

Before changing anything, note the exact wording, which pages show it and whether the address starts with http:// or https://, then check from a second device on another network. Match what you see to this table.

What you seeThe likely causeWho usually fixes it
"Not secure" on every page and the address starts with http://No certificate, or no redirect from http:// to https://Your host or web provider
Fine on one version of the address but not the other, such as with or without wwwThe certificate or redirect covers only one versionYour host or web provider
The certificate is valid but some pages still show a warning or a broken padlockMixed content: an image, script, font or embed loaded over http://Whoever edits the site
A full-page "Your connection is not private" warningAn expired or mismatched certificateYour host; see our website down guide
Warnings started right after a launch or a hosting moveThe certificate wasn't issued because the domain wasn't pointing at the new server yetYour host or web provider

Why it matters more now

In its October 2025 post on HTTPS by default, Google said that with Chrome 154, due in October 2026, it would turn on the "Always Use Secure Connections" setting by default for public sites, so Chrome asks the visitor's permission before the first visit to a public site without HTTPS. Chromium's guide for site owners adds that Chrome remembers the choice for 15 days. Safari on Mac also has a setting to warn before connecting to a website over HTTP. A site without working HTTPS now risks a warning screen before a new visitor sees anything.

Step 1: make sure a certificate exists and covers every version

Log in to your hosting control panel, or ask your provider, and check that an SSL/TLS certificate is active for both the bare domain and the www version, plus any subdomain visitors use.

  • Free certificates are normal. Let's Encrypt's FAQ says its default certificates last 90 days, so renewal has to be automatic.
  • Don't wait for an expiry email. Let's Encrypt ended its expiration emails on June 4, 2025. Ask your host who renews the certificate and who gets told if renewal fails.
  • New launch or recent move? With the common HTTP-01 check, the certificate authority fetches a file from your domain over the web, so issuance can't succeed until the domain points at the server asking for it. Our hosting move guide covers that order.

Step 2: send every address to one HTTPS version

A certificate doesn't help if visitors still land on http://. Choose one preferred address, for example https://www.yourbusiness.com, and set permanent redirects so every other version goes straight there.

  • http:// without www goes to the preferred HTTPS address.
  • http:// with www goes there too.
  • The HTTPS version you didn't choose also redirects to the one you did.
  • Each redirect lands in one step, not a chain of hops.
  • Old links in your Google Business Profile, email signature and social profiles use the HTTPS address.

Once renewals have run reliably for a while, your provider may suggest HSTS, a header that tells browsers to always use HTTPS. Be careful: MDN's Strict-Transport-Security reference explains that browsers then won't let visitors click past certificate errors. If a renewal fails after that, the site is effectively offline until it's fixed.

Step 3: find and fix mixed content

This is the usual cause of "but my certificate is valid". web.dev's explanation of mixed content describes a page whose HTML loads over HTTPS while images, scripts or stylesheets still load over HTTP. MDN's mixed content page says browsers now upgrade some files, like images, to HTTPS automatically and block others, like scripts. So mixed content can show up as a warning, a missing image, or a button or form that quietly stops working.

web.dev's guide to fixing mixed content suggests this routine:

  1. Open each page in Chrome, then open the developer tools console to see mixed content warnings. The console only covers the page you're on, so check each page type.
  2. Search your site's code and content for http://. In a CMS, look at images inserted with full addresses and old embeds.
  3. Change each address to https:// if the file loads that way. If it doesn't, find another source, host the file yourself if you're allowed to, or remove it.
  4. Reload the page and confirm the warning has gone.

MDN describes upgrade-insecure-requests, a setting that rewrites http:// requests to https:// before they're made. It can be a useful safety net, but a file whose host doesn't serve HTTPS will still fail, so fix the source too.

Step 4: retest the pages that make you money

Check the home page, each page template, forms, booking embeds, maps, chat widgets and thank-you pages. Submit a test form and confirm it arrives. A form that sends its data to an http:// address isn't protected on the way, even if the page around it shows a padlock. Chromium's guide also recommends turning on "Always use secure connections" in your own Chrome settings to spot any remaining HTTP. Our launch QA checklist covers the wider check.

Google's site move guide counts a switch from HTTP to HTTPS as a URL change, so keep the redirects and check both variants in Search Console.

When to get help

If you can reach your hosting panel and edit your pages, the steps above are usually manageable. Get help when you can't find who controls the certificate or the DNS, when a fix in one place keeps breaking somewhere else, or when an embedded tool you depend on doesn't support HTTPS. Our page on who owns your domain helps you find out who holds the keys, and Website Maintenance covers monitoring, a monthly form test, backups and edits.

What this guide can't do

Browsers change how they label connections, and hosting panels name these settings differently. Check your browser's and host's current help pages before relying on a setting, and recheck after every launch, move or new embed.

Questions

Does "Not secure" mean my website has been hacked?

Not by itself. It describes the connection between the visitor and your site, not what's on it. If you also see pages you didn't create, strange redirects or a warning about dangerous content, follow our hacked website guide instead.

Do I need to tell Google when I switch to HTTPS?

Google's site move guide treats a change from HTTP to HTTPS as a move with URL changes. Redirect every old address to its HTTPS version and verify both variants in Search Console so you can watch the change.

Sources and further reading

Official documentation changes. Check the current version before you rely on a rule, limit or setting.

Next step

See a site built around your real details.

Look at sample layouts (fictional previews, not client work), read published website pricing, or ask for a free concept preview.

Already happy with your site? Website Maintenance covers monitoring, a monthly form test, backups and edits.