Site not served over HTTPS
high Security no_https
What we check
The homepage only answers over plain HTTP, or HTTPS fails with a certificate or connection error.
Why it matters
Browsers label HTTP pages as not secure, forms leak data on shared networks, and HTTPS is a confirmed (if light) ranking signal.
How to fix it
Issue a TLS certificate (free from most hosts and CDNs), serve every page over HTTPS and 301-redirect HTTP to HTTPS.
How to confirm the fix
Open the site with https:// and check the padlock, then rerun the audit.
In the API response
When this check fails, output.technical_issues contains an item with "id": "no_https", the affected URLs as evidence and the fix. If it is among the highest-priority problems it also appears in actions (as finding_id) and in plan.
Related checks
Run the full audit on your site. One call checks every item in the check reference and ranks the fixes.
Open the playground Endpoint details