🧭 Overview
If your Search Atlas account is authenticated and synced successfully but the OTTO pixel still shows OTTO not found, a WordPress security plugin or Web Application Firewall (WAF) is most likely blocking the pixel script from loading or being written to your site. This is the most common root cause of this error and is not resolved by clearing your cache.
This article walks you through identifying and resolving security plugin conflicts so OTTO can install and verify correctly.
⚠️ Why Security Plugins Block OTTO
Security plugins like Wordfence, Sucuri, iThemes Security, and Cloudflare WAF are designed to block unfamiliar scripts and external code injections. Because the OTTO pixel is injected programmatically during installation, these tools can silently block or remove it before Search Atlas is able to verify its presence — even when your credentials and sync status appear healthy inside the platform.
Common symptoms of this conflict include:
- Account authentication shows as successful in Search Atlas
- Site sync completes without errors
- OTTO pixel status remains OTTO not found after multiple installation attempts
- No visible error message in WordPress or your hosting dashboard
🔍 Step 1 — Identify Whether a Security Plugin Is the Cause
- Log in to your WordPress admin panel.
- Go to Plugins → Installed Plugins and check whether any of the following are active: Wordfence Security, Sucuri Security, iThemes Security (now Solid Security), All In One WP Security, Cloudflare (with WAF enabled), or any other firewall or malware-scanning plugin.
- If one or more of these plugins are active, proceed to Step 2 for your specific plugin. If none are active, skip to Step 4.
🛡️ Step 2 — Whitelist OTTO in Your Security Plugin
The confirmed root cause for this error is a security plugin — most commonly Wordfence — blocking the OTTO pixel script from being written to or loaded on your site. The general fix is to whitelist or allowlist the Search Atlas pixel script within your security plugin's settings so it is not blocked or removed.
Because the exact menu labels and navigation paths vary by plugin and plugin version, consult your security plugin's own documentation for instructions on how to whitelist or allowlist an external script or URL. Apply this to each active security plugin on your site.
When whitelisting, you will need to permit the Search Atlas pixel script domain and endpoint. If you are unsure of the exact URL or script path to whitelist, contact support using the instructions at the bottom of this article and a team member will provide it.
General steps for any security plugin:
- Log in to your WordPress admin panel.
- Open the settings for your active security plugin.
- Locate the firewall, script blocking, or allowlist/whitelist section within that plugin.
- Add the Search Atlas pixel script URL or domain to the allowlist.
- Save your changes and then retry the OTTO pixel installation from within Search Atlas.
🔄 Step 3 — Retry OTTO Installation
- After updating your security plugin settings, return to your Search Atlas account.
- Attempt to reinstall the OTTO pixel.
- Wait a few minutes, then refresh the page to check whether the pixel status has updated from OTTO not found to a verified state.
🚨 Step 4 — If the Issue Persists
If the OTTO pixel still shows as not found after whitelisting within your security plugin, there may be a second conflicting plugin, a hosting-level firewall, or another script-blocking rule in place. When escalating, please have the following ready:
- Your site URL and the Search Atlas project name
- The name and version of all active security or firewall plugins
- Confirmation of what you have already whitelisted
- Any error messages or logs from your security plugin
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.