How to fix x frame options weak on Squarespace

Steps for Squarespace

1. Squarespace does not allow direct HTTP response header customisation for standard plans — headers are controlled at the platform infrastructure level.
2. Verify the current header value using DevTools (F12 → Network → document → Response Headers) or securityheaders.com.
3. If X-Frame-Options is missing or weak, route your custom domain through Cloudflare (set DNS to Cloudflare proxied), then in Cloudflare dashboard → Rules → Transform Rules → Modify Response Header → add X-Frame-Options = DENY for all requests.
4. Contact Squarespace support to report the missing header and request they apply it platform-wide.

X-Frame-Options: DENY

What is x frame options weak?

The X-Frame-Options HTTP header is a one-line instruction your web server sends to every visitor's browser telling it whether your store's pages are allowed to be loaded inside an iframe (a "page within a page") on another website. There are two safe values: DENY (no site, including your own, can frame your pages) and SAMEORIGIN (only pages on your own domain can frame them). A weak or absent value means any website on the internet can load your store inside an invisible or disguised iframe — a classic attack called clickjacking.

Clickjacking lets attackers overlay your real checkout or login page inside a transparent iframe on a fake site, tricking customers into clicking buttons they can't see — handing over payment details, credentials, or completing purchases they didn't intend. This is a direct revenue, fraud, and brand-trust risk. It also violates PCI-DSS requirements around protecting cardholder data environments and can expose you to legal liability if customers are defrauded through your site. Google's Safe Browsing program can flag sites involved in such abuse, which destroys organic search rankings overnight.

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