No signup for basic results

Free GDPR cookie consent checker

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.

Checks initial HTMLBanner, CMP, script references, policy link.
Built for triageFind gaps before a buyer, DPO, or regulator does.
No fake certaintyAutomated results are a first pass, not legal advice.

Live free scan

Check your site now

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.

Open full checker

Search-intent answer

What does a GDPR cookie consent checker tell you?

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

What a compliant cookie consent banner needs

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.

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.

Equally visible accept, reject, and settings paths

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.

Specific purposes and named vendors

The banner and linked policy should explain what each category does, which vendors receive data, and why storage or access is requested.

Withdrawal that works after the first visit

Visitors need a persistent way to reopen choices and withdraw consent, and tag firing must actually change when consent is withdrawn.

Evidence for customers and auditors

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

What to test after the static scan

These checks are not automated results. Use a browser and your own consent records to investigate them.

  • Check network requests and browser storage before any choice. A script reference in HTML does not prove that tracking executed.
  • Test accept and reject in separate clean browser sessions, recording the region and banner version used.
  • Read the purposes and vendor list. Inspect category defaults and whether visitors can choose each optional purpose separately.
  • Reopen preferences and withdraw consent. Record whether later requests and storage change; the static scan cannot test this.
  • Compare the observed choice with your consent records and tag-manager configuration. Public HTML cannot reveal those records.
  • Repeat after a redesign or tag change. Keep dated screenshots, network captures and storage snapshots with their limitations.

Honest limits

Is a free cookie scanner enough? What this scan cannot prove

The checker fetches initial HTML without executing JavaScript or using your browser session. Four things sit outside that view:

  • Geo-variant banners. Regional behavior may differ. A scan from outside a region cannot establish what visitors within that region experience.
  • What happens after the choice. Whether “reject” actually stops tags, whether consent state persists across visits, whether a widget re-fires on scroll — that is post-choice behavior, and it is where most real findings live.
  • Wording quality. Purpose specificity, named vendors, granular category toggles: visible only to a person reading the banner and the policy side by side.
  • Your records. No scan can see which consent states you stored, when, against which banner version. That evidence trail is the part buyers and auditors actually ask for.

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

Turn the scan into an audit trail customers can trust

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 toolkit

For teams that need evidence, owners, and retesting steps after the free scan.

FAQ schema included

Free GDPR cookie consent checker FAQ

Is this free GDPR cookie consent checker legal advice?

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.

Can an automated checker prove I am GDPR compliant?

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.

What does the checker look for?

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.

What should I fix first if the checker finds gaps?

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.

Do I need a cookie banner if I only use analytics?

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.

Is a free cookie scanner enough to find my consent gaps?

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.