Trust fix guide
Privacy Policy Found in Page Content, But No Dedicated Page
Privacy policy text was found in the page body or footer, but no dedicated /privacy page exists. For GDPR/CCPA compliance and user trust, create a standalone Privacy Policy page.
Issue ID: TRUST-PRIVACY-003
Severity: medium
Impact: High
Effort: M
Use this article when
- You need deeper remediation guidance than the issue card can show.
- You want CMS-specific steps before handing the fix to a developer.
- You want a repeatable re-check path after shipping the change.
What this issue is
Privacy policy text was found in the page body or footer, but no dedicated /privacy page exists. For GDPR/CCPA compliance and user trust, create a standalone Privacy Policy page.
Why it matters
Privacy policy text was found in the page body or footer, but no dedicated /privacy page exists. For GDPR/CCPA compliance and user trust, create a standalone Privacy Policy page. This affects buyer confidence and whether a visitor feels comfortable contacting or buying from you.
How we detect it
- FreeSiteAudit flags this issue when the rule for TRUST-PRIVACY-003 fails and the page evidence points to Dom body, Url probe.
- Typical evidence looks like: Privacy policy text detected in page content.
Evidence examples
Privacy policy text detected in page content
No Privacy Policy page found at common URLs
How to fix it
- 1Create a standalone Privacy Policy page at /privacy or /privacy-policy
- 2Link to it from the footer on every page
- 3Cover data collection, cookies, and third-party sharing
How to re-check it
- Confirm a dedicated Privacy Policy page exists and is linked from footer