Troubleshooting & Compatibility

Practical notes for getting CookieRay working cleanly alongside caching, other plugins, and your site setup.

Caching plugins

The CookieRay banner initializes from front-end scripts after the page loads, so it works alongside common caching plugins, including:

• WP Super Cache
• W3 Total Cache
• WP Rocket
• LiteSpeed Cache
• SG Optimizer

That said, every site’s caching rules differ. Always verify the banner appears and behaves correctly with your specific caching configuration after enabling or changing rules.

Multisite

This release targets standard single-site WordPress installs. Network-wide multisite is not supported in this release.

Conflicts with other consent plugins

Running two consent plugins at the same time can cause problems — duplicate banners, or the plugins fighting over script interception. While evaluating CookieRay, disable any overlapping consent plugins so they don’t interfere with each other.

Scan coverage

CookieRay’s scanner reaches what an unauthenticated crawler can see, so coverage is limited by:

• Caches that change what pages return.
• Authenticated-only flows the crawler cannot reach.
• Whatever the unauthenticated crawler can actually crawl.

Keep this in mind when reviewing scan results — pages behind login or only triggered by logged-in interactions may not be fully covered.

Comparing modes during troubleshooting

When diagnosing compatibility issues, compare Strict vs Log Only behavior alongside your caching and optimization stack. Switching to Log Only temporarily can help isolate whether a problem comes from script delaying or from another part of your setup.

CookieRay is not legal advice. Compliance depends on your configuration and the rest of your site.