Docs Security
Clickjacking protection
Checks that other sites cannot load your page inside a frame, using X-Frame-Options or a CSP frame-ancestors rule.
What it checks
It passes when the homepage sends an X-Frame-Options header with any value, or when its Content Security Policy contains a frame-ancestors rule.
The policy can come from the header or a meta tag. Note that browsers ignore frame-ancestors in a meta tag, so to be protected in practice, send it as a header.
- PassX-Frame-Options or frame-ancestors is set.
- FailNeither is set, so any site can frame the page.
Why it matters
In a clickjacking attack, another site loads your page in a frame the visitor cannot see and lines up its own button over one of yours. The visitor thinks they are clicking one thing and clicks yours instead, for example a buy, delete or share button while logged in.
How to fix it
Send X-Frame-Options with SAMEORIGIN or DENY, or a CSP frame-ancestors rule that only allows your own site. frame-ancestors is the newer option and lets you list partner sites if your pages are meant to be embedded somewhere.
Platform notes
WordPress sends X-Frame-Options on its login and admin pages, but not on the public homepage. Add it in server config or with a security header plugin.
Add the header with a Transform Rule that modifies response headers.
Use add_header on Nginx or Header always set on Apache.
Set it in next.config.js headers, vercel.json, or a Netlify _headers file.
These platforms control the response headers on their own hosting, so there is usually no setting for this header in the site editor. If you need it, ask the platform's support what your plan allows.
Your report shows what this check found on your site. Pro shows the exact fix for your site. See pricing.
Free, about 30 seconds, with every other check included.