# **🔍 Overview**

The OTTO Pixel is a small tracking script that connects your WordPress site to Search Atlas, enabling OTTO SEO to read your site's data and apply optimisations. If the Pixel keeps showing as **Disabled** in Search Atlas — even after you've re-engaged it — a conflict or configuration issue on your WordPress site is likely breaking the connection. This article walks you through the most common causes and how to fix them.

# **⚙️ How to Check the Pixel Status**

1. In Search Atlas, click **OTTO SEO** in the left sidebar, then open **SEO Automation** (or go to **/seo-automation-v3**).
2. Locate your connected site and check the OTTO Pixel status indicator.
3. If it shows **Disabled** or **Disengaged**, continue with the steps below before re-engaging.

# **⚠️ Common Causes of Pixel Disengagement**

- **Caching plugins overwriting the page** — Plugins such as WP Rocket, W3 Total Cache, or LiteSpeed Cache can serve a cached version of your pages that does not include the Pixel script, causing Search Atlas to lose the connection.
- **Minification or script optimisation** — JavaScript minification or deferred script loading can corrupt or delay the Pixel, preventing it from firing correctly.
- **Security or firewall plugins blocking the script** — Plugins like Wordfence or iThemes Security may flag the Pixel as an unknown external script and block it.
- **CDN stripping scripts** — A CDN such as Cloudflare may strip or defer third-party scripts, including the OTTO Pixel.
- **Theme or plugin conflicts** — A recently updated theme or plugin may be interfering with script injection.
- **Multiple WordPress installs or staging environments** — If the same Pixel ID is used across a live site and a staging site, the connection can become unstable.

# **🛠️ Step-by-Step Fixes**

1. **Clear all caches.** Go to your caching plugin's settings and purge the entire site cache. If you use a CDN, purge the CDN cache as well. Then re-check the Pixel status in Search Atlas.
2. **Exclude the OTTO Pixel script from minification and deferral.** In your caching or performance plugin, find the JavaScript optimisation settings and add the OTTO Pixel script URL or handle to the exclusion list. Save and clear the cache again.
3. **Whitelist the Pixel in your security plugin.** Check Wordfence, iThemes Security, or any equivalent plugin for blocked scripts. Add the OTTO Pixel domain to the allowlist and ensure it is not being flagged as malicious.
4. **Disable Rocket Loader in Cloudflare (if applicable).** Log in to Cloudflare, go to **Speed → Optimization**, and turn off Rocket Loader. This prevents Cloudflare from deferring the Pixel script. You can also use a Page Rule to disable performance features for your site's key pages.
5. **Test with plugins deactivated.** Temporarily deactivate all plugins except the Search Atlas WordPress plugin, then re-engage the Pixel in Search Atlas. If it stays connected, reactivate plugins one by one to identify the conflicting plugin.
6. **Verify the plugin is installed correctly.** In your WordPress dashboard, go to **Plugins → Installed Plugins** and confirm the Search Atlas plugin is active and up to date. Deactivate it, then reactivate it, and re-engage the Pixel in Search Atlas.
7. **Check for duplicate Pixel IDs.** If you have a staging site, make sure it is using a separate connection or that the Pixel is disabled on staging. Two environments sharing the same Pixel ID can cause repeated disengagement.

# **✅ How to Re-Engage the Pixel After Fixing the Issue**

1. In Search Atlas, click **OTTO SEO** in the left sidebar, then open **SEO Automation**.
2. Select your site and click the option to re-engage or enable the OTTO Pixel.
3. Reload your WordPress site's homepage in a new browser tab (not from cache) to trigger the Pixel.
4. Return to Search Atlas and refresh the page to confirm the Pixel status shows as **Active**.

# **💡 Tips to Keep the Pixel Stable**

- After any WordPress update, plugin update, or cache configuration change, verify the Pixel status in Search Atlas.
- Set your caching plugin to exclude the OTTO Pixel script permanently from optimisation rules.
- Avoid using the same Pixel ID on both your live site and any staging or development environment.

# **🆘 Still Disengaging After All Steps?**

If you have followed every step above and the OTTO Pixel continues to disengage, our support team can investigate further. 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.