SSL Certificates Explained for Small Business Websites

An SSL certificate lets a website use HTTPS. That protects traffic between the visitor and the server, including logins, form submissions, cookies, checkout steps, and admin sessions. For a small business website, HTTPS is not optional; visitors expect it, browsers warn when it is missing, and many integrations require it.

What an SSL Certificate Does

The certificate proves that the website can serve encrypted HTTPS traffic for a specific hostname, such as example.co.uk or www.example.co.uk. It helps stop visitors sending information over plain HTTP.

The certificate does not make the website immune to weak passwords, vulnerable plugins, bad code, or phishing. It is one layer of protection, not the whole security plan.

Certificate Versus HTTPS Redirect

Installing a certificate is only part of the job. You also need visitors and search engines to use the HTTPS version consistently. On TekLan shared hosting, this is handled in Enhance with the Force HTTPS toggle under Security → SSL certificates.

If HTTPS works but HTTP still loads without redirecting, enable Force HTTPS. If enabling it causes a loop, check other redirect rules and any WordPress URL settings.

Root Domain and www

SSL is hostname-specific. A certificate for example.co.uk does not automatically mean www.example.co.uk is working correctly unless that hostname is also covered and pointed at the right server.

Check both versions after launch:

https://example.co.uk
https://www.example.co.uk

Mixed Content

Mixed content happens when an HTTPS page loads images, scripts, stylesheets, fonts, or embeds over HTTP. Browsers may block those resources or show a warning even though the certificate itself is valid.

Mixed content is common after migrations from older HTTP sites. Fix old internal URLs in content, theme settings, CSS files, and the database where needed.

Renewal

Enhance can issue and renew standard Let's Encrypt certificates automatically when DNS points to the correct TekLan server. Renewal can fail if DNS has been moved, the domain no longer resolves, or restrictive CAA records block the issuer.

Check SSL after DNS changes, migrations, domain aliases, and major redirect changes.

Common SSL Problems

The domain still points to the old host.
The www hostname is missing or points elsewhere.
An old IPv6 AAAA record sends some visitors to the wrong server.
Force HTTPS is not enabled.
Old HTTP image or script URLs create mixed content warnings.
A CDN is caching old redirects or certificates.