Cookie missing Secure flag — the fix
One or more cookies are set without the Secure flag, meaning they can be transmitted over unencrypted HTTP connections.
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 cookie missing secure flag hurts your rankings
Without the Secure flag, cookies (including session tokens) can be intercepted by attackers via man-in-the-middle attacks on unencrypted HTTP connections. This is especially dangerous on public Wi-Fi networks where traffic sniffing is trivial.
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
Add the Secure attribute to all cookies, especially session cookies and any cookies containing sensitive data. Ensure your site is served exclusively over HTTPS.
Set-Cookie: sessionId=abc123; Secure; HttpOnly; SameSite=StrictSecurity 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 "Cookie missing Secure flag" mean?
One or more cookies are set without the Secure flag, meaning they can be transmitted over unencrypted HTTP connections.
Why does cookie missing secure flag matter for SEO?
Without the Secure flag, cookies (including session tokens) can be intercepted by attackers via man-in-the-middle attacks on unencrypted HTTP connections. This is especially dangerous on public Wi-Fi networks where traffic sniffing is trivial.
How do I fix cookie missing secure flag?
Add the Secure attribute to all cookies, especially session cookies and any cookies containing sensitive data. Ensure your site is served exclusively over HTTPS.
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 cookie missing secure flag 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 cookie missing secure flag, and hands you a ready-made fix task.
Check my site free