Consentik is a free, fast, GDPR-compliant cookie consent plugin built by people who run real WordPress sites. Drop it in, pick a layout, and you're compliant in about three minutes — without a popup that looks like a 2014 pop-under.
I'll be honest — most cookie banners on WordPress sites are doing nothing useful. They show a "We use cookies" message, the visitor clicks OK, and behind the scenes Google Analytics has already been firing for ten seconds. That's not compliance. That's theater.
Real consent has three jobs: (1) block non-essential cookies and scripts before the visitor agrees, (2) record the choice with a timestamp you can show a regulator, and (3) respect the user when they want to change their mind later. Consentik does all three out of the box, with sensible defaults you don't have to think about.
We've stripped Consentik down to the things that matter: blocking, recording, customizing, and proving consent. No upsells for features you'd expect to be there.
Auto-detects and blocks Google Analytics, Meta Pixel, YouTube embeds, Hotjar and 200+ trackers before the user clicks Accept.
Scans every page on your site and sorts cookies into Necessary, Analytics, Marketing and Personalization. Re-runs monthly.
Five layouts, light/dark/auto, custom colors, fonts, radius and spacing. No "consent.management.tool" branding.
Show the full opt-in banner in the EU, a CCPA "Do not sell" link in California, and nothing at all in countries that don't require it.
Banner copy follows the visitor's browser language. Override per-language from the admin if you want a specific tone.
See your accept rate, reject rate and which categories visitors decline most — without sending data to a third party.
Every choice is logged with timestamp, banner version and IP hash. Export to CSV when a regulator asks.
No jQuery dependency, no render-blocking CSS, no third-party CDN. Lighthouse scores stay where they are.
Tested on Elementor, Divi, Bricks, Astra, Kadence, GeneratePress, Avada, WooCommerce, MemberPress and the rest.
You'll find Consentik exactly where you'd expect it — in the WordPress sidebar, with the same form controls as core. No separate dashboard, no SaaS login, no "connect your account" wall.
Most "compliant" plugins ask you to list your cookies. Consentik does the opposite — it crawls your site, identifies every script that drops a cookie, and maps each one to a consent category automatically.
We've watched a lot of users install Consentik. Here's the path almost everyone takes — from "add new plugin" to a fully compliant site.
Search "Consentik" in your WordPress dashboard, or upload the .zip. Activate. That's it for setup.
One click. We crawl your site and build a categorized inventory of every script and cookie.
Five banner styles. Live preview. Match your theme in about a minute. No CSS required.
Banner goes live. Every consent is recorded with timestamp and version. Export to CSV anytime.
Consentik doesn't replace your tools — it sits in front of them, holding back any script or cookie until consent is granted. These ones we test against every release.
Block payment gateway and analytics scripts until consent. Cart cookies stay essential.
Banner respects your theme styles. Use Elementor templates for the cookie policy page.
Detects and categorizes Divi's built-in scripts. Custom CSS variables match Divi tokens.
Native compatibility with Bricks templates and dynamic data. Tested with the latest Bricks.
Includes Google Consent Mode v2 — analytics still get pinged with anonymized signals.
Push consent state to GTM via dataLayer. Use built-in Consent Mode triggers.
Pixel waits for consent before initializing. CAPI is supported via WooCommerce extension.
Skip the banner for logged-in members who already accepted at signup.
We don't claim Consentik magically makes you compliant — that's a promise no plugin can keep. What it does is implement, by default, the technical requirements every major regulator expects to see.
Prior, freely-given, specific consent. "Reject all" given equal prominence to "Accept all". Withdrawal must be as easy as giving.
ICO-aligned banner that reflects current PECR guidance. Strictly necessary cookies are exempt; everything else needs explicit opt-in.
Opt-out model with a "Do not sell or share my personal information" link. Detects Global Privacy Control headers automatically.
Banner copy and categories aligned with ANPD guidance. Data subject request workflow ships with the plugin.
Optional TCF v2.3 mode. Required if you serve Google Ads, OpenX, Criteo or any programmatic exchange.
Native Consent Mode v2 support — keeps GA4 modeling working when users decline cookies, without firing them.
A note from the team: nothing on this page is legal advice. If you handle special categories of data (health, biometrics, kids), please talk to a real lawyer.
We're part of Google's Consent Management Platform Partner Program — which means our banner is officially recognised to work with Google Ads, AdSense and AdMob's EU user consent policy. If you serve Google ads to European visitors, you're required to use a Google CMP Partner. Consentik is one of them.
Listed in the official Google CMP Partner directory.
Real questions from the WordPress.org support forum and our inbox. If yours isn't here, ask us — we read every message.
mail Email supportYes — all the core features described on this page are free, forever. That includes unlimited cookie scans, geo-targeting, IAB TCF v2.3, Google Consent Mode v2, and consent logging. You install it directly from the WordPress.org plugin directory.
We do offer a paid add-on for sites that want priority email support and an SLA, but the plugin itself is fully usable without it.
The front-end script is around 8 KB gzipped, has no jQuery dependency, and is loaded asynchronously. On a typical WordPress site we see a Lighthouse performance impact of under 1 point.
If you're using a page-cache plugin (WP Rocket, LiteSpeed, etc.), Consentik is fully cache-friendly. Each visitor's consent state is stored client-side, not in the page.
Yes. Consentik treats WooCommerce's session and cart cookies as strictly necessary by default, so checkout never breaks. Marketing pixels (Meta, TikTok, Google Ads) are blocked until consent. We test against the latest WooCommerce on every plugin release.
Honest answer: a cookie banner is necessary for GDPR compliance, but it's not sufficient on its own. You also need a privacy policy, a lawful basis for processing personal data, and a way to handle data subject requests.
What Consentik does handle is the technical side: blocking trackers before consent, recording each consent with a timestamp and version, and giving visitors a way to change their mind later. That covers the part regulators most often check.
No. The auto-blocker handles the 200+ most common trackers (Google Analytics, Meta Pixel, YouTube embeds, Hotjar, etc.) without any code changes. If you have a custom script you want to block, you can add a data-consentik="marketing" attribute and Consentik takes it from there.
It works exactly how Google wants it to work. Consentik ships with native Google Consent Mode v2 — when a visitor declines analytics cookies, GA4 still receives anonymized, cookieless pings. That keeps your conversion modeling and audience reporting alive without storing personal data.
When the visitor accepts, GA4 switches to full tracking. No code changes required.
Yes — colors, fonts, border radius, button styles, layout (bottom bar, modal, side card), copy, language, and logo. If you need to go further, every element is targetable via plain CSS classes. There's no shadow DOM hiding things from you.
Yes. Consentik renders the banner client-side and stores consent state in localStorage, so the cached HTML page is identical for every visitor. We've confirmed compatibility with WP Rocket, LiteSpeed Cache, W3 Total Cache, Cloudflare APO, and most CDN setups.
Consentik records every consent event with a UTC timestamp, the banner version shown, the categories accepted/rejected, the country code derived from IP, and a hashed visitor identifier (no raw IP stored). You can export the log to CSV from the admin or pull it via the REST API. That's typically what data-protection authorities want to see.
Each banner has a version number. When you make a material change — adding a new category, changing what processing is described — you can bump the version, and Consentik will re-prompt all visitors. Cosmetic changes (color, font) don't trigger a re-prompt. The choice is yours and it's a single click.
Free core plugin. No credit card, no "talk to sales." Just a clean, compliant banner you can stop thinking about.
Simplifying privacy compliance, protecting data and building trust.