How to comply with GDPR cookies on WordPress
WordPress powers 43% of the web, but most free cookie plugins show the notice without blocking scripts: technically they don't comply. Here's how to do it right.
Why most WordPress plugins don't comply
GDPR requires blocking non-essential cookies BEFORE consent. Many popular plugins just show a notice and load Google Analytics or pixels anyway, or block too late. That's invalid, penalizable consent.
Where cookies come from in your WordPress
- Google Analytics / Site Kit and other measurement tools.
- Google Ads, Meta or TikTok pixels added by marketing plugins.
- Embeds from YouTube, Google Maps or external fonts.
- Chat, CRM or testimonial plugins.
- Builders like Elementor and some premium themes.
How to comply step by step
- Inventory the plugins and scripts that load cookies.
- Install a banner with real prior blocking (not just a notice).
- Load the snippet in the <head> with high priority, before Analytics.
- Configure the categories and Google Consent Mode v2.
- Publish the cookie policy and store the consent log.
The fast way: the Consentio plugin
With the Consentio plugin for WordPress you install the banner in minutes: real script blocking, Consent Mode v2 and consent logging, without touching code. You'll find the detailed install guide on our WordPress page.
See the WordPress install guide
Common WordPress mistakes
- Using a plugin that notifies but doesn't block.
- Loading Site Kit / Analytics before the banner.
- Hiding «Reject» or showing only an «Accept» button.
- Not reviewing the embeds and pixels other plugins add.
This guide is informational and does not constitute legal advice.