Chrome now defaults to HTTPS: with Oeuvria, your site won't trigger the warning — here's why

What Google announced

• Chrome now tries every connection over HTTPS. If a public site doesn't support it, Chrome asks the visitor for permission before the first visit.
• The change first reached Enhanced Safe Browsing users (Chrome 147, April 2026), and becomes the default for everyone with Chrome 154.
• The warning can be bypassed, and Chrome doesn't repeat it for a site the user visits regularly: it mostly targets new or rarely visited sites — exactly the situation of a prospect discovering you.
• Private sites (local IP addresses, intranets) are not affected.

Google says that in its tests the warning appears on well under 3% of navigations: most of the web is already on HTTPS. Google also recommends fixing sites that only use HTTP to redirect to HTTPS, since those once-invisible redirects now become visible. Source: Chrome Security Team, "HTTPS by default", October 28, 2025.

What it means for a small business

The risk isn't technical, it's commercial: a customer clicking your Google listing, a shared link or an old business card with an http:// address may land on a "not secure" screen before even seeing your offer. Many won't click "continue". The most exposed sites are often the ones nobody has touched in years: expired certificate, contact page still on HTTP, old address with no redirect.

How Oeuvria makes sure your visitors never see the warning

• HTTPS everywhere from launch: any http:// address is permanently redirected to https:// — which is what oeuvria.com does today.
• HSTS enabled: the browser is told to always use HTTPS for the domain and its subdomains, with no detour through HTTP.
• The HTTPS check is part of our free audit: the tool verifies that the final page is on HTTPS and that the http:// address redirects properly; missing HTTPS counts as a critical issue.
• Continuous tracking of Chrome and Google changes, applied first to our own site, then to our clients'.

Why Oeuvria? Because a site isn't "delivered" when it looks good: it is when it's secure, findable, and no warning screen stands between you and your customers. We follow these changes as they happen and we apply them — no vague promises, concrete checks.

Check your site for free

FAQ

Will my site show a warning in Chrome?

Only if it can be reached over HTTP without going to HTTPS. With Chrome 154, Chrome asks for confirmation before the first visit to a public site without HTTPS. If your site is on HTTPS and the http:// address redirects to https://, your visitors see nothing.

How do I know if my site is on HTTPS?

Type your address starting with http:// in Chrome: you should land automatically on the https:// version, with no alert. Our free audit also runs this check for you.

What if my site isn't on HTTPS?

Install an SSL/TLS certificate (often included by your host), redirect every http:// address to https:// and fix internal links and resources still on http://. If your site is old, it's also a good time to check the rest: speed, mobile and search visibility.