What this check tests
Unlike most checks, this one reads a single page: the first crawled page, which is the homepage. It takes that response's headers (names are lower-cased) and records whether each of four is present with a non-empty value:
content-security-policyx-frame-optionsx-content-type-optionsstrict-transport-security
The score is the number present out of four: 0, 25, 50, 75 or 100.
- Pass: three or four headers present.
- Partial: one or two.
- Fail: none.
- Skip: only if no page was crawled, which a normal audit does not produce.
The result lists each header with a tick or a cross. The check does not read the values, so X-Frame-Options: ALLOWALL, a CSP of default-src * and an HSTS max-age=0 all count as present. Only response headers count; a policy set with a <meta http-equiv> tag is not seen. The headers come from the final response after redirects, and other pages are not examined, so an inner page that lacks a header is not reported. Other useful headers such as Referrer-Policy and Permissions-Policy are not tested.
Why it matters to agents
Be clear about the reach. These four headers are instructions that browsers enforce for the people using a site. MDN describes CSP as mainly a defence against cross-site scripting, X-Frame-Options as a way to avoid clickjacking by stopping other sites embedding your pages, X-Content-Type-Options: nosniff as a way to make browsers use the declared Content-Type, and HSTS as telling browsers to reach the host only over HTTPS. MDN also notes that site security testers usually expect X-Content-Type-Options to be set.
This page cites no source saying that an AI assistant or crawler reads, or rewards, these headers when it fetches your page. The link to agents is indirect: they protect the people who follow an agent's answer to your site, and a security scanner or a procurement review may look for them. The weight is 1, and a site can have a high AI-readiness score without them. Treat it as site hygiene.
How to fix it
Set the headers at the server, CDN or framework layer so they apply to every response, not only the homepage.
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Content-Security-Policy: default-src 'self'; frame-ancestors 'self'
Strict-Transport-Security: only send it over HTTPS and once HTTPS works everywhere.max-ageis how many seconds browsers remember the rule. MDN sayspreloadneeds at least a year andincludeSubDomains, so leavepreloadout until you are sure. See HTTPS.X-Content-Type-Options:nosniffis the only value.X-Frame-Options:DENYorSAMEORIGIN. MDN points to the CSPframe-ancestorsdirective for more comprehensive control. This check still looks for the older header, so send both if you want a full score.Content-Security-Policy: the example above is a starting point that will break pages loading scripts, styles or images from other hosts. Write the policy for your site, test it, and roll it out gradually. MDN says CSP can be deployed in report-only mode first, where violations are reported but not enforced. That mode uses a different header name,Content-Security-Policy-Report-Only, which this check does not count, so the cross stays until you switch to the enforcing header.
Check with curl -sI https://example.com/ and read the response headers. If your CDN or host has a headers setting, use that rather than editing every template.