SSL certificate installation is the work of getting a certificate issued for each hostname your business uses, putting it on the host, CDN or server that delivers the page, sending visitors to the HTTPS version and checking that nothing on the page still loads insecurely. For many small business websites, the host or CDN does the first two steps and you do the last three.
This guide is for owners of service businesses in the Twin Cities East Metro, the St. Croix Valley and western Wisconsin who need to know who installs what, which certificate to ask for and how to confirm the result. "SSL" is the familiar name. The certificates in use today are TLS certificates, and the installation steps are the same. For what happens after installation, including renewal and shorter lifetimes, see our guide to SSL certificate management.
What SSL certificate installation involves
Whatever route you take, the work follows the same order.
- List every hostname. The main domain, the www version and any subdomain used for a quote form, booking calendar, payment link or customer portal each need to be covered.
- Decide who issues and installs the certificate. Your host, a CDN, your own server or a software vendor.
- Get the certificate. Often automatic. On a server you manage, you or your contractor generate a key and a certificate signing request and send it to a certificate authority, or use an ACME client, a small program that requests and renews certificates.
- Install it. A control panel, a CDN setting or a command on the server.
- Redirect HTTP to HTTPS. So every visitor lands on the secure version.
- Fix mixed content. Remove any image, script or font still loaded over plain HTTP.
- Check the result. Test every hostname, then write down who owns renewal.
The first step is the one that gets skipped. A business that installs a certificate on the main site and never lists the others can find the gap only when a customer reports a warning on the quote form.
Choosing a certificate for your installation
The types differ in what the certificate authority verifies before it issues. DigiCert, a certificate authority, describes them in its comparison of DV, OV and EV certificates. A domain validated certificate only requires validation that a company or person can demonstrate control over a web domain. An organization validated certificate adds a check on the business behind the site, and an extended validation certificate requires verification of the domain owner, the business organization and the legal entity involved.
In our view, the practical choice for a local service business is usually domain validation. Let's Encrypt, a free authority, says in its FAQ that it offers domain validation certificates, that it has no plans to issue organization or extended validation certificates, and that it does not charge a fee for its certificates. It also says wildcard issuance must use the DNS-01 challenge, which matters if you want one certificate to cover many subdomains. A purchased organization validated certificate makes sense only if a customer or contract asks for documented verification of your company details. Extended validation is governed by separate EV Guidelines from the CA/Browser Forum, so ask the authority what it requires before you buy.
Where the certificate gets installed
The right install path depends on where the page is served from.
Scroll to see all columns
| Where the site runs | Who usually installs it | What you do | What to watch |
|---|---|---|---|
| Managed host | The host, often automatically | Confirm HTTPS is on and ask what the certificate covers | Subdomains on other services are usually not included |
| CDN such as Cloudflare | The CDN, once the domain is active | Check which encryption mode is set and turn on the HTTPS redirect | A mode that leaves the origin unencrypted |
| Your own server | You or your contractor with an ACME client | Install the client, request the certificate, test renewal | You need command access and a renewal owner |
| Purchased certificate | You or your contractor, in a control panel or on the server | Generate a request, send it to the authority, install the files | Every step is manual, so someone must own it |
| Vendor tool on your subdomain | The software vendor | Point the DNS record where the vendor says | Ask the vendor in writing who installs and renews |
Managed hosting and your own server
Let's Encrypt's getting started page says many hosting providers get and manage certificates from Let's Encrypt for their customers, and that you should check your provider's documentation to see whether it happens automatically or needs a setting turned on. If you run your own client, it says you need the ability to run commands on your server with sufficient privileges, and it recommends the Certbot client for most people. If you buy a certificate instead, a web.dev guide to enabling HTTPS, last updated in 2015, describes the manual path: generate a key pair, create a certificate signing request, send it to a certificate authority and install the certificate it returns.
Behind a CDN such as Cloudflare
Cloudflare's documentation says its Universal SSL certificates are issued after your domain is active on Cloudflare, with issuance, renewal and deployment handled automatically. Cloudflare's encryption modes page says Automatic SSL/TLS is the default and selects the most secure mode it finds for your origin; the Custom option lets you set Flexible, Full or Full (strict) yourself. Cloudflare says it strongly recommends Full or Full (strict). Flexible leaves the connection from Cloudflare to your server unencrypted.
Redirect HTTP to HTTPS and fix mixed content
Installing the certificate does not move anyone to the secure page. A web.dev guide last updated in 2015 says to use a 301 (Moved Permanently) redirect to tell search engines and browsers that the HTTPS version is canonical, and says Google uses HTTPS as a positive search quality indicator. We treat that as a minor reason; the main one is that forms and booking pages should load without a browser warning.
Where you set the redirect matters. Cloudflare's Always Use HTTPS page says the setting redirects all visitor requests from http to https, and that Cloudflare recommends not performing redirects at your origin server because that can cause redirect loop errors. It also says to leave the setting off if only some parts of your application support HTTPS. One caution from the same 2015 web.dev guide: do not turn on HSTS until you are sure your site's HTTPS setup is reliable, since clients may hard-fail after a TLS configuration error.
Fix mixed content
Mixed content is a secure page that loads something over HTTP. MDN's mixed content page says browsers auto-upgrade image, video and audio requests from HTTP to HTTPS and block insecure requests for all other resource types. Its advice is to serve all content as HTTPS: make references to resources on your domain relative links or HTTPS links, and use HTTPS versions of resources on other sites where available. Cloudflare's page adds that forcing HTTPS does not fix mixed content by itself.
Look in the places a site editor forgets: old images pasted into pages, embedded maps and videos, a form action that still points at an http address, a chat or review widget copied from an old snippet and fonts loaded from a stylesheet.
Check the result before you call it done
- Test every hostname. Open the main domain, the www version and each subdomain in a browser and look for a warning page.
- Type the http:// address. It should land on the https:// page in one step.
- Submit the forms. Send a test quote request and a test booking, and click each payment link.
- Check the console. A browser's developer tools list mixed content errors for the page you are on.
- Test on a phone. Layouts and embedded widgets can behave differently there.
- Record the owner. For each hostname, note who installed it, who renews it and who gets the alert.
Where local service businesses get caught
In our experience the main site is usually fine and the trouble is often the other hostnames. Consider an illustrative example. Larkspur Lane Plumbing is an invented company based in Woodbury. Its website is on a managed host with HTTPS on, its quote form runs at quotes.larkspurlane.example on a vendor's software, and its payment link lives on the payment processor's own domain. The owner thinks of one certificate. Three hostnames exist, each installed and renewed by a different party, and a lapse on any of them breaks a step the customer takes when ready to hire.
Booking, quote and review tools are common on subdomains, and a certificate on that subdomain may be issued and renewed by the vendor, depending on how you connected the tool. That is why the first step in the list is an inventory, and why the inventory needs to be redone after a redesign or a move to a new host. Our guide to protecting your website from hacks places certificates among the wider security basics, and website management and maintenance shows where certificate checks fit next to updates and backups.
Installation is also not the end of the job. The CA/Browser Forum's Baseline Requirements, version 2.3.1 dated October 4, 2026, limit the validity of publicly trusted TLS certificates to 200 days when they are issued on or after March 15, 2026, 100 days when issued on or after March 15, 2027 and 47 days when issued on or after March 15, 2029. A purchased certificate that someone installs by hand and then forgets will now expire sooner than it used to, so decide at installation time how it will be renewed. Our management guide covers the schedule and the automatic options.
If you want a hostname inventory and a clean HTTPS setup as part of a website design project or a fix to your current site, contact us and we will go through the hostnames with you.