Intensified Consent Banner

Try the live playground — pick colours, mode and position, watch the real banner change, then copy the values into your settings.

Intensified Consent Banner is a cookie consent banner for people who want to know and control what their website loads. You map each tracking script to a consent category yourself, and nothing in that category runs until the visitor agrees.

How it is built

• Vanilla JavaScript only — no jQuery, no framework, a few KB in total

• No frontend database queries — consent state lives in the visitor’s browser (cookie plus a localStorage mirror), so static and server-side caching stay fully intact

• No external requests — every asset is served from your own site

• No custom database tables — a single WordPress option, cleanly removed on uninstall

• Links your privacy policy automatically — it uses the page you already marked under Settings → Privacy

Features

• Three consent categories: Necessary, Statistics, Marketing — with equal-weight Accept and Reject buttons, so refusing is as easy as agreeing

• Script blocking by WordPress script handle, per category, for both external and inline scripts

• Iframe blocking for YouTube, Vimeo and Google Maps, replaced by a placeholder that loads nothing until the visitor consents — extendable with your own domains

• Cookie deletion on consent withdrawal, using the name prefixes you configure per category

• Reopen control as shortcode [zbconsent_settings] and as a block, so consent can be withdrawn as easily as it was given

• Light, Dark and Auto appearance with fully customisable colour palettes and six banner positions

• Consent validity configurable from 1 to 365 days

• Fully internationalised; translations are provided through translate.wordpress.org, and custom banner texts integrate with WPML String Translation

What this plugin does not do

Being clear about the limits matters more than a long feature list:

• No automatic cookie scanner. You tell the plugin which script handles to block and which cookie names to delete. The bundled guide shows you how to find both in your browser; no coding is required.

• Cookie deletion is first-party only. On withdrawal the plugin deletes cookies you listed, on your own domain. It cannot remove a third party’s cookies from a third party’s domain, and JavaScript cannot touch HttpOnly cookies at all. Blocking a script before it runs is the part that actually prevents cookies from being set; deletion is cleanup.

• No consent logs and no dashboard. Nothing is written to your database on the frontend, which is what keeps your page cache working. If you need a stored audit trail for a regulator, this plugin does not provide one.

Note: This plugin provides the technical tools for consent management. It does not constitute legal advice, and legal compliance depends on your specific configuration and jurisdiction.

External services

This plugin does not send any data to external services on its own. It exists to prevent third-party content from loading before the visitor agrees to it.

However, the embed blocker replaces iframes from the following providers with a local placeholder, and restores the original iframe only after the visitor clicks “Load content” or consents to the matching category. At that point the visitor’s browser contacts the provider directly, exactly as it would without this plugin installed, and the provider receives the visitor’s IP address, user agent and referring page.

The providers recognised out of the box are:

• YouTube ( youtube.com, youtube-nocookie.com, youtu.be ) — used to display embedded videos. Terms: https://www.youtube.com/t/terms — Privacy policy: https://policies.google.com/privacy

• Vimeo ( player.vimeo.com ) — used to display embedded videos. Terms: https://vimeo.com/terms — Privacy policy: https://vimeo.com/privacy

• Google Maps ( google.com/maps, maps.googleapis.com ) — used to display embedded maps. Terms: https://policies.google.com/terms — Privacy policy: https://policies.google.com/privacy

These embeds only appear on your site if you have added them to your own content. The plugin never adds them, and it never contacts these providers by itself; it only restores an embed you already placed, once consent allows it. You can add further domains to be blocked the same way under Settings → Cookie Consent.