WordPress fix guide
Weak Content Security Policy on WordPress
The Content-Security-Policy header is present but uses unsafe directives (unsafe-inline, unsafe-eval, or wildcard sources) that significantly reduce its effectiveness.
Issue ID: SEC-CSP-QUALITY-001Severity: moderateEffort: M
Why this matters
The Content-Security-Policy header is present but uses unsafe directives (unsafe-inline, unsafe-eval, or wildcard sources) that significantly reduce its effectiveness. This affects browser trust signals and whether visitors feel safe submitting contact details.
WordPress fix path
How to fix this on WordPress
Use the page editor, theme, or SEO tooling depending on where this issue lives.
- 1Inspect the page and theme output.
- 2Apply the fix in the most direct place.
- 3Publish and validate with a re-audit.
After you fix it
- ✓Check CSP header and confirm no unsafe-inline, unsafe-eval, or wildcard sources
Same fix, other platforms
Fix weak content security policy on a different CMS
Other fixes
More WordPress fixes
See every WordPress issue on your site
This is one issue of many the full audit checks. Run a free scan to see what else might be holding your site back.
Run Free Audit