The Permissions-Policy HTTP header is missing, allowing unrestricted access to sensitive browser APIs.
By Seoxpert Editorial · Published
Without the Permissions-Policy header, third-party scripts on your site may access sensitive APIs like geolocation, camera, or microphone without user awareness. This can increase privacy risks for users and potentially expose your site to security vulnerabilities, which may erode user trust and indirectly impact SEO.
Leaving this unresolved allows third-party scripts unrestricted access to powerful browser features, increasing privacy and security risks.
An automated crawler checks HTTP response headers and flags pages where the Permissions-Policy header is absent.
Apache: Add Permissions-Policy header
Header set Permissions-Policy "geolocation=(), microphone=(), camera=()"Nginx: Add Permissions-Policy header
add_header Permissions-Policy "geolocation=(), microphone=(), camera=()";Express.js: Set Permissions-Policy header
app.use((req, res, next) => {
res.setHeader('Permissions-Policy', 'geolocation=(), microphone=(), camera=()');
next();
});It is an HTTP header that controls which browser features and APIs can be used by the page and its embedded resources.
No, but it can impact user trust and security, which are important for overall site quality.
Restrict features your site does not use, such as geolocation, camera, and microphone, to reduce security risks.
Use browser developer tools or online header checkers to inspect the HTTP response headers for your pages.
Run a scan to see if Missing Permissions-Policy Header affects your pages.
Scan my website →