Home / Insights / Article

All insights

Website security

Chrome now warns before opening HTTP sites: how to check and fix yours

Since Chrome 154, visitors see a full-page warning before any site without HTTPS opens. Here's how to test your site in five minutes, find the cause and fix it for good.

In short: since Chrome 154 rolled out in October 2026, Chrome tries HTTPS first for every public website and stops to ask the visitor's permission before it opens a page over plain HTTP. If your site, or any redirect on the way to it, still runs on HTTP, new visitors now see a full-page warning instead of your homepage. The fix is usually simple: a valid certificate on every version of your domain, one clean redirect to HTTPS, no insecure links or embeds, and a way to make sure the certificate never quietly expires.

For years, a site without HTTPS just got a small "Not secure" label in the address bar, and plenty of small businesses ignored it. That is no longer an option. Google's Chrome team announced on 21 October 2026 that Chrome now asks users before making an insecure HTTP connection, for all users by default. Google says most people won't see these warnings, because most of the web already uses HTTPS. But the sites that do trigger them tend to be older small business sites, parked domains and pages behind cheap domain forwarding, which is exactly where enquiries quietly leak away.

This guide explains what changed, how to check your own site in five minutes, the usual causes and how to fix each one, even if you didn't build the site yourself.

What changed in Chrome

Chrome has had a setting called "Always Use Secure Connections" since 2022. It was opt-in. From Chrome 147 in April 2026 it was switched on for people using Enhanced Safe Browsing, and with Chrome 154 it became the default for everyone, on desktop and mobile. Here is how it behaves, based on Chrome's own documentation:

  • HTTPS first. When someone types your address or clicks a link, Chrome tries the secure version first.
  • A warning before HTTP. If HTTPS doesn't work but HTTP might, Chrome shows a warning page and asks the visitor whether to continue. They can go back or carry on.
  • Once per site, mostly. If they continue, Chrome remembers the choice and won't warn again unless they haven't visited for about two weeks. Your regulars may see it once. Every new visitor sees it.
  • Redirects count. If any step on the way to your site uses HTTP, the warning appears even if the final page is HTTPS.
  • Local addresses are exempt. Home router pages and local IP addresses don't trigger it. Public business websites do.

Visitors can turn the setting off, but you can't count on that. Most people who see a security warning in front of a business they don't know yet simply go back to the search results and pick the next one.

How to check your site in five minutes

You don't need any tools beyond Chrome. Do this on a computer and repeat the key checks on your phone.

  1. Turn the warning on for yourself. Go to chrome://settings/security and make sure "Always use secure connections" is on. Chrome's documentation recommends this for site owners because it shows the warnings your visitors will see.
  2. Test every version of your address. Type each of these into the address bar exactly: http://yourdomain.com, http://www.yourdomain.com, https://yourdomain.com and https://www.yourdomain.com. All four should land on the same HTTPS page with no warning.
  3. Check the certificate. On the HTTPS page, click the icon to the left of the address and open the connection or certificate details. Note who issued it and the expiry date.
  4. Follow your real links. Click the website link on your Google Business Profile, your social profiles, your email signature and any QR codes on flyers or vans. Old links often still say http://.
  5. Watch the redirects. If you see a warning but end up on an HTTPS page, open Chrome DevTools, go to the Network panel, tick "Preserve log" and load the address again. Each hop is listed, and the HTTP one is your problem.
  6. Test the important pages. Open your contact page, booking page and any page with a form, and look for a warning or a "Not secure" label.

If all of that is clean, you're in good shape. If not, the table below tells you where to look.

What's causing the warning

What you seeLikely causeWhere to fix it
Warning on every version of the addressNo certificate installed, or HTTPS never switched onHosting control panel or your web developer
Warning only without www (or only with it)Certificate or redirect covers one version of the domain but not the otherHosting SSL settings and DNS
Warning, then you land on a secure pageAn HTTP hop in a redirect chainRedirect rules, domain forwarding or link tracking
Warning on an old domain that forwards to your new oneDomain registrar forwarding that doesn't support HTTPSRegistrar settings, or move the redirect to your host
"Your connection is not private" (red page)Expired, wrong or misconfigured certificateRenew or reissue the certificate
"Not secure" label or broken padlock on some pagesMixed content, such as images, scripts or forms loading over HTTPThe page code or the website builder's settings

Note the difference between the new HTTP warning and the red "Your connection is not private" page. The red page means HTTPS exists but something is wrong with the certificate. Chrome says those certificate warnings haven't changed, but they're just as damaging, and they tend to appear overnight when a certificate expires.

Fix 1: switch the whole site to HTTPS

If your site has no certificate, this is the main job. Certificates no longer have to cost money. Many certificate authorities offer free ones, most modern hosting includes free SSL that you may just need to switch on, and common web servers can obtain and renew certificates automatically.

  1. Turn on SSL in your hosting panel for the domain, and make sure it covers both yourdomain.com and www.yourdomain.com.
  2. Add one permanent (301) redirect from every HTTP address to the matching HTTPS address, in a single step where possible.
  3. Pick one main version, with or without www, and redirect the other to it.
  4. Update internal links, image paths, canonical tags and your XML sitemap so they all use https://.
  5. Update the links you control elsewhere: Google Business Profile, social bios, directory listings, email signatures and ad destinations.
  6. Check Google Search Console. A domain property covers both versions. Submit the HTTPS sitemap and keep an eye on the Pages report for a few weeks. You don't need the Change of Address tool for an HTTP to HTTPS move.

On WordPress, also update the site address settings to https:// and check that no plugin or theme setting still points at the old address. On hosted builders, HTTPS is usually a toggle in the domain settings, but custom domains connected years ago sometimes need it switched on by hand.

Fix 2: clean up redirect chains and forwarding

This is the cause most owners miss, because the site looks fine once you're on it. Chrome's own example is a site served on https://www.example.com that redirects http://example.com to http://www.example.com first. Because the bare domain has no HTTPS, visitors who type it get a warning before they ever reach the secure page.

Common culprits for small businesses:

  • The bare domain isn't covered. The certificate only lists the www version, or the other way round.
  • Registrar forwarding. An old or extra domain is "forwarded" at the registrar to your main site. Some forwarding services only work over HTTP. Ask the provider whether HTTPS is supported, or point the domain at your host and redirect there instead.
  • Tracking links. Shortened or tracked links in emails and ads can add an HTTP hop. Each insecure hop can show its own warning.
  • Old QR codes. A QR code printed years ago may encode an http:// address. It still works if the redirect is clean, but test it.

The rule from Chrome's guidance is simple: every step in the chain must support HTTPS, not just the final page.

Fix 3: expired or wrong certificates

Certificates expire on a fixed date. If yours renews automatically, it may never be a problem. If someone set it up by hand, or a renewal failed because the domain's DNS moved, the site can go red overnight. Check:

  • The expiry date in the certificate details, and whether it renews automatically.
  • That the certificate names match every address you use, including www.
  • That the domain still points at the server that holds the certificate. Moving hosts without moving the certificate is a common cause.
  • That your domain registration itself isn't about to lapse. An expired domain takes the whole site and email down with it.

This matters more each year. Under rules adopted by the CA/Browser Forum, the industry body for certificates, the maximum life of a public website certificate dropped to 200 days from 15 March 2026. It falls to 100 days from 15 March 2027 and 47 days from 15 March 2029. Renewing by hand once a year is no longer realistic, so automatic renewal plus a monitor that emails you before expiry is the safe setup.

Fix 4: mixed content and insecure forms

A page can be HTTPS and still load some of its parts over HTTP: an image, a font, a script, an embedded map or a form that sends to an http:// address. Chrome has upgraded many passive items such as images to HTTPS automatically since 2020, but anything that can't be upgraded may be blocked or flagged, and an insecure form is the worst case, because it is where people type their name, phone number and enquiry.

To find mixed content, open the page, press F12 to open DevTools and look at the Console for "Mixed Content" messages. Then fix the source: change http:// to https:// in the page or builder, replace embeds whose provider doesn't offer HTTPS, and check form actions and booking widgets. If your form is also getting junk submissions, our guide to stopping contact form spam covers the other half of keeping enquiries clean.

Lock it in so it doesn't come back

Once everything works over HTTPS, two small settings stop the problem returning:

  • HSTS (HTTP Strict Transport Security). A header your server sends to tell browsers to use HTTPS only for your domain. Chrome won't fall back to HTTP on a site with HSTS. Turn it on only after every subdomain you use works over HTTPS, start with a short max-age and increase it later, because a mistake is hard to undo for visitors who already have it.
  • Monitoring. An uptime or certificate monitor that checks the site daily and emails you before the certificate expires. It costs little or nothing and catches failed renewals before customers do.

If you have a website care plan, ask whether certificate renewal and expiry alerts are part of it. They should be.

Example: a plumber with two domains

Here is a typical case. It is an illustration, not a real client. A plumbing business has its main site at https://www.example-plumbing.com, which works fine. Years ago the owner also bought a shorter domain for the van livery and set it to forward at the registrar. The vans, the flyers and the Google Business Profile all use the short domain.

Since Chrome 154, everyone who types the van address or scans the flyer QR code sees a warning first, because the registrar's forwarding runs over HTTP. The main site never shows a problem, so the owner has no idea. The fix takes under an hour: point the short domain at the same host, issue a certificate for it, add a single 301 redirect to the main HTTPS site, update the profile link, and test the van address, the QR code and the profile link in Chrome with the setting turned on.

HTTPS checklist

  • All four versions (http/https, with/without www) land on one HTTPS address
  • No warning appears with "Always use secure connections" turned on
  • Certificate covers every domain and subdomain you use
  • Certificate renews automatically, and someone gets an email before it expires
  • Every extra or old domain redirects over HTTPS, not registrar HTTP forwarding
  • No "Mixed Content" messages in the Console on key pages
  • Contact, quote and booking forms submit to https:// addresses
  • Google Business Profile, social bios, email signatures and QR codes use https://
  • Sitemap, canonical tags and internal links use https://
  • HSTS switched on once everything above is done

FAQ

Why does Chrome show a warning before opening my website?

Since Chrome 154 in October 2026, Chrome tries HTTPS first and asks permission before connecting to a public site over plain HTTP. If your site, or a redirect on the way to it, doesn't support HTTPS, visitors see that warning.

Is my website hacked if it says "Not secure"?

Not usually. "Not secure" and the new HTTP warning mean the connection isn't encrypted, not that the site has been broken into. If you also see spam pages, strange redirects or a Google security warning, follow our hacked website recovery plan.

Do I have to pay for an SSL certificate?

Usually not. Many certificate authorities issue free certificates, and most modern hosting includes free SSL you can switch on. Paid certificates exist for specific needs, but a typical small business website doesn't need one.

Will switching to HTTPS hurt my Google rankings?

A clean move with permanent redirects shouldn't. Google treats HTTPS as a positive signal. Expect some movement for a few weeks while Google recrawls, and keep the redirects in place permanently.

My site uses HTTPS. Why do some visitors still see a warning?

Most often an old domain, the version without www, or a tracking link redirects over HTTP before reaching your site. Test every address and link you use with the Chrome setting turned on.

Can my customers just turn the warning off?

They can, in Chrome's security settings, but you shouldn't rely on it. Most people won't, and a warning in front of a business they don't know yet is a reason to leave.

Next step

If your site shows a warning and you don't know where to start, or nobody remembers who set it up, we can help. Aurel Digital builds and fixes fast, secure small business websites and landing pages with HTTPS on every address, clean redirects and forms tested on real phones before launch. New sites start from $300 with a fixed quote.

Want a second pair of eyes? Send us your web address or email James at james@aureldigitals.com, and we'll tell you what's triggering the warning and what it takes to fix it.

Related: Locked out of your website?, Why is my website slow?, Website not showing on Google?, Website redesign checklist

About the author: James is the founder of Aurel Digital, a remote studio founded in 2026 that builds websites, stores and apps for brands, nonprofits and service businesses. More about James and Aurel Digital.

Work Contact Call