Google Consent Mode Check
Check if Google tags have technical consent mode signals visible and if denied/granted hints appear in the code.
Ideal for GA4, Google Ads, GTM and Consent-Mode QA.
Results
Technical pre-checking of a URL. For multiple URLs, templates and CSV exports, use the GDPR Tracking Audit.
Findings
Detailed hit
What the Google Consent Mode Check evaluated
The exam is deliberately fast and focused. It recognizes technical signals in headers, HTML, JavaScript and resources. Interactions with banners, login, forms and tag triggers should be additionally checked in the browser.
Keeping Consent Signals and Order Apart
Illustrative example · no measurement result of your website
gtag('consent', 'default', { analytics_storage: 'denied' });The example shows a single consensus key. Its occurrence in HTML neither proves a complete configuration nor that the default is executed before all tags. A later update and other consent types must be considered separately.
Then check the results in the browser.
- Check the initial Consent values before the first measurement event with the debug tools of your tag implementation.
- Compare the values after consent, rejection and revocation; check analytics_storage, ad_storage, ad_user_data and ad_personalization to match the tags used.
- Check the actual requests in the browser. A denied signal does not mean in every implementation that no request is sent at all.
What this check leaves open
Text patterns can also occur in comments or unexecuted configurations. A configuration set dynamically via CMP or Tag Manager may be missing from the static HTML. The result does not confirm legal admissibility.
Check Analytics Notices Separately →From individual check to GDPR tracking audit
A tool shows a concrete symptom. The audit checks up to 500 URLs, prioritizes tracking, consent and form risks, and provides export data.
Targeted deepening of GDPR tracking
Check which cookies a URL technically shows, whether tracking cookie candidates appear and which attributes such as Secure, HttpOnly or SameSite are set.
Before consentRecognize tracking and third-party candidates who are already visible in the initial delivered page before a user actively consents.
Third party third partiesFind well-known tracking services, external script hosts, and third-party integrations that are relevant to consent, privacy, and tag governance.
Storage & FingerprintingRecognize technical storage and access signals such as cookies, LocalStorage, SessionStorage, IndexedDB and fingerprinting candidates.
Consent UXCheck whether known consent management platforms and important banner signals such as rejection, settings and revocation are technically findable.
Web analysisCheck if a URL contains more frugal analytics candidates or marketing/tracking signals requiring consent.
Questions about Google Consent Mode Check
Is Consent Mode enough for GDPR compliance?
No. Consent mode is just a technical signal. CMP setup, legal basis, information obligations and tag release must be checked separately.
Why is granted critically mentioned?
An granted signal may be correct, but the default state must be checked manually, especially before active consent.
Is the individual check free of charge?
Yes. The standalone tools check a single URL. For larger crawls, complete tables and CSV export, the premium audit is planned.
Does the tool replace legal advice?
No. The tools provide technical pre-testing. Legal bases, contracts, information obligations and concrete consent flows must be subject to technical review.