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.

**⚠️ Important — Do not use both integration methods at the same time:** Do not use both the Search Atlas WordPress plugin and the JS snippet simultaneously. Duplicate installations have been reported to generate hundreds of duplicate form entries in Website Studio. Choose one integration method only.

**Note:** Search Atlas can be integrated in two ways — via the official WordPress plugin or via the JavaScript snippet (pixel/manual script). Some of the conflicts below apply only to one integration path, so each entry indicates whether it affects the **plugin**, the **JS snippet**, or **both**.

## 🔍 Common Compatibility Issues and Fixes

Tool

Common Conflict

Suggested Fix

Applies To

**WP Rocket**

JS snippet is delayed or blocked

Use Delay JS execution and exclude Search Atlas script

JS snippet

**Sucuri WAF/CDN**

Cached version blocks dynamic JS

Bypass cache for admin and plugin routes; clear cache after install. In the Sucuri dashboard, navigate to **Firewall → Cache → Cache Exceptions** and add your site's admin and plugin asset paths. Alternatively, enable **Development Mode** temporarily during initial setup.

Both

**LiteSpeed Cache**

Can block plugin rendering

Disable cache for logged-in users or plugin-specific URLs

Plugin

**W3 Total Cache**

Object cache prevents plugin load

Temporarily disable object caching during setup

Plugin

## 🎨 Divi-Specific Notes

**Applies to:** JS snippet integration.

**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 are generally more reliable for inserting custom code than theme options, but if OTTO changes still do not appear after correct injection, contact support — some builder configurations require backend intervention.

## 🧩 Using the Official Search Atlas WordPress Plugin

**Applies to:** Plugin integration.

We recommend using the **native Search Atlas plugin** provided by Search Atlas for a more stable and optimized experience.

**When to prefer the plugin over the JS snippet:**

- You want a managed integration that handles CMS connector syncing and updates automatically.
- You are publishing content from Search Atlas into WordPress.
- Your theme or page builder (such as Divi) sanitizes custom scripts inserted via theme options.

**Installation steps:**

1. In WordPress, go to **Plugins → Add New → Upload Plugin** and upload the Search Atlas plugin .zip file provided by Search Atlas.
2. Install and activate the plugin.
3. Connect the plugin to your Search Atlas account using the API key from your dashboard.
4. Clear all caching layers (WordPress, CDN such as Sucuri, and browser) after activation.

**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.

### ⚠️ Known issue: Duplicate form entries when both integrations are active

If both the Search Atlas plugin and the JS snippet are installed simultaneously, the integration may register the same form repeatedly, producing hundreds of duplicate entries in **Website Studio → Forms**. To avoid this, choose only one integration method. If you have already encountered duplicates, deactivate one of the integrations and contact support to help clean up the duplicate records.

### 🧭 Known issue: Site navigation menu fully expanded after plugin activation

In some themes, activating the Search Atlas WordPress plugin may cause the public-facing site's navigation menu to render fully expanded. While our engineering team works on a permanent fix, you can apply a CSS override via **Appearance → Customizer → Additional CSS** to restore the intended menu behavior. When filing a support ticket, please include your active theme name so we can reproduce and track the issue.

### 🔌 Known issue: Atlas Brain shows CMS connector as disconnected despite active plugin

If the **CMS Connectors** dashboard or **Atlas Brain** displays a "+" or disconnected state even though the plugin is installed and WordPress publishing works correctly, this may be a display bug. Before reinstalling the plugin, contact support to verify the backend connection status — in most reported cases the connection is healthy and only the UI indicator is stale.

## 📌 Note on JS Snippet Deprecation

**Applies to:** JS snippet / pixel / manual script integration.

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.

**OTTO crawler and pixel/manual script installs:** If you are using the pixel/manual script installation and see that Site Audit still reports original page titles rather than OTTO-deployed titles, this may indicate a known crawling issue. Ensure JS rendering is enabled in your project settings and contact support if titles remain stale after a recrawl.

## 🛠️ 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.