The page is served over plain HTTP
The page's final address, after any redirects, starts with http://. Browsers mark such pages as "Not secure", and Google prefers HTTPS. Turn on a TLS certificate and redirect every HTTP address to HTTPS with a 301.
What it means
Without HTTPS browsers mark the page as not secure, and Google prefers secure pages. Get a certificate (free from Let's Encrypt or your host) and redirect every HTTP address to HTTPS with a 301.
Why it matters for AI search
Without HTTPS, anything between the visitor and the server can read or change the page on the way, including forms and logins. Browsers label such pages "Not secure", and HTTPS is part of Google's page experience signals.
The check looks at the address the page ends on. If the HTTP address redirects to HTTPS, it passes; if HTTPS works but nothing redirects to it, or a redirect goes the other way, the page is reported. Certificates are free from Let's Encrypt, and most hosts and CDNs issue them automatically.
How to fix it
- Turn on a certificate for the domain: in the hosting panel, with Certbot and Let's Encrypt on your own server, or by putting the site behind a CDN such as Cloudflare.
- Redirect every
http://address to the same path onhttps://with a 301 (on Cloudflare: SSL/TLS → Edge Certificates → Always Use HTTPS). - Change internal links, canonicals, the sitemap and the site address in your CMS (in WordPress: Settings → General) to
https://. - Once HTTPS works everywhere, add the HSTS header so browsers stop trying HTTP.
- Run "Check again" on the page report to confirm the result.
Example
# nginx
server {
listen 80;
server_name example.com www.example.com;
return 301 https://example.com$request_uri;
}
# Apache (.htaccess)
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] How to confirm the fix
After the change, press "Check again" on the report: it lists what was fixed and how the score changed.