CookieCrumb vs Cookiebot
Gratuito con pagine illimitate vs prezzi in base al numero di sottopagine.
Cookiebot è molto diffuso e il suo scanner è accurato, ma il prezzo cresce con il numero di sottopagine del sito e ogni sottodominio viene fatturato a parte. CookieCrumb è gratuito, senza limiti di pagine o di visualizzazioni.
Differenze Chiave
Nessun prezzo per pagina
Cookiebot calcola il prezzo dei suoi piani in base al numero di sottopagine, a partire da 7 € al mese per i siti piccoli; il piano gratuito copre un dominio con al massimo 50 sottopagine. Il piano gratuito di CookieCrumb non ha limiti di pagine né di visualizzazioni, per un massimo di 10 siti.
Uno script di caricamento molto più leggero
Il file uc.js di Cookiebot pesa circa 121 KB (28 KB con gzip); il loader di CookieCrumb circa 25 KB (9 KB con gzip), misurati a ottobre 2026. Viene caricato su ogni pagina, prima degli altri tuoi tag.
Scansioni on demand, prima e dopo il consenso
Cookiebot esegue le scansioni secondo una pianificazione. CookieCrumb le esegue quando vuoi tu (dalla dashboard, tramite l'API o dalla tua CI dopo un rilascio) in un browser reale, prima e dopo l'accettazione del banner, e segnala i cookie impostati troppo presto.
CookieCrumb vs Cookiebot: the detailed comparison
Cookiebot (by Usercentrics) is one of the longest-standing consent platforms in the EU market, known for its thorough scheduled scanning and enterprise-friendly compliance posture. Choosing between Cookiebot and CookieCrumb is mostly a question of where you want the rigor: in reporting depth and vendor pedigree, or in on-page enforcement and performance.
Here is the honest comparison — where CookieCrumb is genuinely better, where Cookiebot is, and how to migrate if you decide to.
| Feature | CookieCrumb | Cookiebot |
|---|---|---|
| Price | Free — Enterprise limits on request | Free for 1 domain up to 50 subpages; paid from €7 / mo, priced by subpages |
| Free tier | 10 sites, unlimited pages and pageviews | 1 domain, up to 50 subpages |
| Script size on your pages | ~25 KB (9 KB gzipped) | ~121 KB (28 KB gzipped) |
| Prior-blocking | Tagged scripts held until consent; fails closed | Auto-blocking mode available; correctness depends on markup |
| Cookie scanner | HTTP crawler + optional headless-browser engine, on demand or scheduled | Monthly scheduled deep scans (a long-standing strength) |
| Existing-CMP detection on scan | Browser engine detects an installed CMP and imports its declaration | — |
| Pricing model | Free; custom limits on request | Scales with subpage count; each subdomain billed separately |
| Full REST API + OpenAPI + agent discovery | Yes — every dashboard action | API exists; automation is not the product's center |
| Global Privacy Control | Honored automatically once enabled (one setting) | Supported |
Where CookieCrumb is genuinely better
Free, however big your sitemap
Cookiebot's plans are priced by number of subpages, and each subdomain is billed separately, so a growing content site drifts into higher tiers on its own. CookieCrumb is free with no page or pageview limit; publishing more pages is never a pricing event.
A fifth of the page weight
About 25 KB against about 121 KB for Cookiebot's uc.js (9 KB vs 28 KB gzipped, measured October 2026), loaded on every page before your other tags. If you care about LCP and INP, the consent layer is the wrong place to spend 96 KB.
Scans when you want them, not once a month
Cookiebot's scheduled monthly deep scan is genuinely thorough, but a deploy can add a tracker on day 2 of a 30-day cycle. CookieCrumb lets you trigger a scan on demand — from the dashboard, the API, or your CI pipeline after each release.
Migration without a re-audit
CookieCrumb's scanner detects an installed Cookiebot instance and imports its declared cookies and vendors, so you keep the inventory Cookiebot spent months building.
Where Cookiebot is the better fit
An honest comparison names the cases it loses. These are Cookiebot's.
Scanning pedigree and reporting depth
Cookiebot's scan reports are detailed and widely accepted by auditors, and the Usercentrics platform behind it serves genuine enterprise compliance programs. If your legal team already standardized on their report format, that is worth something.
IAB TCF ecosystem
If you run programmatic advertising that requires the IAB Transparency & Consent Framework with its full vendor list machinery, Cookiebot/Usercentrics is deeply invested there. CookieCrumb focuses on category-based consent, which fits most non-adtech sites better but is a real difference for publishers.
Migrating from Cookiebot to CookieCrumb
- 1Create a CookieCrumb site and run a browser-engine scan — it will detect Cookiebot and import the declared cookies and vendors.
- 2Review categories and translations; with language auto-detection on, CookieCrumb's banner follows the visitor's browser language, so check your locale texts in the dashboard.
- 3Place the CookieCrumb snippet in the <head> above your tags; if you used Cookiebot's manual markup (data-cookieconsent attributes), replace it with CookieCrumb's category tagging where needed.
- 4Remove the Cookiebot script and any CMS plugin so only one banner runs.
- 5Verify prior-blocking in devtools (non-essential cookies only after opt-in) and confirm consents are landing in the log.
CookieCrumb vs Cookiebot: common questions
Is CookieCrumb cheaper than Cookiebot?
Yes — CookieCrumb is free, with no page or pageview limit for up to 10 sites. Cookiebot's free plan covers one domain of up to 50 subpages; paid plans start at €7/month and scale with the number of subpages, so larger content sites pay progressively more.
Does CookieCrumb support the IAB TCF like Cookiebot does?
CookieCrumb uses clear category-based consent (necessary, preferences, analytics, marketing) rather than the IAB TCF vendor-list machinery. For sites running programmatic advertising that contractually requires TCF, Cookiebot is the safer fit; for everyone else, category consent is simpler for visitors and regulators alike.
Can I keep the cookie inventory Cookiebot built for me?
Yes — CookieCrumb's scanner detects an installed Cookiebot instance and imports its declared cookies and vendors as the starting inventory, which you can then re-verify with a fresh browser-engine scan.
How disruptive is the switch?
It is one script tag out, one script tag in, plus a scan review. The riskiest step is forgetting to remove the old banner — never run two consent platforms at once.
Numbers reflect public entry-tier pricing and typical script payloads at the time of writing; verify current figures with each vendor. See also the full comparison hub and how CookieCrumb works.