Softwr

Legal · head to head

Cookiebot vs Termly

Cookiebot logo

Cookiebot

Legal

Automated cookie scanning and consent banner for websites, owned by Usercentrics

From
Free
Rated
-
Full reviewWebsite
Termly logo

Termly

Cybersecurity

Legal policy generator and cookie consent banner for small websites

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Cookiebot pricing is per domain and banded by subpage count, so an organisation with many brand domains or a large content site pays many multiples of the 7 euro headline, and the bands are counted from the scan rather than from what you think you publish.; Termly a standard plan licenses one website, so an agency or a business with several brand domains multiplies the headline price by the number of sites and the cheap option stops being cheap at four or five domains.
  • They diverge on capability: Cookiebot covers Automated cookie scanning, Termly covers Policy generator.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Cookiebot and Termly actually diverge.

Attributes where Cookiebot and Termly differ
AttributeCookiebotTermly
Pricing modelPer domain per month by subpage countPer website per month
CategoryLegalCybersecurity

Identical on both: starting price (Free), free tier (Yes), platforms (Web), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Cookiebot

  • Automated cookie scanning
  • Prior blocking
  • Google Consent Mode v2
  • IAB TCF support
  • Consent logging
  • Cookie declaration
  • Multi-language banners
  • Geotargeting

Only in Termly

  • Policy generator
  • Automatic policy updates
  • Consent banner
  • Script auto blocker
  • Cookie scanner
  • Consent log
  • WordPress plugin
  • Do not sell handling

What people use each for

The jobs each tool is most often brought in to do.

Cookiebot

  • A marketing team that needs a defensible consent record for European visitors without adding privacy engineering headcountnot Termly
  • A site using Google Ads and Analytics that must send Consent Mode v2 signals or lose conversion measurement in the EEAnot Termly
  • An agency managing many small client sites that wants per-domain billing it can pass through at costnot Termly
  • A content-heavy publisher needing IAB TCF signals passed to advertising partnersnot Termly

Termly

  • A small e-commerce shop that needs a privacy policy, terms and a compliant cookie banner before launch without engaging a solicitornot Cookiebot
  • A freelance web developer standardising the legal and consent layer across client sites, buying a licence per site or an agency arrangementnot Cookiebot
  • A WordPress site owner who needs scripts blocked before consent and does not have a tag manager set upnot Cookiebot
  • A US small business newly in scope for a state privacy law that needs a do not sell opt-out on the site quicklynot Cookiebot

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Cookiebot

  • Pricing is per domain and banded by subpage count, so an organisation with many brand domains or a large content site pays many multiples of the 7 euro headline, and the bands are counted from the scan rather than from what you think you publish.
  • Enterprise features such as single sign-on, banner A and B testing and a dedicated account manager sit on Usercentrics Web CMP rather than on Cookiebot, so growing out of Cookiebot means migrating to a sibling product with its own dashboard and contract.
  • Prior blocking depends on Cookiebot recognising the script, and custom or first-party tags frequently need manual tagging, which means a site can believe it is blocking trackers when it is not until someone audits it.
  • Scans crawl a limited number of subpages per band, so trackers that only appear on deep or gated pages can go undiscovered and unblocked between scans.
  • The free tier carries Cookiebot branding and is limited to one domain and 50 subpages, which makes it a demonstration rather than a workable option for anything but a brochure site.

Termly

  • A standard plan licenses one website, so an agency or a business with several brand domains multiplies the headline price by the number of sites and the cheap option stops being cheap at four or five domains.
  • Generated policies are templates conditioned on questionnaire answers, so they describe the data practices you claimed rather than the ones your code performs, and a regulator comparing the policy to actual tracking finds the gap not the vendor.
  • Banner view limits apply on the lower tiers, and a site that spikes in traffic can exhaust its allowance mid month, which is the worst possible moment for consent handling to degrade.
  • It covers websites well but has little for mobile apps, so a company with an iOS and Android app alongside its site needs a second consent mechanism and a second consent record.
  • There is no data mapping, subject rights automation or vendor inventory, so any company that grows into real privacy programme obligations outgrows Termly entirely rather than upgrading within it.

Pricing, plan by plan

Cookiebot

Free
  • FreeFree
    • 1 domain, up to 50 subpages
    • Automated scanning
    • Google Consent Mode
  • Premium Lite$7/month
    • 1 domain, up to 50 subpages
    • Custom banner design and logo
    • Multi-language banners
  • Premium Small$15/month
    • Per domain
    • Up to 350 subpages per domain
    • Multiple domains supported
  • Premium Medium$30/month
    • Per domain
    • Up to 3,500 subpages per domain

Termly

Free
  • FreeFree
    • 1 basic legal policy
    • 10,000 monthly banner views
    • Cookie consent banner
  • Starter$10/month
    • 2 legal policies
    • 10 policy edits
    • 50,000 monthly banner views
  • Pro Plus$15/month
    • Unlimited banner views
    • Additional legal policies
    • Multilingual banners

Which should you pick?

Choose Cookiebot if

  • You need automated cookie scanning.
  • You want to start without paying.
  • You also want prior blocking.
Cookiebot review

Choose Termly if

  • You need policy generator.
  • You want to start without paying.
  • You also want automatic policy updates.
Termly review

Questions people ask

Is Cookiebot or Termly better?
Neither clearly leads. Cookiebot starts at Free and Termly at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cookiebot or Termly?
Cookiebot starts at Free and Termly at Free.
Does Cookiebot or Termly run on more platforms?
Both run on Web, so platform support will not decide this one for you.
Can I use Cookiebot for free?
Both have a free tier, so you can try either at no cost before committing.
What is Cookiebot best used for?
Cookiebot is most often used for a marketing team that needs a defensible consent record for european visitors without adding privacy engineering headcount, a site using google ads and analytics that must send consent mode v2 signals or lose conversion measurement in the eea, an agency managing many small client sites that wants per-domain billing it can pass through at cost, a content-heavy publisher needing iab tcf signals passed to advertising partners. Of those, a marketing team that needs a defensible consent record for european visitors without adding privacy engineering headcount and a site using google ads and analytics that must send consent mode v2 signals or lose conversion measurement in the eea are not what Termly is typically brought in for.
What can Cookiebot do that Termly cannot?
Cookiebot covers Automated cookie scanning, Prior blocking, Google Consent Mode v2, IAB TCF support. Termly covers Policy generator, Automatic policy updates, Consent banner, Script auto blocker.

Answered from the vendors’ own pages

Cookiebot: Who owns Cookiebot?

Usercentrics, which acquired the Danish developer Cybot in September 2021. It is sold as Cookiebot by Usercentrics alongside the separate Usercentrics Web CMP.

Termly: Does one Termly plan cover all my websites?

No. A standard plan licenses one website. Multiple domains need multiple licences or an agency arrangement, and this is the single most common surprise on the bill.

Cookiebot: What does a real deployment cost?

Between 7 and 90 euros per domain per month depending on subpage count. Ten domains on the medium band is 300 euros a month, not 7.

Termly: Are the generated policies legally sufficient?

They are templates conditioned on your answers and are not legal advice. They are proportionate for a simple site and inadequate where actual data flows are complex or regulated.

Cookiebot: Does it support Google Consent Mode v2?

Yes, and Cookiebot is in Google CMP partner programme, which matters if you run Google advertising into the EEA.

Termly: Is there a genuinely free plan?

Yes, one basic policy, one site, 10,000 monthly banner views and quarterly cookie scans, with no card required.

Cookiebot: Is the free plan usable in production?

Only for a single very small site. It caps at one domain and 50 subpages and shows Cookiebot branding on the banner.

Termly: Does it handle US state privacy opt-outs?

Yes, including a do not sell or share mechanism and regional rule sets, alongside GDPR consent for EU visitors.

Share

Related pages

More on Cookiebot

More on Termly

Keep looking

Other head to heads