
"Not secure" in Chrome: why it shows and how to fix it
By Leonel Rocha · Product Designer
· 7 min read
The "Not secure" warning shows up when a site doesn't use HTTPS, when its SSL certificate has expired or was installed incorrectly, or when the page loads images and scripts over HTTP. Starting with Chrome 154, which Google expects in October 2026, the browser will ask for permission before opening any public site without HTTPS. The fix is to install a valid certificate, force HTTPS on every page, and automate renewal.
The "Not secure" warning shows up when a site doesn't use HTTPS, when its SSL certificate has expired or was installed incorrectly, or when the page loads images and scripts over HTTP. Starting with Chrome 154, which Google expects in October 2026, the browser will ask for permission before opening any public site without HTTPS. The fix is to install a valid certificate, force HTTPS on every page, and automate renewal.
- Chrome 154
- is the version in which Google plans to turn on, for everyone, the warning before opening public sites without HTTPS (October 2026)
- 200 days
- is the maximum validity of an SSL certificate issued since March 15, 2026, according to the CA/Browser Forum
- 47 days
- will be the maximum validity starting March 15, 2029
A customer types in your site's address and, before seeing your page, gets a browser warning screen. Or they open the site and find the words “Not secure” next to the address. Either way, the first impression of your company is a risk warning.
This is no longer a technical detail. Google has announced that Chrome will ask for permission before opening any public site without HTTPS, for all users, and the validity of security certificates is getting shorter every year. This guide explains why the warning appears, what changes now, and how to fix it for good.
What changes in Chrome 154
In October 2025, the Chrome security team published the HTTPS by default plan. It turns on a setting called “Always use secure connections” in two steps:
- Chrome 147, in April 2026: the setting would be turned on for users who opted into Enhanced Safe Browsing, more than 1 billion people, according to Google.
- Chrome 154, expected in October 2026: the setting comes turned on for all users.
With it on, Chrome, in Google's words, “will ask for the user's permission before the first access to any public site without HTTPS.” Visitors can click through, and the browser doesn't repeat the warning on sites people visit regularly. But your new customer, who found you through search or an ad, is exactly the person who has never visited your site before. They're the one who sees the warning screen.
Google itself shows these sites are already a minority. According to the same post, between 2015 and 2020 the share of HTTPS page loads went from somewhere between 30% and 45% to somewhere between 95% and 99%. In other words, sites still on HTTP are more and more isolated, and the warning is more and more visible.
Why your site shows as “Not secure”

The warning almost always comes from one of these causes. Check them in order:
- The site never had HTTPS. The address starts with “http://” and no certificate is installed. This is common on old sites built years ago and never reviewed.
- The certificate expired. The site had HTTPS and, overnight, the browser started showing an error. Someone needed to renew it and didn't, or automatic renewal broke.
- The certificate covers only part of the address. It works for “yourcompany.com” but not for “www.yourcompany.com”, or the other way around. Anyone who types the wrong version hits the warning.
- The redirect is missing. HTTPS exists, but the site still responds over HTTP. Anyone coming from an old link or typing the address without “https” comes in through the insecure door.
- Mixed content. The page opens over HTTPS but loads images, fonts, or scripts over HTTP. The browser blocks part of the content or stops showing the padlock.
Causes 2 and 3 catch companies off guard the most, because the site was working and stopped without anyone touching it.
Certificate lifetimes are shrinking
Until recently, an SSL certificate was valid for more than a year, and renewal was a yearly task someone put on the calendar. Not anymore.
In April 2025, the CA/Browser Forum, which brings together certificate authorities and browsers (Apple, Google, Microsoft, and Mozilla voted in favor), approved a gradual reduction in certificate validity. The timeline summarized by DNSimple looks like this:
- Since March 15, 2026: maximum validity of 200 days.
- Starting March 15, 2027: 100 days.
- Starting March 15, 2029: 47 days.
In practice, a certificate issued today has to be renewed at least twice a year. In 2029, almost eight times a year. Manual renewal becomes a guaranteed risk: all it takes is one person going on vacation, changing jobs, or missing an email, and the site wakes up to a warning screen.
If your site depends on someone remembering to renew, the problem isn't the certificate. It's the process.
The cost of leaving the warning up
A site with a security warning loses on every front:
- Visitors: people who see a red screen before getting to know your company rarely push through. They go back to search and click the next result.
- Ads: if you pay per click on Google Ads or Meta, every person who gives up at the warning is money paid for a visit that never happened.
- Forms and WhatsApp: over HTTP, the data customers type into a form travels unencrypted. Your customer's name, phone number, and email are exposed along the way.
- Trust: a “Not secure” warning on the site of a clinic, a firm, or a store sends the message of an outdated business, even if the service is great.
If, while looking into the warning, you find pages no one created, strange redirects, or unknown users in the admin panel, the problem is something else. Follow our guide on what to do in the first hours after a site is hacked.
How to fix it, step by step
The fix is quick when you have access to everything. It stalls when you don't. That's why the first step is administrative.
- Confirm your access. You need to log in to the hosting and the domain panel. If the password is with your old agency or a freelancer who disappeared, start with our step-by-step guide to recover your site's domain and hosting.
- Install a valid certificate that covers the domain with and without www and the subdomains the site uses.
- Turn on automatic renewal and check that it actually works. With 200-day validity today and 47 days in 2029, this is no longer optional.
- Force HTTPS with a 301 redirect from every HTTP page to its matching HTTPS version, one by one, not everything to the home page.
- Fix mixed content. Replace links to images, fonts, videos, and scripts that still point to “http://”.
- Update Google. Submit the sitemap with the HTTPS addresses in Search Console and check that your pages are still indexed.
- Test from the outside. Open the site in an incognito window, on your phone, and in another browser, typing the address without “https” and without “www”.
On sites built with lots of plugins, old themes, or code no one on the team knows, steps 4 and 5 are usually the hardest. That's where a site that “just needed a padlock” turns into days of fixes.
When the warning points to a bigger problem
Sometimes the certificate is just the tip. If the site sits on hosting no one at the company knows how to access, runs a WordPress version that hasn't been updated in years, or depends on someone who no longer responds, Chrome's warning is the first visible sign of a site with no owner.
In these cases, look at the whole picture before paying for a one-off fix: who takes care of the site, how often, and what's included. We've already shown how much website maintenance costs per month and what it should cover. A certificate with automatic, monitored renewal is a basic item in any serious maintenance contract.
What this means for you
Run the test today: open your site in Chrome, in an incognito window, typing only the address, without “https”. If any warning shows up, or if the padlock isn't there, treat it as urgent. Chrome 154 puts this warning in front of every new customer.
Then answer three questions: who renews the certificate, when it expires, and whether renewal is automatic. If no one at the company can answer, the problem will come back.
At the Studio, the code, files and access of every project are in the client's name, and the price is set after the audit, with the deadline written in the contract. Our hand-coded sites, like studioresponsivo.com.br, run on our server with HTTPS from day one. If your site shows a “not secure” warning, is locked out or stuck with someone who no longer answers, talk to our project rescue team.
Common questions
My site doesn't sell anything or have a form. Do I still need HTTPS?
Yes. Chrome's warning doesn't check whether the site has a form: it shows up for any public site without HTTPS. And people who hit a warning screen before reaching a company's site usually close the tab and go to a competitor.
Do SSL certificates cost money?
Not necessarily. There are free certificates with automatic renewal that work for most business sites. What costs money is the work: installing it, forcing HTTPS, fixing old links, and making sure renewal doesn't depend on someone remembering.
I installed the certificate and the warning is still there. What could it be?
The most common causes are a certificate installed only on the www address or only on the non-www one, a missing HTTP to HTTPS redirect, and images or scripts still loading over HTTP. It can also be an expired certificate on a subdomain the site uses.
Will switching to HTTPS hurt my Google ranking?
No, as long as you set up a 301 redirect from each old address to the new one, update the sitemap, and fix internal links. The risk comes when the switch is rushed and leaves broken or duplicate pages.
Sources
- HTTPS by defaultGoogle Security Blog · Chris Thompson, Mustafa Emre Acer, Serena Chen, Joe DeBlasio, Emily Stark and David Adrian · 2025-10-28 · EN
- Ballot SC081v3: Introduce Schedule of Reducing Validity and Data Reuse PeriodsCA/Browser Forum · 2025-04-11 · EN
- SSL Certificate Validity Changes (2026 - 2029)DNSimple · EN
Related service
Systems and apps
Systems, SaaS and iOS and Android apps from diagnosis to launch, with design, code and AI on the same team
News Responsivo
Get the next article in your inbox
Cost, timelines, AI and behind the scenes of shipping products. No spam.


