Site Still on HTTP? Chrome Now Stops Visitors at the Door: What Is an SSL Certificate? — post content
A new customer opens your website for the first time and Chrome stops them with a full-page prompt asking permission to continue. Some click “Continue.” Some go back. If your site still runs on plain HTTP, that is now the normal experience. An SSL certificate (technically TLS, though everyone says SSL) encrypts the connection between the visitor’s browser and your server and puts https at the start of your address. Without one, Chrome no longer opens your site without asking the visitor first.
What exactly did Chrome change in October 2026?
On 28 October 2025, Google announced that the “Always Use Secure Connections” setting would become the default in October 2026 (Chrome 154). A Chrome blog post dated 21 October 2026 says the protection has now been extended to all users by default. The logic: Chrome tries HTTPS first and warns only if it isn’t available.
The details matter for a business owner:
- Chrome asks the user to approve HTTP the first time they visit a site. If the site isn’t visited for at least two weeks after approval, the prompt returns.
- It applies to public sites. Single-label hostnames like intranet and local IPs like 192.168.0.1 are exempt.
- The user can still continue, so your site isn’t blocked. But the warning tests a first-time visitor’s trust at the front door.
According to Google’s early rollout data, nearly 95% of Chrome desktop users don’t see any HTTP warning in a given week. The web has already moved to HTTPS; the site left behind is the one that looks neglected.
What does a site without SSL cost you?
Three things, and none of them is technical.
- First impression: A visitor arriving from an ad, a map listing or a business card meets a warning and leaves before finding your phone number.
- Form trust: Quote, booking and contact forms sent over HTTP aren’t encrypted. Names, phone numbers and emails travel unprotected.
- Perceived professionalism: For a business site, https is now the default expectation, not an extra.
Check in two minutes whether your site is HTTP or HTTPS
- Open a private window and visit your site with https:// at the start of the address.
- If it loads without a warning, a certificate is installed. If you get an error, it is missing or expired.
- Now try http://. If it doesn’t redirect to https, your redirect is missing and Google may treat the two addresses as separate sites.
- If images or fonts fail to load, or the address bar shows a warning instead of a padlock, you have a mixed content problem: the page is https but some files it calls are http.
How to install an SSL certificate, step by step
- Activate the certificate. Most hosting companies offer free certificates in the control panel (cPanel, Plesk or their own), usually based on Let’s Encrypt. Find the SSL/TLS or Security section and enable it for your domain. If you can’t find it, ask hosting support.
- Update your site address. In WordPress, change both addresses under Settings → General to start with https.
- Redirect all traffic to HTTPS with a permanent (301) redirect, via the panel’s HTTPS option or a redirect rule.
- Clean up mixed content. Fix http image links in old posts and http calls in theme or plugin files. The browser’s developer console tells you which file is the culprit.
- Update Google. Add the https property in Search Console, resubmit your sitemap, and update the address in Analytics and ad accounts.
For official information about the free option, see Let’s Encrypt’s About page.
Is paid SSL worth it?
For most business brochure sites, blogs and service sites with a quote form, a free certificate is enough: the same padlock and the same level of encryption. Paid certificates make sense when you need organization-validated (OV/EV) certificates, a tender or corporate requirement demands one, you want a warranty and support package, or you must cover many subdomains with one wildcard certificate.
Free or paid, the real risk is expiry. An expired certificate looks worse than none: visitors get a full-page error. Make sure auto-renewal is on and set a calendar reminder.
Certificate installed, still not working? The 5 usual causes
- Mixed content: One http image is enough to break the padlock.
- Redirect loop: If both hosting and a plugin redirect, you get a “too many redirects” error. Turn one off.
- Cache: Browser or site cache may show the old version. Test in a private window after clearing the cache.
- www vs non-www: If the certificate covers only one, the other throws an error.
- Expired certificate: Renewal failed; renew it manually from the panel.
Frequently asked questions
What is an SSL certificate and what does it do?
It encrypts data between browser and server and verifies the site’s identity. The address starts with https and form data can’t be read by third parties.
Is SSL free?
Yes, many hosting panels offer a free certificate. Paid options are mostly for organization validation, warranty or many subdomains.
Does Chrome still open HTTP sites?
Yes, but it now asks users for approval on their first visit to a public HTTP site, and some visitors may give up at that point.
Does installing SSL affect SEO?
With correct redirects, it causes no problem. Wrong redirects or mixed content can make Google see two separate addresses, so don’t skip the redirect and Search Console steps.
In short
Chrome now warns on first visits to public HTTP sites. Serving your site over https, 301-redirecting http to it, cleaning mixed content and automating certificate renewal takes the warning away. Skipping it risks losing trust at the first impression.