HTTP does not redirect to HTTPS
medium Security http_not_redirected
What we check
We request the http:// homepage separately. If it answers 200 instead of redirecting to HTTPS, two copies of the site are live.
Why it matters
Duplicate protocol versions split links and signals, and visitors who type the bare domain may land on the insecure copy.
How to fix it
Add a site-wide 301 from http:// to https:// at the server, load balancer or CDN.
How to confirm the fix
curl -sI http://yoursite.com/ should return 301 with an https location. Glossary: 301 redirect.
In the API response
When this check fails, output.technical_issues contains an item with "id": "http_not_redirected", the affected URLs as evidence and the fix. If it is among the highest-priority problems it also appears in actions (as finding_id) and in plan.
Related checks
Run the full audit on your site. One call checks every item in the check reference and ranks the fixes.
Open the playground Endpoint details