Cookiebot free plan

Free for 50 subpages.
Page 51 changes the plan.

Cookiebot’s free plan covers one domain with up to 50 subpages, with no limit on traffic. A subpage is any unique URL its scanner can reach, blog posts and WordPress attachment pages included. Past 50 you need Premium, and one site with more than 50 and under 350 subpages is billed as Premium Medium, €30 a month, because the €15 Small tier needs four or more domains. If a domain no longer qualifies for Free and no payment details are added by the end of the trial, the account is suspended and the Cookiebot scripts stop working. Below: what Free includes, what happens past 50, a calculator for your own domains, a converter that rewrites Cookiebot markup for Builderify’s cookie banner, and an honest word on when to stay.

Price my site Convert my markup
Cookiebot free: 50 subpages, 1 domain Unpaid trial: scripts stop Checked 17 Oct 2026

By the Builderify team

Illustration · A small studio site on Cookiebot Free. The scanner’s 51st URL takes it past the line; the steps after it follow Cookiebot’s help centre.
01 / The free plan

What is in the Cookiebot free plan?
A working banner, on Cookiebot’s defaults.

Cookiebot says Free “contains all functionality necessary to enable a fully compliant consent solution”. What it limits is size and polish: one small domain, one language, the standard look, and consent that is asked again after a month. Every plan is priced by pages, never by traffic.

Cookiebot Free, Premium Lite and Premium, from cookiebot.com/en/pricing on 17 October 2026, euros before VAT, per domain
Cookiebot, per domain Free €0 one domain per account Premium Lite €7 a month, one domain under 50 Premium €15–€90 a month per domain, by subpages
Subpages Up to 50 Under 50 Small under 350, Medium under 3,500, Large under 7,000, Extra Large above
Domains 1, and no other on the account 1 As many as you pay for, each billed
Traffic Not counted Not counted Not counted
Banner languages 1 47+ 47+
Consent lasts Up to 1 month Up to 12 months Up to 12 months
Blocking cookies and trackers Manual Manual and automatic Manual and automatic
Scans When you sign up; no monthly scan Monthly Monthly; daily for €99 a month more
Consent records kept Up to 12 months Up to 12 months Up to 12 months
CSV export of consents No Yes Yes
Own colours, logo, HTML and CSS No Yes Yes
Geotargeting No Yes Yes
Google Consent Mode and GPC Yes Yes Yes
IAB TCF 2.4 No Yes Yes
Email support No: help centre Yes Yes

What counts as a subpage

Any unique URL on your domain. The scanner follows every link a visitor could, links in your sitemap included, and scans what it reaches: pages, blog posts, archive pages, and the attachment pages WordPress makes for media. Image files themselves don’t count, and 404 pages are left out.

One domain means one hostname

example.com and shop.example.com are two domains, each scanned and billed on its own; example.com/fr is the same domain. Adding both example.com and www.example.com bills both. Free cannot sit on an account with any other domain.

Free means the defaults

Cookiebot’s standard colour scheme, no logo, the default Privacy Trigger and Cookie Declaration, one language, one legal framework, and consent that lasts up to a month before the visitor is asked again. Moving to Free after the trial switches off automated monthly scans.

From Cookiebot’s pricing page and help centre on 17 October 2026, prices in euros before VAT. The pricing page lists blocking on Free as “Manual” and on Premium as “Manual and Automatic”. It also says Free is “up to 50” subpages in one place and Lite “fewer than 50” in another.

02 / Past 50 subpages

What happens when Cookiebot finds more than 50 subpages?
Free stops being an option.

In order, from Cookiebot’s help centre

  1. Sign-up

    Every new account starts with a 14-day trial with all Premium features. Cookiebot scans the domain straight away and counts its pages.

  2. Trial ends, one domain, 50 or fewer

    You can choose Free or Premium. On Free, extra languages, domains and custom colours are removed and the automated monthly scan stops.

  3. More than 50, or a second domain

    Free is not offered. If you were on Free, Cookiebot emails you a list of up to 200 of the URLs its scanner found.

  4. No payment details when the trial ends

    The account is suspended. The Cookiebot scripts stop working, so no banner shows and no scans run.

  5. Payment details added

    Everything works again straight away. The price follows the highest page count recorded in the domain’s scan history.

  6. Back under 50 later

    A Premium domain is not moved back to Free. Cookiebot’s route is cancelling, which purges your data, and starting a new trial.

“If our scanner finds more than 50 pages on your domain after the 14-day trial ended, you will need a Premium subscription. If you haven't added payment information by the end of the trial, your account will be suspended.”
How can I get a Free subscription?
“While the account is suspended the Cookiebot CMP scripts will stop working and no further scans will be performed.”
What is a 'Free Trial'?
“If the scanner detects that the domain has more than 50 subpages and does not qualify for the free subscription, then it will automatically be put on a free 14 days trial (with full Premium functionality).”
Will domains with fewer than 50 pages be set as a 'free subscription'? (an article for Cookiebot partners)

One older help article calls the converted account a 30-day trial; the pricing page and the other articles say 14 days.

When the scripts stop, which trackers run?

It depends on how your scripts were blocked, and Cookiebot’s own documentation tells you which way each fails.

Manual markup: fails closed

A script you marked type="text/plain" never runs on its own. Cookiebot’s manual-blocking guide says this markup prevents cookies “even if the Cookiebot script fails to load”. With the account suspended, those tags stay off for everyone, including visitors who would have said yes.

Untagged scripts: fail open

Anything Cookiebot only held back with automatic blocking, which needs its script running, now loads like any other script. So does anything you never tagged. With no banner on screen, nobody has been asked. In the UK, the ICO’s position is that non-essential cookies need consent before they are set. This is general information, not legal advice.

The safe reading: know your page count before the trial ends, not after. Running Google Analytics too? Read whether GA is legal where you are and how Consent Mode v2 defaults work.

03 / Price calculator

How much is Cookiebot past 50 subpages?
Your domains, on Cookiebot’s rules.

Enter the subpages on each domain, subdomains as their own rows. Not sure of the count? Paste your sitemap below and treat the number as a floor: the scanner also counts pages it reaches through links that the sitemap leaves out.

Subpages on each domain
01
Cookiebot prices in

Cookiebot ignores this. Builderify meters it.

Open yoursite.com/sitemap.xml (on WordPress, /wp-sitemap.xml and the sitemaps it lists), copy the XML and paste it here.

No <loc> URLs yet.

On Cookiebot, per domain
  • 01 Premium Medium · 64 subpages
    €30 / mo
€30 a month, €360 a year.

Premium Small, €15 a month, needs four or more domains on the account, so one site with 64 subpages is billed as Premium Medium.

Domains
1
A month
€30
A year
€360
CookiebotEUR
Priced by subpages
Each month€30
Twelve months€360
TrafficNot counted

Before VAT. On Cookiebot’s pricing page today, the yearly price is twelve times the monthly one.

BuilderifyUSD
Priced by page loads
Credits a month200
Free every month−200
Twelve months$0

Covered by the 250 free credits a month, as long as nothing else on your widget uses them.

Cookiebot: prices per domain from its pricing page on 17 October 2026, before VAT. Free and Premium Lite need an account with a single domain of up to 50 subpages; with two or more domains, every domain is Premium. Cookiebot assigns the tier itself after its scan, so ask it for a quote before you rely on a figure. Builderify: its rate card, 10 credits per 1,000 page loads of the widget that carries the banner, 250 free credits a month, the first website included and 100 credits once for each website after it, one-time packs from $9. Subpages cost Builderify nothing. Assumes one Builderify website per domain and every page carrying the widget.

04 / Markup converter

Moving off Cookiebot?
Convert data-cookieconsent in one paste.

On Free, Cookiebot’s blocking is manual, so your scripts and embeds already carry its markup. Builderify uses the same idea with different words. Paste a page, a template or a theme file: everything runs in your browser and nothing is sent anywhere.

For Builderify 
<head>
  <script src="https://app.builderify.com/consent/YOUR-SITE-ID.js" data-cfasync="false"></script>

  <!-- Hotjar, held back until Statistics -->
  <script type="text/plain" data-bdf-consent="analytics">
    (function (h, o) { /* Hotjar's snippet */ })(window, document);
  </script>
  <script type="text/plain" data-bdf-consent="analytics marketing"
          src="https://ads.example.com/tag.js"></script>
  <script async src="https://connect.facebook.net/en_US/fbevents.js"></script>
</head>
<body>
  <iframe data-src="https://www.youtube.com/embed/fyvwLAPNfXY"
          data-bdf-consent="marketing" width="560" height="315" allowfullscreen></iframe>
  <div class="cookieconsent-optout-marketing">
    Please <a href="#cookie-settings">accept marketing cookies</a> to watch this video.
  </div>
  <script>
    if (bdfConsent.has('analytics')) { startChat(); }
  </script>
  <!-- Cookie list: in the Builderify banner's preferences. Link to it with <a href="#cookie-settings">Cookie settings</a> -->
</body>

What changed, and what needs you

7 changed · 3 to check

  1. Done Line 2

    Cookiebot script replaced with the Builderify consent tag. Put your own site ID in its URL and keep it first in <head>.

  2. Check Line 2

    Automatic blocking was on (data-blockingmode="auto"). Scripts Cookiebot blocked for you carry no markup, so nothing here holds them back: mark them up, or connect them by ID in Builderify.

  3. Done Line 7

    Script waits for consent to analytics.

  4. Done Line 10

    Script waits for consent to analytics and marketing.

  5. Check Line 12

    The Meta Pixel runs before consent. Add type="text/plain" data-bdf-consent="marketing", or delete it and connect it by ID in Builderify.

  6. Done Line 15

    <iframe> loads from data-src after consent to marketing.

  7. Check Line 17

    Placeholder class cookieconsent-optout-marketing. Builderify has no show-and-hide classes, so this element now shows to everyone. Remove it, or show it from your own code with bdfConsent.onChange().

  8. Done Line 18

    Cookiebot.renew() link now points to #cookie-settings, which opens Builderify's preferences.

  9. Done Line 20

    Cookiebot JavaScript rewritten for window.bdfConsent.

  10. Done Line 23

    Cookie Declaration script removed. Builderify lists your cookies in the banner's preferences, and a link to #cookie-settings opens them.

The same job, word for word
Job Cookiebot Builderify
Hold a script back type="text/plain" data-cookieconsent="statistics" type="text/plain" data-bdf-consent="analytics"
Hold an embed back data-cookieblock-src="…" data-cookieconsent="marketing" data-src="…" data-bdf-consent="marketing"
Categories preferences, statistics, marketing preferences, analytics, marketing (statistics is understood too)
Several categories data-cookieconsent="statistics, marketing" data-bdf-consent="analytics marketing" (all must be allowed)
Reopen the choices javascript: Cookiebot.renew() href="#cookie-settings" or bdfConsent.showPreferences()
Check in code Cookiebot.consent.marketing bdfConsent.has('marketing')
Run code on consent CookiebotOnAccept event bdfConsent.onConsent('marketing', fn)
Placeholder for a blocked embed class="cookieconsent-optout-marketing" None
Cookie list on a page Cookie Declaration script (cd.js) In the banner's preferences

Builderify releases script, iframe, img and video elements, including ones added after the page loads. Checking a page for pixels that fire before consent? The Meta Pixel cookie consent guide covers the Meta, TikTok and Microsoft tags in detail.

05 / Moving off it

How to replace Cookiebot
without a day unprotected.

Swap in one sitting, in this order, so there is never a moment with no banner or with two. Visitors are asked once more afterwards: Builderify keeps its own consent cookie and does not read Cookiebot’s.

Where the consent tag goes

WordPress

Install the Builderify plugin from your dashboard (it is not on WordPress.org yet), add your site key under Settings › Builderify, and tick “Load the cookie consent tag first in <head>”. Then deactivate the Cookiebot plugin.

Shopify

At the top of theme.liquid’s <head>. Choices are passed to Shopify’s Customer Privacy API for you.

Squarespace

Settings › Advanced › Code Injection › Header, on the very first line.

Wix

Settings › Custom Code › Add Custom Code, in Head, on all pages, dragged to the top of the list.

Webflow

Site settings › Custom code › Head code, above everything else, then republish.

  1. Keep your consent records

    Cookiebot keeps consent records for up to 12 months on every plan, but lists CSV export for Premium only, and cancelling an account purges its data. Download what you can, or note when the last consent was given, before you cancel.

  2. Put the Builderify consent tag first in <head>

    Builderify’s gate lives in that tag. It sets Google Consent Mode’s defaults and releases tagged scripts, so it must come before them.

  3. Convert your markup

    Run your templates through the converter above, page builders’ custom-code blocks included. Look at every “Check” line before you publish.

  4. Connect your pixels by ID

    Thirteen tags, from GA4 and Google Ads to the Meta Pixel, Hotjar and Microsoft Clarity, can be loaded by Builderify instead. Paste the ID in the dashboard and delete the old code, or it fires twice.

  5. Remove Cookiebot’s script and Cookie Declaration

    Then test in a private window. Before you answer the banner, your browser’s developer tools should show no _ga or _fbp cookies under Application, Cookies.

  6. Cancel Cookiebot last

    Only once the new banner works everywhere. A paid domain removed mid-term can still get a final invoice, because Cookiebot bills in arrears.

06 / With Builderify

A Cookiebot alternative
that never counts your pages.

Builderify Cookie Consent is a banner in the Builderify widget plus a small consent tag first in <head>. Your page count never enters the price: what is metered is page loads of the widget, 10 credits per 1,000, with 250 free credits a month.

Cookiebot Free and Builderify, side by side
On the free plan Cookiebot Free Builderify
Limited by 50 subpages and one domain; traffic not counted 250 credits a month; banner page loads cost 10 per 1,000, about 25,000 if nothing else uses them
When you outgrow it Premium per domain, or a suspended account and no banner At a zero balance the banner keeps running; popups and chat pause
Blocking Manual markup Manual markup, plus 13 tags loaded by ID only after their category is allowed
Consent lasts Up to 1 month 6, 12 or 13 months, your choice; a new policy version asks again
Consent records Kept up to 12 months; CSV export is Premium Kept 24 months with a masked IP; CSV export
Rules by region Geotargeting is Premium Opt-in or opt-out by the visitor’s time zone
Global Privacy Control Supported Honoured by default: where consent is opt-out, it keeps Marketing off
Placeholders, cookie declaration page Both, in Cookiebot’s default style Neither; the cookie list sits in the banner’s preferences
IAB TCF, Google-certified CMP TCF is Premium; Cookiebot is certified Neither
More websites Each domain on Premium The first is included; 100 credits once for each after it
What the banner costsCredits
Subpages, however many0
The consent tag in <head>0
Consent decisions and the log0
The cookie scanner0
Page loads of the widget, banner included10 / 1,000
Free every month250
Banner-only page loads, free≈ 25,000 a month

The cookie scanner works differently too: instead of crawling your site, a sample of real visits reports the cookie names they can see, and known ones are matched to a library of 117 patterns. Nothing to count, so nothing to bill.

Know this first

  1. 1

    No automatic blocking.

    Builderify holds back what you tag and the tags you connect by ID. A script with neither runs before consent, exactly as it would on Cookiebot Free without markup.

  2. 2

    Not a Google-certified CMP, and no IAB TCF.

    If you show ads on your own site through AdSense, Ad Manager or AdMob to visitors in Europe, Google asks for a certified consent platform. Cookiebot is one; stay with it for that.

  3. 3

    No placeholder for a blocked embed.

    A held-back YouTube or map iframe stays empty until consent. Withdrawing consent reloads the page when refused code has already run, so it stops.

  4. 4

    At zero credits, the banner stays; the rest pauses.

    If your balance reaches zero, the banner and the consent tag keep running unmetered. Popups, chat and the other modules pause until you add credits or your 250 free credits renew.

  5. 5

    The WordPress plugin isn’t on WordPress.org yet.

    You download it from your Builderify dashboard and upload it. Elsewhere it is one script tag and the consent tag, on Shopify, Squarespace, Wix, Webflow or any site.

Weighing CookieYes too? Its free plan counts pageviews instead: the CookieYes free plan limit. Visitors sending a privacy signal? What Global Privacy Control asks of you. On WordPress with a consent plugin, a stats plugin and a popup plugin, the too-many-plugins guide shows what one script tag can replace.

07 / Which to pick

Stay on Cookiebot Free, pay,
or switch?

If

One domain, comfortably under 50 subpages, and growing slowly.

Pick

Stay on Cookiebot Free. It does the job, traffic is never counted, and your manual markup fails safe. Accept its default banner, one language and consent that is asked again after a month.

If

One small domain, and you want your own design, languages or geotargeting.

Pick

Cookiebot Premium Lite. €7 a month for every Premium feature, as long as it stays a single domain under 50 subpages.

If

You show AdSense, Ad Manager or AdMob ads to visitors in Europe, or need IAB TCF.

Pick

Cookiebot Premium, or another Google-certified platform. Not Builderify, which is neither certified nor on TCF.

If

Hundreds or thousands of pages and plenty of traffic, and you want blocking done for you.

Pick

Cookiebot Premium priced by page count, or CookieYes, priced by pageviews; compare its limits. Builderify’s cost follows traffic and you tag scripts yourself.

If

A site past 50 subpages, traffic in the tens of thousands a month, scripts you can tag.

Pick

Builderify. 25,000 banner-only page loads a month on the free credits, then one-time packs from $9. No page count, consent kept up to 13 months, and at zero credits the banner keeps running.

Questions

Cookiebot's free plan, before you ask.

Yes, for one domain with up to 50 subpages, with no limit on traffic. The free plan shows Cookiebot's standard banner in one language, keeps consent for up to a month, and lists cookie blocking as manual only. Every new account starts with a 14-day trial of the Premium features.

Any unique URL on your domain that Cookiebot's scanner can reach by following links, including links in your sitemap. Blog posts, archive pages and the attachment pages WordPress creates for media all count; image files and 404 pages do not. Each subdomain is a separate domain.

The domain no longer qualifies for the free plan and needs a Premium subscription. Cookiebot says that if no payment details are added by the end of the trial, the account is suspended and its scripts stop working, so no banner is shown. Scripts you marked up manually stay blocked; untagged ones run.

Premium Lite is €7 a month for a single domain under 50 subpages. Past that, a single domain under 350 subpages is billed as Premium Medium, €30 a month, because the €15 Small tier needs four or more domains. Large is €50 and Extra Large €90 a month per domain, before VAT.

Builderify does not count pages: its cookie banner is metered by page loads of its widget, 10 credits per 1,000, with 250 free credits a month, about 25,000 banner-only page loads. Like Cookiebot Free, it blocks only the scripts you tag or connect by ID. It is not a Google-certified CMP, so AdSense publishers in Europe should stay with Cookiebot or another certified platform.

Sources

Cookiebot’s pricing page, help centre and plugin listing, and the ICO. Read on 17 October 2026.

← All guides The CookieYes free plan limit

Stop losing the visitors
you already paid for.

More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.

Start free See what it does