AuditLabHQ

Consent Audit · Public-signal precheck

See whether Consent Mode is visibly wired on the public site.

This audit checks homepage-level implementation signals: CMP traces, Google tags, gtag('consent') calls, denied defaults, update calls and common timing mistakes.

CMP · Google tags · consent default · consent update · sequencing

Free · No email required · Results in seconds

AuditLabHQ only reads public page signals. Nothing is modified.

Read the guides →

Example audit

Consent public-signal precheck

82/100 B

Example severity: medium

Homepage

PASS

Public HTML was inspected.

CMP

PASS

A consent platform signal is visible.

Google tags

PASS

Google tagging is present.

Consent API

WARN

The visible lifecycle needs validation.

Runtime timing

NOT VERIFIED

Confirm in GTM preview or devtools.

5 signal groups CMP, Google tags, consent calls, denied defaults and sequencing clues.
Fast scan Useful before GTM preview, Tag Assistant or a deeper browser runtime trace.
PDF option A short decision brief or a fuller evidence and implementation report.

Method

What this audit can and cannot tell you

What it looks for

  • CMP vendor or banner signals in the homepage HTML and first-party scripts.
  • GTM or gtag presence plus visible Google tag IDs.
  • consent default and consent update calls.
  • Denied defaults for analytics and advertising storage keys.
  • Basic sequencing risks such as config before consent default.

Useful signals

  • Whether the homepage publicly exposes a CMP and Google consent bootstrap.
  • Whether denied defaults and update calls are visible in source-level signals.
  • Whether basic sequencing issues look likely before deeper validation.

Limits

  • It does not replace a full runtime trace in GTM preview or browser devtools.
  • It cannot guarantee what every event sends after every user journey.
  • It is strongest for homepage-level public implementations, not private app flows.

Consent Mode guides

Understand, implement and debug the same signals the audit checks

Browse all consent audit guides →

Google Consent Mode v2 explained

Signals, implementation choices and the minimum technical sequence.

Consent Mode default denied

Set the initial state early and avoid sequencing mistakes.

Consent Mode in Google Tag Manager

Consent Initialization, CMP updates and tag-level controls.

Consent Mode debugging checklist

Test defaults, updates, requests, storage and revisit flows.

CMP vs Google Consent Mode

Understand each component’s role and validate the handoff.

FAQ

Does this prove my setup is legally compliant?

No. It audits technical implementation signals, not legal compliance or consent wording quality.

Does this replace GTM preview?

No. Think of it as a fast external audit before the deeper runtime debugging pass.