ubricHelp

What is a missing CSP header?

Rubric check: missing CSP header (check id hdr_csp)

A missing CSP header means your home page sends no Content-Security-Policy, the rule that tells browsers which scripts, styles and frames the page may load. It is a security step, not a search factor, so Rubric counts it as minor. Response headers are set once for the whole site, in your server, host or CDN settings (on Cloudflare, a Transform Rule), so this is one site-wide fix, not a page-by-page one.

Free, no card. Your report opens with this check first.

Why it matters for SEO

Google and Bing don't rank pages on security headers. A Content-Security-Policy protects your visitors from injected scripts, which is how many hacked sites end up serving spam that search engines then penalise. That is the real search risk: a compromised site, not a missing header.

Does this matter for ChatGPT and AI Overviews?

There's no public evidence that AI search tools check security headers before citing a page. Rubric includes this check as a small sign that a site is maintained, and it shares a capped allowance with the other security header checks, so missing all of them never costs much.

How Rubric scores it

MinorMinor checks cost a quarter to a half of a standard check when they fail.

Why this tier: A basic security step that shows the site is maintained; not a search factor.

It is read from your home page's response headers, and compared with a few other pages the crawl already fetched. Headers are set once for the whole site, so this is a site-wide finding.

Every Rubric score starts at 100. When this check fails, it takes up to 3 points off. Even one failing page costs at least 1.5 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.

This is one of 4 security header checks. Together they can take off at most 9 points, so a site isn't marked down many times for one kind of problem.

All the minor checks share one limit: together they can take off at most 25 points, however many of them fail.

This check doesn't cap your score. It only takes off its own points.

From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).

How common it is

Found on 153 of 300 sites where Rubric could judge it (51%). That is 144 of 287 judged sites in Rubric's 313-site test set and 9 of 13 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.

51% of the sites Rubric could judge have this problem. Check yours.

Free, no card. Your report opens with this check first.

How accurate the check is

Lab test: passed. On test pages built with this problem, it caught 3 of 3. On clean test pages, it stayed quiet 2 of 2 times. (Engine build bbcec7c.)

Real sites: people checked 34 of its findings by hand and 2 were wrong (5.9%). Last checked 14 Nov 2026.

Holdout test 5 (sites the check had never seen): 0 of 50 findings judged wrong.

Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.

How to fix it

WordPress

  1. Start small. A policy of upgrade-insecure-requests changes nothing visible and won't break plugins.
  2. Add it with a security headers plugin, your host's control panel, or on Apache with this line in .htaccess: Header always set Content-Security-Policy "upgrade-insecure-requests"
  3. For a stricter policy, use Content-Security-Policy-Report-Only first and watch for blocked scripts before you enforce it.

Behind Cloudflare? Set it once there instead, for every page at the same time: see the Cloudflare steps under Custom code.

Shopify

Shopify sets the storefront's response headers and doesn't let you add your own. Rubric also accepts a CSP meta tag:

  1. Go to Online Store > Themes > Edit code and open theme.liquid.
  2. Inside <head>, add <meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests">.
  3. Save, then check the storefront still loads its apps and payment buttons.

Webflow

  1. Go to Site settings > Custom code > Head code.
  2. Add <meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests">.
  3. Save and publish. Test any embeds or third-party scripts before you tighten the policy further.

Custom code

Send the header from your server or CDN. Nginx:

nginx
add_header Content-Security-Policy "upgrade-insecure-requests" always;

To build a stricter policy, send Content-Security-Policy-Report-Only with your planned rules, collect the reports, then switch to the enforcing header.

On Cloudflare (one rule covers every page):

  1. In the Cloudflare dashboard, open your domain and go to Rules > Overview.
  2. Choose Create rule > Response Header Transform Rule and apply it to All incoming requests.
  3. Add Set static: header Content-Security-Policy, value upgrade-insecure-requests.
  4. Select Deploy, then re-run the audit.

More security checks · The full AI SEO glossary

Free, no card. Your report opens with this check first.