Skip to main content
Security

How to Set Up Free SSL and Force HTTPS on Your Website

MMercy Chepkemoi29 October 202615 min read44 views

Open a website that still loads over plain HTTP and modern browsers will label it "Not secure" and increasingly warn visitors before the page even loads. For a business website, that warning costs trust, enquiries and sales. The fix is straightforward: install an SSL certificate, then force HTTPS so that every visitor, every link and every search engine lands on the secure version of your site.

This guide shows you how to set up a free SSL certificate and force HTTPS on your website, step by step. You will also learn how to fix the problems that usually follow, such as redirect loops and mixed content warnings, and how to protect your search rankings while you make the switch.

Key takeaways

  • An SSL certificate enables HTTPS, which encrypts the connection between your visitors and your website.

  • A free Let's Encrypt certificate gives you the same encrypted connection as most paid certificates. Paid options differ mainly in validation level, warranty and support.

  • Installing a certificate is not enough. You must also redirect HTTP to HTTPS with a permanent (301) redirect.

  • After redirecting, fix mixed content, update Google Search Console and your sitemap, and test every version of your URL.

  • On SteboHost web hosting, SSL certificates are included with hosting plans and renew automatically. Current plan terms are on the pricing page.

What Are SSL, TLS and HTTPS?

These three terms are often used as if they mean the same thing, so it helps to separate them.

  • SSL (Secure Sockets Layer) is the original security protocol. It was replaced years ago by TLS (Transport Layer Security), but the name "SSL certificate" stuck, and almost everyone still uses it.

  • A certificate is a digital file installed on your server. It proves that your server really controls your domain name and contains the keys used to encrypt traffic.

  • HTTPS is simply HTTP running over TLS. When you see https:// and a padlock, the connection between the browser and the server is encrypted.

HTTPS does three things: it encrypts data in transit, it confirms the visitor is talking to the server that holds a valid certificate for your domain, and it stops attackers on the network from silently altering the pages your visitors receive.

One important clarification: HTTPS means the connection is private. It does not mean the website itself is trustworthy or free of malware. That is why encryption works best alongside broader website security such as a web application firewall and malware scanning.

Why Every Website Needs HTTPS

1. Visitor trust. Browsers flag HTTP pages as "Not secure". Visitors who see that label are less likely to fill in a contact form, create an account or pay you.

2. Protection for data in transit. Contact forms, login pages and checkout pages all send information that should never travel in plain text. Securing data in transit is also part of the good security practice expected of anyone handling personal data, including under Kenya's Data Protection Act. (This is general information, not legal advice.)

3. SEO. Google has confirmed HTTPS as a lightweight ranking signal since 2014. It will not catapult a weak page to the top of the results, but running on HTTP removes a basic quality signal and can undermine user trust and engagement.

4. Modern performance and features. Browsers only support HTTP/2 and HTTP/3 over HTTPS, and many modern browser features require a secure connection. Moving to HTTPS is often a prerequisite for a faster site, not a drag on it.

Before You Start: A Quick Checklist

A few minutes of preparation prevents most HTTPS migration problems.

  1. Point your domain at your hosting. Certificates are issued only after your domain's DNS points to the server. If you manage records yourself, check them in your managed DNS settings. If you have not registered a domain yet, you can register your domain and host it in one place.

  2. Take a backup. You are about to edit your .htaccess file and possibly your database. Download a copy of .htaccess and export your database before you begin. On SteboHost, daily backups with 7-day retention and one-click restore give you a safety net, and you can read more about backup and disaster recovery.

  3. Choose one canonical address. Decide whether your site lives at example.com or www.example.com, and stick with it. Search engines treat them as separate addresses, so you want every other variation to redirect to your chosen one.

  4. Know your platform. The exact steps differ for WordPress, other CMSs and custom sites. This guide covers all three.

Step 1: Get a Free SSL Certificate

Let's Encrypt is a non-profit certificate authority that issues certificates at no charge. Its certificates are issued after you prove control of your website address, not after any check on who your organisation is. For most business websites, blogs and online stores that is exactly what is needed.

Certificates from Let's Encrypt are deliberately short-lived, and the wider industry keeps tightening certificate lifetimes. That makes automatic renewal essential. A certificate that expires because nobody renewed it produces a full-screen browser error that scares visitors away.

On SteboHost

SteboHost hosting plans include automatic SSL using Let's Encrypt certificates, issued and renewed for the domains on your hosting, so HTTPS is the default and there is nothing to install by hand. Current plan terms are on the pricing page. Once your domain points to your hosting account, simply open your site with https:// in front of the address.

How to confirm the certificate is working

  1. Visit https://yourdomain.com in your browser.

  2. Click the padlock or site-information icon next to the address and view the certificate details.

  3. Check that it was issued to your domain, shows Let's Encrypt as the issuer and has a future expiry date.

  4. Repeat the check for the www version of your domain.

For a deeper check, run your domain through the free SSL Server Test from Qualys SSL Labs, which reports on certificate validity, chain and protocol support.

If the certificate does not appear

  • DNS is not pointing at your hosting yet. This is the most common cause. DNS changes can take time to propagate, so wait and retry.

  • A CAA record is blocking issuance. If your domain has CAA records in DNS that do not authorise Let's Encrypt (letsencrypt.org), certificates cannot be issued. Add or correct the record.

  • You changed nameservers recently. Allow time for the change to settle, then check again.

Still stuck? SteboHost support can check it with you, or you can search the knowledge base.

Need something beyond a standard Let's Encrypt certificate, for example for a particular compliance or business requirement? Explore the available SSL certificates.

Step 2: Force HTTPS on Your Website

Having a certificate installed does not stop people reaching the old HTTP version of your site. Forcing HTTPS means sending every HTTP request to HTTPS with a 301 (permanent) redirect, which also tells search engines that the secure address is the real one.

Option A: Use the cPanel toggle

On many cPanel versions you can open the Domains section, find your domain and switch on Force HTTPS Redirect. It is the simplest method and needs no code. The exact label and location can vary between cPanel versions, so if you do not see it, use Option B.

Option B: Add a redirect rule to .htaccess

On Apache-compatible servers, including LiteSpeed, you can add a rewrite rule to the .htaccess file in your site's root folder (usually public_html):

# Force HTTPS
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

This reads: if the request is not using HTTPS, send the visitor to the same address over HTTPS with a permanent redirect. Place it near the top of the file. On WordPress sites, put it above the block that starts with # BEGIN WordPress so it runs first.

If you also want to remove www and avoid a two-step redirect chain, use a single combined rule (replace example.com with your own domain):

RewriteEngine On
RewriteCond %{HTTPS} !=on [OR]
RewriteCond %{HTTP_HOST} ^www\. [NC]
RewriteRule ^ https://example.com%{REQUEST_URI} [L,R=301]

If you prefer the www version, adjust the condition and target accordingly. The goal is that every variation reaches your preferred address in a single hop.

Option C: WordPress settings

For WordPress, the redirect is only half the job. WordPress itself should also know its address is HTTPS.

  1. In the dashboard, go to Settings > General and change both WordPress Address (URL) and Site Address (URL) to the https:// version.

  2. Update old http:// links stored in your database. You can use a trusted search-and-replace plugin, or WP-CLI if you have SSH access (for example on a VPS). Always run a dry run first:

wp search-replace 'http://example.com' 'https://example.com' --skip-columns=guid --dry-run

If the result looks right, run it again without --dry-run.

Finally, clear every cache: your caching plugin, LiteSpeed Cache if you use it, and any CDN.

If you lock yourself out after changing the addresses, you can set them directly in wp-config.php:

define('WP_HOME', 'https://example.com');
define('WP_SITEURL', 'https://example.com');

Running WordPress? Managed WordPress hosting with staging sites lets you test a change like this before it touches your live site.

Option D: You use a CDN or proxy

If a CDN or reverse proxy sits in front of your server, a basic redirect rule can create an endless loop, because your server only ever sees plain HTTP from the proxy. The usual fixes are to set the CDN's SSL mode to a full end-to-end option (not "flexible") or to make the rule check the X-Forwarded-Proto header the proxy sends. Check your CDN's documentation for the exact setting.

Step 3: Fix Mixed Content

Mixed content happens when an HTTPS page still loads some resources, such as images, scripts, fonts or stylesheets, over HTTP. Browsers block the riskiest kinds and warn about others, and the padlock may vanish or show a warning even though your certificate is perfectly valid.

How to find it: open the affected page, press F12 to open developer tools, and check the Console tab. Mixed content messages list the exact insecure URLs.

How to fix it:

  • Change hard-coded http:// URLs to https:// in your theme files, widgets, page content, CSS and plugin settings.

  • On WordPress, the database search-and-replace from Step 2 fixes most image and link references.

  • Update third-party embeds (maps, videos, fonts, forms) to their https:// versions.

  • As a temporary safety net, you can ask browsers to upgrade insecure requests with this header, but treat it as a stopgap and still fix the underlying URLs:

Header always set Content-Security-Policy "upgrade-insecure-requests"

Step 4: Add HSTS (Recommended, With Care)

A redirect still leaves one small gap: the very first request a browser makes may go over HTTP before being redirected. HTTP Strict Transport Security (HSTS) closes it. It is a response header that tells browsers to connect to your site over HTTPS only, for a set period.

Start with a short duration while you test:

Header always set Strict-Transport-Security "max-age=300"

If everything works, raise it in stages (for example to one day, then one week, then one year, which is 31536000 seconds).

Be aware of two things:

  • Once a browser has seen the header, it will refuse to load your site over HTTP, and visitors cannot click through certificate errors. A broken or expired certificate becomes a hard failure, which is another reason automatic renewal matters.

  • Adding includeSubDomains applies the rule to every subdomain, so only use it once all of them work over HTTPS. Submitting your domain to the HSTS preload list is even harder to undo, so only do it deliberately and after long-term testing.

Continuous monitoring of your site helps you spot certificate or availability problems early.

Step 5: Protect Your SEO

Done properly, switching to HTTPS should not hurt your rankings. These steps help search engines understand the change:

  • Use 301 redirects only. Temporary redirects (302) do not signal a permanent move.

  • Avoid redirect chains. Aim for HTTP to the final HTTPS address in one hop.

  • Update Google Search Console. Add the HTTPS version of your site, or use a Domain property, which covers every protocol and subdomain, and submit your updated sitemap with https:// URLs.

  • Update canonical tags, internal links and structured data so they point to https:// addresses.

  • Update external profiles: Google Business Profile, social media bios, email signatures, ad campaigns and analytics settings.

  • Be patient. Search engines need time to recrawl and consolidate signals, and small temporary fluctuations can happen.

Step 6: Test Everything

Before you call the job done, check the following:

  1. All four address variations (http://example.com, http://www.example.com, https://example.com and https://www.example.com) should end up at the same final HTTPS address.

  2. The redirect type. Run curl -I http://example.com and confirm the response shows a 301 status and a Location header beginning with https://.

  3. The padlock appears on your homepage, key landing pages, login page and checkout or contact forms.

  4. No mixed content messages appear in the browser console.

  5. The SSL Labs test shows a valid certificate and a healthy configuration.

Common Problems and Fixes

  • ERR_TOO_MANY_REDIRECTS (redirect loop). Usually caused by conflicting redirect rules, a CMS that keeps forcing HTTP, or a CDN in flexible SSL mode. Remove duplicate rules, confirm the WordPress addresses use https:// and review your CDN's SSL mode.

  • "Your connection is not private" or a certificate name mismatch. The certificate does not cover the address you typed. Check that both the www and non-www versions are covered and that your DNS points to the correct server.

  • Padlock missing despite a valid certificate. Mixed content. Use the console to find and fix the insecure URLs.

  • Site works on HTTPS but old links still show HTTP. Clear caches and re-run your database search-and-replace.

  • Certificate expired. Check that automatic renewal is active. On SteboHost it is automatic, and support can help if anything looks wrong.

Why SteboHost Makes HTTPS Simple

Setting up SSL should not mean extra invoices and extra work. With SteboHost, security is part of the foundation of every plan:

  • Automatic SSL included with hosting plans, using Let's Encrypt certificates that renew automatically. Current plan terms are on the pricing page.

  • A web application firewall and malware scanning on every plan, so encryption is backed by real protection.

  • Daily backups with 7-day retention and one-click restore, so you can experiment with confidence.

  • 24/7 infrastructure monitoring and a 99.9% uptime SLA.

  • Free migration from your current host on annual plans (terms are shown on the pricing page and at checkout), so you can move your site, databases and email without the hassle.

  • Local support and M-Pesa, card or bank transfer billing in KES.

Current plan and renewal prices are shown before you buy. You can compare plans and pricing or head straight to SteboHost web hosting to get started.

Conclusion

Securing your website with HTTPS comes down to a clear sequence: get a certificate, force the redirect, fix mixed content, add HSTS carefully, update your SEO settings and test every variation. With a host that issues and renews free SSL for you, most of the work disappears, leaving you with a few configuration checks rather than a technical project.

Ready for a hosting platform where HTTPS is on by default? Explore SteboHost web hosting, or call +254 703 610 464 or email support@stebohost.com and the team will help you get set up.

Frequently Asked Questions

Is free SSL as secure as paid SSL?

For encrypting the connection, a free Let's Encrypt certificate and a paid certificate of the same type provide comparable protection. The differences lie elsewhere: paid certificates can offer organisation validation, warranties, extended support and options for specific business or compliance needs. For most business websites, blogs and stores, a standard Let's Encrypt certificate is entirely sufficient.

Does SSL slow down my website?

The overhead of modern TLS is small and rarely noticeable. In fact, HTTPS is required for browsers to use HTTP/2 and HTTP/3, which can improve loading speed. Good hosting, caching and optimised images affect performance far more than the certificate does.

Will forcing HTTPS hurt my SEO?

Not if you do it correctly. Use permanent 301 redirects, avoid redirect chains, update your canonical tags, sitemap and Google Search Console, and fix mixed content. You may see small temporary fluctuations while search engines recrawl your site, but HTTPS is the standard and a lightweight ranking signal.

How often does a free SSL certificate need to be renewed?

Free certificates are short-lived by design, so they must renew regularly. You should never do this by hand. On SteboHost, certificates are renewed automatically, so you do not need to track expiry dates.

Why do I still see "Not secure" after installing SSL?

The most common causes are mixed content (some resources still load over HTTP), visiting the http:// version of your site because no redirect is in place, cached pages that still contain old links, or a certificate that does not cover the address you are using. Work through Steps 2, 3 and 6 above to find the cause.

Do I need SSL if my website has no login or payments?

Yes. HTTPS protects the integrity of your pages so they cannot be altered in transit, builds visitor trust, avoids browser warnings and supports your SEO. Even a simple brochure site benefits.

Should I use www or non-www with HTTPS?

Either works. What matters is choosing one, redirecting the other to it in a single step, and making sure your certificate covers both versions. Keep your canonical tags, sitemap and internal links consistent with your choice.

#SSL#HTTPS#Website Security#Free SSL#Let's Encrypt#WordPress#cPanel#HSTS#Web Hosting
M

Written by Mercy Chepkemoi

SteboHost engineering and operations team. We write practical guides on hosting, domains, email and security for African businesses — based on what we see in the field, not marketing copy.

Ready to get started?

Browse our hosting plans or contact our team for help choosing the right one.