Skip to main content
Security fix guide

No SSL Certificate (Not HTTPS)

Google penalizes non-HTTPS sites. Browsers show "Not Secure" warning.

Issue ID: SEC-SSL-001
Severity: critical
Impact: High
Effort: M

Use this article when

  • You need deeper remediation guidance than the issue card can show.
  • You want CMS-specific steps before handing the fix to a developer.
  • You want a repeatable re-check path after shipping the change.
Re-run full audit

What this issue is

Google penalizes non-HTTPS sites. Browsers show "Not Secure" warning.

Why it matters

Google penalizes non-HTTPS sites. Browsers show "Not Secure" warning. This affects browser trust signals and whether visitors feel safe submitting contact details.

How we detect it

  • FreeSiteAudit flags this issue when the rule for SEC-SSL-001 fails and the page evidence points to Http headers.
  • You can usually confirm this by checking the page source or the relevant page settings inside your CMS.

Evidence examples

Check the affected page source, rendered output, or relevant CMS setting to confirm the missing or incorrect element.

How to fix it

  1. 1Get a free SSL certificate from Let's Encrypt
  2. 2Install on your web server or hosting provider
  3. 3Redirect all HTTP traffic to HTTPS
  4. 4Update internal links to use https://

How to re-check it

  • Visit site and confirm browser shows secure lock icon

Related tools

This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.