New

The new HostCloud is live. Web Hosting for ₹1 for your first month.

Web Hosting for ₹1 · first month

Claim offerClaim
Security

Chrome now warns before opening HTTP sites: what "Always Use Secure Connections" means for your website

From Chrome 154 (October 2026) Chrome asks visitors to confirm before loading a public HTTP page. Here is what changes, who sees the warning and how to fix your site.

13 November 2026 · 8 min read
Chrome now warns before opening HTTP sites: what "Always Use Secure Connections" means for your website

Chrome now warns before opening HTTP sites: what "Always Use Secure Connections" means for your website

TL;DR: Google's schedule is: Chrome 147 (April 2026) turned on "Always Use Secure Connections" for Enhanced Safe Browsing users, and Chrome 154 (October 2026) turns it on for everyone. When a visitor goes to a public site that does not use HTTPS, Chrome shows a warning they must click through before the first visit. Private and local addresses are excluded. If your site is on HTTPS with a valid certificate and your old HTTP URLs redirect, visitors will not notice. If not, some will turn back.

What Chrome is doing

According to Google's Chrome security team, the setting "Always Use Secure Connections" has a public-sites variant that:

  • Was enabled in Chrome 147 (April 2026) for users with Enhanced Safe Browsing.
  • Is enabled by default for all users in Chrome 154 (October 2026).
  • Shows a warning before the first visit to a public site that does not use HTTPS. The user can click through.
  • Does not repeat the warning for a site the user visits regularly.
  • Excludes private sites such as local IP addresses, single-label hostnames and intranet shortlinks.

In a Chrome 141 experiment Google reported that the median user saw fewer than one warning a week. Users can also disable the setting in Chrome's security settings.

Timeline of Chrome's HTTPS warning: Chrome 147 for Enhanced Safe Browsing users in April 2026 and Chrome 154 for everyone in October 2026

Who is affected

Any public website that still serves content over HTTP, including:

  • Old sites that never installed a certificate
  • Subdomains that were skipped, such as old., staging. or blog.
  • Links in emails, QR codes and printed material that use http://
  • Sites where HTTP does not redirect to HTTPS
  • Pages loaded in iframes or embedded from HTTP sources

If your HTTP address already redirects to HTTPS, Chrome upgrades the navigation, so most visitors see nothing.

How to check your site

  1. Open http://yourdomain.com in a private window. It should redirect to https:// in one step.
  2. Test www and non-www, and every subdomain.
  3. Run a crawl for links that start with http://.
  4. Look for mixed content (HTTPS pages loading HTTP files) in the browser's console.
  5. Check that the certificate is valid and not close to expiry. See how to monitor SSL expiry.

How to fix it

What if you have an old HTTP-only site?

Do not leave it. Search engines already prefer HTTPS, and Chrome's warning adds friction. If a legacy page cannot move, put a reverse proxy or CDN in front that terminates HTTPS. See what a CDN does.

Internal and local sites

Intranet pages and local IP addresses are excluded from the default, though users may choose to include them. Google notes that Chrome's local network access permission lets an HTTPS page reach local devices once the user allows it.

FAQs

When does Chrome warn about HTTP sites?

Google says Chrome 154 (October 2026) enables the setting by default for all users, after an earlier rollout in Chrome 147 to Enhanced Safe Browsing users.

Will Chrome block HTTP sites completely?

No. It shows a warning that users can bypass before the first visit.

Does this affect sites that redirect to HTTPS?

Mostly not, because the navigation is upgraded.

Are local and private sites affected?

No, private sites are excluded by default.

Can users turn it off?

Yes, in Chrome's security settings.

Will this affect SEO?

HTTPS is already expected. The warning mainly affects visitors who reach your HTTP URLs.

Crawl the site, search the database for http:// and check the browser console for mixed content.

Do I need to buy a certificate?

Not necessarily. A free, valid certificate is enough.

Conclusion

The change is small if your site is already on HTTPS and redirects cleanly. Use it as a deadline to find forgotten HTTP subdomains, hard-coded links and mixed content, then add HSTS once everything works.

HostCloud helps Indian websites with reliable hosting, domains and support. See the options at https://hostcloud.in.

Sources:

Related posts