SSL Certificate for Your Website: Moving to HTTPS Properly
What an SSL certificate does, which type you need, how to switch to HTTPS without mixed content errors, and how to make sure renewals never lapse.
Published 10 min read
A visitor opens your company website and the browser tells them the page is “Not secure”. Most people close the tab without reading further. An SSL certificate fixes that, but only if it’s installed correctly, covers every address the site uses and renews on time. Below you’ll find what the certificate actually does, which type you need, how to move your site to HTTPS step by step, and the mistakes that quietly break everything a few months later.
What an SSL certificate actually does
When someone opens https://company.ro, the browser and the server set up an encrypted connection. Everything that passes through it, from the password for your admin panel to the phone number typed into the contact form, can no longer be read in transit. Without HTTPS, anyone who controls the network the traffic crosses (public Wi-Fi, a compromised router) can see that data in plain text.
The certificate does one more thing: it proves that the server you’ve connected to really does answer for company.ro. Before issuing it, the certificate authority checks that whoever asked for it controls the domain. Browsers carry a list of authorities they trust and only accept certificates signed by them.
Strictly speaking, the right name today is TLS, not SSL. The SSL protocol was replaced a long time ago, but the name stuck in everyday language, in hosting control panels and in providers’ price lists. When you read “SSL certificate”, it means the same thing.
What the certificate doesn’t do is protect your site from being hacked. A WordPress site with an outdated plugin can be compromised just as easily over HTTPS as over HTTP. The padlock shows the connection is encrypted, not that the site is clean. We cover that other side in a separate guide to WordPress security.
Which type of certificate you need
Certificates differ in how much the authority checks before issuing them:
- DV (Domain Validation). The authority only checks that you control the domain, usually through a file placed on the server or a DNS record. It’s issued in minutes. This is what most brochure sites and small online shops use.
- OV (Organisation Validation). The authority also checks that the company exists, using official registers. Company details appear in the certificate, but browsers display it exactly like a DV certificate.
- EV (Extended Validation). A more thorough check of the company. Modern browsers no longer show the old green address bar, so the average visitor can’t tell the difference.
For a small business website, a DV certificate is enough in almost every case. The encryption is identical across all three types. An OV or EV certificate makes sense when a large client, a public tender or an auditor explicitly asks for one.
Depending on how many addresses you need to cover, there are two more useful options:
- Multi-name certificate (SAN). Covers, for example,
company.ro,www.company.roandshop.company.roin one certificate. - Wildcard certificate. Covers every subdomain at one level, in the form
*.company.ro. It’s usually issued with DNS validation.
The free Let’s Encrypt certificate: what you get
Let’s Encrypt is a non-profit authority that issues DV certificates free of charge. Browsers trust them exactly as they trust paid ones. Most hosting control panels, Plesk included, install them in one click and renew them automatically.
Two details matter for a business:
- The lifetime is short. Let’s Encrypt certificates are valid for 90 days. The organisation has announced that it is cutting the default lifetime to 64 days from 10 February 2027 and to 45 days from 16 February 2028, and it says plainly that manual renewal is no longer recommended. In practice, you can’t do without automatic renewal.
- DV only. Let’s Encrypt doesn’t issue OV or EV certificates and has no plans to. If you need one, you buy it from a commercial authority.
The price gap between a free certificate and a paid one has nothing to do with encryption. You’re paying for the company checks (for OV and EV), sometimes a warranty offered by the authority, and support. For a brochure site, the free one does the same job.
How to move your site to HTTPS, step by step
Installing the certificate is only the first step. A site is truly “on HTTPS” only when every page, image and form loads over HTTPS and nobody lands on the old version any more.
- Check that the domain points to the right server. The certificate is only issued if the authority can verify the domain. If you’ve just moved the site, wait for the DNS change to propagate. There’s more on this in our article on DNS explained.
- Issue the certificate for every variant. Include both
company.roandwww.company.ro. If you use subdomains (such asmail.company.roorshop.company.ro), add them too. In Plesk, go to Websites & Domains, then SSL/TLS Certificates, and tick the addresses the certificate should cover. - Turn on a permanent (301) redirect from HTTP to HTTPS. In Plesk, under Hosting Settings, tick the permanent redirect to HTTPS. On other servers it’s done in the
.htaccessfile or the web server configuration. - Pick one main version. Either
https://company.roorhttps://www.company.ro. The other one redirects to it. Otherwise search engines see two identical sites. - Update the address in the application. In WordPress, go to Settings, then General, and change “WordPress Address (URL)” and “Site Address (URL)” to the
https://version. - Replace old links in your content. Images inserted into posts before the switch still have
http://addresses. Replace them with a search-and-replace tool on the database, after a full backup. - Test your forms. Send a message through the contact form and check it arrives. Some form plugins store the site address separately.
Mixed content: why the padlock won’t appear even with a certificate
The most common problem after moving to HTTPS is called mixed content. The page arrives over HTTPS, but an image, script or font still loads over HTTP. Browsers block insecure scripts and stylesheets, and for images they may show a warning or try to upgrade them to HTTPS automatically.
How to find the culprit:
- Open the page in Chrome or Edge.
- Press F12 and go to the Console tab.
- Look for messages containing “Mixed Content”. Each one shows the exact address of the resource loaded over HTTP.
The usual sources are images inserted into posts years ago, a logo set with a full address in the theme settings, an old analytics script, or an embedded map pasted from another site. The fix is to change the address to https:// or, where possible, use relative addresses.
Mistakes that surface a few months later
The certificate works on the day it’s installed. The trouble comes later, usually without any warning.
- Automatic renewal fails. The typical cause is a DNS change: the domain was pointed at a different server, and the old one can no longer validate it. The certificate expires and visitors see a red warning screen.
- The forgotten variant.
wwwworks, butcompany.rowithoutwwwgives a certificate error because it wasn’t included. - The certificate covers the website but not email. Email programs that connect to
mail.company.roshow certificate warnings. Staff get used to clicking “Continue”, which is a dangerous habit. - A paid certificate bought by an agency. The agency no longer works with you, the certificate expires, and nobody has access to the account it was bought from.
One simple fix covers all of these: a calendar with the expiry date of every certificate and a monthly check. Open the site, click the padlock, then the certificate details, and read the “Valid to” date. If it’s less than two weeks away and renewal should have been automatic, something is wrong.
The error messages you’ll come across
Browsers show technical codes that look cryptic but say fairly precisely what happened:
- The certificate has expired (for example
NET::ERR_CERT_DATE_INVALIDin Chrome). Renewal didn’t work. First check that the domain still points to the server issuing the certificate. If the error only shows up on one computer, check that computer’s clock as well: a wrong date makes every certificate look expired. - The name doesn’t match (
NET::ERR_CERT_COMMON_NAME_INVALID). A certificate exists but doesn’t cover the address you opened, usually the version with or withoutwww, or a subdomain. - The authority isn’t trusted (
NET::ERR_CERT_AUTHORITY_INVALID). The server has a self-signed certificate installed, the kind some panels set by default, or the intermediate certificate is missing.
HSTS: the last step, once everything works
A 301 redirect has one small weakness: a visitor’s very first request still goes out over HTTP before it’s sent on to HTTPS. HSTS (HTTP Strict Transport Security) closes that gap. The server sends a header telling the browser “from now on, open this domain over HTTPS only”. The browser remembers the rule for the period specified.
Only turn HSTS on once the site and all its subdomains work smoothly over HTTPS. If you enable it too early and a subdomain has no certificate, visitors who’ve already received the rule won’t be able to open it at all until the rule expires. Start with a short duration, a few days, and increase it once you’ve seen nothing break.
In Plesk, the option sits in the domain’s SSL/TLS settings. On other servers, you add it in the web server configuration.
HTTPS, search engines and customer trust
HTTPS is a ranking signal in search, but a small one. The bigger effect is elsewhere. Browsers flag HTTP pages as not secure, especially pages with forms, and a visitor who sees that warning leaves.
There’s one more detail: many modern browser features, such as location, notifications and some payment methods, only work over HTTPS. A site without a certificate can’t use them at all.
If your site has run on HTTP for years and already gets search traffic, the 301 redirect from step 3 carries the page history across as well. After the move, check that each old address leads to its matching new page, not everything to the home page.
Frequently asked questions
Is a free SSL certificate as secure as a paid one?
Yes, as far as encryption goes. A free DV certificate and a paid DV certificate use the same algorithms and get the same browser trust. The difference lies in what the authority checks before issuing it and in the extra services, not in how well the connection is protected.
What happens if my SSL certificate expires?
The browser shows a full-screen warning telling visitors the connection isn’t private. Most people stop there. Forms, the shop and the admin panel become practically unusable until the certificate is renewed.
Do I need a certificate if my site has no forms or shop?
Yes. Browsers mark any HTTP page as not secure, whatever its content. On top of that, your site’s admin panel has a password, which travels unencrypted every time you log in without HTTPS.
Can I use the same certificate for my website and email?
You can, if the certificate also includes the name your mail server uses, such as mail.company.ro. On many servers, Plesk included, the certificate can be assigned to the mail service too, so email programs stop showing warnings.
How long does it take to issue a certificate?
A DV certificate is usually issued within minutes, provided the domain already points to the server. OV and EV certificates take longer because the authority checks the company’s documents.
If you’re wondering what a hosting package normally includes, what is meant by web hosting gives a short explanation, and how to choose a website host helps you compare offers.
When it’s easier to hand it to a technician
Installing a certificate on hosting with a control panel takes a few minutes. Help is worth it when the site has mixed content that’s hard to track down, when you need to move off HTTP without losing your search positions, or when the certificate has to cover email and several subdomains as well.
On TECH Consult web hosting, SSL certificates are included and renew automatically, and we move your site to HTTPS together with you. If your site is with another provider and you’d like to bring it to us, read our guide to moving a website to a new host first.