Skip to content
6 min read

SSL Certificate for Your Website: How to Choose and Install

An SSL certificate for your website is not decoration for the address bar: without one, the browser tells every visitor 'Not secure' in plain words. That warning scares people off before the first screen loads, and for a shop or a lead form it costs real money. Below: what the certificate does, which one to pick, how to install it and how to verify the result.

Why you need an SSL certificate for your website

SSL (strictly speaking, modern TLS) encrypts the channel between the visitor's browser and your server. Without it, everything typed into a form, whether a name, phone number, comment or password, travels the network in clear text and can be intercepted at any hop, including public Wi-Fi in a shopping mall.

The second effect is proof that the visitor opened your actual domain and not a spoofed copy. For an online shop taking payments through Payme or Click, HTTPS is a hard requirement: payment services will not connect a site that runs over plain http.

The third is search engines and browsers. Google has long used HTTPS as a ranking signal, a small one, and Chrome flags http pages as not secure. A site without a certificate loses on trust both in search results and on screen.

Free or paid: which certificate to choose

For protection there is no difference: a free Let's Encrypt certificate and a paid one encrypt identically. What differs is how the owner is verified. DV only confirms control of the domain and is issued in minutes. OV also checks the legal entity, and EV is an even stricter company check; getting these takes a few days at minimum.

DV is enough for a service site, landing page, blog and most shops. Let's Encrypt is issued automatically, lasts 90 days and renews by script. OV and EV make sense for banks, insurers and financial services, where a verifiable link between domain and company matters. Paid certificates cost roughly 150,000 to 3,000,000 UZS per year depending on type and term. Treat that as a rough guide and check the exact price with the seller.

A separate case is a wildcard certificate covering all subdomains (*.site.uz). Let's Encrypt issues it when you confirm ownership through DNS, which is more convenient than a separate certificate for each subdomain if you have many.

How to install HTTPS step by step

Step 1: check that the domain points to your server, meaning the DNS A record holds the right IP and not the old host. Step 2: in the hosting panel open the SSL or Security section and enable Let's Encrypt for the domain and its www version. Step 3: on a VPS, issue the certificate with certbot or the web server's built-in mechanism (Caddy, for example, does it on its own).

If the site sits behind Cloudflare, set the encryption mode to Full (strict) and install a certificate on the origin server. Flexible mode encrypts only the leg up to Cloudflare, while traffic to your server stays open, so the protection is cosmetic.

Step 4: open the site over https and click the padlock. Check that the certificate was issued for your domain and that its expiry date is in the future. Then run the domain through SSL Labs: the free test shows TLS versions, the certificate chain and typical configuration errors.

What to configure after issuing: redirects and SEO

The certificate alone does not move the site to https. Set up a permanent 301 redirect so that http, and the www and non-www variants, all lead to one canonical https address. Otherwise you end up with four versions of the site and the search engine splits ranking weight between them.

Then update internal links, canonical tags, sitemap.xml and robots.txt, add the https property to Google Search Console and make sure analytics and ad accounts use the new address. Enable the HSTS header once you are sure the entire site works over https without errors.

Why 'not secure' still shows with a valid certificate

The most common cause is mixed content: the page is served over https while images, fonts or scripts are linked over http. Open the browser console (F12), find the Mixed Content warnings and replace the links in the template, widgets and database with https.

The second cause is an expired certificate or auto-renewal that broke after a migration or DNS change. The third is a name mismatch (issued for site.uz but opened as www.site.uz) or a missing intermediate chain. The fourth, a rare one, is a wrong date on the visitor's device.

Set an expiry alert in any monitoring service two to three weeks before the date, and check auto-renewal after every server move.

FAQ

How long does it take to install SSL? A free DV certificate takes a few minutes when DNS is correct; OV and EV require document checks and take from a few days.

Does a brochure site without forms need SSL? Yes: the browser will still show 'Not secure', and search engines prefer the https version.

Can one certificate serve several sites? Yes, a multi-domain (SAN) or wildcard certificate covers several names, but if it leaks, the risk hits all those sites at once.

Will rankings drop after moving to https? With correct 301 redirects and updated links the move normally goes smoothly, and any losses are usually temporary; Google may need a few weeks to reindex the pages.

If you need help

When we build a website turnkey at 4 Digital (from 1,399,000 UZS), HTTPS, redirects and the certificate check are done at launch, so the site opens without warnings.

Need a website or ads? Let’s discuss your project.

Turnkey Website Development + CRM · от 2 399000 сум

We reply within 15 minutes during business hours. No spam.