Skip to main content

WordPress Issues

Symptom A: Plugin installed but banner not showing​

How to check: View Page Source → search for consentforge. Is the script tag in <head>?

Causes:

  1. Plugin is installed but your embed token hasn't been entered
  2. A caching plugin is serving an old version of the page without the script

Fix:

  1. Go to WordPress Admin → Settings → ConsentForge and ensure your Embed Token is saved
  2. Clear your caching plugin's cache (WP Rocket: Dashboard → Clear cache; W3 Total Cache: Performance → Purge all caches)

Symptom B: ConsentForge script being minified or deferred by caching plugin​

Symptom: Banner loads after a delay or not at all. DevTools shows the script loading late.

Fix: Exclude consentforge.min.js from optimisation in your caching plugin:

  • WP Rocket: Settings → File Optimization → Excluded JavaScript Files → add cdn.consentforge.com
  • W3 Total Cache: Performance → Minify → JS minify settings → exclude ConsentForge URL
  • LiteSpeed Cache: Page Optimization → JS Settings → JS Excludes → add cdn.consentforge.com

Symptom C: Two banners showing (ConsentForge + another plugin)​

Cause: Another WordPress plugin (Cookie Notice, Cookiebot plugin, etc.) is still active.

Fix: Deactivate and delete any other cookie consent plugins. Only one CMP should be active at a time.

Symptom D: Google Site Kit / MonsterInsights still loading before consent​

Cause: These plugins load their own scripts independently of the ConsentForge script tag approach.

Fix: Disable direct script loading in the Google Site Kit settings and use GTM instead. Configure via GTM setup guide for proper Consent Mode integration.

Multisite / subdomain installs​

For WordPress Multisite, install the ConsentForge plugin network-wide and configure each sub-site with its own embed token (create a separate ConsentForge property per sub-site).