← Repair Hub

“Not Secure” Warning in the Browser

SSL, Security & Connection

Chrome is labeling your business untrustworthy in the address bar.

datacram.com/fix/not-secure-warning
Likely causes, ranked
“Not Secure” Warning in the Browser
The site has no HTTPS at allmost likely
HTTPS exists but is not enforcedcommon
Mixed content on the pagecommon
Hardcoded URLs in the databasepossible
Fix steps in this guide5
the causes explained below, most likely first
What you’re seeing

The address bar shows “Not secure” next to your domain, sometimes with a red warning triangle. It gets louder the moment a visitor clicks into a form field.

What it actually means

This is not the same as an expired certificate. The page loads normally, without an interstitial. The browser is simply telling the visitor that the connection is not fully encrypted, and it puts that message exactly where people look before deciding whether to trust a business.

There are two ways to earn it. Either the page is being served over plain HTTP, or the page is HTTPS but is pulling some of its parts over HTTP — which the browser treats as good as insecure, because a single unencrypted script can compromise the whole page.

What usually causes it

Most likely first.

  1. 1

    The site has no HTTPS at all

    Increasingly rare, and increasingly punished. Certificates are free, so there is no longer any reason to serve a business site over HTTP.

  2. 2

    HTTPS exists but is not enforced

    Both versions work and nothing redirects, so visitors — and Google — land on the insecure one depending on how they arrived.

  3. 3

    Mixed content on the page

    Images, scripts, or stylesheets hardcoded with http:// URLs. The page is encrypted; its ingredients are not.

  4. 4

    Hardcoded URLs in the database

    On WordPress, old http:// links live inside post content and options, surviving every attempt to fix it in the theme.

  5. 5

    A third-party embed on HTTP

    An old widget, tracker, or font served insecurely drags the whole page's status down with it.

How to fix it

Work through these in order. Take a backup before you change anything.

  1. Step 1Install and verify a certificate

    If there is no HTTPS yet, issue a certificate first — nothing else can be fixed until the secure version of the site actually works.

  2. Step 2Force HTTPS everywhere

    Redirect all HTTP traffic to HTTPS at the server, and update the site address settings so the canonical version is the secure one.

  3. Step 3Find the insecure assets

    Open the browser console — it names every blocked or insecure request outright. That list is your to-do list, no guessing required.

  4. Step 4Fix hardcoded links in the database

    Run a careful search-and-replace for http://yourdomain to https://yourdomain across the database, using a tool that handles serialized data properly. Back up first.

  5. Step 5Add HSTS once it is clean

    Only after everything loads over HTTPS. It tells browsers never to try the insecure version again, and it is hard to undo if you enable it too early.

When to stop and call someone

Call someone if the warning persists after enforcing HTTPS, if a database search-and-replace feels risky on a live store, or if you take payments and forms — a “Not secure” label beside a checkout field is the most expensive four seconds on your website.

Frequently asked

Because the page is either served over plain HTTP or is loading some resources insecurely on an HTTPS page. Chrome marks any page without a fully encrypted connection, and the warning becomes more prominent as soon as a visitor clicks into a form field.

No. An expired certificate produces a full-page interstitial the visitor must click through. The Not Secure label appears in the address bar while the page loads normally — quieter, but seen by every visitor on every page.

It is an HTTPS page that loads some of its resources — images, scripts, stylesheets — over insecure HTTP. Browsers treat the whole page as compromised, because an unencrypted script can alter everything around it, and often block those resources outright.

Yes, in both directions. HTTPS is a confirmed ranking signal, and the warning also drives visitors away, which weakens the engagement signals search engines watch. Fixing it usually helps rankings and conversion at the same time.

No — free certificates from Let's Encrypt are trusted by every major browser and are what most hosts install by default. Paid certificates buy warranties and organizational validation, not stronger encryption.

Free · AI-powered · Emailed to you

See exactly what’s holding your website back.

Get a free audit of your site — speed, SEO, mobile, and security — with the fixes that matter most, delivered as a PDF to your inbox.

Get my free audit
CallGet a quote