A WordPress cookie banner, without another plugin
WordPress sites collect plugins, and plugins collect trackers. allowedit sits in your head as one script tag, blocks what those plugins load, and doesn't add another thing to update.
Your site's head
A consent plugin plus 6 tracking plugins loading on their own
<script src="https://allowedit.com/c/<siteId>.js"></script> first, the rest waiting
What goes wrong
- Analytics, form, chat and social plugins each add their own scripts and cookies, often before any banner runs.
- Consent plugins add database tables, settings pages and updates to an already busy admin.
- Page caching can serve one visitor's banner state to everyone if the banner is rendered on the server.
- Agencies and freelancers end up with a different consent setup on every client's WordPress site.
How allowedit helps
One script tag
No plugin to install, update or keep compatible. The banner runs in the visitor's browser, so page caching doesn't affect it.
Blocks what plugins add
Known trackers from analytics, pixel and embed plugins are held until consent, with rules for anything else.
Embeds wait too
YouTube videos and Google Maps from your editor are replaced with a placeholder until marketing is allowed.
A cookie list for your privacy page
Paste the declaration script into your privacy page in the block editor and it stays current.
Setup checklist
- Add the script as the first thing in your head: a header plugin with the highest priority, your child theme's header, or GTM.
- Deactivate any old cookie banner plugin.
- Clear your page cache and any CDN cache.
- Check that combine or defer settings in your optimisation plugin don't move or delay the allowedit script.
- Run a scan and categorise anything unclassified.
- Add the cookie declaration to your privacy policy page with a Custom HTML block.
Tips
- Exclude the allowedit script from JavaScript delay and combine features in caching plugins; it has to run first, as written.
- If a plugin prints a tracker inline, tag it by hand with type="text/plain" and data-category, or add a URL rule.
- Add a Cookie settings link in your footer menu with the URL #cookie-settings.
- After adding a plugin, run a manual scan to see whether it set new cookies.
Why isn't there an allowedit WordPress plugin?
Because the banner doesn't need one. Everything runs from the script, and your settings live in your allowedit account, so a plugin would only paste a script tag. Header plugins, child themes and Google Tag Manager already do that, without another plugin to update.
If you'd rather have a plugin that manages consent inside WordPress itself, tools like Complianz do that. Our comparison page covers the trade-offs.
Questions
Does it work with caching plugins?
Yes. The banner is drawn in the visitor's browser, so cached pages are fine. Exclude the script from delay or combine options so it still loads first.
Does it work with WooCommerce?
Yes. WooCommerce's basket and session cookies are necessary and keep working. Ad and analytics tags wait for consent.
Is it free for one WordPress site?
Yes, with unlimited page views. Pro covers 3 sites for $10 a month, and Agency covers unlimited sites for $39 a month.
Can it block Google Fonts or other things themes load?
Add a URL rule for the address and pick a category, and matching scripts and iframes wait for consent. Fonts loaded by CSS aren't scripts or iframes, so host them on your own server instead.
Related guides
Other use cases
Cookie consent that just works
Free for 1 site with every feature. One flat price when you need more. No card needed.
Create a free account