Page served over HTTP instead of HTTPS: what it is, why it matters, and how to fix it
This page is served over an unencrypted HTTP connection instead of HTTPS. All data transmitted between the user's browser and the server is visible to anyone on the network.
Where this fits: security in SEO
Why page served over http instead of https hurts your rankings
HTTPS has been a confirmed Google ranking signal since 2014, and Chrome marks HTTP sites as "Not Secure" in the address bar. Users are increasingly wary of sites without HTTPS, especially for e-commerce, login pages, or any page collecting user data. Google's crawler strongly prefers indexing HTTPS versions of pages. Not using HTTPS is effectively giving up a baseline ranking advantage.
This is a critical issue: it can remove pages from search results entirely or block them from being crawled at all. Treat it as an outage, not a backlog item — every day it persists is compounding lost visibility.
How to fix it
Obtain and install an SSL/TLS certificate (free certificates are available from Let's Encrypt). Configure your server to redirect all HTTP traffic to HTTPS with 301 redirects. Update all internal links, canonical tags, and sitemaps to use HTTPS URLs. Ensure HTTPS pages do not have mixed content issues.
# Nginx: redirect all HTTP to HTTPS
server {
listen 80;
server_name example.com www.example.com;
return 301 https://$server_name$request_uri;
}Frequently asked questions
What does "Page served over HTTP instead of HTTPS" mean?
This page is served over an unencrypted HTTP connection instead of HTTPS. All data transmitted between the user's browser and the server is visible to anyone on the network.
Why does page served over http instead of https matter for SEO?
HTTPS has been a confirmed Google ranking signal since 2014, and Chrome marks HTTP sites as "Not Secure" in the address bar. Users are increasingly wary of sites without HTTPS, especially for e-commerce, login pages, or any page collecting user data. Google's crawler strongly prefers indexing HTTPS versions of pages. Not using HTTPS is effectively giving up a baseline ranking advantage.
How do I fix page served over http instead of https?
Obtain and install an SSL/TLS certificate (free certificates are available from Let's Encrypt). Configure your server to redirect all HTTP traffic to HTTPS with 301 redirects. Update all internal links, canonical tags, and sitemaps to use HTTPS URLs. Ensure HTTPS pages do not have mixed content issues.
How serious is this issue?
This is a critical issue: it can remove pages from search results entirely or block them from being crawled at all. Treat it as an outage, not a backlog item — every day it persists is compounding lost visibility. It belongs to the security family of checks.
How do I find every page affected by this on my site?
Run a free Dr Urls audit: it crawls your site, detects page served over http instead of https on every affected page, shows example URLs, and generates a ready-to-use fix task. Re-scan after fixing to verify the issue is gone.
Does your site have this issue?
A free Dr Urls audit crawls your site, finds every page affected by page served over http instead of https, and hands you a ready-made fix task.
Check my site free