Why does my website say Not Secure?
Rubric check: pages served over http (check id http_pages)
Because the page loads over plain http:// instead of https://. Rubric flags pages that are served over http rather than redirecting to an https address.
Why it matters for SEO
Google uses https as a small ranking signal and prefers the https version when both exist. Chrome and other browsers label http pages "Not secure", which puts people off, most of all on forms. Every http address should 301-redirect to its https version.
Does this matter for ChatGPT and AI Overviews?
Probably not much on its own. There's no public evidence that AI search tools skip http pages. But they pick sources from search results, which favour https, and a page split across http and https addresses has its signals split too.
How Rubric scores it
MajorMajor checks cost twice as much as a standard check when they fail.
Why this tier: Browsers mark http pages Not Secure, and search engines prefer the https version.
It is judged on every page Rubric scores.
Every Rubric score starts at 100. When this check fails, it takes up to 24 points off. Even one failing page costs at least 12 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.
This check doesn't cap your score. It only takes off its own points.
From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).
How common it is
Found on 2 of 300 sites where Rubric could judge it (0.7%). That is 2 of 287 judged sites in Rubric's 313-site test set and 0 of 13 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.
How accurate the check is
Lab test: passed. On test pages built with this problem, it caught 2 of 2. On clean test pages, it stayed quiet 2 of 2 times. (Engine build bbcec7c.)
Real sites: people checked 6 of its findings by hand and 0 were wrong (0%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
- Make sure your host has an SSL certificate on the domain. Most hosts offer a free one from Let's Encrypt in the control panel.
- Go to Settings > General and change WordPress Address (URL) and Site Address (URL) to start with
https://. - Add a 301 from http to https in your host's settings or
.htaccess, then update any hard-coded http links in content.
Shopify
Shopify gives every connected domain a free SSL certificate and redirects http to https for you. If Rubric reports http pages, go to Settings > Domains and check each domain's SSL status. A domain that is still pending usually has a DNS record pointing somewhere else.
Webflow
Webflow issues SSL certificates for hosted sites. Go to Site settings > Publishing, check SSL is enabled for your custom domains, then publish. If the domain's DNS records aren't set up as Webflow shows, the certificate can't be issued.
Custom code
Install a certificate (Let's Encrypt is free) and redirect every http request. Nginx:
server {
listen 80;
server_name example.com;
return 301 https://example.com$request_uri;
}Then add an HSTS header so browsers go straight to https next time.