Three rows that cover every site
The Consent Mode v2 table in our privacy index splits all 47,420 scored sites three ways:
- 2,104 (4.4%) had a working v2 signal observed.
- 23,301 (49.1%) ran Google tags with no Consent Mode signal.
- 22,015 (46.4%) had no Google products detected.
Those three add up to all 47,420. Nearly half the sample ran no Google tags we could detect.
That matters because a lot of consent advice is written as if every site runs Google. The review becomes "is Consent Mode set up?" For nearly half of these sites, that question has nothing to check.
What Consent Mode actually covers
Google's Consent mode overview describes it this way:
"Consent mode allows web and app developers to adjust tag and app SDK behavior based on user consent choices."
The tags that do the adjusting are Google's. The same page lists the products whose tags "contain built-in consent checks": the Google tag, Google Analytics, Google Ads, Floodlight and Conversion Linker. Its own checklist puts the rest on you:
"Ensure that Google tags and third-party tags behave according to the user's consent choice."
What a Consent-Mode-first checklist misses
On a site with no Google tags, a Consent Mode check has nothing to report. It can come back empty and look like a pass.
On a site that does run Google, it only speaks for Google's tags. Every other vendor on the page, from the social pixels to the chat widget, needs its own consent check. Consent Mode says nothing about any of them.
Where non-Google tags get their consent check
There are three places, and only two of them are in the tag manager:
- Tag Manager consent settings. Google's page says: "If you create tags that don't have built-in consent checks, you can add checks in Tag Manager using configuration in Advanced > Consent Settings."
- The consent platform's own blocking, for the tags it's set up to hold back.
- Neither of the above, for scripts loaded outside any tag manager. The Trackers That Never Pass Through Your Tag Manager shows how to find them.
The vendor-neutral test
The test that works on every site, Google or not, asks the same two questions the index records: what fired before anyone touched the banner, and what fired after a refusal.
- Open a private browser window with developer tools on the Network tab.
- Load your site and don't touch the banner. Note every request to an analytics or advertising domain.
- Click reject, then browse two pages.
- Note what still goes out.
It doesn't matter whose domain the request goes to. If it goes out before an answer or after a refusal, that tag needs a consent check.
What "no Google products detected" does not mean
It's detection language. It describes what the scanner observed on one first-visit page load. It isn't proof that no Google code exists anywhere on the site, and it says nothing about whether the site tracks or doesn't.
The point isn't that these sites are clean. It's that the Consent Mode question doesn't reach them, so a different question has to.
Review the tags you actually run
Start from the list of tags on the page, not the checklist you were handed. Consent Mode is one row on that list if you run Google, and zero rows if you don't. Consent Mode Is A Measurement Problem Before It Is A Compliance One covers the Google half; Basic vs Advanced Consent Mode covers the choice you make inside it.
The free privacy scan shows what fires on your site before a visitor answers, Google or not.
Source: Rawsoft Website Privacy Index, 47,506 sites scanned and 47,420 scored, January to October 2026. The crawl covers restaurant, hospitality and independent ecommerce sites, so it is not a sample of the whole web.
Rawsoft provides technical implementation and analysis, not legal advice. Please confirm any regulatory interpretation with your counsel.
Part of the guide: Consent Mode v2: Setup, Testing and Common Failures