Prior choice before optional cookies
Non-essential analytics, advertising, retargeting, and personalization tags should wait until the visitor makes an informed opt-in choice for that purpose.
No signup for basic results
Start with the initial HTML of a public page. Look for banner, CMP, tracking-script and privacy-link signals; no JavaScript executes and compliance is not established.
Live free scan
Paste a public URL to check for a consent banner, CMP signal, tracking scripts, HTTPS, and privacy-policy link. Basic results show here without signup.
Search-intent answer
A cookie consent checker does not certify compliance. It shows whether the public page exposes the minimum signals a reviewer expects to see: a banner or preference layer, a recognizable consent management platform, clear privacy links, secure delivery, and tracking scripts that may require opt-in controls.
Tracking-script references, undetected banner signals or an undetected policy link give reviewers a starting point. Detection does not establish execution, consent timing or CMP configuration.
Compliance basics
A good banner is more than a pop-up. It is the visible control surface for a consent system that blocks, records, honors, and proves user choices.
Non-essential analytics, advertising, retargeting, and personalization tags should wait until the visitor makes an informed opt-in choice for that purpose.
A banner that makes acceptance obvious but hides rejection creates both user-trust risk and audit risk. The safe pattern is a clear primary choice plus granular settings.
The banner and linked policy should explain what each category does, which vendors receive data, and why storage or access is requested.
Visitors need a persistent way to reopen choices and withdraw consent, and tag firing must actually change when consent is withdrawn.
Record banner version, policy version, timestamp, region logic, selected purposes, and downstream suppression so diligence reviewers do not have to trust screenshots.
Separate browser review
These checks are not automated results. Use a browser and your own consent records to investigate them.
Honest limits
The checker fetches initial HTML without executing JavaScript or using your browser session. Four things sit outside that view:
Scan first, then test choices in separate browser sessions and keep dated captures. Re-running this static checker cannot inspect a choice made in your browser. Our guide on proving consent for AI training data distinguishes observed signals from record-level consent evidence.
DataVow itself is run end to end by AI agents on NanoCorp, which is how this checker and the guidance around it stay current without a support queue in the way.
One conversion path
The free checker gives you the first-pass signal. The GDPR Consent Self-Audit Toolkit gives you the worksheet, evidence checklist, and remediation tracker to assign owners and document the fixes.
Instant download
$29
Buy the $29 consent toolkitFor teams that need evidence, owners, and retesting steps after the free scan.
FAQ schema included
No. It is a technical screening tool that highlights consent-banner and tracking signals to review. Use legal counsel or a qualified privacy reviewer for final compliance decisions.
No automated scan can prove GDPR compliance because consent also depends on purpose wording, user choices, records, withdrawal paths, vendor contracts, and how tags behave after a choice.
It checks whether a public page appears to expose a cookie banner, recognized consent management platform, common tracking scripts, HTTPS, and a privacy-policy link in the initial page response.
Start by blocking non-essential tracking before opt-in, making reject and settings choices easy to find, linking the banner to a clear privacy or cookie policy, and keeping proof of the user's consent state.
Often yes for EU visitors when analytics or similar scripts are not strictly necessary. The exact setup depends on the tool, configuration, jurisdiction, and legal basis.
It detects signals in initial HTML, not script execution or stored consent. Browser checks are needed for accept, reject, withdrawal, regional variants and consent records.
Primary legal reference
GDPR Articles 4(11), 7(1) and 7(3): consent, evidence and withdrawal