Is Your Cookie Banner Actually Blocking Trackers? How to Test a WordPress Site
You’ve installed a cookie consent plugin, customized the banner, and added a privacy policy to your WordPress website. Everything looks ready. But here’s something worth checking: what happens behind the scenes when someone clicks “Reject All”?
A cookie banner might look perfectly functional while analytics scripts or advertising trackers continue operating without the required permission. Visitors won’t notice this, and website owners may never discover it without testing.
That’s why cookie consent compliance involves more than displaying a notice. It requires checking whether your website responds correctly to visitor choices.
The good news? You can perform several useful checks with free browser tools, even without extensive technical experience.
Does Having a Cookie Banner Mean Your WordPress Site Is Compliant?
No. A cookie banner alone doesn’t establish compliance. Non-essential tracking must follow applicable consent requirements, and visitors’ preferences must be respected.
For example, a website might display “Accept All” and “Reject All” buttons while Google Analytics continues setting cookies before either option is selected.
Under UK privacy rules, the Information Commissioner’s Office (ICO) explains that non-exempt storage technologies generally require valid consent.
Essential technologies used for necessary functions, such as authentication or shopping carts, may qualify for exceptions.
The key question isn’t whether a banner appears. It’s whether your website’s actual behavior matches the permissions visitors provide.
How to Test Cookie Banner Blocking on a WordPress Website
You can perform cookie banner testing using Google Chrome’s Developer Tools to inspect stored cookies and tracking requests before and after consent.
Follow these steps to identify potential problems.
Step 1: Start With a Clean Browser Session
Open your website in a new incognito window and make sure you’re logged out of WordPress.
Before proceeding:
- Clear existing cookies and site data.
- Disable tracking-blocking extensions.
- Open a page where your cookie banner appears.
- Avoid clicking any consent option.
This helps you observe what a new visitor experiences. Remember that incognito mode doesn’t automatically disable every tracking technology.
Step 2: Inspect Cookies Before Accepting
Right-click the page, select Inspect, and navigate to:
Application → Storage → Cookies
Select the website’s domain and review the stored cookies.
Common analytics and advertising cookie names include _ga, _ga_*, and _fbp.
Finding these before consent deserves investigation if they serve purposes requiring permission.
Google’s Chrome DevTools documentation explains how to inspect cookie names, domains, and expiration details.
Don’t assume every cookie indicates a problem. Identify its purpose before deciding whether it should have been blocked.
Step 3: Check Network Requests
Open the Network tab in Developer Tools and refresh the page without interacting with the banner.
Filter requests using terms such as collect, analytics, or facebook.
This can reveal communication with analytics and advertising services.
However, there’s an important distinction: Google’s advanced Consent Mode can send limited measurements without analytics cookies while consent is denied. Therefore, a network request alone doesn’t prove improper tracking.
Review the request’s purpose, transmitted information, and consent state before reaching a conclusion.
Step 4: Test Every Consent Option
Now test the banner’s different choices in separate clean sessions.
Start with “Reject All.” Refresh the page and check whether optional cookies remain blocked.
Next, clear your site data, reopen the website, and choose “Accept All.” Confirm that permitted technologies activate.
Finally, try customized consent settings. For example, allow analytics while rejecting advertising.
Each category should operate according to the visitor’s selection.
What Should Cookie Banner Testing Results Look Like?
A properly configured consent system should apply visitors’ choices consistently across page loads and relevant tracking technologies.
Use this comparison as a practical reference.
| Test scenario | Expected behavior |
| No consent selected | Technologies requiring consent remain restricted |
| Accept All | Tracking permitted by the selection can activate |
| Reject All | Non-essential technologies requiring consent remain blocked |
| Analytics accepted only | Analytics may operate; rejected advertising tracking stays restricted |
| Preferences changed | Subsequent activity follows the updated choice |
| Page refreshed | Saved consent preferences remain effective |
This table describes general expectations, not an automatic legal pass/fail test. Consent requirements and permitted technical behavior depend on jurisdiction and implementation.
Why Do Some WordPress Trackers Continue Running After Rejection?
Tracking can continue when scripts bypass the consent plugin, multiple integrations install the same tracker, or consent settings are applied too late.
Tracking Code Added Outside the Consent Plugin
A developer may have inserted Google Analytics directly into the theme, through a header-injection plugin, or using Google Tag Manager.
If the consent system doesn’t control that integration, the script may execute independently.
Conflicting Tracking Plugins
Imagine a website using both a marketing plugin and a separate analytics integration.
Disabling tracking through one system might not affect the other.
Review installed plugins and tag configurations to identify duplicate tracking installations.
Caching or Script Optimization Issues
Performance tools can change when JavaScript executes.
If consent defaults are established after tracking code runs, visitor preferences may not be applied correctly.
Third-Party Embeds
Embedded videos, advertising widgets, and social media content can introduce external requests.
These technologies should be included in your tracking inventory rather than assuming the cookie plugin automatically controls everything.
What Does a Real WordPress Cookie Blocking Problem Look Like?
Consider a hypothetical WordPress business website using Google Analytics, Google Tag Manager, and a cookie consent plugin.
The owner opens the website in a clean browser session and rejects analytics cookies.
During testing, an _ga cookie still appears after refreshing the page.
Further inspection reveals that an analytics integration loads independently of the consent plugin.
The owner removes the duplicate installation, configures consent controls, and repeats the same test.
This time, the analytics cookie doesn’t appear until the relevant permission is granted.
The lesson: A visually correct banner can hide a configuration problem. Testing helps identify the actual source rather than assuming the banner plugin itself is defective.
How Can You Maintain Reliable Cookie Consent Over Time?
For agencies managing multiple websites, keeping cookie consent reliable means tracking different plugins, marketing tools, and consent settings across every site. A plugin update or new integration can change cookie behavior, making it easy to miss issues between maintenance reviews.
To stay on top of these changes, use a consistent testing process across your portfolio. Check each website’s consent behavior after installing plugins, adding marketing tools, or modifying caching settings.
Agencies can manage multiple WordPress sites from one dashboard to coordinate maintenance, but each website still needs its own consent checks.
Record the testing date, consent choices, detected technologies, and corrective actions. This creates a useful history for troubleshooting future issues.
Make Sure Your Cookie Banner Does What It Promises
A cookie banner should provide meaningful control over how a website uses tracking technologies, not simply display a privacy message.
By examining cookies, reviewing network activity, and testing different consent choices, WordPress owners can uncover problems that would otherwise go unnoticed.
The most valuable outcome isn’t a perfect-looking banner. It’s a website that consistently respects visitor preferences.
Frequently Asked Questions
1. Can websites track visitors without storing cookies?
Yes. Technologies such as browser fingerprinting and certain server-side tracking methods can collect information without traditional cookies. A complete assessment should consider these methods.
2. Does Google Consent Mode guarantee legal compliance?
No. Consent Mode helps Google tags respond to consent signals, but appropriate configuration and applicable legal obligations remain the website owner’s responsibility.
3. Can ad blockers affect cookie testing?
Yes. Browser extensions may independently block trackers, making an incorrectly configured consent system appear effective. Test without these extensions.
4. Should cookie banners be tested on mobile devices?
Yes. Mobile-specific scripts, responsive interfaces, and embedded elements can behave differently from desktop implementations.
5. Can visitors withdraw cookie consent after accepting?
Yes. Where consent is required, users should be able to withdraw it easily. Future tracking must respect the updated choice.
6. Are automated cookie scanners enough for testing?
Not entirely. Automated scanners help identify cookies and third-party services, but manual checks are valuable for verifying user interactions, consent updates, and conditional tracking behavior.
