Page without HTTPS

security.http_urls
Priority
High
Severity
Warning

What we look for

These pages were served from an http:// address, without HTTPS (the encrypted connection that shows a padlock in the browser). Pages on a local test address are skipped.

Why it matters

Browsers mark these pages Not secure, which puts visitors off, and anything typed into them can be read on the way. Google also uses HTTPS as a small ranking signal.

How to fix

Install an SSL certificate (the file that lets a site use HTTPS, often free from your host or Let's Encrypt), serve every page over https://, and send each http:// address to its https:// version with a 301 redirect (a permanent forwarding rule).

Where you’ll see it

The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.

Terminal
When it is one of the five findings under Fix first, raptor crawl prints the id under it.
Check: security.http_urls
crawl.json and the CSV
The crawl JSON names the finding by this id, and so do the CSV and raptor_query.
"check_id": "security.http_urls"
The HTML report
This link opens the finding in the report, and each finding shows its id.
crawl.html#finding=security.http_urls
MCP
raptor_findings with this check_id returns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.
raptor_findings {
  "job_id": "...",
  "check_id": "security.http_urls"
}