b/cited
← Glossary
[ Term ]

CSP (Content Security Policy)

A header that tells browsers which sources of script, style, and other content are allowed to load on your page. The main defense against cross-site scripting — and a serious EEAT trust signal when implemented well.

Also known as:Content Security PolicyContent-Security-Policy

CSP is a security policy declared via the Content-Security-Policy response header that whitelists which sources the browser is allowed to load resources from. If your page tries to execute a script from a domain not on the whitelist, the browser blocks it.

A modern CSP looks something like:

Content-Security-Policy:
  default-src 'self';
  script-src 'self' 'nonce-abc123' 'strict-dynamic';
  style-src 'self' 'unsafe-inline';
  img-src 'self' data: https:;
  frame-ancestors 'none';
  base-uri 'self';

Key concepts:

CSPs that allow 'unsafe-inline' for scripts are mostly security theater — that's the directive that lets ANY inline script run, including injected XSS payloads. Modern CSPs use nonces or hashes instead.

Why it matters for AEO

Like HSTS, CSP contributes indirectly to EEAT — well-secured sites read as more trustworthy to both Google and AI engines. A CSP that survives security scrutiny (e.g., a clean Mozilla Observatory grade) shows up as a baseline-trust signal in audits that some LLM training corpora include.

Direct impact: CSP doesn't change how AI engines parse content. But misconfigured CSPs can break JSON-LD insertion (rare) or block legitimate analytics, which can knock other AEO signals offline.

What b/cited does about it

The audit treats CSP as a medium-impact lever: requires real effort to implement (especially with React/Next.js), but the EEAT trust signal is meaningfully better than the no-CSP baseline.

[ Related ]