How to fix x frame options weak on Webflow

Steps for Webflow

1. Webflow does not provide a UI to set custom HTTP response headers for standard hosted sites.
2. If your Webflow site is published to a custom domain and proxied through Cloudflare (common setup): log in to Cloudflare → your domain → Rules → Transform Rules → Modify Response Header → Add Rule → set Header Name: X-Frame-Options, Value: DENY, Action: Set.
3. Also add a second rule for Content-Security-Policy with value: frame-ancestors 'none';
4. If not using Cloudflare: contact Webflow support to report the issue, or export your site and host it on a server where you control headers (e.g. Netlify — see below).
5. For Webflow exported sites on Netlify: add a netlify.toml file to the repo root with the headers block shown in the code snippets below.

What is x frame options weak?

The `X-Frame-Options` HTTP response header tells browsers whether your website is allowed to be loaded inside an `<iframe>`, `<frame>`, or `<object>` on another site. There are two safe values: `DENY` (no framing allowed anywhere) and `SAMEORIGIN` (only your own site can frame your pages). A third value, `ALLOW-FROM`, was once supported to whitelist a specific external domain — but it is now obsolete, ignored by most modern browsers, and therefore provides no real protection. When this header is missing, set to an unsupported value like `ALLOW-FROM`, or combined with `SAMEORIGIN` in a way that browsers parse inconsistently, your pages are effectively unprotected against framing by attackers.

Without a properly enforced `X-Frame-Options` header, attackers can silently embed your store's checkout, login, or account pages inside invisible iframes on malicious websites — a technique called clickjacking. A shopper thinks they're clicking a button on the attacker's page, but they're actually clicking your hidden iframe: entering payment details, changing account settings, or completing unwanted purchases. This is a real theft and fraud vector that can lead to chargebacks, customer complaints, regulatory scrutiny under PCI-DSS, and loss of consumer trust. Search engines like Google also consider security posture signals when evaluating site quality; a site known to be compromised through clickjacking can suffer ranking and reputation damage. Fixing this header takes under 30 minutes and closes the vulnerability entirely for all modern browsers.

See the complete X frame options weak guide for every platform and the full background.