Skip to content
CitationLab
Back to home

Consent check

Is your website’s tracking legal?

A free consent check shows how cookies, analytics tools and ad tags behave before consent and after “reject all”. Test one page in a real browser and get practical findings about your cookie banner and Google Consent Mode v2.

Read the consent and tracking guide
  1. Your website
  2. Free preview
  3. Full report

02Consent requirements

When do cookies and tracking need consent?

In the EU/EEA, national rules implementing the ePrivacy Directive regulate storing or accessing information on a user's device. These rules extend beyond cookies. Where consent is required, it must meet the GDPR standard: freely given, specific, informed and unambiguous. Check the rules that apply to your market.

An active choice
Visitors must choose for themselves. Pre-ticked boxes, silence or continued browsing do not provide valid consent.
Understandable information
Explain the purposes of tracking and who uses the information. A vague reference to a “better experience” is not enough.
Choices by purpose
Consent must relate to specific purposes. Separate analytics from marketing, for example, so visitors can choose what they want.
A real option to say no
Rejecting should be as easy as accepting. Do not hide rejection behind extra clicks or make it harder to find.
Consent before relevant tracking
Technologies that require consent must be managed before storing or accessing information. The banner needs to control the tags.
The ability to change your mind
Withdrawing consent must be as easy as giving it. Keep consent settings accessible.

Your organisation must be able to demonstrate consent; this test does not check consent logs. A limited exemption applies to technology strictly necessary to provide a service the user explicitly requests, and to transmitting communications. Analytics or advertising being useful to a business does not make it strictly necessary. Processing personal data also requires a separate GDPR assessment.

03From banner to tags

Common issues a cookie check can reveal

Problems often arise where the consent platform, website and tag configuration meet. Check the first visit as well as what happens after a choice.

Analytics starts too early
GA4 or another analytics tool sets cookies that require consent before the visitor responds. A tag may sit directly in the page template even when GTM is configured correctly.
Rejecting only dismisses the banner
The banner disappears, but marketing cookies or tags continue. Check what “Reject all” actually does in a fresh browser session.
Unequal choices in the banner
A prominent accept button combined with hidden rejection, unclear categories or preselected boxes weakens the visitor's ability to choose freely.
Only Google receives the choice
Google Consent Mode controls the behaviour of Google tags. Meta Pixel, embedded videos and other providers need their own consent configuration or blocking where required.
Settings differ between pages
Landing pages, forms or a new plugin may introduce tracking that does not follow the main site's setup. Check representative pages individually.

05Use the report

How to follow up your result

Start with the observed findings and give whoever owns your consent setup access to the full report. A practical follow-up can look like this:

Find where tracking originates
Connect cookies and requests to GTM, page templates, plugins or embedded content. Clarify their purposes and whether the technology needs consent.
Fix the consent flow
Update the banner's choices, tag conditions and Google signals. Check that withdrawing consent affects subsequent tracking too.
Test more situations
Run another check after making changes. Also manually test landing pages, mobile devices, fresh browser sessions and relevant regions.
Document and maintain
Record changes and responsibilities. Repeat the check when you change your CMP, tags, plugins or website content.

06Scope

A technical check is not legal approval

The result covers one URL and the browser sessions tested. Content behind a login, other pages, regional variations or tags triggered by scrolling and other actions may behave differently. If the consent platform is not recognised, some checks may be skipped. Unknown providers need review; they are not automatically unlawful.

The check does not assess your entire privacy policy, data processing agreements, consent records, legal bases or information forwarded on the server without being visible in the browser. A good result describes what the test observed; it does not certify that all tracking is lawful. Use technical findings alongside an assessment of your own data processing.

Sources and rules

Sources reviewed on 1 October 2026.

07FAQ

Questions about consent checks and cookies

Your feedback

Was this page helpful?

Your feedback helps us improve this guide.

Need help fixing the findings?

We review your banner, tag triggers and Google Consent Mode v2, then test what changes before consent and after rejection.