The plugin pairs your site with your CookieHug account in two clicks. Banner, scanner and Consent Mode v2 are configured in the dashboard — WordPress just serves the script.
The problem
Running GA4, Google Ads or Meta Pixel on WordPress? Directory cookie plugins often just display a banner — they don't block scripts before consent, don't send Consent Mode signals and leave no proof of consent. Which is exactly what an audit checks.
The solution
CookieHug does the whole job: blocks scripts until consent, keeps a decision log, sends Consent Mode v2 signals — and the nightly scan watches whether a plugin update slipped in a new tracker. Core and plugin versions are compared against wordpress.org, with warnings for outdated ones.
Download the ZIP from your CookieHug dashboard and upload it in wp-admin: Plugins → Add New → Upload Plugin. Updates arrive automatically from then on.
Click "Connect with CookieHug" — pick the domain on cookiehug.com and you're back in wp-admin with the connection saved.
The script injects into <head> automatically. Looks, categories and copy are managed in the CookieHug dashboard.
No — it only adds one lightweight script to <head>. All logic runs on CookieHug's side, with no queries against your WordPress database.
In the CookieHug dashboard — the plugin deliberately doesn't duplicate settings. One configuration, even when you run multiple sites.
The script stops loading and the banner disappears. Deleting the plugin removes its WordPress data; you can also revoke the connection in the CookieHug dashboard.
Yes — the snippet is a static line in <head>, so page caching doesn't interfere. Consent decisions live in the visitor's first-party cookie.
GDPR- and Consent Mode v2-compliant consent plus an anomaly radar — in a single script.