top of page

What Is an SSL Certificate and Why Your Store Needs One

1 hour ago
14 min read

What Is an SSL Certificate

Disclosure: this article contains affiliate links, and we may earn a commission at no extra cost to you if you sign up through them.


If you run an online store, the small padlock next to your web address is doing more work than it looks like. It tells shoppers their connection is private, it keeps card numbers and passwords away from anyone listening in, and it's one of the first things browsers and search engines check before they decide how much to trust your site. All of that comes from one thing: an SSL certificate.


This guide explains what an SSL certificate actually is, how it protects an ecommerce store, which type you need, what it costs and how to set it up without breaking anything. It's written for store owners rather than system administrators, so we'll keep the jargon to a minimum and focus on the decisions you'll actually have to make.


What is an SSL certificate?


An SSL certificate is a small data file, issued by a trusted organization called a certificate authority (CA), that does two jobs. It proves that a website really belongs to the domain it claims to be, and it lets the browser and the server set up an encrypted connection so nobody in between can read or change the data passing through.


SSL stands for Secure Sockets Layer. Strictly speaking, SSL itself was retired years ago and replaced by a newer protocol called TLS (Transport Layer Security), with TLS 1.2 and TLS 1.3 being the versions in use today. The name stuck, though, so "SSL certificate" and "TLS certificate" mean the same thing in everyday use. When you see either term on a hosting or website builder pricing page, it's the same product.


When a site has a valid certificate installed, its address starts with https:// instead of http://, and most browsers show a padlock or a "connection is secure" indicator. The "s" in HTTPS stands for secure, and it's the visible sign that the certificate is working.


How SSL works when a customer visits your store


You don't need to understand the cryptography to run a secure store, but a rough picture helps you troubleshoot problems later. Here's what happens in the fraction of a second after a shopper types your address:


  1. The shopper's browser contacts your server and asks it to prove who it is.

  2. Your server sends back its SSL certificate, which includes your domain name, the certificate authority that issued it, an expiry date and a public key.

  3. The browser checks that the certificate was issued by a CA it trusts, that it hasn't expired and that the domain on the certificate matches the domain in the address bar.

  4. If everything checks out, the browser and server agree on a set of temporary session keys. This step is called the TLS handshake.

  5. From then on, every page, form submission and checkout request travels in encrypted form until the shopper leaves.


If any of those checks fail, for example because the certificate has expired or was issued for a different domain, the browser shows a full-page warning instead of your store. For an ecommerce business, that warning is about as damaging as a locked front door during business hours.


Why your online store needs an SSL certificate


Every website benefits from HTTPS, but for a store it isn't optional. There are five separate reasons, and any one of them would be enough on its own.


It protects payment and personal data


An online store handles exactly the kind of data criminals want: names, home addresses, email addresses, phone numbers, account passwords and, at checkout, payment details. Without encryption, that information travels across the internet as readable text. Anyone with access to the network in between, such as someone on the same public Wi-Fi as your customer, could intercept it.


With an SSL certificate in place, the data is scrambled in transit, so even if it's intercepted it's useless without the session keys. That's the core security benefit, and it applies to every page where a customer types something in, not only the payment step. Login pages, account pages, contact forms and newsletter signups all collect personal information too.


Browsers warn shoppers away from sites without it


Google Chrome has labeled HTTP pages as "Not secure" in the address bar since 2018, and other major browsers behave similarly. On pages with forms, the warning is even more prominent. Some browsers now try to upgrade connections to HTTPS automatically and show an interstitial warning when they can't.


For a store, that label is a conversion killer. Shoppers who see "Not secure" next to a checkout form are being told, by their own browser, not to trust you. Most will leave rather than risk it, and many won't come back.


Payment rules expect encrypted connections


If you accept card payments, you're expected to follow the Payment Card Industry Data Security Standard (PCI DSS). Among other things, it requires strong cryptography whenever cardholder data is sent over open, public networks. In plain terms, any page that handles card details needs to be served over HTTPS with a current, properly configured certificate.


In practice, most small stores use a hosted payment provider or an all-in-one ecommerce platform that handles the card data itself, which reduces how much of PCI DSS falls on you. You still need HTTPS across your own site, though, because the pages that lead to checkout, and the account and login pages around it, collect personal data too. Payment providers also expect the sites they're embedded in to be secure.


Search engines favor secure sites


Google confirmed back in 2014 that HTTPS is a ranking signal. It's a light signal compared with content quality and relevance, so a certificate won't push a thin page to the top of search results. But in a competitive niche where two product pages are otherwise similar, the insecure one is at a disadvantage, and the browser warnings it triggers will hurt engagement anyway.


HTTPS also preserves referral data in your analytics. When visitors move from a secure site to an insecure one, the referral information is often stripped, which makes it harder to see where your traffic and sales are really coming from.


It builds trust at the moment it matters most


Trust is the currency of online retail. A first-time visitor has never held your products, met your team or seen your premises. Every signal on the page either adds to their confidence or chips away at it, and the security indicator is one they've been trained to look for.


A valid certificate won't sell your products for you, but a missing or broken one will lose sales you would otherwise have made. It's one of the cheapest trust signals you can add, and on most modern platforms it's included at no extra cost.


The three types of SSL certificate


Certificate authorities offer certificates at three validation levels. All three use the same strength of encryption. What changes is how thoroughly the CA checks who you are before issuing the certificate.


Domain Validated (DV)


A DV certificate confirms only that you control the domain. The CA checks this automatically, usually by asking you to add a DNS record or place a file on your server, and the certificate can be issued in minutes. DV certificates are what most website builders and hosting companies install by default, and they're what free certificate authorities such as Let's Encrypt provide.


For the vast majority of small and medium-sized stores, a DV certificate is all you need. It gives you full encryption, the padlock and HTTPS, and shoppers can't tell the difference in normal browsing.


Organization Validated (OV)


An OV certificate adds a check on the business itself. The CA verifies that your organization is legally registered and that it controls the domain, and the company name is included in the certificate details. Issuance takes longer, typically a few days, and there's a cost.


OV certificates suit established businesses, B2B suppliers and organizations that want their verified legal name visible to anyone who inspects the certificate. The encryption is no stronger than DV.


Extended Validation (EV)


An EV certificate involves the most rigorous checks, including documentation of the business's legal, physical and operational existence. Years ago, EV certificates triggered a green address bar with the company name, which made them popular with banks and large retailers.


Modern browsers removed that green bar, so the visual difference between EV and DV is now minimal for most users. EV still has a place for large enterprises, financial services and businesses with specific compliance needs, but it's rarely worth the cost for a typical online store.


SSL certificate types compared


Here's a quick side-by-side view of the main options, including the two coverage variations you'll see on pricing pages.


Certificate type

What it verifies

Typical issuance time

Best for

Domain Validated (DV)

Control of the domain

Minutes

Most small and mid-sized stores

Organization Validated (OV)

Domain plus registered business

A few days

Established brands and B2B sellers

Extended Validation (EV)

Domain plus in-depth business checks

Several days to weeks

Large enterprises and regulated industries

Wildcard

One domain and all its subdomains

Depends on validation level

Stores using shop., help. or blog. subdomains

Multi-domain (SAN)

Several different domains on one certificate

Depends on validation level

Businesses running several storefronts


Free vs paid SSL certificates


One of the most common questions store owners ask is whether a free certificate is good enough. For most stores, the answer is yes.


Free certificates, including those issued by Let's Encrypt and the ones bundled with website builders, are Domain Validated and use the same encryption standards as paid DV certificates. Browsers trust them in exactly the same way. The main differences with paid certificates are elsewhere:


  • Validation level: free certificates are DV only, so if you need OV or EV you'll pay for it.

  • Warranty: paid certificates often come with a warranty that pays out if the CA's mistake causes a loss. Claims are rare, and the warranty doesn't cover breaches of your own systems.

  • Support: commercial CAs offer support and installation help, which can matter if you manage your own server.

  • Renewal handling: free certificates are designed for automated renewal. That's ideal on a managed platform and can be a headache on a self-managed server if automation isn't set up.


If your store runs on a managed website builder, you probably won't have to think about any of this. The certificate is issued, installed and renewed for you as part of your plan.


How much does an SSL certificate cost?


The price range is wide, which is why the topic confuses so many new store owners. A basic DV certificate can cost nothing at all, while a premium EV certificate from a commercial CA can run to hundreds of dollars a year. The encryption is the same at both ends, so what you're paying for is validation, warranty, support and convenience.


In practice, store owners fall into three groups:


  • Website builder users usually pay nothing extra, because SSL is bundled into the plan and renewed automatically.

  • Self-hosted stores on mainstream hosting often get a free DV certificate through the host's control panel, with paid upgrades offered as an option.

  • Businesses that need OV or EV buy directly from a certificate authority or a reseller and budget for annual or multi-year costs, plus the time it takes to complete validation.


Be wary of hosting checkouts that add a paid certificate by default. If your host already offers free SSL, a paid DV certificate rarely adds anything a typical shopper will notice. Spend that money on things that do move sales, such as better product photos, faster pages or a smoother checkout.


How to check your store's certificate details


It's worth knowing how to inspect your own certificate, because it's the fastest way to diagnose a warning a customer reports. In most desktop browsers, click the padlock or site information icon to the left of your address, then open the connection or certificate details.


You'll see who issued the certificate, which domain names it covers, when it was issued and when it expires. Check that every hostname you use is listed, including the www version, and note the expiry date. If you're on a managed platform, the expiry date should move forward on its own every few months. If it doesn't, contact support before the date arrives rather than after.


Free online SSL checkers can run a deeper test, flagging outdated protocol versions, missing intermediate certificates or weak configurations. They're useful after a migration, a domain change or any time you edit server settings yourself.


Certificate lifetimes are getting shorter


SSL certificates don't last forever. For several years, the maximum lifetime for a publicly trusted certificate was 398 days, roughly 13 months. In 2025, the CA/Browser Forum, the industry body that sets the rules, approved a schedule to shrink that number in stages.


Since March 15, 2026, the maximum lifetime has been 200 days. It drops to 100 days in March 2027 and to 47 days in March 2029. Let's Encrypt certificates were already valid for only 90 days, which is one reason automated renewal became standard.


For store owners, the practical takeaway is simple. Manual renewal is becoming unrealistic, so you want a platform or host that renews certificates automatically. If you manage your own server, make sure renewal is automated and monitored, because an expired certificate takes your store offline just as surely as a server crash.


How to get an SSL certificate for your store


How you get a certificate depends on how your store is built. There are three common setups.


On an all-in-one website builder


Most hosted website builders include SSL on every site, often including free sites on a subdomain. When you connect a custom domain, the platform issues a certificate for it automatically, usually within minutes to a few hours, and renews it in the background.


Wix, for example, enables HTTPS on sites by default and handles certificate renewal for you, so store owners don't need to buy, install or track a certificate. If you're still choosing where to build, an easy website builder with built-in hosting and security takes the whole topic off your to-do list, and it's worth checking that any platform you shortlist does the same.


AI-first builders typically follow the same model. AI Website Builder, for instance, generates a full site from a short description and includes hosting and automatic SSL on its paid plans, so a new store is secure from the day it goes live.


On a hosting plan you manage


If you run an open-source platform such as WooCommerce on your own hosting account, the steps are a little more hands-on:


  1. Check whether your host includes a free certificate. Most do, often powered by Let's Encrypt, with a one-click option in the control panel.

  2. If not, generate a certificate signing request (CSR) on your server and buy a certificate from a CA or reseller.

  3. Complete the CA's validation step, which for DV usually means adding a DNS record or uploading a file.

  4. Install the certificate and any intermediate certificates on your server.

  5. Set up automatic renewal and a monitoring alert so you hear about problems before your customers do.


On a fully custom stack


Developers running custom infrastructure usually automate certificates with the ACME protocol, the same system Let's Encrypt uses, or use a content delivery network that terminates TLS at the edge. If someone else built your store, ask them how certificates are issued and renewed, and who gets alerted when renewal fails. If you want your own custom frontend without managing servers, Wix Headless lets you create a website from anywhere, including an AI coding tool, and run it on Wix, where hosting, SSL and DNS are handled for you.


How to move your store from HTTP to HTTPS


If your store has been running without HTTPS, switching over is straightforward, but a few steps protect your search rankings and avoid broken pages.


Redirect every HTTP URL to HTTPS


Set up permanent (301) redirects so that every old http:// address sends visitors and search engines to the matching https:// address. Managed platforms usually do this automatically once SSL is active. On self-hosted sites, you'll add redirect rules at the server level or through your platform's settings.


Fix mixed content


Mixed content happens when a page loads over HTTPS but some of its resources, such as images, scripts or fonts, still load over HTTP. Browsers may block those resources or downgrade the padlock, which can break product galleries, checkout widgets or tracking scripts.


To fix it, update hard-coded http:// links in your theme, product descriptions and custom code to https://. Your browser's developer tools will list any insecure resources on a page, and many platforms flag them for you.


Update your tools and listings


After the switch, update the URL in your analytics property, your search console account, your ad campaigns, your marketplace listings and your social profiles. Submit an updated sitemap so search engines pick up the HTTPS versions faster.


Consider HSTS


HTTP Strict Transport Security (HSTS) is a setting that tells browsers to always use HTTPS for your domain, even if someone types http:// or clicks an old link. It closes a small window for interception on the first request. Turn it on only once you're confident every part of your site works over HTTPS, because browsers will remember the rule for the period you set.


Common SSL problems and how to fix them


Even on managed platforms, certificate issues occasionally pop up. These are the ones store owners run into most.


"Your connection is not private" warnings


This full-page warning usually means the certificate has expired, was issued for a different domain or isn't trusted by the browser. Check the expiry date and the domain listed on the certificate. If you recently connected a new domain, the platform may still be issuing the certificate, which can take a little time after DNS changes.


The padlock is missing on some pages


If most pages show the padlock but a few don't, mixed content is the usual cause. Look for images, embedded videos or scripts loading over HTTP on the affected pages and update their addresses.


The certificate doesn't cover www or a subdomain


A certificate issued for example.com won't always cover www.example.com or shop.example.com. Make sure your certificate lists every hostname you use, or use a wildcard certificate if you run several subdomains.


Renewal failed


Automated renewal can fail if DNS records change, a domain lapses or validation files are blocked. Keep your domain registration current, avoid removing DNS records you don't recognize without checking first, and set up an expiry alert so you have time to fix problems.


SSL is one layer of store security, not the whole thing


A certificate protects data in transit between the shopper and your server. It doesn't protect against weak passwords, outdated plugins, phishing emails or a compromised admin account. A secure store combines HTTPS with a few other habits:


  • Use strong, unique passwords and turn on two-factor authentication for every admin account.

  • Keep your platform, theme and any plugins or apps up to date.

  • Use a reputable payment provider rather than storing card details yourself.

  • Limit staff accounts to the permissions they actually need.

  • Back up your store regularly and know how to restore it.

  • Watch for unusual orders, login attempts or changes to payout details.


Managed platforms handle much of the infrastructure side, including server patching, DDoS protection and certificate management, which is one reason many small retailers choose them over self-hosting.


SSL certificate ecommerce checklist


Before you launch or relaunch your store, run through this quick list:


  • Every page loads over https://, including the homepage, product pages, cart, checkout, login and account pages.

  • HTTP addresses redirect permanently to their HTTPS versions.

  • The certificate covers every hostname you use, including www and any subdomains.

  • There are no mixed content warnings on key pages.

  • Certificate renewal is automatic, and someone gets alerted if it fails.

  • Your analytics, search console and ad accounts point to the HTTPS version of the site.

  • Your payment provider is PCI DSS compliant and handles card data on its side.


If you'd rather not manage any of this yourself, the simplest route is a platform that bundles hosting, SSL and renewals into one plan. You can generate a secure store with AI Website Builder and have HTTPS in place from the first day you publish.


SSL certificate ecommerce FAQ


Do I need an SSL certificate if I don't take payments on my own site?

Yes. Even if a payment provider handles the card details, your store still collects names, emails, addresses and passwords on its own pages. Browsers also flag any page without HTTPS as not secure, which hurts trust and conversions.

For most stores, yes. Free certificates are Domain Validated and use the same encryption strength as paid DV certificates. You'd only need a paid certificate if you want organization or extended validation, a warranty or dedicated support.

Visit your store and check that the address starts with https:// and that the browser shows a padlock or secure connection indicator. Clicking it shows who issued the certificate, which domain it covers and when it expires.

Since March 15, 2026, publicly trusted certificates can be valid for a maximum of 200 days, dropping to 100 days in 2027 and 47 days in 2029. That's why automatic renewal, which most website builders handle for you, is now essential.

HTTPS is a confirmed but lightweight Google ranking signal. It won't outweigh content quality or relevance, but it removes a disadvantage and prevents browser warnings that drive visitors away.

TLS is the modern successor to SSL. The original SSL protocol is no longer used, but the name stuck, so certificates are still commonly called SSL certificates even though they secure TLS connections.


Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page