Repair workflow
- Serve the canonical page over HTTPS.
- Redirect equivalent HTTP URLs.
- Replace insecure resource references.
- Submit forms only to secure destinations.
Issue library · 3 https and forms checks
HTTPS, mixed content, and insecure form issues
Keep public pages, active resources, and form destinations on secure, consistent HTTPS connections.
Direct answer
Public pages, active resources, and form destinations should use HTTPS. Remove mixed content and redirect HTTP versions to the preferred secure URL.
Why this area matters
Insecure delivery exposes users to tampering and can break browser features. Security problems also weaken trust and can disrupt crawling or rendering.
Verification checklist
- Inspect browser security warnings.
- Review the Network panel for HTTP requests.
- Test redirects, canonicals, forms, and internal links.
Exact findings explained
Page is not served over HTTPS
The current page URL uses HTTP.
What to do
Redirect to the equivalent HTTPS URL and update canonical and internal references.
How to verify
Open the HTTP URL and confirm one clean permanent redirect to HTTPS.
HTTPS page loads HTTP resources
The page requests insecure images, scripts, styles, fonts, or media.
What to do
Update resources to HTTPS or remove them when no secure version exists.
How to verify
Reload with the Network panel open and confirm no HTTP resource remains.
Form submits to HTTP
A secure page sends a form to an insecure destination.
What to do
Submit the form over HTTPS and verify every redirect remains secure.
How to verify
Inspect the rendered action and complete a safe test submission.