# Cookiebot Pricing: Domains, Pages and Plan Requirements Canonical URL: https://www.martechdevs.com/blog/cookiebot-pricing By [Jafrin Akter Alo](https://www.martechdevs.com/authors/jafrin-akter-alo) Data Engineer and Co-founder, martechdevs Published: 2026-06-15 Last updated: 2026-09-11 Cookiebot Core pricing depends on the domains in your account and the scanned page count on each domain. Traffic volume does not determine its Core tier. Small sites can qualify for Free or Premium Lite, while account-level domain rules affect other tiers. Count production domains, inspect the scanner’s URL list and confirm the applicable plan before treating the headline price as your budget. A website with 25 navigation links may expose hundreds of URLs through its blog, product filters, language versions and old campaign pages. A founder budgeting from the visible menu can therefore end up in a different Cookiebot tier after the first scan. The other common surprise is account structure. Several small sites do not automatically become one small subscription just because one team manages them. Establish the domain inventory alongside the [consent and tracking implementation](https://www.martechdevs.com/analytics-tracking), so the budget and technical scope describe the same sites. ## Which Cookiebot product does the price describe? Cookiebot’s current pricing page presents Cookiebot Core alongside Usercentrics Advanced. The page distinguishes Core’s subpage-based model from Advanced’s session-based model. Treat the products and their commercial units separately when asking for a quote. See the [current pricing page](https://www.cookiebot.com/en/pricing/). This article focuses on Cookiebot Core’s Free and Premium tiers. An Advanced proposal may include different governance, integration and support requirements. It needs its own written scope and usage forecast. Before comparing a number from a sales page, invoice or older article, record: - The exact product and account type. - The selected currency and billing period. - The domains and subdomains covered. - The scanner’s count for each site. - The features and support arrangement required. That five-line description prevents a monthly-equivalent annual rate, a reseller arrangement and a retail monthly subscription being treated as the same offer. ## What are the published Core prices? On 11 September 2026, the pricing page’s USD monthly view lists Premium Lite at USD8, Small at USD16, Medium at USD34, Large at USD56 and Extra Large at USD96. These are per-domain prices excluding applicable VAT. The page lists page-count bands around 50, 350, 3,500 and 7,000 pages; check the assigned tier when a scan lands exactly on a boundary. The account-level qualification matters. Cookiebot’s [Premium Small change notice](https://support.cookiebot.com/hc/en-us/articles/20167285180188-Changes-to-the-Premium-Small-subscription) says Small is reserved for accounts with four or more domains, with the single-domain Lite exception preserved. A single site with 200 pages therefore should not be budgeted from the Small price merely because 200 sits below its page threshold. Free and Lite also serve different needs. A small site should compare the functions it needs after the trial, including ongoing scan behavior, banner configuration and support. A paid tier is useful only when its capabilities or account eligibility fit the requirement. The [Premium Lite documentation](https://support.cookiebot.com/hc/en-us/articles/13775776141468-Premium-Lite-Plan) describes its single-domain eligibility and the effect of adding domains or exceeding the small-site threshold. Some older help wording about multi-domain moves differs from the newer Small eligibility notice. Use the current account assessment or a written vendor quote for that transition. ## Do subdomains need separate subscriptions? Cookiebot’s [multi-website billing guidance](https://support.cookiebot.com/hc/en-us/articles/360004051054-Can-I-add-several-websites-under-1-subscription) says prices apply per domain and subdomain. Putting sites in the same account does not combine their page allowances into one subscription. Inventory the actual hosts used by customers. A main marketing site, a help centre and an application can have different owners and tracking behavior even when they share a brand. Record whether each needs the CMP implementation and how it is represented in the vendor account. A language folder and a language subdomain also produce different domain inventories. Do not change your website architecture just to chase a smaller CMP invoice without considering redirects, SEO, authentication and operating ownership. First establish what the current design needs. Avoid adding duplicate representations of the same intended site without checking the vendor’s domain guidance. The pricing FAQ specifically discusses apex and www handling. Have the person who owns the website’s redirect behavior confirm which host should be configured. For staging and development, ask about the supported alias arrangement. Cookiebot’s [terms](https://www.cookiebot.com/en/terms-of-service/) describe internal domain aliases for non-production use with limited functionality. A test alias should not be assumed to provide the same consent logging as a production subscription. ## Why can the scanner count more pages than your CMS? The scanner follows accessible HTML URLs and links. Its view of the site can therefore include pages beyond the CMS’s primary “Pages” list. Cookiebot’s [scanner definition](https://support.cookiebot.com/hc/en-us/articles/360003773214-How-does-the-Cookiebot-scanner-define-pages) explains the downloadable URL list and the originating-link information used to inspect findings. Start with that evidence. Sort the URLs into patterns such as product pages, blog posts, category archives, language versions, query variants and obsolete pages. Compare a sample from each group with the site the visitor can actually reach. An illustrative content site might have 35 main pages, 180 articles, 20 category pages and 15 public campaign pages. That is 250 URLs before considering dynamic variants. The 35-page CMS count would be an incomplete forecast, even though nobody created 215 new navigation items. Use the list to answer three different questions: - Which pages are legitimate parts of the live website? - Which obsolete or accidental pages should the web team remove or redirect for business reasons? - Which count appears questionable and needs a vendor review? Do not block the scanner from legitimate pages solely to force a cheaper tier while those pages continue setting trackers. That would reduce the usefulness of the inventory you are paying for. If the crawler encounters a technical trap or an unintended URL expansion, document the pattern and resolve it with the web team and vendor. Keep the before-and-after URL lists. They make a billing question reviewable and reveal whether a cleanup actually changed the accessible site. ![Inventory domains, scan and review URLs, correct account or site issues, then confirm the eligible tier and operating budget.](https://www.martechdevs.com/assets/blog/cookiebot-pricing.svg) ## What do realistic budget examples look like? Use domain-level inputs and label assumptions. The following examples apply the published USD monthly amounts to hypothetical accounts; they exclude taxes, services and any negotiated terms. A single 30-page site requiring Premium Lite would have a software planning cost of USD8 per month, or USD96 across 12 monthly payments. Confirm that the scan and account qualify before applying that figure. A single 200-page site subject to the current Small eligibility rule would use Medium at USD34 per month in this example, or USD408 across 12 monthly payments. Four separate 200-page domains qualifying for Small would total 4 × USD16 = USD64 per month, or USD768 across 12 payments. These examples deliberately stay away from exact page-band boundaries. They also show why multiplying every small domain by the lowest advertised rate produces a misleading budget. Now add the work. Suppose a hypothetical two-domain deployment requires eight internal hours for configuration and testing and one hour each month for review. That is 20 hours in the first year. At an assumed internal cost of USD75 per hour, the effort is valued at USD1,500, separate from the subscription invoice. Replace the hours with your own scope. A site with a standard integration and a few tags can require different work from a multilingual application with custom event collection, regional policies and several destination systems. The [GTM pricing guide](https://www.martechdevs.com/blog/google-tag-manager-pricing) uses the same separation between software, infrastructure and implementation. It helps prevent a free tag-management licence from hiding the work needed to connect consent state to actual tags. ## Can the subscription increase automatically? Yes. Cookiebot describes automatic tier changes based on the scanned page count. Its [subscription-plan guide](https://support.cookiebot.com/hc/en-us/articles/360004162973-What-is-my-subscription-plan-Cookiebot-Admin) also tells customers who have reduced page counts to contact support about moving to a smaller plan. Do not assume that deleting content immediately reverses a prior invoice or changes the next bill without checking the process. Make content growth visible in the forecast. If the company plans to add 100 articles or launch a second language, include those pages before approving the current tier. If it plans to retire a microsite, verify the domain’s removal and cancellation steps rather than only deleting the banner script. Assign billing and scan notifications to an owner who understands both the site and the budget. A finance mailbox may receive an upgrade notice without knowing that an application release created thousands of accessible URL variants. When a charge changes, collect the invoice period, configured domains, relevant scan result and prior configuration. Ask the vendor to explain the calculation from those records. This is more useful than comparing the bill with a generic headline price. ## What work does the subscription leave with your team? The CMP can collect and distribute consent choices within its supported implementation. Your team still needs to decide which tools and purposes are present, configure the integration and test the behavior required by the business’s privacy specification. Price these tasks when they are part of the project: ## Checklist - [ ] Reviewing the tracker inventory and resolving unclassified items. - [ ] Connecting consent defaults and updates to the tag-management setup. - [ ] Checking embedded video, chat, forms and other third-party components. - [ ] Testing first visits, returning visits and changed consent choices. - [ ] Confirming required language and regional behavior. - [ ] Repeating key checks after a site release or a new marketing tool. Treat this as technical implementation work. A subscription does not by itself establish that every legal obligation is satisfied. The responsible privacy owner supplies the requirements, and the implementation should provide evidence that the configured behavior matches them. The [Cookiebot implementation guide](https://www.martechdevs.com/blog/cookiebot-implementation-mistakes) covers the runtime checks. The [Consent Mode v2 guide](https://www.martechdevs.com/blog/consent-mode-v2) explains the Google signals so a team can distinguish a visible banner from a working measurement integration. ## How should you evaluate a different CMP quote? Compare the same websites and required behavior. A page-based price, a session-based price and an enterprise agreement can each fit different operating needs. None can be judged fairly from its smallest advertised number. Send the candidate vendor a domain list, the known page or traffic volume in its billable unit, required frameworks and languages, tag stack, support needs and intended billing term. Request a breakdown of software, onboarding and ongoing services. For a migration, add the work needed to change scripts, preserve or renew consent appropriately, update tag behavior and verify every important journey. A lower monthly price can still require a meaningful one-time project. Use the [CMP comparison](https://www.martechdevs.com/blog/consent-management-platforms) to choose a shortlist by capability before negotiating the final amount. ## Frequently asked questions ### Is Cookiebot free for a small website? A single small domain can qualify for the Free plan, subject to the documented page limit and reduced functionality. Check the scan result and the features you will use after the trial. A site’s navigation count is not enough to determine eligibility. ### Does Cookiebot charge for page views? Cookiebot Core uses domains and scanned subpages for its tier structure. The Advanced product presented on the same pricing page uses a different model. Keep the exact product name and billable unit on your budget. ### Why is a small website on Premium Medium? Account-level eligibility can affect the available tier even when the page count seems small. Review the current Premium Small rule, the total configured domains and the scanner’s count. Ask support for the calculation if the assigned plan remains unclear. ### Can several domains share one subscription? A shared account can manage multiple domains, but Cookiebot’s guidance prices domains and subdomains separately. Domain groups organize configuration; they do not automatically pool all sites into one paid allowance. Confirm any reseller or negotiated arrangement separately. ### Can I reduce the bill by deleting pages? Removing obsolete accessible content can change the scan result when the site genuinely becomes smaller. Follow the vendor’s downgrade process and retain evidence of the new count. Keep legitimate live pages within the scan so your tracker inventory remains useful. ## Sources 1. Cookiebot, [Pricing and plans](https://www.cookiebot.com/en/pricing/), USD monthly view accessed 11 September 2026. 2. Cookiebot, [Changes to the Premium Small subscription](https://support.cookiebot.com/hc/en-us/articles/20167285180188-Changes-to-the-Premium-Small-subscription), updated 8 June 2026, accessed 11 September 2026. 3. Cookiebot, [Premium Lite Plan](https://support.cookiebot.com/hc/en-us/articles/13775776141468-Premium-Lite-Plan), updated 2 December 2025, accessed 11 September 2026. 4. Cookiebot, [Can I add several websites under one subscription?](https://support.cookiebot.com/hc/en-us/articles/360004051054-Can-I-add-several-websites-under-1-subscription), updated 2 June 2026, accessed 11 September 2026. 5. Cookiebot, [How the scanner defines pages](https://support.cookiebot.com/hc/en-us/articles/360003773214-How-does-the-Cookiebot-scanner-define-pages), accessed 11 September 2026. 6. Cookiebot, [Subscription plan in Cookiebot Admin](https://support.cookiebot.com/hc/en-us/articles/360004162973-What-is-my-subscription-plan-Cookiebot-Admin), updated 26 March 2026, accessed 11 September 2026. 7. Cookiebot, [Terms of Service](https://www.cookiebot.com/en/terms-of-service/), accessed 11 September 2026.