Everything the complete plugin does, theme by theme. Every feature is in the 30-day trial.
- 248jurisdictions applied
- 675tools recognised
- 54languages
- 11.43 kBon a first visit
A banner that respects visitors
Equal choice
Accept and reject on the first layer, with the same weight.
No pre-ticked boxes, no consent by scrolling.
Choose tool by tool
Visitors can accept a category or a single tool, and change their choice at any time from a link or the cookie button.
Accessible
Keyboard and screen reader friendly.
Light, dark or automatic theme, a discreet box or a bar, rounded or square corners, in your colours.
Global Privacy Control
On with country rules or with one click, and Cookie Rocks warns you when your visitors’ laws require it.
When a visitor’s browser sends the GPC signal, marketing stays refused, as several US states require. The signal also cancels an earlier yes to marketing, the cookie button says “Opt-out request honored”, and a signed-in visitor’s refusal follows their account to their other browsers. The “Do Not Sell or Share” link opens a one-click opt-out. With a browser opt-out signal, Cookie Rocks stops advertising. Statistics can keep running: a measurement tool bound by a service contract is not a sale or sharing. If your analytics tool shares data for advertising, turn that sharing off.
Fonts from other sites
The free Audit lists the fonts your pages load from another site before any choice, with what each licence allows.
Pro copies the Google Fonts it finds in your pages and stylesheets, and shows the state of each font.
Consent and refusal do not last the same time
Cookie Rocks keeps a consent no longer than the strictest country you target allows, and keeps a refusal at least as long as the strictest country requires before asking again.
Example: a site that targets France and California keeps consent for 6 months at most, and a refusal for 12 months at least. In Colorado, a visitor who refused is not asked again.
Where the law allows less
Where the law only asks you to inform, the banner informs and lets visitors refuse: cookies work until the visitor opts out.
Where your countries allow it, audience measurement set up for it can run until the visitor objects.
In their language
The banner, its details panel and the cookie policy in 54 languages: English, Arabic, Azerbaijani, Bulgarian, Bangla, Catalan, Czech, Danish, German, Greek, Spanish (Spain), Spanish (Mexico), Estonian, Finnish, French, Irish, Hindi, Croatian, Hungarian, Armenian, Indonesian, Icelandic, Italian, Japanese, Georgian, Kazakh, Korean, Kyrgyz, Lithuanian, Latvian, Macedonian, Mongolian, Malay, Maltese, Norwegian Bokmål, Nepali, Dutch, Polish, Portuguese (Brazil), Portuguese (Portugal), Romanian, Russian, Slovak, Slovenian, Albanian, Serbian (Cyrillic), Serbian (Latin), Swedish, Turkish, Ukrainian, Uzbek, Vietnamese, Chinese (Simplified) and Chinese (Traditional).
With Polylang or WPML, the banner follows the language of each page. One option shows it in the visitor’s browser language instead, even when your site has no version in that language. The dashboard comes in 28 languages, the law sheets in 28.
What your visitors see
Choices, category by category
“Let me choose” opens this panel.
Necessary cookies are always on; the others wait for consent. Only the categories your site really uses are shown: no empty marketing switch on a site without marketing.
A small button to change the choice
After the first choice, a discreet round button stays in a corner of every page.
Or hide it and put a “Manage cookies” link in your footer instead.
A ring when the refusal is applied
It shows visitors that their refusal is applied and, for the United States, that their opt-out request was honoured, as California requires.
- For whom: every visitor who refuses, on every site. Visitors from the United States read “Opt-out request honored”, the others “Refusal applied”.
- When: after “Reject all”, “Do Not Sell or Share” or a category turned off in the details, and from the first page when the browser sends Global Privacy Control. A category hidden from the details never lights it.
- What: a ring around the button in the colour you choose, or none if you turn it off, and a message that stays 5 seconds.
A cookie policy that writes itself
Every tool found on your pages, with its provider, what its cookies do in one sentence and its privacy policy, grouped by category and dated.
Cookie names and durations are kept, shown on request. Made to look right on any theme, with two settings in Pro: a title and a width. See ours, live.
What a cookie policy must contain
Paste this in a page:
Rules by country
the strictest one wins
Each visitor, their own rules
One setting, for the whole world.
Each visitor gets the rules of their own country, read from its law sheet; texts, colours and services stay shared. The rules of your own country apply to every visitor, on top of theirs, except for a site in the United States. In the EU, the UK or Brazil, that means prior consent for everyone. Try the simulator.
Read where your site already knows it
The country is read on your own server or at your CDN (Cloudflare, Bunny, Kinsta, WP Engine and others), or, for a site without one, in a country database kept on your server and checked by its signature.
Only one source is trusted, after a check. The visitor’s IP address is never kept or sent.
Unknown means strict
Unknown country, unverified source, missing law sheet: the strict rules apply.
Consent is never assumed. A yes ends at the shortest limit of both countries; a no lasts at least what the visitor’s law asks.
A banner for each group of countries
Each group of countries can have its own banner: layout, position, texts and cookie button.
Choose your target countries one by one, or by region of the world.
Same page for everyone
The page stays the same for all visitors, so your page cache keeps working.
The country is asked once, on the first visit, and never again once the visitor has chosen. Sites that leave the option off load nothing more.
The lightest first visit we measured among banners that hold trackers
Written by us, for consent only
No framework and no third-party library: a tiny core in the page head reads the choice and sets Google Consent Mode before anything else, and a small script handles the banner, the signals and the release of held tools.
Nothing is loaded from our servers. The banner uses your site’s own font: no font file to download, no font service contacted.
Light on every page
11.43 kB on a first visit, banner included, then 1.00 kB on each next page.
Measured on a blank WordPress. And the engine is built for your site: it only carries the options you use. The measured figures.
How Cookie Rocks compares with other banners, measured →
Inside the 11.43 kB
11.43 kB on the first visit, with the options you pick below
First visit
Each next page 1.00 kB
- Engine 3.31 kB
Reads the choice, holds the tools, sets Google Consent Mode. - Banner 2.93 kB
The banner and the choices, only until the visitor answers. - Starter and settings 1.50 kB
A small script in the page head, and the settings of your site. - Styles 3.48 kB
The look of the banner, in your colours. - Other 0.21 kB
The few lines added to the page itself.
Added only when a site uses them. Click to add one.
Box, bar or discreet
A floating box at the bottom left or right, a bar across the page, or a small discreet box.
The cookie button shows your logo or ours.
Light or dark, automatically
In automatic mode the banner follows your site’s own light/dark switch (data-theme, data-bs-theme, a dark class on the page) and, without one, the visitor’s device.
The accent colour is picked from your theme, Divi or Elementor palette, and the text colour adapts to stay readable.
Your words
Write your own banner texts, language by language, or keep ours in 54 languages.
Live preview
See the banner on your own home page while you adjust it, before your visitors do.
Vote for the default colour of 2027 →
Every option, at a glance
- A box at the bottom left
- A box at the bottom right
- A bar across the page
- A small discreet box
- Rounded or square corners
- Light, dark or automatic theme
- Follows your site’s dark mode
- Accent colour from your theme
- Divi and Elementor palettes
- Your logo on the cookie button
- Button position on phone, tablet and computer
- Button size
- Hide the button, use a footer link
- Your own texts, language by language
- Texts in 54 languages
- Language of each page (WPML, Polylang)
- “Accept all” that stands out, or not
- Banner per group of countries
- Live preview on your home page
- Categories shown only when used
Settings you can finally understand
Four questions about your site, then a plain list of what the law asks of it, following the laws of the countries you target, and only those: each point marked done or to do, with a button that fixes it. Every setting says what it does and why. Not sure where your site is hosted? “Not known” is an accepted answer.
Alerts by e-mail or Slack
When a serious problem appears, such as the banner switched off, a second consent tool or Google consent set twice, Cookie Rocks Pro tells you by e-mail or in a Slack channel.
Warnings that matter
The dashboard tells you when a country you target requires a language your banner does not speak, when payment scripts load on every page instead of the checkout, or when comment avatars come from Gravatar.
Each warning says what to do, often in one click.
Fixes for other plugins
When another plugin has its own consent option, such as the GDPR setting of Smash Balloon feeds, the dashboard sets it for you in one click, after you confirm.
Signed updates
Every update is signed and checked before it installs: an older version, or a zip that is not the right plugin, is refused.
Each language pack is signed too.
Correct signals, everywhere
Google Consent Mode v2
Default and update set at the very top of the page, on every page view.
Basic or advanced mode, with a recommendation for your site.
- Google Tag Manager
WP Consent API
Kept in sync on every page view, so Site Kit, WooCommerce and other plugins never read a stale choice.
Microsoft, Matomo and WP Statistics
Clarity and Microsoft Advertising wait for consent like any other tool, then receive the visitor’s choice.
Matomo loads as usual and writes no cookie before consent. WooCommerce and WP Statistics load as usual and read the choice through the WP Consent API plugin.
Microsoft Clarity- Microsoft Advertising
- Matomo
Google Tag Manager, read for you
Cookie Rocks reads your public container every day, without a Google account.
The tools it loads go into your cookie policy by themselves, paused tags are left out, and the dashboard tells you which tags to make wait for consent.
- Google Tag Manager
- Google Analytics
- Google Tag Manager
- YouTube
- Google Maps
- Meta Pixel
Google reCAPTCHA- Google Ads
Google AdSense- Google Analytics / Google Ads (gtag.js)
- Facebook social plugins
- Instagram embeds
- X Pixel
- LinkedIn Insight Tag
- TikTok Pixel
- Pinterest Tag
- Vimeo
- Hotjar
Microsoft Clarity- Microsoft Advertising (UET)
- Stripe
- PayPal
- HubSpot (tracking)
- Mailchimp (connected site and pop-up)
- Cloudflare Turnstile
- Snap Pixel
- Reddit Pixel
- Matomo
- Intercom
- Zendesk Web Widget
- Spotify
- SoundCloud
- Calendly
- Typeform
Criteo
Taboola (recommendations)
Outbrain (recommendations)
675 tools recognised by name. See them all.
675 tools recognised
Meta, LinkedIn, TikTok, Pinterest, Hotjar, AdSense, chats, e-mail marketing and more are held until consent, automatically.
The scan finds the ones it does not know yet too. See the list.
- Meta Pixel
- TikTok
- Hotjar
AdSense
Back at once after consent
The visitor accepts, and the held tools start right there, on the same page, without a reload: the video plays, the map appears, the visit is counted.
Allowing only Google reCAPTCHA or hCaptcha from a form reloads the page once, and what the visitor typed stays in the form. After consent, held scripts download together, then run in the order of the page.
Placeholders, not holes
Videos, maps, music, social media posts and forms (YouTube, Vimeo, Google Maps, Spotify, Instagram, X, TikTok, Typeform…) show a placeholder with a load button, in place, without breaking your layout.
- YouTube
- Vimeo
- Google Maps
- Spotify
- Tiktok
- Typeform
Forms keep working
Contact Form 7, WPForms, Gravity Forms, Forminator, Spectra and Divi forms protected by reCAPTCHA or hCaptcha ask before sending, and nothing the visitor typed is lost.
reCAPTCHA
One plugin, several tools
Some plugins load several tools from one script, like PixelYourSite or Pixel Manager for WooCommerce.
Each tool waits for its own consent: allowing the Meta Pixel does not start Google or Microsoft. When consent is withdrawn, their cookies are removed, from the first visit.
Social posts in place
Instagram, Threads, X and TikTok posts show a short message and a Load button while their script waits for consent, instead of a bare link.
Sites aimed at children
One setting removes advertising and consent-based statistics from the banner, and videos, maps and social posts load only after a parent or guardian confirms.
Strict payments
An optional setting lets payment and anti-fraud scripts load without consent only on cart, checkout and account pages, and holds them everywhere else.
AI chat widgets
Chatbot widgets wait for consent like the other tools, and the dashboard reminds you that the EU AI Act asks a chatbot to say it is an AI.
Cookies a scan cannot see
Some cookies appear only after a click, a sign-in or a payment.
Cookie Rocks reads the code of your theme and plugins to find their names, and in Cookie Rocks Pro, Record a visit notes the cookies and keys your site writes while you use it.
Hold anything by hand
A script or an iframe Cookie Rocks does not know yet?
Hold it from the Cookies screen in a few clicks, or give it a category in your theme (type="text/plain" data-cr-category="statistics") and it waits for the visitor’s yes. The categories you use show up in the panel, even before the first scan.
Cache friendly
Nothing is personalised on the server, so every visitor gets the same cached page.
The cache is cleared when you save, for WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, SiteGround Optimizer, WP-Optimize and Jetpack Boost, and the consent script is kept out of Autoptimize, Jetpack Boost, WP-Optimize, FlyingPress, Perfmatters, NitroPack and the others. Scripts that WP Rocket, Perfmatters or LiteSpeed delay until the first interaction stay held until consent too. Caching plugins · The weight.
When the page reloads
Accepting never reloads the page. Withdrawing a consent reloads it once, because a script that has already run cannot be stopped any other way.
- Accept all0no reload
- Allow YouTube only0no reload
- Allow reCAPTCHA only1reload
- Accept, then refuse all1reload
A form needs reCAPTCHA from the moment the page loads, hence the one reload when it is allowed alone.
Identifiers that come back
Some tools keep a copy of their identifier in the browser’s storage, so the identifier survives when the cookie is deleted (Microsoft Advertising (UET), Quantcast Measure and Criteo, as their code or our tests show). Most cookie plugins only clear cookies, so these identifiers come back. When a visitor refuses or changes their mind, Cookie Rocks clears both.
Proof and peace of mind
Register of proofs
Every choice is recorded on your site and kept for the months you choose, never less than the choice itself plus 12 months, or what a country you target requires.
Then it is deleted automatically. An optional daily or weekly copy goes to your own storage: Dropbox, a WebDAV server, a signed webhook or an e-mail address. It goes straight from your site, never through ours.
Cookie policy
Generated from the cookies really found on your pages, with their durations.
For sites that address the United States, it also explains how the site answers browser privacy signals (Global Privacy Control, Do Not Track).
Laws of your countries
The rules of 248 jurisdictions with their official texts, and your settings checked against them.
Country by country, too: proof of consent (248 jurisdictions), storing data in the country (218), hosting abroad (246), the local representative where one is needed, AI chatbots (50) and accessibility (99). The law sheets also give the language the banner must speak, the age of digital consent, the rule on cookie walls, the highest fine and recent decisions of the authorities.
Proofs you can hand over
One click downloads a zip: the proofs of the period with the expiry of each choice and its planned deletion date, the texts each version of the banner showed, a copy of the banner to open in a browser, and a manifest with a SHA-256 fingerprint of each file.
Checking it needs nothing from your site.
Refusals sent by the browser
An optional setting also records the refusals that browsers send with Global Privacy Control, without a click.
Opt-out records are kept for at least 24 months, as California and Colorado require.
Statistics
How visitors answer the banner, day by day, over 30 days, 90 days or 12 months, drawn by the plugin from the register of proofs, without any outside service.
Your privacy policy, checked in every language
Cookie Rocks reads your privacy policy and each translation (WPML, Polylang), point by point. Each missing point comes with a text to copy in the language of the page. A help to check, not a verdict.
What your privacy policy must say, country by country
- Who is responsible
- How to contact you
- Legal basis
- How long you keep data
- Rights
- Supervisory authority
- Tools used
- Transfers outside the EU
- How to withdraw consent
- Local representative
- Browser privacy signals
- Where proofs are copied
- Last update
One key for your whole workflow
- 1domain per key, with or without www
- 3subdomains of that domain
- 2places for staging hosts
- 0keys used by local sites
A key covers your domain with or without www and 3 of its subdomains. Local sites (localhost, .local, .test, .localhost, IP addresses) are free and never counted, and 2 extra places are kept for known staging hosts such as WP Engine, Kinsta, WordPress.com, InstaWP, Pantheon or Cloudways. If your site moves, you can change the domain of a key up to 3 times a year.
Entirely on your site
No cloud dashboard, no account to create, no page or visitor quota. The banner, the choices, the proofs and the settings live in your WordPress, so nothing is capped when your traffic grows. And it stays light on your server: the measured figures.
What Cookie Rocks does not do
- It is not certified for the IAB Transparency and Consent Framework. Personalised AdSense ads in Europe need a certified tool.
- It does not give legal advice. It explains the rules and checks your settings; for your own case, ask a lawyer.
- It does not send your visitors’ data anywhere, except to your own storage if you turn on a copy of your proofs.
- It does not eat your cookies.
Cookie plugins the free Audit reads →
The free Audit and Cookie Rocks Pro, side by side
| Feature | Audit (free) | Cookie Rocks Pro |
|---|---|---|
| Rules of 248 jurisdictions, in plain words | ✓ | ✓ |
| Your obligations, done and missing | ✓ | ✓ |
| Scan of your pages as your visitors see them, even when you are logged in: tools and cookies found | ✓ | ✓ |
| Your current consent banner recognised and checked, from WordPress plugins to hosted services | ✓ | ✓ |
| Rules on AI chatbots (50 jurisdictions) and accessibility (99) | ✓ | ✓ |
| Global Privacy Control and US “Do Not Sell” links, state by state | ✓ | ✓ |
| How visitors must be able to withdraw consent, country by country: a footer link where it is enough, a visible button where more is asked | ✓ | ✓ |
| Browser storage found on your pages (local, session, IndexedDB) and listed in your cookie policy | ✓ | ✓ |
| Advertising identifiers hidden in browser storage, flagged in red when they appear before consent | ✓ | ✓ |
| Local representative: when your company needs one in a country you target | ✓ | ✓ |
| Fonts loaded from other sites, with what each licence allows | ✓ | ✓ |
| Health dashboard and Site Health test | ✓ | ✓ |
| Generated cookie policy | ✓ | ✓ |
| Law updates, every day | ✓ | ✓ |
| Dashboard in 28 languages | ✓ | ✓ |
| Fair banner in 54 languages, light or dark | – | ✓ |
| Trackers held until consent, placeholders for videos and maps | – | ✓ |
| Rules by country: one setting, and each visitor gets the rules that apply to them | – | ✓ |
| Setting for sites aimed at children, and “strict payments” for shops | – | ✓ |
| Google Consent Mode v2 and WP Consent API signals sent (the audit checks them) | – | ✓ |
| Scripts delayed by WP Rocket, Perfmatters or LiteSpeed still held until consent | – | ✓ |
| Identifiers that come back: the cookie and its copy in browser storage cleared together | – | ✓ |
| Google Fonts found in your pages and stylesheets, copied to your site | – | ✓ |
| Register of proofs | – | ✓ |
| Statistics of the answers | – | ✓ |
| Plugin updates, including the ones that follow the law | ✓ | ✓ |
| Support by ticket | – | ✓ |
30 days free
Try the complete plugin. Nothing breaks on day 31.
no card, no catch
Every feature, every update and support, for 30 days. Setting it up takes a few minutes; the month gives you time to get the purchase through your accounting.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support

Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.