That red warning page saying 'Your connection is not private' is one of the few website problems customers will actually tell you about — and then leave. It means the SSL — The certificate that encrypts traffic and turns http:// into the padlock https:// shoppers trust./TLS certificate that encrypts your site has expired, is issued for a different name, or the chain is incomplete. Modern browsers refuse to load the page at all, and search engines quietly demote 'not secure' sites.
Check these first, yourself
Click the padlock (or the warning) and read the exact reason: 'expired', 'name mismatch', or 'not trusted' each means a different fix.
Check whether the domain shows as expired in your host's SSL panel and whether auto-renew is on — an off-by-default auto-renew is the classic cause.
Confirm the certificate covers the exact hostname people use: a cert for example.com does not cover www.example.com unless it's listed.
Don't hide it with a 'proceed anyway' link — customers see the warning, not your reassurance.
Should you fix it yourself or call a rescue?
Still have questions?
Will fixing the certificate lose me my Google ranking?
The opposite. While the site is 'not secure', Search Console flags it and browsers block it, which suppresses traffic. Restoring a valid certificate removes the warning and the penalty signal.
Why does the warning come back after I renew?
Usually because the renewed cert doesn't cover all the hostnames in use, or an old redirect points at the wrong one. The redirect and the certificate have to be fixed together, not separately.