🧩 Overview
If your WordPress site displays the message OTTO Pixel is not installed correctly even after following the standard installation guide, a security plugin is often the hidden cause. This article walks you through the most common reason detection can fail and how to resolve it: security plugins blocking the pixel from loading or being detected correctly.
🛡️ Security Plugin Interference (Most Common Cause)
Security plugins protect your site by restricting external scripts and HTTP requests. Unfortunately, this protection can also block the OTTO Pixel from loading or being detected correctly. Plugins that include features such as a firewall, script manager, content security policy (CSP) editor, or external request blocker are known categories of tools that can interfere with OTTO Pixel detection.
Follow these steps to rule out or fix security plugin interference:
- Log in to your WordPress admin dashboard.
- Go to Plugins → Installed Plugins and identify any active security plugins.
- Temporarily deactivate each security plugin one at a time.
- After each deactivation, return to Search Atlas and trigger a fresh pixel detection check.
- If detection succeeds after deactivating a specific plugin, that plugin is the cause.
- Re-activate the plugin and configure it to allow the OTTO Pixel script — consult your security plugin's own documentation for instructions on whitelisting external scripts or domains.
⚙️ Whitelisting the OTTO Pixel in Your Security Plugin
Once you have identified which security plugin is blocking detection, configure it to allow the OTTO Pixel rather than leaving it deactivated permanently. Most security plugins provide a way to whitelist specific scripts or external domains — refer to your plugin's official documentation or support resources for the exact steps, as menu locations and option names vary between plugins and versions.
In general, look for settings related to any of the following within your security plugin:
- Firewall whitelist or allowlist rules
- Script or resource allowlist
- Content Security Policy (CSP) exceptions
- External HTTP request permissions
Add the Search Atlas / OTTO Pixel script domain to the relevant allowlist, then re-run the pixel detection check in Search Atlas to confirm the issue is resolved.
📋 Before Contacting Support
If you are unable to resolve the detection failure after working through the steps above, please have the following information ready when you reach out:
- The name and version of the security plugin(s) active on your site
- The exact error message shown in Search Atlas
- Any blocked-request log entries from your security plugin, if available
- A note of when the issue started and any recent changes made to your site or plugins
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.