iubenda bundles three things: a cookie banner, a consent database and generators for the privacy policy, cookie policy and terms. The search for an alternative usually starts when pageview-based pricing climbs or when a team wants the banner and the policies from different vendors. These are the options, what each covers, and how to check the new banner before switching the old one off.
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 plus policy generators, with a free plan for small sites.
Best for: Small businesses that want policies and a banner with little setup.
Hosted consent banner with an automatic cookie scan, now part of Usercentrics; one of the most widely installed banners on the web.
Best for: Small and mid-sized sites that want a banner and a cookie declaration maintained for them.
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.
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 management alongside a wider data-privacy platform (subject requests, vendor monitoring).
Best for: Teams that want consent as part of a broader privacy program.
Staying with iubenda? Our iubenda 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 tied to pageviews, with overage when traffic grows.
Wanting the policies from one tool and the banner from another, rather than the bundle.
Teams on WordPress or Shopify that prefer a banner native to their platform.
Policy generators kept up to date with legal changes, in several languages, from the same vendor as the banner.
A consent database that stores the proof of each consent.
One contract and one admin for banner, policies and records.
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 iubenda replacement. It is the independent check that whichever banner you pick does what it says: nothing fires before consent, and rejecting actually rejects.”
No. iubenda 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 iubenda, 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.
No. Policy generation is what iubenda and Termly do; a scanner has no business writing your legal documents. What the scan gives you is the list of what the policy has to disclose: every cookie, every third-party domain, with the tag that set it.
See exactly what's running on your site right now.
Run a free scanNo credit card required · Instant insights