AMP is "HTML with some restrictions". Speaks nothing of HTTP (otherwise they could've done the right thing and added a "text/html;amp=1" content-type). In the

AMP is "HTML with some restrictions". Speaks nothing of HTTP (otherwise they could've done the right thing and added a "text/html;amp=1" content-type). In theory this should still work: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-... But I doubt that Google's AMP cache will respect existing headers (the very nature of the cache stuff means that they won't, but what they will do to non-cache headers on an item is undefined AFAIK and so they will probably just strip them).