Cookiebot is one of the most-used consent management platforms in Europe, and for WordPress sites it's a legitimate choice, particularly if you have a multi-brand corporate setup or need the compliance certifications. It installs in under 30 minutes, handles Google Consent Mode v2 correctly, and scans your site for cookies automatically.
But Cookiebot isn't the only answer, and it's not always the right one. Free only goes up to 100 subpages. The paid tiers hit 49 EUR/month fast. And because it's a cloud service, every page load fetches a script from an external domain before anything else renders.
If you're running a standard WordPress site, you have a WordPress-native alternative that costs nothing and does the same Consent Mode v2 work: Cookie Banner Pro. That's my plugin, and I'll be upfront about when it makes sense versus when Cookiebot is the better call.
Below: the honest Cookiebot install steps, where it shines, where it hurts, and when to switch to a native WP alternative. Based on consent setups I've delivered for European e-commerce, SaaS, and publisher sites since 2022.
Key Takeaways
Cookiebot installs on WordPress in 6 steps (register, script tag, auto-blocking, categories, Consent Mode v2, test). Takes 20-30 minutes.
Free plan covers 100 subpages total. Most WordPress blogs cross that limit within 18-24 months of consistent publishing.
Paid tiers: 11 EUR/mo (up to 500 subpages), 29 EUR/mo (up to 2,500), 49 EUR/mo (up to 10,000). Enterprise for more.
Cookiebot is strong for multi-site corporations, sites that need IAB TCF 2.2 compliance, and teams that want cloud-managed consent logs.
Cookie Banner Pro (my free WordPress plugin) covers the same Consent Mode v2 + auto-blocking + 12 languages + consent analytics, natively inside WordPress. Pick it when you want zero external dependencies and zero recurring cost.
What Cookiebot Is and Who It's For
Cookiebot is a SaaS consent management platform (CMP) by Usercentrics. You pay a monthly subscription; in return, you get a hosted cookie banner, automatic cookie scanning, per-category consent controls, and compliance documentation that holds up in a GDPR audit.
It's strong for:
- Multi-site corporations. If you manage 20 brand sites on different stacks, a cloud CMP is easier than 20 native plugins.
- Sites requiring IAB TCF 2.2. If you serve programmatic ads through ad exchanges, Cookiebot handles the Transparency and Consent Framework natively.
- Teams that need audit-ready consent logs in a vendor dashboard. Legal can log into cookiebot.com and pull evidence without touching your CMS.
It's less of a fit for:
- Single WordPress sites with 50-500 pages, where a free native plugin handles the same compliance.
- Sites already fighting Core Web Vitals, because every page load fetches consent.cookiebot.com before the banner renders.
- Tight-budget publishers and e-commerce that grow past 100 subpages quickly.
Install Cookiebot on WordPress, Step by Step
Step 1: Register and get your Domain Group ID
Go to cookiebot.com, sign up for the free plan, add your domain. Cookiebot gives you a Domain Group ID (looks like 00000000-0000-0000-0000-000000000000). You'll paste this into WordPress.
Free plan activates instantly. No credit card. The limit is 100 subpages, when you cross it, Cookiebot still loads, but you get nag emails and eventually prompts to upgrade.
Step 2: Add the Cookiebot script to WordPress
Two options:
Option A, via a plugin. Install "Cookiebot CMP by Usercentrics" from the WordPress plugin directory. Activate. Paste your Domain Group ID in Settings. Done.
Option B, manual script tag (better for performance control). Edit your theme's header.php and add this as the FIRST script in :
<script id="Cookiebot" src="https://consent.cookiebot.com/uc.js" data-cbid="YOUR-DOMAIN-GROUP-ID" data-blockingmode="auto" type="text/javascript"></script>
The data-blockingmode="auto" flag is critical. It tells Cookiebot to auto-block all tracking scripts until consent is given.
Step 3: Configure Auto-Blocking
Auto-blocking means Cookiebot rewrites the type attribute on tags so browsers don't execute them before consent. It's the core GDPR feature, without it, Google Analytics and Facebook pixels fire before the user accepts.
In cookiebot.com dashboard: enable "Automatic cookie blocking based on prior consent". Cookiebot will scan your site weekly and categorize every cookie it finds.
For WordPress specifically: if you use Yoast, Rank Math, Elementor, or WooCommerce, they work out of the box with Cookiebot's auto-blocking. If you use a caching plugin (WP Rocket, W3 Total Cache), test twice, some caching plugins inline scripts in ways that bypass auto-blocking.
Step 4: Map Cookie Categories
Cookiebot separates cookies into four categories: Necessary (always on), Preferences, Statistics, Marketing. Go through the scanned cookie list and confirm the categorization. This takes 15 minutes for a standard site.
The key is honesty here. Don't hide marketing cookies under "Statistics" to get higher opt-in rates. It's a GDPR violation and Cookiebot's audit log captures the mapping you chose.
Step 5: Enable Google Consent Mode v2
This is the part most teams get wrong. Since March 2024, Google requires Consent Mode v2 signals for EEA traffic, or you lose conversion data in Google Ads and audience building breaks.
In Cookiebot dashboard: enable "Google Consent Mode v2 (with ad_personalization and ad_user_data)". This tells Cookiebot to emit the four consent signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) based on the user's banner choices.
If you use Google Tag Manager, the integration just works, Cookiebot sets the dataLayer flags, GTM reads them. If you use direct GA4 or Google Ads tags, the integration is still automatic but requires the Cookiebot script to load before any Google tag.
For more on Consent Mode v2 and why it matters, see my upcoming Consent Mode v2 deep-dive guide (publishing next Friday).
Step 6: Test with the consent.cookiebot.com debugger
Open your site in Chrome, load DevTools, Network tab, filter by "cookiebot". You should see:
uc.jsloading first (Cookiebot script)consent.cookiebot.com/consentchoicelogging the user's decision after they click- Other tracking scripts (google-analytics.com, googletagmanager.com) loading ONLY after consent
If GA4 or GTM fires before the user clicks, your auto-blocking isn't working. Common culprit: the Cookiebot script isn't the FIRST script in .
Want an honest audit of whether your consent setup is actually firing correctly? Run the free GTM audit, it'll flag consent issues alongside tag management problems.
Cookiebot Pricing: The Real Numbers
Cookiebot's free tier is generous, but understand where the paywall hits.
| Plan | Subpages | Price | Best for |
|---|---|---|---|
| Free | up to 100 | 0 EUR | Small blogs, landing pages, micro-sites |
| Premium Small | up to 500 | 11 EUR/mo | Local businesses, small e-commerce |
| Premium Medium | up to 2,500 | 29 EUR/mo | Mid-size WP sites, magazines |
| Premium Large | up to 10,000 | 49 EUR/mo | Large publishers, multi-brand sites |
| Enterprise | 10,000+ | Custom | Corporations, agencies managing multiple brands |
The subpage counter is aggressive. Every URL Cookiebot crawls counts, including /page/2/, /category/xyz/, /tag/abc/, and product variants. A WordPress blog with 60 published posts can hit 200+ subpages in Cookiebot's count after including pagination, tags, and categories.
When Tomek, who runs an analytics blog on WordPress, hit 118 subpages six months after launch, Cookiebot's nag emails started. He upgraded to Premium Small (11 EUR/mo), which works out to 132 EUR/year. Over three years, that's 400 EUR for a feature he could get free from a WordPress-native plugin.
A Mini-Story: When Cookiebot Saved Time
Fair play to Cookiebot: there are cases where it's the right call.
Agata, marketing director at a European apparel brand, inherited a multi-site setup in early 2025: 8 country-specific WordPress sites (UK, DE, FR, PL, IT, ES, NL, BE). Each was a separate WP install, each needed Consent Mode v2 compliance before a Q2 Google Ads campaign launched.
Native per-site plugin configuration would have meant 8 separate banner designs, 8 consent logs to audit, 8 deployments to synchronize. She picked Cookiebot's Premium Medium plan (29 EUR/mo), configured once in the cookiebot.com dashboard, deployed the same script tag across all 8 sites, and had unified consent analytics her legal team could audit in one place. Total setup: 2 days. Compliance confirmed by her DPO the following week.
For that use case, Cookiebot earned its price.
When Cookiebot Is Not the Best Fit for WordPress
Three scenarios where you should think twice:
1. Performance-sensitive WordPress sites. Every page load fetches uc.js from consent.cookiebot.com before the banner renders. For sites obsessing over LCP and INP in Core Web Vitals, an inline WordPress-native banner wins every time.
2. Sites growing past 100 subpages. If your blog publishes weekly, your category and tag pages count too. You'll cross 100 subpages in 12-18 months. At that point you're paying 132 EUR/year for consent management, that's money a free WP plugin leaves in your budget.
3. Teams that want consent data inside WordPress, not on a vendor dashboard. Cookiebot's analytics live at cookiebot.com. Your marketing team has to log into yet another tool. WordPress-native plugins show consent stats inside wp-admin, next to every other metric.
The WordPress-Native Alternative: Cookie Banner Pro
I'll be direct: I built Cookie Banner Pro because I kept hitting these three limitations on client sites, and a proper free WordPress plugin didn't exist for teams that wanted real Consent Mode v2 support without the Cookiebot subscription.
Cookie Banner Pro is a free WordPress plugin (install from wp-admin or upload ZIP) that delivers:
- Google Consent Mode v2, full implementation with all four signals (
ad_storage,analytics_storage,ad_user_data,ad_personalization), emitted via dataLayer before any tracking script can fire. - Cookie scanner + auto-blocking, the same "block scripts until consent" behavior as Cookiebot, applied natively in PHP before scripts reach the browser.
- Consent analytics dashboard, accept/reject rates, per-category breakdowns, trend over time, visible inside wp-admin, no external login.
- 12 languages built-in, PL, EN, DE, FR, ES, IT, CS, NL, PT, SV, UK, RO. Auto-detects from WordPress locale or lets users switch.
- GTM template export, one-click download of a GTM container template that reads the consent state correctly.
- Full style customization, colors, animations, button weight (equal vs highlight Accept), banner position.
- Unlimited subpages, no soft limit, no nag emails, no forced upgrade at 100 URLs.
Premium cross-domain sync (10 EUR/mo) is the one paid feature, for teams managing multiple non-WP subdomains that need to share consent state. For single WP sites, never needed.
Feature Comparison
| Feature | Cookiebot Free | Cookiebot Premium Medium | Cookie Banner Pro (free) |
|---|---|---|---|
| Subpage limit | 100 | 2,500 | Unlimited |
| Consent Mode v2 | ✓ | ✓ | ✓ |
| Cookie auto-blocking | ✓ | ✓ | ✓ |
| Cookie scanner | ✓ (cloud) | ✓ (cloud) | ✓ (native PHP) |
| Consent analytics | Cloud dashboard | Cloud dashboard | wp-admin dashboard |
| Language support | 40+ | 40+ | 12 |
| GTM template | Manual | Manual | One-click export |
| Monthly cost | 0 EUR | 29 EUR | 0 EUR |
| External script dependency | Yes | Yes | No |
| IAB TCF 2.2 | Add-on | Add-on | Not included |
A Second Mini-Story
Marek is a freelance WordPress developer in Krakow. He manages Cookie consent for 30 small-business client sites. At Cookiebot Premium Small (11 EUR/mo per site), that's 330 EUR/month, 3,960 EUR/year, just for consent management. Most of those clients have sites under 200 pages.
Marek deployed Cookie Banner Pro to all 30 client sites in two afternoons. Same Consent Mode v2 compliance, same auto-blocking, same GDPR-safe setup, nested configuration per client. The clients pay nothing extra for consent, Marek doesn't pass through a 132 EUR/year subscription to each one, and legal compliance is identical.
If you're an agency or freelancer deploying to multiple WP sites, the math is unambiguous.
How to Choose: Cookiebot vs Cookie Banner Pro
Choose Cookiebot when:
- You run a multi-stack enterprise with mixed tech (WP + Shopify + custom).
- You need IAB TCF 2.2 for programmatic advertising.
- Your legal team wants consent logs on a vendor-hosted audit dashboard.
- Budget isn't a constraint (enterprise tier).
Choose Cookie Banner Pro when:
- You run one or more WordPress sites and want zero recurring cost.
- You want consent analytics inside wp-admin, next to your other WordPress metrics.
- Core Web Vitals matter and you want a native script, not an external fetch.
- You're an agency managing multiple client WP sites.
Both tools implement Consent Mode v2 correctly. Both auto-block scripts until consent. Both survive a GDPR audit. The decision is about deployment scale, team workflow, and cost sensitivity.
Ready to test the free alternative? Install Cookie Banner Pro, free, WordPress-native, Consent Mode v2 out of the box.
Frequently Asked Questions
Is Cookiebot really free for WordPress?
Yes, up to 100 subpages. Every URL Cookiebot crawls counts, including pagination, tags, and categories, so most actively-published WordPress blogs cross that limit within 12-18 months. After that, pricing starts at 11 EUR/mo.
Does Cookiebot work with Google Consent Mode v2?
Yes. Cookiebot emits all four Consent Mode v2 signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) based on the user's banner choices. Enable "Google Consent Mode v2" in your Cookiebot dashboard. It works with direct Google tags and with Google Tag Manager.
What happens when I exceed 100 subpages on the Cookiebot free plan?
Cookiebot still loads and the consent banner keeps working, but you start receiving weekly email reminders to upgrade. Eventually, unresolved, the account can be downgraded to show a Cookiebot-branded banner or suspended on the compliance dashboard side. Upgrading to Premium Small (500 subpages, 11 EUR/mo) is the typical next step.
Can I use Cookiebot with Google Tag Manager?
Yes, and the integration just works when set up correctly. Load the Cookiebot script before your GTM container. Cookiebot writes the consent state to window.dataLayer. Your GTM tags read those flags via built-in "Consent Initialization" triggers. If Google Analytics 4 fires before the user consents, your Cookiebot script isn't loading first in .
What's the best free WordPress-native alternative to Cookiebot?
Cookie Banner Pro is my own free WordPress plugin. It covers the same Consent Mode v2 + auto-blocking + 12-language support, natively inside WordPress, with consent analytics visible in wp-admin and no subpage limits. Install at cookiebanner.pro.
Does Cookiebot block scripts automatically?
Yes, with data-blockingmode="auto" in the script tag. Cookiebot rewrites the type attribute on all tracking scripts before they execute, preventing GA4, Facebook Pixel, TikTok Pixel, etc. from firing until the user consents. This is the key GDPR-compliance feature, without auto-blocking, scripts fire before consent and you're non-compliant.
Conclusion
Cookiebot installs cleanly on WordPress in six steps and does what it promises: GDPR-compliant cookie consent with Google Consent Mode v2 support. For enterprise multi-stack setups and sites needing IAB TCF 2.2, it's a legitimate choice.
For most single-WordPress sites, especially blogs and e-commerce that cross 100 subpages within two years, a WordPress-native free plugin covers the same compliance without the recurring cost and external script dependency. That's the gap Cookie Banner Pro fills.
Pick the tool that matches your scale and stack. Both do the compliance work; the difference is cost, performance, and where your team prefers to see the consent analytics.
Want to verify your current consent setup is actually firing Consent Mode v2 correctly? Run the free GTM audit. It scans for consent misconfiguration alongside tag management issues, and tells you straight if something's broken. No signup required.
Meta Elements
```
Meta Title: Cookiebot on WordPress: Install Guide + Alternative
Meta Description: Step-by-step Cookiebot install for WordPress with Consent Mode v2. Plus when a free WP-native alternative makes more sense. Honest 2025 guide.
Primary Keyword: cookiebot wordpress
Secondary Keywords: cookiebot install, cookie banner wordpress, free cookie consent wordpress, consent mode v2 wordpress, cookie banner pro
URL Slug: /articles/en/cookiebot-wordpress-install-guide.html
Internal Links:
- https://piotrlitwa.com/articles/en/google-analytics-4-what-is-it-how-it-works.html
- https://piotrlitwa.com/articles/en/5-gtm-mistakes-costing-you-conversions.html
- https://piotrlitwa.com/checkGTM/ (x2 CTAs)
External Links:
- https://cookiebanner.pro (x2, own product)
- https://cookiebot.com (obvious)
- https://developers.google.com/tag-platform/security/guides/consent (Consent Mode v2 docs)
Word Count: ~2700
```
Want the free WordPress-native alternative?
Cookie Banner Pro gives you the same Consent Mode v2 + auto-blocking + 12 languages, natively inside WordPress. Free, no subpage limits.
Get Cookie Banner ProNeed help? Get in touch
Have a question about your analytics setup? Fill out the form, I usually reply within 24 hours.