Checks / Links, canonical and speed
HTTP version does not redirect to HTTPS
http:// still serves the site instead of redirecting, so two copies of every page exist and visitors can land on the insecure one.
http_not_redirected · Links, canonical and speed · Warning
What triggers it
On a site that works over https, the http:// address of your home page answers 200 instead of redirecting to https.
What to change
Redirect every http:// URL to its https:// version with a 301.
Example
Server setting:
# nginx
server {
listen 80;
server_name _;
return 301 https://$host$request_uri;
}
How to confirm the fix
- Run curl -I http://example.com/: the answer is 301 with Location: https://...
- Run a new crawl
How common it is
We have not measured how common this is on a sample of sites. Counts appear here when a study covers it.
About this check
| Check ID | http_not_redirected |
|---|---|
| Report section | Links, canonical and speed |
| Severity | Warning |
| How it is decided | Measured: read directly from the page or the server's response. |
| Added | Before 19 Oct 2026 (versions 1 and 2), or a site-wide check with no version date yet |
| Status | Measured in every report |
| Report gives the code | Yes, one block for the site |
Settings by platform
Where the setting lives on a few platforms, from each platform's own help page, read on 26 October 2026. On any other server, apply the fix box above.
Cloudflare
In Cloudflare: SSL/TLS → Edge Certificates → Always Use HTTPS. (Cloudflare help page)
Related checks
See whether it applies to your site
Paste your address and we crawl up to 10 pages and show every issue we find, with its fix. No account, no card.
Every plan crawls up to its page limit and lists these checks with the fix: plans.
How an audit works: method