Why Does My Website Say Not Secure in Chrome?

If your website says Not Secure in Chrome, it means the browser cannot confirm a safe, encrypted connection to your site. The page either loads over plain HTTP, or it loads over HTTPS but has a problem with its SSL certificate. The warning is not a punishment. It is Chrome telling visitors that anything they type on the page could be read by someone else on the network.

The good news is that most cases have a simple fix. In many cases a free certificate from your host and one redirect solve the problem in an afternoon. This guide explains what the warning means, how to find the cause, and how to fix it step by step.

What the Warning Means

When you visit a website, your browser and the server exchange information. On a secure site, that exchange is encrypted with HTTPS. Encryption scrambles the data so only your browser and the server can read it. On an insecure site, the same data travels as plain text.

Chrome marks a page Not Secure when that encryption is missing or broken. The label sits in the address bar, to the left of the web address. In older versions of Chrome it replaced the padlock icon. In recent versions the warning has become harder to miss. Since October 2026, Chrome also asks visitors for permission before it opens a public site that only works over HTTP. That means some visitors now see a full warning page before your homepage loads at all.

A Not Secure label does not always mean your site was hacked. It usually means one of a small set of setup problems. The most common causes are:

  • No SSL certificate is installed on the site.
  • The certificate has expired and needs to renew.
  • The certificate does not cover the version of the address visitors use, for example the www version or a subdomain.
  • The page loads over HTTPS but some images, scripts or stylesheets still load over HTTP. This is called mixed content.
  • Visitors land on the HTTP version because no redirect sends them to HTTPS.

A different warning, the red “Your connection is not private” page, points to a certificate problem on an HTTPS page. Our guide to Chrome error fixes explains that warning and its fixes in detail.

Why It Matters

The warning costs trust before a visitor reads a single word. People leave insecure pages faster, and they rarely type personal details into them. That matters for every site with a contact form, a login page or a checkout.

Google has treated HTTPS as a ranking signal since 2014. A secure site also ranks better in practice because visitors stay longer and bounce less. Fixing the warning is therefore both a security job and a search job.

If You Own the Site: the Fix Checklist

Work through these steps in order. Check your site in Chrome after each step, so you know which fix solved it.

1. Check which version of your address shows the warning

Open all four versions of your address in Chrome: http://yourdomain.com, http://www.yourdomain.com, https://yourdomain.com and https://www.yourdomain.com. All four should end on the same secure page with no warning. If only one version warns, the problem is narrow. If every version warns, the site probably has no working certificate at all.

2. Install or switch on an SSL certificate

Most hosts now include a free certificate from Let’s Encrypt with every hosting plan. Log in to your hosting control panel and look for SSL, Security or Certificates. If a free certificate is offered, switch it on for your domain. Allow up to 48 hours after a new certificate or a DNS change for everything to settle, though it usually works within minutes.

If your host charges for certificates, ask about the free option first. A basic certificate is enough for most small sites. You only need a paid certificate if you want warranty cover or a company name in the certificate details. If you are still choosing a host, our guide on what web hosting is in simple terms explains what a host does and what a beginner actually needs.

3. Renew or replace an expired certificate

Certificates expire. Most last 90 days to one year, and many hosts renew them automatically. If yours did not renew, check the expiry date by clicking the icon to the left of the address bar on the secure version of your site. If the date has passed, renew the certificate in your hosting panel. Then check that automatic renewal is switched on, so the same problem does not return quietly in a few months.

4. Redirect every HTTP page to HTTPS

A certificate alone is not enough. Visitors who type your address without https, or follow an old HTTP link, must be sent to the secure version automatically. Most hosts offer a “Force HTTPS” switch in the control panel. Switch it on. If your site runs on WordPress, you can also set the site address to https in Settings, then General. After the redirect is live, test an old HTTP link and confirm it lands on HTTPS.

5. Fix mixed content

If the homepage is secure but some pages still warn, mixed content is the likely cause. The page itself loads over HTTPS, but an image, a script, a font or a stylesheet loads over HTTP. Open the page in Chrome, press F12, and look at the Console tab. Chrome lists each insecure item there. Update each link to https, or to a relative address with no protocol at all. A WordPress plugin such as Really Simple SSL can find and fix these links, but check the result by hand afterwards.

6. Update internal links and your sitemap

Once the redirect works, update your internal links, your sitemap and any links in your email signatures or social profiles to use https. Search engines treat the HTTP and HTTPS versions as separate pages, so a clean sitemap helps Google index the secure version. Resubmit the sitemap in Google Search Console if you use it.

7. Test from a clean browser

Test the site in a private window and on a second device. This rules out a cached redirect or a saved certificate on your own computer. If the warning is gone everywhere, the fix is complete. If it persists only on one device, clear that browser’s cache and check the device clock, because a wrong system date can break certificate checks.

If You Are Just Visiting: Stay Safe

If the warning appears on someone else’s site, the risk sits with you. Do not log in, and do not enter payment details, passwords or personal information on a Not Secure page. The connection is unencrypted, so that information could be intercepted.

You can still read a plain article on an insecure site, but treat it as public. Never submit a form on it. If you need to contact the owner, use their social media page or an email address from a trusted source, and let them know their site shows the warning.

Be extra careful when a Not Secure page also pressures you to act fast. Scam pages often combine an insecure connection with urgent messages about parcels, refunds or account closures. Our guide on how to spot a phishing email shows the red flags to check before you click or reply.

FAQs

Does Not Secure mean my website was hacked?

Not usually. The warning means the connection is not encrypted or the certificate has a problem. A hacked site is a separate issue. If you fix the certificate and the warning stays, ask your host to scan the site for malware.

How long does it take to fix a Not Secure warning?

Most fixes take under an hour once you find the cause. A free certificate from your host usually activates within minutes. DNS changes can take up to 48 hours, but that is the exception rather than the rule.

Is a free SSL certificate good enough?

Yes, for most small sites. A free certificate from Let’s Encrypt gives the same encryption as a paid one. Paid certificates add warranty cover and organisation checks, which matter more for large shops and financial sites.

Why does my site show Not Secure on mobile but not on desktop?

The two browsers may cache different versions of the site, or one may follow a different redirect. Clear the mobile browser cache, then test the HTTP and HTTPS versions again. If the warning stays only on mobile, check for mixed content in images that load only on small screens.

Will the warning hurt my Google ranking?

HTTPS is a confirmed ranking signal, and visitors leave insecure pages sooner. Both effects work against you. Fixing the warning removes a ranking disadvantage and restores visitor trust at the same time.

Conclusion

A Not Secure warning in Chrome means the connection to your site is not encrypted, or the SSL certificate has a problem. Start by testing all four versions of your address, then install or renew a certificate, force HTTPS with a redirect, and fix any mixed content. Most sites are secure again within an hour. Do the fix now, before the warning costs you visitors, sales or search rankings.