Form submits to insecure HTTP endpoint — the fix
A form on this HTTPS page submits data to an HTTP (non-encrypted) endpoint. This exposes form data (including potential passwords and personal information) to interception.
Where this fits: security in SEO
Security issues erode both rankings and trust. HTTPS has been a ranking signal since 2014, and browsers actively warn users away from insecure or mixed-content pages — a warning interstitial is a 100% bounce rate. Missing security headers rarely block indexing, but they widen your attack surface, and a hacked site (injected spam, malicious redirects) can be removed from results entirely. Security is the SEO work you do so you never have to do recovery work.
Why form submits to insecure http endpoint hurts your rankings
Forms that submit to HTTP endpoints transmit user data in plaintext, making it vulnerable to interception by anyone on the network. Chrome and other browsers display prominent security warnings when forms submit to insecure endpoints. This erodes user trust, increases form abandonment, and can violate data protection regulations (GDPR, CCPA).
This is a high-severity issue: it directly suppresses rankings or click-through on the pages it affects. It belongs in your current sprint, prioritised by how many pages carry it.
How to fix it
Update the form action URL to use HTTPS. Ensure the receiving server supports HTTPS and has a valid SSL certificate. If the form posts to a third-party service, verify they support HTTPS endpoints.
<!-- Before -->
<form action="http://api.example.com/submit">
<!-- After -->
<form action="https://api.example.com/submit">Security best practices
- Serve everything over HTTPS and redirect HTTP with a single 301.
- Send HSTS, X-Content-Type-Options, and a Content-Security-Policy on every response.
- Eliminate mixed content — one insecure asset breaks the padlock.
- Keep dependencies and CMS plugins patched; most site hacks are known-CVE exploits.
- Monitor Search Console's security section — Google often knows you're hacked before you do.
The full library: SEO best practices, by category.
Frequently asked questions
What does "Form submits to insecure HTTP endpoint" mean?
A form on this HTTPS page submits data to an HTTP (non-encrypted) endpoint. This exposes form data (including potential passwords and personal information) to interception.
Why does form submits to insecure http endpoint matter for SEO?
Forms that submit to HTTP endpoints transmit user data in plaintext, making it vulnerable to interception by anyone on the network. Chrome and other browsers display prominent security warnings when forms submit to insecure endpoints. This erodes user trust, increases form abandonment, and can violate data protection regulations (GDPR, CCPA).
How do I fix form submits to insecure http endpoint?
Update the form action URL to use HTTPS. Ensure the receiving server supports HTTPS and has a valid SSL certificate. If the form posts to a third-party service, verify they support HTTPS endpoints.
How serious is this issue?
This is a high-severity issue: it directly suppresses rankings or click-through on the pages it affects. It belongs in your current sprint, prioritised by how many pages carry it. It belongs to the security family of checks.
How do I find every page affected by this on my site?
Run a free Dr Urls audit: it crawls your site, detects form submits to insecure http endpoint on every affected page, shows example URLs, and generates a ready-to-use fix task. Re-scan after fixing to verify the issue is gone.
Does your site have this issue?
A free Dr Urls audit crawls your site, finds every page affected by form submits to insecure http endpoint, and hands you a ready-made fix task.
Check my site free