Cookiebot is the banner most people install first, which is also why most people eventually search for a way out: pricing that moves with page count, a scanner that rewrites the cookie declaration on its own schedule, and the Usercentrics migration. Here are the alternatives people pick, what each is good for, and how to verify the switch did not leave Google Analytics firing before the click.
Free, no signup. See what fires before your banner is answered.
Free · No signup · Nothing to install
Every one of these is a consent banner, which CookieInspector is not. Descriptions stick to what each vendor says on its own site; no pricing, because it changes faster than we can keep up.
Consent banner with a free tier and a popular WordPress plugin, plus consent logs and Google Consent Mode support.
Best for: WordPress sites and small businesses that want a quick install.
WordPress plugin that builds the banner and the cookie policy from a wizard, with a free core version and a premium tier.
Best for: WordPress sites that prefer to run the banner inside WordPress rather than from a hosted service.
Privacy suite from Italy: cookie banner, consent database and generators for privacy policy, cookie policy and terms.
Best for: Sites that want policies and the banner from one vendor.
Enterprise consent platform (IAB TCF, server-side consent, app SDKs), the company that also owns Cookiebot.
Best for: Publishers and larger organisations with programmatic advertising or mobile apps.
Consent banner plus policy generators, with a free plan for small sites.
Best for: Small businesses that want policies and a banner with little setup.
Consent management alongside a wider data-privacy platform (subject requests, vendor monitoring).
Best for: Teams that want consent as part of a broader privacy program.
Enterprise consent and preference management, strong in media and TCF-heavy setups.
Best for: Publishers and enterprises in Europe with advertising stacks.
Staying with Cookiebot? Our Cookiebot scanner comparison goes through what its built-in scanner checks and what it misses, and the list of 30+ consent platforms we recognise by name covers every option above.
Pricing by pages and domains: a growing site changes tier without changing anything else.
The automatic scan rewrites the cookie declaration, and the categories it picks are not always the ones you would.
The move to Usercentrics changed plans and admin for long-time accounts.
A banner that works on any platform with one script, no plugin to maintain.
An automatic monthly scan that keeps the cookie declaration current.
Mature Google Consent Mode v2 support and a long track record with regulators' expectations in the EU.
Install the new banner, then run a free scan of the page. The report shows every cookie, script and third-party request that fired before a first-time visitor clicked anything, split from what fired after, and whether "reject" blocked them. A banner that is installed but not wired to the tags is the most common thing we find, and it looks identical from the outside.
If the site uses Google tags, the same scan reads Consent Mode v2 off the network: the default state before the click and the update after it. That is the check that catches a template which loads gtag.js before the banner sets the default to denied.
“CookieInspector is not a Cookiebot replacement. It is the independent check that whichever banner you pick does what it says: nothing fires before consent, and rejecting actually rejects.”
No. Cookiebot shows the banner and records consent; CookieInspector does neither. It audits the site from the outside: which cookies and trackers fire before the visitor answers, and whether rejecting actually blocks them. People use it next to Cookiebot, or next to whatever they pick instead.
Run a free scan on a staging or production page with the new banner installed. The report shows every request that fired before the click, split from what fired after, so a banner that is installed but not blocking shows up on day one instead of in an audit.
It can. Consent Mode needs the default state set to denied before the Google tag loads and an update after the click; a template that loads the tag outside the banner's control quietly disables it. The scan reads the real state off the network (G100 before, G111 after) so you can verify it after the switch.
It tells you which cookies exist so the banner can list them. It does not show what fired before the visitor clicked, which is what a regulator looks at. Our Cookiebot comparison page covers the difference.
See exactly what's running on your site right now.
Run a free scanNo credit card required · Instant insights