There is a funny thing about free website tools: sometimes the price of using them changes when your website starts doing better.
You publish more articles. Add product pages. Create a few landing pages. Maybe WordPress generates attachment pages you never even knew existed.
Then your cookie consent tool scans the website and finds something you didn't expect: 51 subpages.
If you're using Cookiebot's free plan, that number matters.
I went through Cookiebot's pricing and help documentation to understand exactly how the limit works, what happens when you exceed it, and what alternatives are worth considering.
Here's what I found.
First, what does Cookiebot actually count?
Cookiebot's free plan covers one domain with up to 50 subpages. Traffic isn't the limiting factor; the number of pages is.
And a subpage doesn't necessarily mean a page you deliberately created.
The scanner can count:
Regular website pages
Blog posts
Archive pages
WordPress media attachment pages
Other unique URLs it can discover by following links or crawling your sitemap
Image files themselves don't count, and 404 pages are excluded.
Subdomains are treated separately, too. example.com and shop.example.com aren't the same domain for billing purposes.
This is where things can get a little surprising for WordPress sites. You might have 30 articles and a handful of product pages, but your actual scanned URL count could be higher.
The 50-page limit is only half the story
New Cookiebot accounts start with a 14-day trial that includes Premium features.
Once that trial ends, what happens depends on the website.
If your domain qualifies for the free plan, you can continue with its limitations: one language, the standard banner design, and no automated monthly scans.
If the scanner finds more than 50 subpages, you'll need a Premium subscription.
And here's the part I'd pay attention to: if you don't add payment details before the trial ends, the account can be suspended and the Cookiebot scripts stop working.
That means the consent banner may disappear entirely.
There is another detail worth understanding. Cookiebot's manual blocking method can keep explicitly marked scripts from running when its script fails, but untagged scripts may still load. If your analytics or advertising tags depend on consent, you should know exactly how they're configured rather than assuming everything is blocked automatically.
For a production website, that's something I'd check before the trial expires, not after.
So, how much does it cost?
Let's use a simple example.
Imagine you run a small business website with 64 subpages on a single domain.
According to Cookiebot's published pricing information, that puts the domain in the Premium Medium tier at €30 per month.
That's €360 over twelve months, before VAT.
The €15 Premium Small tier has an additional condition: it requires four or more domains on the account. It isn't necessarily available to a single website with 64 pages.
The important distinction is that Cookiebot doesn't charge more because your website gets more visitors. Its pricing is based on the number of subpages.
For some websites, that's perfectly reasonable. For others, particularly content-heavy sites, it's worth comparing alternatives.
Pricing can change, so check the current Cookiebot pricing page before making a decision.
What about alternatives?
One option is to keep using Cookiebot and pay for the features your website needs. If you need a certified consent management platform for Google advertising products in Europe, that's an important consideration.
Another option is to look at a tool with a different pricing model.
I looked at how Builderify approaches cookie consent because it solves the problem differently.
Instead of counting subpages, Builderify meters the page loads of the widget that carries the consent banner.
The published free allowance is 250 credits per month. The banner uses 10 credits per 1,000 page loads, which works out to approximately 25,000 banner-only page loads per month, assuming those credits aren't being used by other Builderify features.
The distinction is simple:
Cookiebot: pricing depends on subpages and the plan you qualify for.
Builderify: usage depends on widget page loads and available credits.
Builderify also offers a cookie consent banner, consent preferences, and controls for scripts you explicitly tag or connect by ID.
There are trade-offs, though. Builderify does not offer Google-certified CMP status or IAB TCF support. If your website serves Google ads through AdSense, Ad Manager, or AdMob to visitors in Europe, you should choose a certified platform that meets your requirements instead.
Neither pricing model is automatically better for everyone. It depends on your website, traffic, and compliance needs.
You can read the full comparison here:
Cookiebot Free Plan: Limits, Pricing, and an Alternative
The guide also includes a price calculator for multiple domains and a markup converter for developers considering a move from Cookiebot to Builderify.
One last thing: check your actual URL count
If you're running WordPress, don't rely only on the number of pages shown in your admin dashboard.
Check your sitemap first. Depending on your setup, it might be available at /wp-sitemap.xml or /sitemap.xml.
Look at the URLs it contains, including posts, archives, and attachment pages. Remember that the sitemap is only a starting point: the scanner may discover additional URLs by following links.
Then compare the result with the limit on your current plan.
It takes a few minutes, and it's much better than discovering a billing issue when your trial expires.
Full guide: https://builderify.com/guides/cookiebot-free-plan
Pricing details in this article are based on the published information reviewed on October 17, 2026. Verify current pricing and consent requirements before changing your setup.
Top comments (0)