What is clickjacking protection?
Rubric check: clickjacking protection (check id hdr_frame)
Clickjacking protection is a header that stops other sites showing your page inside a hidden frame to trick people into clicking. Rubric flags it when your home page sends neither X-Frame-Options nor a CSP frame-ancestors rule. It is a security step, not a search factor.
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.
Why it matters for SEO
Search engines don't rank on this header, and it doesn't stop them crawling or showing your pages. It protects logged-in visitors and forms from being tricked inside someone else's frame. If you deliberately let partner sites embed your pages, keep that working by allowing those sites in frame-ancestors.
Does this matter for ChatGPT and AI Overviews?
AI tools fetch your page directly, not inside a frame, so this header doesn't affect whether they can read or cite you. Rubric counts it as a small sign of a maintained site, inside a capped allowance shared with the other security header checks.
How Rubric scores it
MinorMinor checks cost a quarter to a half of a standard check when they fail.
Why this tier: A 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 109 of 300 sites where Rubric could judge it (36%). That is 101 of 287 judged sites in Rubric's 313-site test set and 8 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.
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 17 of its findings by hand and 1 was wrong (5.9%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.
Holdout test 5 (sites the check had never seen): 0 of 30 findings judged wrong.
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
WordPress already sends X-Frame-Options: SAMEORIGIN on its login and admin pages, but not on the public site. Add it site-wide with a security headers plugin, your host's control panel, or on Apache in .htaccess:
Header always set X-Frame-Options "SAMEORIGIN"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 you can't add your own. A meta tag doesn't work for this rule. If Rubric reports it on a Shopify store, check whether a proxy or CDN on your domain drops Shopify's headers. If nothing does, there's no setting to change.
Webflow
Webflow sets the response headers for sites it hosts, and standard plans have no setting for custom headers. Browsers ignore frame-ancestors in a meta tag, so it must be a header. Ask Webflow support, or leave this minor check.
Custom code
Send one of these on every page. The CSP rule is the modern option:
add_header Content-Security-Policy "frame-ancestors 'self'" always;
add_header X-Frame-Options "SAMEORIGIN" always;If you already send a Content-Security-Policy, add frame-ancestors 'self' to it rather than sending a second policy.
On Cloudflare (one rule covers every page):
- In the Cloudflare dashboard, open your domain and go to Rules > Overview.
- Choose Create rule > Response Header Transform Rule and apply it to All incoming requests.
- Add Set static: header
X-Frame-Options, valueSAMEORIGIN. - Select Deploy, then re-run the audit.