Severity: HighOwner: CMP adminTime to fix: 30-90 min
No consent banner
Restore or deploy a first-layer consent banner before any optional tracking or storage begins.
Covers: no_consent_banner, no_consent_banner_cmp_signals
Why this matters
If non-essential cookies or trackers can run without any consent interface, users have no first-layer control and no lawful way to refuse processing at collection time.
How to verify manually
- Open the homepage in incognito with cache disabled.
- Wait for late-loading scripts to finish and confirm whether any banner appears.
- Test on desktop and mobile viewports because some banners are viewport-specific.
Typical root causes
- CMP script missing from production template or blocked by CSP.
- Banner intentionally disabled for some geographies or routes.
- Caching or theme changes prevent the banner container from rendering.
GTM fix
- Deploy a CMP tag in GTM that initializes before analytics and marketing tags.
- Pass CMP consent states into GTM consent checks.
- Ensure default state is denied until explicit action by the user.
WordPress fix
- Install a CMP plugin such as CookieYes or Complianz.
- Run the setup wizard to classify cookies and enable prior blocking.
- Ensure the banner appears before any non-essential scripts are loaded.
Generic fix
- Add a first-layer consent banner that appears on first visit.
- Require an explicit user action before enabling non-essential processing.
- Persist and honor the choice across pages and subsequent visits.
How to confirm the fix worked
- Clear cookies and re-open the site to confirm the banner appears immediately.
- Reject optional cookies and verify the site remains usable.
- Run a fresh scan and confirm the missing-banner finding is gone.
Next step
Re-scan after deployment to confirm that the runtime behavior changed, not just the banner copy.