Security fix guide
Google Consent Mode Not Detected
Google tags are present but Google Consent Mode v2 is not configured. Consent Mode enables privacy-safe measurement and may be required for EU compliance.
Issue ID: SEC-CONSENT-MODE-001
Severity: minor
Impact: Low
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
Google tags are present but Google Consent Mode v2 is not configured. Consent Mode enables privacy-safe measurement and may be required for EU compliance.
Why it matters
Google tags are present but Google Consent Mode v2 is not configured. Consent Mode enables privacy-safe measurement and may be required for EU compliance. This affects browser trust signals and whether visitors feel safe submitting contact details.
How we detect it
- FreeSiteAudit flags this issue when the rule for SEC-CONSENT-MODE-001 fails and the page evidence points to Dom body.
- You can usually confirm this by checking the page source or the relevant page settings inside your CMS.
Evidence examples
Check the affected page source, rendered output, or relevant CMS setting to confirm the missing or incorrect element.
How to fix it
- 1Implement Google Consent Mode v2 with your CMP
- 2Set default consent states (denied) before loading Google tags
- 3Update consent state when users make choices
How to re-check it
- Check Google Tag Assistant to confirm Consent Mode is active
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.