Finds the analytics, pixels, fonts and embeds that fire before your cookie banner is answered - in the source, before you deploy. 24 rules.
What it does for free
Audit the open file against all 24 rules
Audit just the lines you select
Reopen the last report, with line numbers and severity
Read every rule that ships inside, in plain English
With a licence
Audit the whole client repository — One pass over every file in the project instead of the one that happens to be open.
Dated evidence report (CSV, JSON or HTML) — Writes the findings to a file you can hand to the client or keep with the release.
Re-audit on every save — Catches the tag someone pastes back in three sprints from now.
Machine-readable output for CI — Writes a JSON report so a pipeline can fail the build on a new violation.
Apply the mechanical fixes — Adds the CMP blocking attributes, flips consent defaults to denied and swaps YouTube for youtube-nocookie, in place. Anything that needs judgement stays in the report.
$29 once, one licence key per person or team seat. Consent scanners are billed per domain every month (CookieYes $10-$55 per domain per month; Cookiebot near EUR 30 since it doubled its base price in August 2025) and only see the page once it is already live.