One-page decision brief
Score summary, top risks and the first validation actions to share with a decision-maker.
Consent Audit
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.
Useful for a fast first pass before you open GTM preview, Tag Assistant or a full browser session trace.
Quick: one-page decision brief. Full: evidence, implementation examples and a verification plan.
No account
No install
Results in seconds
Free scan preview
Run a free scan to see the public-signal score, top findings and next validation steps here...
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.
Evidence and implementation report
Detailed findings, consent signal evidence, implementation examples and a retest checklist.
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 defaultandconsent updatecalls.- 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
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.