Cookiebot by Usercentrics wins on scanning depth. Its crawler runs pages in a real browser environment, which means it catches cookies set by JavaScript, third-party embeds, and advertising networks — not just the first-party cookies your own WordPress sets. The declaration table updates after every scan, so the documentation matches what the site actually does. Combined with prior-consent blocking (nothing non-essential fires before the visitor chooses), IAB TCF support for the European ad ecosystem, and Google Consent Mode v2, it’s the tool agencies standardize on when compliance evidence needs to survive scrutiny. Against lighter options like cookie consent banners, the trade is clarity of setup versus depth of detection.
The 4.7 line is notable for operations people: WP-CLI commands (wp cookiebot status, verify, compliance, set-cbid, toggle-gcm) enable scripted configuration across server fleets, and the new Abilities API integration exposes configuration to REST clients and AI agents — with an audit log capping and recording every automated write. That’s consent management treated as infrastructure, not just a banner.
Competitive Features
- Real-browser deep scanning — detects third-party, session, and persistent cookies from embedded services
- Prior consent blocking — no non-essential cookies before explicit visitor choice
- IAB TCF framework support — ad networks read consent state directly from Cookiebot
- Google Consent Mode v2 — full default/update signal passing to Google services
- Auto-updating declaration — cookie list refreshes after every scan with descriptions and durations
- 35+ language banners — automatic locale adaptation
- WP-CLI command suite — scripted configuration, verification, and compliance checks
Key Features
- Scheduled weekly scans — selective re-scan of changed pages keeps detection current
- Consent statistics — rates by category and country in the dashboard
[cookie_declaration]shortcode — publish a live cookie list on any page- Domain group management — one consent across multiple domains and subdomains
- Custom blocking rules — APIs for scripts the auto-detection misses
- Consent history log — timestamped records for compliance documentation
- Abilities API + audit log — six REST-exposed abilities with every automated write recorded
Comparison with Competitors
Cookiebot Premium vs CookieYes
| Aspect | Cookiebot Premium | CookieYes |
|---|---|---|
| Scanning depth | Real-browser, all sources | Standard crawl |
| IAB TCF support | Yes | Yes |
| Banner auto-translation | 35+ languages | 45+ languages |
| Privacy policy generator | No | Yes |
| Consent statistics | By category and country | By category |
| WP-CLI management | Yes | No |
Bottom line: CookieYes packages more extras (policy generator, wider auto-translation); Cookiebot’s scanning finds what others miss — especially ad-network cookies set through embedded iframes. Compliance-sensitive sites choose depth.
Cookiebot Premium vs Complianz GDPR
| Aspect | Cookiebot Premium | Complianz GDPR |
|---|---|---|
| Data location | Usercentrics cloud | Your WordPress server |
| Legal documents | Via external service | Built-in generator |
| IAB TCF | Native | Premium |
| Scanning | Deep cloud crawler | Plugin-based scan |
| Multi-domain management | Domain groups | Per-site |
Bottom line: Complianz keeps everything self-hosted with law-firm documents built in; Cookiebot outsources scanning to a specialized cloud and handles multi-domain consent centrally. Enterprises with several properties get more from Cookiebot’s domain groups.
Recommended Stack — consent platforms and backup tools both guard irreplaceable records. Pair Cookiebot with UpdraftPlus Premium so consent logs and configuration survive any site-level failure.
Official Changelog
Version 4.7.2
Release Date: June 22, 2026
- Improvement: WordPress tested-up-to version set to 7.0.
- Fix: Gutenberg block registered with API version 1 instead of version 3, resolving a deprecation warning in the block editor.
Version 4.7.1
Release Date: May 20, 2026
- Improvement: WordPress tested-up-to version set to 7.0-RC1.
- Improvement: Updated UTM parameters on AI assistant setup links in AGENTS.md and CLAUDE.md for improved tracking.
Version 4.7.0
Release Date: May 7, 2026
- New: WP-CLI commands for scripted configuration —
wp cookiebot status,wp cookiebot verify,wp cookiebot compliance,wp cookiebot set-cbid,wp cookiebot toggle-gcm, andwp cookiebot install-ppg. - New: WordPress Abilities API integration — six abilities expose plugin configuration to AI agents and REST clients:
cookiebot/get-status,cookiebot/verify-setup,cookiebot/get-compliance-summary,cookiebot/set-cbid,cookiebot/toggle-gcm, andcookiebot/install-ppg. - New: Audit log for AI-driven write operations — changes made via abilities are stored in
cookiebot-ai-action-log(capped at 50 entries, with timestamp, ability name, user, old and new values). - Improvement: Added AGENTS.md and CLAUDE.md to the plugin root with agent-readable setup guidance, compliance coverage map, and post-install verification checklist.
Frequently Asked Questions
How does Cookiebot scan for cookies?
The scanner loads your pages in a real browser environment, executing JavaScript and capturing cookies set by scripts, third-party embeds, and server responses. Each cookie is categorized by purpose, and the declaration updates automatically after each scan.
Is there a free version of Cookiebot?
Yes — a limited plan covers one domain with up to 50 subpages and one banner language. Paid tiers add unlimited subpages, multiple languages, prior consent, and statistics.
Does Cookiebot work with Google Consent Mode?
Yes, fully. It passes both default and update consent signals to Google Analytics, Google Ads, and Tag Manager, so measurement adapts in real time to each visitor’s choices.
What is IAB TCF support for?
The IAB Transparency and Consent Framework lets advertising networks and exchanges read the visitor’s consent state directly from Cookiebot. Without it, ad personalization on European traffic operates in a legal gray zone.
Can I manage consent across several domains?
Yes. Domain group management applies one consent state across multiple domains and subdomains from a single account — visitors tracked across your properties see consistent banner behavior.
Leave a Reply