How Much Does Cookiebot Cost? Consent Pricing Explained

The short version: Cookiebot's paid plans start from 7 euro (8 dollars) a month for a single small site, scale up based on how many subpages the scanner crawls, and the free tier covers one domain with up to 50 subpages. Most small business owners land on one of the lower tiers once the scanner has counted their pages, but the bigger cost most people miss isn't the subscription, it's the time it takes to set the thing up so it does what GDPR requires.

What Cookiebot charges, plan by plan

Cookiebot (now sold under the Usercentrics brand after the two companies merged) prices itself by domain and by the number of unique subpages its scanner checks each month, not by traffic volume. That's different from a lot of SaaS tools you're used to, and it trips people up. For everything else it does, read my full Cookiebot review.

Here's how the structure works:

• Free: one domain, up to 50 subpages, with manual blocking. Fine for a tiny brochure site or a landing page with no blog.
• Lite: from 7 euro (8 dollars) a month for up to 50 subpages, with automatic blocking and every premium feature. Small covers a higher subpage limit, usually enough for a WordPress site with a blog that's been going a year or two.
• Medium, Large and Extra Large tiers: step up from there as subpage counts rise into the thousands, which is where multi-location businesses or content-heavy sites land.
• Enterprise/Custom: priced on application, for agencies managing consent across dozens of client domains or large retailers with huge catalogues.

Prices are set in euros since Cookiebot is a Danish product (Cybot ApS), so UK buyers pay in GBP equivalent, and the exchange rate moves the number around a bit month to month. Always check the live price on their site before you commit, because these figures shift and I'm giving you the shape of it, not a locked-in quote.

Why "subpages" is the number that decides your cost

This is the bit most comparison articles skate past. Cookiebot doesn't care how many visitors you get. It cares how many unique URLs its scanner finds on your domain, because that's what it crawls to detect cookies and trackers automatically.

Say you run a small coaching business with a five-page site: home, about, services, a contact form, and a blog with 40 posts. That's 45 pages. You'll likely sit comfortably in the free tier or the cheapest paid one. But say you run an ecommerce store with 2,000 product pages, each one technically a unique subpage. Suddenly you're in a mid tier plan whether your traffic is 50 visitors a month or 50,000. A site with huge traffic but few pages pays less than a site with modest traffic but a sprawling catalogue. That's the opposite of what most people assume when they go looking for pricing.

A worked example: what a small site pays over a year

Say you run a local accountancy firm website. You've got 30 pages, including a blog you update twice a month, plus a contact form that uses Google Analytics and a Facebook pixel for remarketing. Here's how the maths plays out:

• Subpage count after a year of blogging twice monthly: roughly 54 pages.
• That's just over the 50-subpage limit of the Free and Lite plans, so you'd move up to the Small tier. Cookiebot scans your site and tells you which tier you need.
• Annual cost: twelve months of that tier, so check the live price for your page count before you commit.
• If you add a second domain (say a separate booking portal), that's a second subscription, because Cookiebot licenses per domain, not per business.

Compare that to the cost of getting it wrong: the UK's ICO can issue fines of up to 4% of global turnover or 17.5 million pounds, whichever is higher, for serious data protection breaches, though in practice most cookie consent enforcement so far has been warning letters and smaller penalties rather than headline-grabbing fines. Still, a small monthly subscription against even a modest enforcement risk is not a hard sell.

What the subscription doesn't include

Here's the part people tend to skip. The tool detects cookies, blocks them until consent, shows a banner and switches on Google Consent Mode v2 for you (it's on by default in the WordPress plugin). It does not decide whether you've classified your trackers correctly and it does not write your privacy policy, so it's still worth checking that each of your Google tags behaves the way you expect when a visitor accepts or declines. Plenty of small business owners install the banner, see it pop up looking official, and assume the legal job is done. It isn't.

I've seen (and you'll see this too if you check analytics setups) sites where the cookie banner is live and beautifully styled, but Google Analytics was still firing before anyone clicked accept, because the integration between the consent tool and the tag manager was never finished. The banner becomes decoration rather than protection. If you're unsure whether your setup requires this level of care, it's worth reading up on whether Google Analytics requires cookie consent under GDPR before you assume any plan solves everything.

Free tier limits that catch people out

The free Cookiebot plan is free, not a bait and switch, but it has real ceilings:

• One domain only. Subdomains like shop.yoursite.com may or may not count depending on configuration, so check before assuming you're covered.
• 50 subpages is the cap. A growing blog will cross that within a year of regular posting.
• Manual blocking only. Automatic blocking needs a paid plan.
• Only your first scan is automatic. After that, you run new scans yourself from inside your account.
• No multilingual banner customisation beyond the basics, which matters if you serve UK and Israeli or US audiences in different languages.
• Support is community-level, meaning if the scanner misses a tracker, you're troubleshooting it yourself.

For a one-page landing site promoting a single offer, free is fine and you shouldn't pay a penny more. For anything with an active blog or more than one product line, budget for the paid tier from day one rather than getting a nasty surprise when the scanner locks you out mid-growth.

How Cookiebot compares on price to the alternatives

There are other consent management platforms: OneTrust, Termly, CookieYes, Osano. Roughly speaking:

• CookieYes tends to be cheaper at the entry level, often a few pounds less a month for similar small-site coverage, and is popular with WordPress users specifically.
• OneTrust is built for enterprise and its pricing reflects that, often requiring a sales call rather than a published price, which tells you it's not built for a five-person consultancy.
• Termly offers a generous free tier similar to Cookiebot's but with different subpage logic.

Cookiebot's edge isn't being the cheapest. It's the automatic scanning and reasonably strong integration with Google tag ecosystems, which matters if your main tracking is Google Analytics and Google Ads remarketing, which covers most small businesses I come across.

The uncomfortable bit about compliance spending

Here's what doesn't get said enough: paying for a cookie banner tool makes you feel compliant far more effectively than it makes you compliant. The subscription fee buys you a scanning engine and a widget. It does not buy you a correctly configured tag manager, a privacy policy that matches what your banner says, or a team that understands the difference between "necessary" and "statistics" cookies when they're classifying a new tracking pixel next month. Small business owners pay for a year's subscription and feel the job is ticked off, while the actual risk, firing analytics before consent, mislabelling marketing cookies as functional, never reviewing the setup after the first week, sits untouched. If you want to know whether your current setup protects you rather than just looking tidy, read through what real visitor consent for Google Analytics looks like rather than trusting the banner alone.

A simple setup checklist for a small website

If you're deciding whether Cookiebot's paid tier is worth it, run through this before you buy:

• Count your live pages, including blog posts, and add 20% for growth over the next year.
• Check which tier that count falls into on Cookiebot's current pricing page.
• List every tracking script on your site: Analytics, Meta Pixel, LinkedIn Insight, any ad platform tags.
• Confirm each tracker is correctly tagged as necessary, preferences, statistics, or marketing inside Cookiebot's dashboard, don't just accept the auto-detection blindly.
• Test the banner in an incognito browser window to confirm trackers don't fire until you click accept.
• Update your privacy policy to match exactly what the banner says you're doing.

That last step is where most small sites fall down, because the policy was written two years before the banner was installed and nobody went back to reconcile the two.

When it's worth paying someone to set this up

If you've read through this and your eyes have glazed over at the words "tag manager" and "consent mode," that's a fair signal you need help rather than a cheaper plan. A half-day of real setup from someone who knows Google Tag Manager and GDPR requirements together usually costs far less than a single enforcement letter, and it means the monthly fee you're paying Cookiebot is doing the job you think it's doing. If you want this handled rather than pieced together from forum posts, it's worth looking at working with an AI consultant for small business who can audit your tracking stack alongside your wider marketing setup, since cookie consent rarely sits in isolation from the rest of your analytics and ad tracking.

Frequently asked questions

Is Cookiebot really free for small websites?

Yes, for a single domain with up to 50 subpages the free tier is free with no hidden charge, but it uses manual blocking and is limited on customisation, and most sites with an active blog outgrow the 50 subpage cap within a year.

Does Cookiebot pricing depend on website traffic?

No. Cookiebot prices by domain and by number of unique subpages scanned, not by visitor numbers, so a high-traffic five-page site pays less than a low-traffic 2,000-page ecommerce catalogue.

Do I still need a privacy policy if I pay for Cookiebot?

Yes. Cookiebot handles the consent banner and cookie scanning, but it doesn't write or update your privacy policy, and mismatches between what your policy says and what your banner does are a common compliance gap on small sites.

Is Cookiebot enough on its own for GDPR compliance?

Not fully. It's a strong tool for detecting cookies and managing consent choices, but full compliance also depends on correctly configuring Google Consent Mode, classifying every tracker accurately, and keeping your policy documents aligned with what the banner blocks.