WhatsApp
Chat on WhatsApp

SSL Certificates and HTTPS: A Guide for Business Websites

When someone lands on your website, they want two reassurances: that they are on the real site, and that nobody else can read what they type into your forms. An SSL certificate provides both. Without one, the browser labels your site "Not secure", some visitors leave before reading a single line, and every form on the page sends its data across the internet in plain text.

The good news is that a basic certificate is now free, and on platforms such as Webflow and Wix it is switched on almost automatically. The less good news is that we still regularly see business websites with expired certificates, "mixed content" warnings after a hosting move, or configurations that only encrypt half of the journey between the visitor and the server.

In this guide we cover:

  • what an SSL certificate is and how SSL differs from TLS;
  • how an HTTPS connection works, step by step;
  • why every business website needs HTTPS, even without an online shop;
  • which types of certificate exist and when a paid one makes sense;
  • how to set up a certificate on Webflow, Wix, WordPress and behind Cloudflare;
  • how to move from HTTP to HTTPS without losing search traffic, and which mistakes to avoid.

What an SSL certificate is and how SSL differs from TLS

An SSL certificate is a small digital file installed on the server that hosts your website. It does two jobs. First, it makes an encrypted connection possible between the visitor's browser and your server, so that nobody along the way can read or alter the data. Second, it proves to the browser that the server really belongs to the domain the visitor typed, and not to an impostor.

The name SSL (Secure Sockets Layer) is historical. The original protocol was developed in the 1990s, and all of its versions are now considered insecure and are disabled in every modern browser. It was replaced by TLS (Transport Layer Security), and the versions in use today are TLS 1.2 and TLS 1.3. Even so, the market still says "SSL certificate", and so will we in this guide. Technically, what you install is an X.509 certificate used for TLS connections.

What a certificate contains

If you click the icon to the left of the address bar in your browser and open the certificate details, you will see roughly the following information:

  • the domain name (and sometimes several domains and subdomains) that the certificate covers;
  • who issued it, that is, the Certificate Authority (CA);
  • the date of issue and the expiry date;
  • the server's public key;
  • the digital signature of the Certificate Authority;
  • for OV and EV certificates, the name and country of the organisation as well.
A glossy glass padlock between a browser window and a server, with glowing locked data cubes moving through a transparent glass tube that connects them
An SSL certificate lets the browser and the server talk over an encrypted channel. Illustration: RJL Studio

How an HTTPS connection works

HTTPS is the same HTTP protocol that browsers use to request pages from a server, except that it travels inside an encrypted TLS "tunnel". The S at the end stands for Secure.

When a visitor opens an address that starts with https://, the browser and the server perform a "TLS handshake". In simplified form it looks like this:

1. The browser contacts the server and lists the TLS versions and encryption methods it supports.

2. The server replies, picks a method both sides support and sends its certificate.

3. The browser checks the certificate: that it belongs to this domain, that it has not expired, and that it is signed by a Certificate Authority the browser or operating system trusts.

4. The browser and the server jointly work out a one-time encryption key for this session, without ever sending that key across the network.

5. From this point on, everything is encrypted, including page addresses, cookies and whatever the visitor types into forms.

The whole process takes milliseconds. With TLS 1.3 the handshake is even shorter than before, so encryption has long stopped being an excuse for a slow website. If speed matters to you, read our guide to content delivery networks as well: a CDN shortens the distance between the visitor and the server and can handle encryption at the same time.

What happens when something is wrong

If the certificate has expired, belongs to a different domain or is signed by an authority the browser does not recognise, the visitor sees a full-page warning instead of your website. Most people will not click "Proceed anyway", and they are right not to. For your business, it is the equivalent of a "Closed" sign on the front door.

Why every business website needs HTTPS

Some business owners still believe HTTPS is only necessary for online shops. That is a mistake, for several reasons.

Visitor trust

Chrome, Safari, Firefox and Edge mark HTTP sites as "Not secure", and on forms served over HTTP the browser adds a warning right next to the fields. A visitor who sees that next to your contact form will think twice before leaving a phone number. Google has also announced a gradual move in Chrome towards asking visitors for confirmation before opening public websites over plain HTTP.

Data protection

Even a simple brochure website collects personal data: names, phone numbers, email addresses, and sometimes CVs or photos. On public Wi-Fi in a café, a hotel or an airport, an attacker on the same network can read anything that travels unencrypted. On top of that, logging into your website's admin panel without HTTPS exposes the administrator's password.

Search visibility

Google announced back in 2014 that HTTPS is a ranking signal. It is a light signal, but in a close race it is not irrelevant. More importantly, a site that shows security warnings loses clicks, and visitors who bounce straight back to the search results are a bad sign. Beyond rankings, many modern browser features, such as HTTP/2 and HTTP/3, service workers and geolocation, in practice only work on secure sites.

Law and regulation

In the European Union, the GDPR requires any organisation that processes personal data to apply appropriate technical and organisational security measures, and encryption is explicitly named as one of them. Data protection authorities across Europe can impose significant fines when personal data is poorly protected. Encrypting the data that travels between your website and your server is the baseline: without it, it is hard to argue that your measures were appropriate. And if your website takes card payments, the PCI DSS standard set by the card industry requires cardholder data to be transmitted in encrypted form. This is general information, not legal advice; for your specific obligations, speak to a qualified data protection adviser.

A glossy glass shield above a browser window with an abstract form, surrounded by a floating padlock, a key and a glowing rating star
HTTPS means trust, protected data and a basic requirement for search visibility. Illustration: RJL Studio

Types of SSL certificates

Certificates differ in two ways: who signed them, and what exactly was checked before they were issued.

Self-signed certificates vs certificates from a Certificate Authority

You can create a self-signed certificate on a server in under a minute, but no browser will trust it, and visitors will see a full warning page. It is only suitable for internal development environments. A public website needs a certificate issued by a recognised Certificate Authority, such as Let's Encrypt, Google Trust Services, DigiCert, Sectigo or GlobalSign.

Validation levels: DV, OV and EV

  • DV (Domain Validation). The authority only checks that you control the domain, for example through a DNS record or a file placed on the server. Issuance is automated and takes minutes. This is the most common type of certificate on the internet, and free certificates are of this type.
  • OV (Organization Validation). In addition to the domain, the authority checks that the organisation actually exists, based on official registration documents. The company name appears in the certificate details.
  • EV (Extended Validation). A more thorough check of the organisation. Browsers used to show the company name in a green bar next to the address, but they stopped doing so years ago, and today the name only appears if you open the certificate details.

The key point: the encryption itself is identical at all three levels. An EV certificate does not encrypt "more strongly" than a DV certificate. The only difference is how much verified information about the owner is included in the certificate.

How many domains a certificate covers

  • Single domain. For example, example.com and www.example.com.
  • Wildcard. All subdomains at one level: *.example.com, which covers shop, blog, app and so on.
  • SAN or multi-domain. A list of several different domains in a single certificate, for example an English website and a Portuguese website that live on separate domains.
Three glass certificates floating side by side, each with a round seal and a different number of coloured ribbons, with a magnifying glass examining the middle one
DV, OV and EV encrypt at the same level and differ in how the owner is verified. Illustration: RJL Studio

Free vs paid SSL certificates

For most business websites, including company sites, landing pages, blogs and many online shops, a free DV certificate is entirely sufficient. Let's Encrypt is a non-profit Certificate Authority that issues these certificates at no cost, and modern browsers trust them exactly as much as paid ones. Cloudflare, Webflow, Wix and most hosting providers also include a certificate as part of their service.

When paying makes sense

  • You need an OV or EV certificate because of a requirement from a corporate or public-sector client, a tender, a bank or your own internal policy.
  • A system does not support automatic renewal, such as an older server or network appliance, where a manually managed certificate is the only practical option.
  • You need support and a warranty from the certificate provider, for example in a large organisation with many domains.

Certificate lifetimes are getting shorter

The CA/Browser Forum, the body that sets the rules for Certificate Authorities and browsers, has decided to reduce the maximum lifetime of certificates step by step. Since March 2026 the maximum is 200 days; from March 2027 it drops to 100 days, and from March 2029 to 47 days. Let's Encrypt certificates are already valid for only 90 days.

The practical consequence: the era of "buy a certificate for a year and install it by hand" is over. Every certificate needs to renew automatically, through ACME (the protocol used by Let's Encrypt and most other providers), through your hosting company, or through a platform such as Webflow. Anyone still replacing certificates manually will run into trouble several times a year.

How to install an SSL certificate

The process depends on the platform your website is built on.

Webflow

When you connect your own domain to a Webflow site, the platform issues and renews the certificate for you. All you need to do is set up the DNS records correctly, following the instructions in the site settings, and make sure the SSL option is enabled in the hosting settings. If your domain is routed through Cloudflare, follow Webflow's guidance on the proxy mode carefully.

Wix

On Wix, the certificate is activated automatically for every site with a connected domain, and HTTPS is on by default. If your domain is managed by an external registrar, make sure the DNS records point to Wix exactly as Wix instructs. Otherwise the certificate will not be issued.

WordPress

With WordPress, everything depends on your hosting. Most hosting providers offer a free Let's Encrypt certificate with one click in the control panel, with automatic renewal. After installation you need to:

1. change the site addresses in the General Settings from http to https;

2. set up a 301 redirect from every HTTP address to its HTTPS equivalent;

3. fix links and images that still load over http (more on "mixed content" below).

Plugins such as Really Simple Security handle some of these steps, but it is better to configure redirects at server level rather than rely on a plugin alone.

Websites behind Cloudflare

Cloudflare gives you a free certificate at the "edge" of its network, that is, between the visitor and Cloudflare's servers. But there is a second leg of the journey: between Cloudflare and your own server. In Flexible mode that leg runs over unencrypted HTTP, and the browser shows a padlock even though the connection is not encrypted end to end. The correct setting is Full (strict), with a valid certificate on your origin server as well. To understand how your domain, DNS records and server fit together, read our guide to DNS.

Four floating glass platforms, each holding a different website window, with a glowing padlock above them connected to all four by lines of light
Every platform handles setup differently, but the principle is the same: a valid certificate and automatic renewal. Illustration: RJL Studio

Moving from HTTP to HTTPS without losing traffic

As far as Google is concerned, http://example.com and https://example.com are two different addresses. If you switch without a plan, you can lose rankings, break links and trigger warnings. Here is the order of work.

Step 1: Install the certificate and test it

Before changing anything else, make sure the site opens over https:// without warnings, both with and without www. You can check the configuration with the free SSL Server Test from Qualys SSL Labs: it shows the TLS versions in use, the certificate chain and common problems.

Step 2: Set up 301 redirects

Every HTTP address should redirect permanently (301) to its matching HTTPS address, one to one. Not to the home page, and not through a chain of several redirects.

Step 3: Fix mixed content

"Mixed content" is when the page itself loads over HTTPS, but an image, script or font inside it loads over http://. The browser blocks some of these files or shows a warning. You can spot them in the browser's developer tools (the Console tab) and fix the addresses in your content, templates and any embedded code.

Step 4: Update everything around the site

  • internal links and canonical URLs;
  • the sitemap (sitemap.xml) and the robots.txt file;
  • a Google Search Console property for the HTTPS version (a Domain property covers both);
  • the website address in Google Analytics, your Google Business Profile, social media profiles and ad campaigns;
  • webhooks and connections to external systems, such as your CRM or payment provider, that still point to the old address.

Step 5: Enable HSTS

HSTS is a response header that tells the browser: "always open this site over HTTPS only". It prevents attempts to downgrade the connection to HTTP. Only switch it on after you have confirmed that the entire site, including subdomains, works over HTTPS, and start with a short max-age.

After the migration, keep an eye on the indexing reports in Search Console for a few weeks. For a complete technical review of your website, see our technical SEO audit guide.

A glowing glass arrow leading from an open browser window with a cracked padlock to a browser window with a closed, shiny padlock, with small pages and redirect lines floating along it
A proper move to HTTPS: certificate, 301 redirects, mixed content fixes and updated tools. Illustration: RJL Studio

Common SSL certificate mistakes

A certificate that expires without anyone noticing

This is the most common failure. Automatic renewal fails silently, for example after a DNS change or a hosting move, and the site shows a warning until a customer calls to tell you. The fix is external monitoring that checks the expiry date and alerts you in advance. Do not rely on reminder emails from your certificate provider.

A certificate that does not cover every address

The certificate covers example.com but not www.example.com, or the other way round. A visitor who types the other version gets a warning. Test both versions and every subdomain you actually use.

A padlock that does not encrypt end to end

Cloudflare's Flexible mode, or any other proxy that talks to your server over HTTP. The visitor sees a secure connection, but the data travels in plain text on the second leg of the journey.

Moving to HTTPS without redirects

The site opens over both HTTP and HTTPS, and both versions get indexed. Google sees duplicate content, and the authority of your links is split between them.

Assuming the padlock means the site is trustworthy

Anyone can get a DV certificate for free in minutes, which is why phishing sites use them too. HTTPS guarantees that the connection is encrypted and that you are talking to the domain in the address bar, nothing more. It does not replace software updates, strong passwords, two-factor authentication and backups.

Sending the private key by email

The certificate's private key is a secret. If it has been sent over chat or email to a freelancer, a supplier or an employee, assume it has leaked. In that case, revoke the certificate and issue a new one with a new key.

A short checklist for website owners

  • the site opens over https:// with and without www, with no warnings;
  • every HTTP address redirects with a 301 to its HTTPS equivalent;
  • there are no mixed content warnings on key pages and forms;
  • the certificate renews automatically, and monitoring alerts you before it expires;
  • behind Cloudflare, the SSL mode is set to Full (strict);
  • Search Console has a property that covers the HTTPS version;
  • you know where your domain, DNS and certificate are managed, and who has access.

How RJL Studio keeps your website secure

At RJL Studio we build and maintain websites on Webflow, WordPress and Wix, and every site we launch goes live with HTTPS configured properly: a certificate that renews automatically, 301 redirects, no mixed content, and tidy DNS and Cloudflare settings. When you move hosting or switch platforms, we plan the redirect map, test every form and integration, and update Search Console, so your website does not lose traffic along the way.

Want to check that your website is set up correctly, or move to a new platform without surprises? Read about our Webflow website development and our SEO services, or get in touch and we will get back to you.

Frequently asked questions

Is a free SSL certificate good enough for a business website?

For most websites, yes. A free DV certificate, for example from Let's Encrypt, encrypts traffic exactly as well as a paid one, and browsers trust it to the same degree. A paid certificate is mainly needed when you require organisation validation (OV or EV) or commercial support from the provider.

What is the difference between SSL and TLS?

SSL is the name of the old protocol, and all of its versions are now disabled in every browser. Today, secure connections run on TLS 1.2 or TLS 1.3. The name "SSL certificate" has stuck for historical reasons, but in practice it is the same certificate.

How often does a certificate need to be renewed?

Let's Encrypt certificates are valid for 90 days, and the maximum lifetime of certificates in general is shrinking step by step: 200 days from 2026, 100 days from 2027 and 47 days from 2029. That is why renewal must be automatic, ideally with monitoring that alerts you before a certificate expires.

Why does my browser say "Not secure" even though I have a certificate?

The usual causes are mixed content (images or scripts loading over http://), an expired certificate, a certificate that does not cover the www or non-www version, or an address that opens over HTTP because there is no redirect to HTTPS. Your browser's developer tools and the SSL Labs test will show you where the problem is.

Does moving to HTTPS hurt my Google rankings?

Not if you do it properly: one-to-one 301 redirects, updated internal links and sitemap, and the right property in Search Console. You may see small fluctuations in the first few weeks while Google updates its index. In the long run, HTTPS is an advantage, not a drawback.

Disclaimer: blog content is for general information and learning only and is accurate as of its publication date. It is not professional, legal, financial or business advice, nor a recommendation or call to take any action. Any use of this information is at the reader's own risk, and we accept no liability for any resulting loss. Links to external websites and tools are provided for convenience only. We recommend consulting a qualified professional before making decisions.