# **🔍 Why the OTTO Pixel Goes Missing**

If the OTTO pixel script is not appearing in your WordPress site's page source — even though the Search Atlas plugin is active, your API key is synced, and server-side rendering is enabled — Cloudflare's bot protection is almost certainly the cause. Cloudflare can intercept and strip scripts it identifies as bot-like activity before they ever reach your browser, making it appear as though the pixel was never injected.

This is one of the most common reasons for OTTO pixel detection failures and is straightforward to resolve by adjusting your Cloudflare settings.

# **⚙️ How Cloudflare Blocks the OTTO Pixel**

Cloudflare sits between your server and your visitors. When its security rules are set too aggressively, they can:

- Block or silently remove script tags injected by WordPress plugins
- Challenge requests that the OTTO pixel makes during page rendering
- Strip scripts flagged as potential bot traffic before the HTML reaches the browser

Because the block happens at the CDN layer, the Search Atlas plugin has no way to override it — the fix must be applied inside your Cloudflare dashboard.

# **✅ Step-by-Step Fix: Whitelist the OTTO Pixel in Cloudflare**

1. **Log in to your Cloudflare dashboard** at cloudflare.com and select the domain where OTTO is installed.
2. **Go to Security → WAF** (Web Application Firewall) in the left sidebar.
3. **Check your Firewall Rules and Managed Rules** for any rules that block or challenge JavaScript injection or third-party scripts. Disable or adjust rules that may target plugin-generated scripts.
4. **Navigate to Security → Bots** and review your Bot Fight Mode setting. If **Super Bot Fight Mode** or **Bot Fight Mode** is enabled, it may be challenging the OTTO script. Consider switching to **Allow** for verified bots, or create an exception.
5. **Create a WAF Exception (Skip Rule)** to whitelist the OTTO pixel endpoint:

   - Go to **Security → WAF → Custom Rules** and click **Create rule**.
   - Set the rule to match requests where the URI path contains the OTTO script path or originates from the Search Atlas domain.
   - Set the action to **Skip → All remaining custom rules**.
   - Save and deploy the rule.
6. **Disable Rocket Loader for your site temporarily** (under **Speed → Optimization → Rocket Loader**). Rocket Loader rewrites how JavaScript loads and can prevent plugin scripts from injecting correctly. Test whether the pixel appears after disabling it.
7. **Clear your Cloudflare cache** by going to **Caching → Configuration → Purge Everything** after making any changes.

# **🧪 How to Verify the Pixel Is Now Detected**

1. Open your WordPress site in a browser and navigate to any page where OTTO is active.
2. Right-click the page and select **View Page Source**.
3. Use **Ctrl + F** (or **Cmd + F** on Mac) and search for **otto** or your Search Atlas script snippet.
4. If the script appears in the source, the pixel is now being injected successfully.
5. Return to Search Atlas by navigating to **OTTO SEO → All Sites (SEO Automation)** in the left sidebar (or go to **/seo-automation-v3**), and confirm that OTTO shows the pixel as detected.

# **💡 Additional Things to Check**

- **Other security plugins:** Plugins like Wordfence, Sucuri, or iThemes Security can also block script injection independently of Cloudflare. Check their settings if the issue persists after the Cloudflare fix.
- **Caching plugins:** WP Rocket, W3 Total Cache, or LiteSpeed Cache may serve a cached version of the page that pre-dates the OTTO pixel. Purge all caches after any configuration change.
- **Server-side rendering confirmation:** Double-check that server-side rendering is toggled **on** inside the Search Atlas plugin settings on your WordPress site, not just within the Search Atlas platform.
- **API key sync:** Re-save your API key inside the plugin settings to force a fresh connection, then check the page source again.

# **💬 Still Seeing the Issue?**

If you have followed all the steps above and the OTTO pixel is still not appearing in your page source, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.