Critical Security
Page served over HTTP
- Severity
- Critical
- Impact
- High
- Effort to fix
- Medium
- Issue code
not_https
Why it matters
Pages without HTTPS are flagged as not secure by browsers, and HTTPS is a ranking signal.
How to fix it
Serve the page over HTTPS and 301 redirect the HTTP version.
How it affects your score
Finding this issue on any page costs the Security score 8 points, plus up to 25 more depending on the share of crawled pages affected. As a critical issue type it also takes 3 points off overall site health (critical deductions stop at 15 points). Blocks indexing, breaks pages or loses traffic. Fix these first.
Find the affected URLs
Open Crawl > Issues and pick Page served over HTTP. Each affected URL is listed with its evidence, and Copy URLs or Export URLs hands the list to a developer. The issue also appears in the Action Plan, ranked by impact (high) and effort (medium), and in the issues CSV under the code not_https. After fixing, run a new audit and use Compare to confirm the URLs moved to fixed.