Matan · Security · Exposure
Cookie flags (Security)
Session cookies need Secure, HttpOnly and SameSite.
Pass condition in our engine: Set-Cookie values include Secure and HttpOnly, or no cookies are set.
This Security check is part of SEO-GEO scoring 3.0.0, last updated 2026-10-25. The number on this page is the developer scoring version. It is not an announcement that public release 3.0.0 is live. A free report shows the same pass condition for the pages it fetched.
1. Problem description
We parse Set-Cookie on this response. Missing Secure allows HTTP theft; missing HttpOnly allows XSS to read the cookie; missing SameSite eases CSRF. If no cookies are set, the check passes.
2. Most common causes
- A framework default from years ago.
- A tracking cookie without SameSite.
- Secure omitted because HTTPS was added later.
Test this check
We fetch only this URL (plus robots.txt / llms.txt at the domain root when the check needs them). We do not crawl the rest of the site like a full report.
3. How to fix it
- Set Secure; HttpOnly; SameSite=Lax (or Strict) on session cookies.
- Use __Host- cookie prefixes where you can.
- Do not put secrets in non-HttpOnly cookies.
Scoring rules for the scan of fetched pages are documented in methodology. Want every category at once? Generate a free report.
Get your free website audit
Enter a public URL. The scan reads up to 300 pages and returns an HTML report with scores for measured pillars and a recommendation for each finding. No sign-up required.