How to Fix a Missing Permissions-Policy Header on Your Site
Your homepage is served without a Permissions-Policy response header, so browsers let any page or embedded iframe on your site request powerful features such as the camera, microphone or location. By the end of this guide your homepage, and ideally every page, will send a Permissions-Policy header that disables the browser features you don't use while keeping the ones you need.

Why it matters
Permissions-Policy limits the damage if a third-party script, ad or compromised iframe on your site tries to access the camera, microphone, location, USB devices or payment APIs. With features set to (), the browser refuses those requests on your pages. It has no direct effect on rankings or AI answers, which is why the impact is low, but it costs little to add and is one of the headers security scanners and procurement checklists look for.
What you need
Step-by-step fix
List the browser features your site really uses
Before you block anything, check which features your pages or embeds rely on. Common ones:
- geolocation: store locators, "near me" maps
- payment: Payment Request API buttons such as Apple Pay or Google Pay in some checkout widgets
- camera / microphone: video chat, ID verification, voice search
- fullscreen: YouTube or Vimeo embeds
Anything not on your list can be set to an empty allowlist ().
Write your policy value
Each directive is feature=allowlist. com")` also allows a specific embedded origin. Separate directives with commas.
Use only real feature names, because browsers log console warnings for unknown ones. The deprecated interest-cohort (FLoC) is one example of a name you should not include.
camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=()
Add the header in Nginx
Put the directive inside the server { } block that serves your HTTPS site. Include always so the header is also sent on error and redirect responses. Test the config and reload Nginx.
add_header Permissions-Policy "camera=(), microphone=(), geolocation=(), payment=(), usb=()" always; # then run: # sudo nginx -t && sudo systemctl reload nginx
Or add it in Apache / .htaccess
Apache needs mod_headers enabled (sudo a2enmod headers on Debian/Ubuntu). Add the line to your VirtualHost or to the .htaccess file in your site root. Shared hosts running Apache or LiteSpeed usually accept this in .htaccess.
<IfModule mod_headers.c> Header always set Permissions-Policy "camera=(), microphone=(), geolocation=(), payment=(), usb=()" </IfModule>
Or set it in your framework or hosting config
js. js server. json instead.
On Netlify or Cloudflare Pages, add the rule to a _headers file in the publish directory.
// next.config.js
module.exports = {
async headers() {
return [
{
source: '/(.*)',
headers: [
{
key: 'Permissions-Policy',
value: 'camera=(), microphone=(), geolocation=(), payment=(), usb=()',
},
],
},
];
},
};Purge caches and test the features you kept
Clear your CDN and page cache so the new header reaches visitors. Then click through the pages that use location, payments, video embeds or camera access, and make sure they still work. If something breaks, open DevTools Console.
A blocked feature shows a "permissions policy" violation message naming the feature.
Confirm the header on your homepage
Request the final homepage URL (after any http→https or www redirects) and look for the header. The audit reads the homepage response, so this is the response that must carry it.
curl -sIL https://example.com | grep -i permissions-policy
Platform-specific notes
WordPress
The cleanest option is the server config (Nginx or .htaccess, above), so cached pages also get the header. If you can't edit those, add `add_action('send_headers', function () { header('Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=()'); });` to a small custom plugin or your child theme's functions.php. Full-page caches served before PHP runs may skip this, so verify with curl. Security header plugins such as Headers Security Advanced & HSTS WP can also set it.
Cloudflare
Go to Rules > Overview > Create rule > Response Header Transform Rule. Match all incoming requests, then choose Set static: header name Permissions-Policy and your policy as the value. Deploy the rule. This works whatever your origin server is, as long as the hostname is proxied (orange cloud).
Shopify
Shopify-hosted storefronts don't let merchants add custom HTTP response headers, and the Nginx snippet doesn't apply because you have no server access. A meta tag cannot replace this header. Unless you run a headless storefront on your own host (for example Hydrogen on Oxygen or Vercel, where you can set headers in code), treat this warning as an accepted platform limitation.
Wix / Squarespace
Neither platform exposes response-header settings on standard plans. Custom headers are only possible if a proxy you control, such as Cloudflare in proxy mode, sits in front of the site.
Vercel / Next.js
The vercel.json "headers" array (source "/(.*)", key "Permissions-Policy") and next.config.js headers() both work on Vercel. On self-hosted Next.js, use next.config.js or your reverse proxy. Static exports (output: 'export') ignore headers(), so set the header on the host instead.
Check that it worked
✅ How to verify
- Run `curl -sIL https://example.com | grep -i permissions-policy` and confirm the line appears on the final 200 response.
- Open DevTools > Network, reload, click the document request and find permissions-policy under Response Headers.
- Scan the homepage at securityheaders.com and check that Permissions-Policy is listed as present.
- Re-run the audit and confirm the check reports 'Permissions-Policy header is set.'
⚠️ Common mistakes
- Sending the old Feature-Policy header instead of Permissions-Policy. It uses a different syntax and doesn't satisfy the check.
- Disabling geolocation, payment or fullscreen without testing, which breaks store locators, wallet checkout buttons or embedded video.
- Adding the header in an Nginx server block when a location block has its own add_header lines, so the homepage response never includes it.
- Using Feature-Policy-style syntax such as `camera 'none'` or `geolocation 'self'` inside Permissions-Policy. The correct form is `camera=()` and `geolocation=(self)`.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
What is the difference between Permissions-Policy and Feature-Policy?
Permissions-Policy is the renamed, current version of Feature-Policy with a structured syntax (camera=()). Modern browsers read Permissions-Policy. Feature-Policy is legacy and only worth keeping if you specifically need to support very old browsers.
Can I set Permissions-Policy with a meta tag?
No. Browsers only honour Permissions-Policy when it is sent as an HTTP response header. For individual iframes you can additionally use the allow attribute, for example <iframe allow="fullscreen">, but that doesn't replace the header.
Does Permissions-Policy affect SEO?
Not directly. Search engines don't rank pages on it. It is a hardening header that limits what scripts and embeds can access in visitors' browsers.
What is a safe default Permissions-Policy?
For most marketing sites, camera=(), microphone=(), geolocation=(), payment=(), usb=() is safe. Switch any feature your site actually uses to (self), or to (self "https://trusted.example.com") if an embed needs it.
How to Fix Vulnerable JavaScript Libraries on Your Site
How to Fix Missing Clickjacking Protection (frame-ancestors)
How to Fix Server Version Disclosure in HTTP Headers
How to Fix Cookies Missing the SameSite Attribute
How to Add Subresource Integrity (SRI) to CDN Scripts
How to Fix Cookies Missing the HttpOnly Flag on Your Site