Cookiebot's pricing page looks simple until you add a second domain. Then a staging site. Then a subdomain for the blog. A tool you budgeted at 15 euros a month quietly turns into a few hundred euros a year.
This is a plain breakdown of what Cookiebot costs in 2026, how the pricing model actually works, and where the surprises come from. No affiliate spin. We build a competing consent management platform, so read the last section with that in mind.
How much does Cookiebot cost in 2026?
Cookiebot is free for one domain with up to 50 subpages. Paid Premium plans are priced per domain based on subpage count, starting at roughly 7 euros per month for the smallest tier and reaching around 90 euros per month for domains with more than 7,000 subpages. Every domain is billed separately.
The important word there is per domain. Cookiebot does not sell you a company licence that covers your sites. It sells you a licence for one hostname, and the tier is set by how big that hostname is. A published breakdown of Cookiebot's 2026 pricing tiers puts the ladder roughly like this:
- Free: 1 domain, up to 50 subpages, Cookiebot branding on the banner
- Premium Lite: around 7 euros per month, small sites
- Premium Small: around 15 euros per month, mid-size sites
- Premium Medium and Large: scales up with subpage count
- Premium XLarge: around 90 euros per month for 7,000 plus subpages
Exact figures shift with currency and billing period, and Cookiebot quotes different numbers depending on how many domains you buy at once. G2's pricing listing for Cookiebot shows Premium Small at about 16 dollars per domain per month if you buy four or more domains, but roughly 34 dollars per domain if you only need one to three. That gap matters more than most people expect.
Why does Cookiebot charge by subpages instead of traffic?
Cookiebot scans your site to build its cookie declaration, so its cost driver is crawling, not serving. More subpages means a longer crawl. That is why a low-traffic site with thousands of URLs can land on a higher tier than a busy landing page with ten URLs.
The model has an awkward side effect. Sites that generate URLs automatically get punished. An e-commerce catalogue, a multi-language site, a blog with tag and category archives, or anything with paginated listings can multiply its subpage count without adding a single visitor. If you run a Shopify store with 800 products in three languages, the crawler sees a very different site than you do.
What changed in Cookiebot's pricing in 2025?
In August 2025, Cookiebot roughly doubled its base Premium pricing and moved accounts covering fewer than four domains onto a more expensive tier automatically. Many existing customers saw their bill rise without changing anything about their plan or their site.
That change is the single biggest reason searches for Cookiebot alternatives spiked. It also created a strange incentive: buying four domains can cost less per domain than buying two. We covered the fallout and the main competitors in our guide to Cookiebot alternatives in 2026.
The costs that don't show up on the pricing page
Four things reliably push the real bill above the advertised one.
Subdomains count as separate domains
If you run example.com, shop.example.com and blog.example.com, that is three licences, not one. Plenty of teams discover this after the banner stops appearing on a subdomain.
Staging and dev sites
Testing your consent setup before it goes live is good practice. Doing it on a separate hostname means paying for another domain, or shipping untested and hoping.
No volume discount at the low end
Freelancers and small agencies sit in the worst spot. You have too many sites for the free tier and too few to reach the cheaper per-domain rate.
Annual commitment for the best rate
The lowest advertised numbers usually assume annual billing. Monthly billing costs more per month, which is fine, but it means the price you saw in a comparison table is not the price you pay if you want flexibility.
Is the Cookiebot free plan actually free?
Yes, but it is narrow. The free tier covers one domain with up to 50 subpages and puts Cookiebot branding on your banner. It works for a personal site or a small brochure site. Most real business sites cross 50 subpages long before they notice.
Free tiers in this category almost always trade something. Usually it is branding, a pageview cap, or a subpage cap. Read which one you are agreeing to before you build a client site on it.
What does Cookiebot cost an agency with 12 client sites?
Take a small web agency with 12 live client sites, all modest in size and all landing on the Premium Small tier. At roughly 15 euros per domain per month, that is 180 euros a month, or about 2,160 euros a year, purely for consent banners. Add a staging domain per client and it doubles.
Most agencies do not pass that through cleanly. It becomes a line item nobody wants to explain, so it gets absorbed. If you manage sites for other people, per-domain pricing is the number that decides whether a CMP is viable for you, not the feature list. Our consent management for agencies page covers how multi-domain pricing works on our side.
How does Consentify compare on price?
Consentify prices by plan rather than by crawled subpages, and the free plan covers one domain with no time limit. It is a real free plan, not a trial. Paid plans add multiple domains from one dashboard, which is where per-domain models get expensive fastest. Current numbers are on the Consentify pricing page.
Where Cookiebot is genuinely stronger: it has a large automated cookie declaration database and a long compliance track record, which matters if you are a large organisation with legal review cycles. If that is you, the price is probably justified. If you are a developer, freelancer, or small business paying enterprise rates for a banner, it probably is not. We put the two side by side in our Cookiebot alternative comparison.
How do I switch away from Cookiebot without breaking consent?
Switching takes about 20 minutes per site. Scan first so you know what you are blocking, add the new script, verify nothing fires before consent, then remove the old one. Do not remove the old banner first, because that leaves a window where trackers run with no consent layer at all.
The order that works:
- Run a free GDPR scan on the site and note every tracker it finds
- Create the domain in your new CMP and rebuild the categories to match
- Add the new script tag:
<script src="https://consentify.app/api/gateway?token=YOUR_TOKEN"></script> - Test in a private window, confirm nothing loads before you click accept
- Remove the Cookiebot script and cancel the subscription
- Re-scan to confirm the result
Add an element with the id revoke-consent-btn on your privacy page and Consentify wires the withdraw-consent flow to it automatically. Details are in the Consentify documentation.
Is a cheaper CMP still compliant?
Price has nothing to do with compliance. What regulators look at is technical behaviour: whether trackers fire before consent, whether rejecting is as easy as accepting, and whether you can prove what a visitor agreed to. A 90 euro tool that loads Google Analytics on page load is less compliant than a free one that blocks it properly.
That is not a hypothetical. France's data protection authority fined Google 150 million euros and Facebook 60 million euros because rejecting cookies took more clicks than accepting them. Both had banners. The banners were the problem.
Paying per domain for a cookie banner? Try Consentify free, one domain, no time limit, and see what your setup should cost.