Pages still on HTTP
Short answer
Pages still on HTTP means: these pages load without encryption. Browsers mark them "Not secure" and Google prefers HTTPS. To fix it: install a certificate (most hosts offer a free one) and 301-redirect every http:// URL to its https:// version.
By the SmooxSEO team. Updated on 16 November 2026.
What it means and why it matters
These pages load without encryption. Browsers mark them "Not secure" and Google prefers HTTPS.
How to fix it
Install a certificate (most hosts offer a free one) and 301-redirect every http:// URL to its https:// version.
Common causes
- The site has no SSL certificate, or it was never switched on.
- Internal links still written with http:// after moving to HTTPS.
- Some sections (an old blog, a subdomain) were left out of the move.
How to spot it
Look at the address bar: Chrome shows "Not secure" on HTTP pages. Search your pages' source for links starting with http://. SmooxSEO lists every page it reached over HTTP.
Example
<a href="http://example.com/pricing">Pricing</a><a href="https://example.com/pricing">Pricing</a>Mistakes to avoid
- Adding a certificate but not redirecting HTTP to HTTPS: both versions stay online.
- Forgetting images, scripts and stylesheets: on an HTTPS page, HTTP files are blocked or flagged as mixed content.
How serious is it?
A page can't be found, indexed or trusted, or search engines can't read part of the site. Fix it soon: it costs traffic.
About security checks
HTTPS, certificates, mixed content and security headers. Browsers warn visitors about insecure pages, and search engines prefer secure sites.
Find this problem on your site
SmooxSEO checks every page of your site for this problem and 311 others, lists the pages concerned, and tells you what to fix first.