WordPress Cookie Consent Plugin: Free and Self-Hosted
A GDPR-ready cookie banner with no subscription and no third-party service: script blocking before consent, jurisdiction presets, a proof log — free.
The cookie banner has become the most hated tollbooth on the web — and yet, done badly, it protects no one: not your visitors, whose data leaks out before they’ve said yes, and not you, still exposed to regulators behind a purely decorative banner. The market’s answer was cloud services on subscription, billing you every month for the right to be compliant. I took the opposite road: a complete consent module, self-hosted, free — because compliance shouldn’t be a rent payment.
The essentials
- The European rule fits in one sentence: no non-essential cookie before freely given consent, and refusing must be as easy as accepting — France’s CNIL, one of the strictest enforcers, spells it out that way in its 2020 guidelines.
- The module blocks the scripts, inline snippets and iframes of the 50-odd services in its catalogue (Google Analytics, YouTube, maps…) until their category is accepted — the first thing any audit checks.
- 15 jurisdiction presets (plus 12 applied automatically when visitor geolocation is on) set which categories start pre-ticked: strict European opt-in, American opt-out that honours the Global Privacy Control (GPC) signal, Brazil’s LGPD…
- The consent log covers 13 months as hashed fingerprints: no IP address or account stored. A visitor’s choice is kept for 13 months too, longer than the 6 months France’s CNIL calls a good practice.
- 100% self-hosted and free: no subscription, no billed scans, no third-party server inside your consent loop (the optional IAB TCF mode, off by default, downloads the IAB vendor list).
What must a cookie banner do to be genuinely compliant?
Three things, in this order: prevent any non-essential cookie from being set before the visitor chooses, make refusal as accessible as acceptance, and keep proof of the consent collected. Everything else — colors, position, wording — is decoration around those three obligations.
The first one disqualifies most WordPress cookie consent plugins in the wild. A banner that displays while Google Analytics, the Meta pixel, or a YouTube video are already dropping their cookies is not a consent mechanism: it’s a decorative notification. France’s CNIL has stated it without ambiguity since its 2020 guidelines and recommendation, and it’s the first point tested during an audit — just open your browser’s inspector on your homepage, Cookies tab, before clicking anything.
The second killed the single-button banner: if accepting takes one click, refusing must take one click. Flows where refusal has to be earned — “settings,” then uncheck, then confirm — are explicitly targeted by enforcement orders.
The third is the least known: if you’re audited, the burden is on you to demonstrate that consent was collected, when, and for what. Without a log, your compliance rests on your word.
Why a self-hosted banner rather than a cloud service?
Because your visitors’ consent has no reason to pass through a third-party server, and your compliance no reason to become a subscription: a self-hosted banner does the same job from your own site, with no rent and no dependency.
The market organized itself around SaaS solutions — Cookiebot, CookieYes, Usercentrics — whose model is to bill by traffic, pages scanned, or domain. That model has three consequences you discover after the fact: the price climbs with your audience, the banner stops working if the subscription does, and one more actor slips into your consent data pipeline — ironic, for a data-protection mechanism. Complianz and CookieYes, at over a million active installations each on WordPress.org, show the scale of the demand; both sell paid tiers on top of the free plugin.
Self-hosting flips every term of that deal: the banner is served by your site, the log lives in your database, the cost is zero and will stay zero. The trade-off is that your server does the work — light work, but real: the module rewrites your pages to neutralize scripts before consent.
How does the module handle different laws — GDPR, CCPA, LGPD?
Through its jurisdiction presets: you pick the applicable law in the General tab (15 to choose from), and the banner adopts the matching starting point — strict European opt-in, American opt-out with GPC, Canadian or Australian hybrids, Brazil’s LGPD, India’s DPDP… Each preset sets which categories start pre-ticked (and, for the US, whether the GPC signal is honoured); every preset shows Accept all, Reject all and Customize, and a choice is kept for 13 months before the banner asks again. On that last point the module is more lenient than France’s CNIL, whose 2020 recommendation calls keeping the choice for 6 months a good practice (judged case by case, not a hard rule); a developer can shorten the 13 months with the blaminhor_cookies_consent_ttl filter. Twelve more presets (Argentina, Mexico, Singapore…) only apply through visitor geolocation.
Two presets deserve a closer look. The French preset is the European one, with the one-click refusal the CNIL insists on — a “Reject all” button every preset shows next to “Accept all”. The US preset honors the Global Privacy Control signal: a visitor whose browser emits GPC has non-essential categories refused without seeing the banner, and the site answers with a Sec-GPC-Acknowledged header — a requirement with fresh teeth, since new CCPA regulations took effect in January 2026 and put opt-out mechanics under closer scrutiny. The module does not add a “Do Not Sell or Share My Personal Information” link: add that one to your footer yourself.
How do I install and configure it in practice?
Activate the Cookie Banner module, pick your jurisdiction preset, tick your services, generate the policy page: four steps, no account to create.
- Install Blaminhor Essentials and activate the Cookie Banner module.
- Select the preset matching your situation — for a site serving EU visitors: the European opt-in, one-click refusal included.
- In the Services tab, tick the services your site uses (Google Analytics, YouTube, pixels…) from the catalogue of about 50, each in its fixed category: this selection drives both the pre-consent blocking and the cookie policy table. For YouTube, the plugin’s lazy-load facade for embeds is the natural companion: the player loads only when the visitor clicks.
- In the Diagnostic tab, click Create cookie policy page: the module generates the page with the
[blaminhor_cookie_declaration]shortcode, which displays a declaration table grouped by category — and which updates itself whenever you tick a service. That page nobody ever writes is nonetheless a legal requirement.

I ran this exact setup on a test site to take the screenshots for this article: from module activation to a working banner with its generated policy page, without leaving the WordPress admin once. If you use a Google product, the module sends the visitor’s choice through Consent Mode v2 as soon as it is made, in the format Analytics and Ads have expected since March 2024.
How does the module compare with Cookiebot, CookieYes and Complianz?
A SaaS banner such as Cookiebot or CookieYes hosts consent on the vendor’s servers and bills by traffic; Complianz runs on your server with a limited free tier and a paid Premium; the Blaminhor Essentials Cookie Banner module runs on your server, free with no tiers: pre-consent blocking, 15 presets, Global Privacy Control, a local 13-month log — no IAB TCF certification.
| Criterion | SaaS (Cookiebot, CookieYes…) | Complianz (freemium) | Blaminhor Essentials Cookie Banner module |
|---|---|---|---|
| Where consent is hosted | The vendor’s servers | Your server | Your server |
| Price | Subscription, grows with traffic | Limited free tier, Premium per site | Free, no tiers |
| Blocking before consent | Yes | Yes | Yes, for the services in its catalogue, inline scripts and iframes included |
| Jurisdiction presets | Depends on plan | Yes | 15 to choose from (plus 12 by geolocation), from GDPR to India’s DPDP |
| Global Privacy Control | Rare, in JS | Partial | Honored with the US preset + confirmation header |
| Proof log | On the vendor’s side | Local | Local, 13 months, hashed fingerprints |
| IAB TCF certification | Depends on plan | Add-on | No — by design, outside the ad-tech target |
What are the fines actually worth for a modest site?
The headline records — hundreds of millions against Google or Meta — are not your risk; your risk is a visitor’s complaint, free to file, that triggers an audit, a public compliance order, and the obligation to fix everything in a hurry. European authorities regularly publish sanctions and formal notices aimed at perfectly ordinary businesses — France’s CNIL is the most visible example — and California’s regulator now has its own enforcement track. The double penalty is mostly reputational: the order is public, and your duct-taped banner becomes a press release.
The good news is that the required level is entirely reachable: blocking before consent, one-click refusal, proof kept. Exactly what a well-designed WordPress cookie consent plugin automates.
Why isn’t compliance a subscription?
A cookie banner is no loss leader for a SaaS: it’s a stable legal obligation that resolves perfectly well with code running on your own server. Block before consenting, refuse as fast as accepting, prove without profiling — the Cookie Banner module does that work for free, and your visitors share their choice with you and no one else.
It’s one of the modules of Blaminhor Essentials, the free and modular plugin — alongside the CAPTCHA-free anti-spam, which shares the same philosophy: your data stays home, and the invoice doesn’t exist.
FAQ
Is a cookie banner mandatory on every WordPress site?
As soon as the site sets non-essential cookies — analytics, advertising, embedded videos — before or without consent, yes: the GDPR and the ePrivacy Directive require it for any site within reach of European law, wherever it is hosted. A brochure site with no analytics and no third-party embeds can do without one; in practice, that's rare.
What does a site risk without compliant consent?
European regulators — France's CNIL among the strictest — have issued fines running to hundreds of millions of euros against the giants, but they also audit and formally order small businesses to comply. The most concrete risk for a small site remains a visitor's complaint — free to file — and the compliance order that follows, with the public exposure that comes with it.
Why avoid cloud solutions like Cookiebot or CookieYes?
They run on subscriptions, put their own servers inside your consent loop, and the bill climbs with your traffic or the number of pages scanned. A self-hosted banner does the same job from your own server: no monthly invoice, no dependency, and your visitors' consent passes through nobody else's hands.
Does the module really block scripts before consent?
Yes, for the 50-odd services in its catalogue (Google Analytics, Meta Pixel, YouTube, maps…): their scripts, inline snippets included, and their iframes are neutralized until the visitor accepts the matching category, then executed once consent is given. It's the first thing regulators check — a banner that displays while Google Analytics is already running protects nobody.
How do I prove consent if I get audited?
The module keeps a consent log for 13 months as hashed fingerprints, with no IP address or account stored: you can demonstrate that consent was collected, and when, without keeping your visitors' addresses to prove it. The register is available right in the admin, with a CSV export; the 13 months are the module's own choice, not a figure set by a regulator.
What is Google Consent Mode v2, and does it concern me?
It's the mechanism through which your banner reports consent status to Google Analytics and Google Ads, required since March 2024 to use advertising measurement in the European Economic Area. If you use a Google product, it concerns you; the module sends Google the visitor's choice (a Consent Mode v2 update) as soon as it is made.
Does per-visitor geolocation work on its own?
No: adapting the banner to the visitor's country requires switching on visitor geolocation in the Advanced tab, then either Cloudflare's country header if your site runs behind it, or the MaxMind database, uploaded manually, plus a MaxMind reader library (WooCommerce ships one). Without country resolution, the module applies the strictest preset — you are compliant by default, never the other way around.
Comments