Advanced WordPress setups often include performance, security, and caching tools such as WP Rocket, LiteSpeed Cache, Sucuri WAF/CDN, and W3 Total Cache. These tools can sometimes interfere with the normal functioning of the Search Atlas plugin — particularly during JavaScript injection into headers or with aggressive caching.
This guide outlines known compatibility issues, workarounds, and best practices to ensure smooth implementation of the Search Atlas plugin in advanced environments.
⚙️ Common Plugin and CDN Conflicts
⚙️ Common Plugin and CDN Conflicts
Tool | Potential Conflict | Notes |
WP Rocket | Delays or blocks Search Atlas JS snippet injection | Use exclusion rules and delay JS execution settings |
Sucuri WAF/CDN | Cached versions may prevent dynamic JS injection | Clear cache and bypass caching for dynamic pages |
LiteSpeed Cache | Works only with LiteSpeed server; may block custom JS | Use bypass for logged-in users or exclude plugin routes |
W3 Total Cache | Aggressive object caching can affect plugin injection | Disable object caching for plugin routes |
🧪 Divi + JS Injection Issues
🧪 Divi + JS Injection Issues
Issue: When adding the Search Atlas JS snippet via Divi’s Theme Options or Page Settings (in <head>), Divi may sanitize or ignore parts of the script.
Workaround:
Use a plugin like “Insert Headers and Footers” or “WPCode” to inject the JS in the global header. This avoids Divi's internal sanitation filters.
🚀 Best Practices for WP Integration
🚀 Best Practices for WP Integration
If using the new WP Integration (native plugin):
Ensure your caching/CDN layers are not serving cached versions of the plugin's admin interface.
Clear all cache after activation.
Temporarily disable minification to test compatibility.
⚠️ Deprecation of JS Snippet (Heads-up)
⚠️ Deprecation of JS Snippet (Heads-up)
With the move to native WP plugin integration, the traditional JavaScript snippet method is being phased out. While still supported, future updates may remove or limit it. Users should plan to migrate to the official plugin integration.
🛠️ Temporary Workarounds
🛠️ Temporary Workarounds
Head & Footer Plugin: Recommended for bypassing theme-level restrictions.
Exclusion Rules in Cache Tools: Exclude the Search Atlas plugin’s routes, URLs, and scripts.
Bypass Mode for Authenticated Admins: Useful for ensuring backend experiences are not cached.
📚 Support and Contribution
📚 Support and Contribution
If you are using a non-standard configuration and need tailored support, reach out via support or Slack. We're currently collecting edge cases to enrich our documentation.
✅ Next Steps
✅ Next Steps
[Download the Official Plugin] (if applicable)
[Troubleshooting Checklist for Advanced Users]
Submit your setup details to help us improve this guide.
🛠 This SOP is part of our internal technical knowledge collection.
It reflects current field insights and requires validation by Product/Engineering.
Please flag updates or contradictions to Knowledge Management for revision.
Last updated: [21.08.2025] | Owner: Camilo Aponte, KB Manager.