Some WordPress users — especially agencies, developers, and SEOs — use advanced performance or security plugins such as WP Rocket, Sucuri WAF/CDN, LiteSpeed Cache, or page builders like Divi. While powerful, these tools can sometimes conflict with Search Atlas's plugin or JavaScript snippet integration.
This guide summarizes common issues and workarounds for advanced setups. If you're experiencing problems with Search Atlas not displaying, not injecting properly, or behaving inconsistently, this article is for you.
🔍 Common Compatibility Issues and Fixes
🔍 Common Compatibility Issues and Fixes
Tool | Common Conflict | Suggested Fix |
WP Rocket | JS snippet is delayed or blocked | Use Delay JS execution and exclude Search Atlas script |
Sucuri WAF/CDN | Cached version blocks dynamic JS | Bypass cache for admin and plugin routes; clear cache after install |
LiteSpeed Cache | Can block plugin rendering | Disable cache for logged-in users or plugin-specific URLs |
W3 Total Cache | Object cache prevents plugin load | Temporarily disable object caching during setup |
🎨 Divi-Specific Notes
🎨 Divi-Specific Notes
Issue: When inserting the Search Atlas JS snippet via Divi’s Theme Options or Page Settings, the script may be sanitized or ignored.
Solution:
Use a plugin like Insert Headers and Footers or WPCode to inject the script at the site-wide <head> level. These plugins bypass theme limitations and are reliable for inserting custom code.
🧩 Using the Official Search Atlas WordPress Plugin
🧩 Using the Official Search Atlas WordPress Plugin
We recommend using the native Search Atlas plugin from the WordPress plugin directory for a more stable and optimized experience.
Tips:
Disable caching and minification during plugin activation.
After setup, clear all layers of cache: WordPress, CDN (Sucuri), and browser.
Avoid using both the JS snippet and the plugin at the same time unless advised by support.
📌 Note on JS Snippet Deprecation
📌 Note on JS Snippet Deprecation
Some users have asked whether the JavaScript snippet will be deprecated in the future. As of now, there is no official deprecation notice, but the plugin is the preferred integration method going forward.
🛠️ Still Need Help?
If you’re running a custom setup or using advanced server-level tools, we’d love to hear from you. Our team is actively collecting edge cases like this to improve both documentation and product compatibility.
💡 This article is part of our advanced user documentation. If you're an agency or technical user with performance tools, caching layers, or custom themes, this guide will help ensure Search Atlas works optimally in your stack.
We’ll continue updating this article based on new cases and user contributions.