🧩 Why These Errors Happen
After installing the OTTO pixel on WordPress, you may see errors in your Search Atlas dashboard indicating that the pixel was not detected or that a duplicate installation was found. These issues typically occur because a caching layer is preserving an outdated snapshot of your page. The pixel exists in your live code, but the detection check is reading stale cached output instead.
A common scenario for duplicate detection errors is switching from one installation method to another (for example, from a manual script to the OTTO WordPress plugin) without fully clearing the old cached version, so both appear active at the same time.
In both cases the root cause is the same: a caching layer is preserving an outdated snapshot of your page. Simply disabling a caching plugin does not fix this — the cached files already saved to your server continue to be served until you actively purge them.
⚠️ Disabling vs. Purging: A Critical Difference
Many customers turn off their caching plugin expecting the problem to clear automatically. This is the most common reason these errors persist. Understand the distinction:
- Disabling a caching plugin stops new cache files from being created, but leaves all existing cached pages on your server untouched. Detection checks still read those old files.
- Purging the cache deletes the stored snapshots immediately, forcing WordPress to rebuild each page from live code the next time it is requested. This is the step that allows the OTTO pixel detector to see your current installation.
Always purge — do not just disable.
🛠️ Step 1: Purge Your WordPress Cache
Follow the instructions for whichever caching solution your site uses. The exact menu location and button label will vary by plugin and version — consult your plugin's own documentation if you are unsure where to find the purge option.
WordPress caching plugins (WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache, and others)
- Log in to your WordPress admin panel.
- Locate your caching plugin in the admin sidebar or Settings menu.
- Look for a Purge, Clear Cache, or equivalent option and run it.
- Wait for confirmation that the cache has been cleared before proceeding.
Hosting-level cache (SiteGround, Cloudways, Kinsta, and other managed hosts)
Many managed hosts add a server-side caching layer that is separate from any plugin. Log in to your hosting control panel and look for a Purge Cache or Clear Cache option.
🔄 Step 2: Re-check Pixel Detection
After purging all cache layers, return to the Home page and re-run the OTTO pixel detection check. In most cases the error will resolve once the cached pages have been replaced with the current live version of your site.
If you have recently switched installation methods (for example, from a manual script to the OTTO WordPress plugin), verify that the old installation method has been fully removed before re-checking. Having two installation methods active simultaneously is the most common cause of duplicate detection errors.
📋 If the Error Persists
If the pixel is still showing as not detected or duplicated after purging your cache, gather the following before reaching out for support:
- Your WordPress site URL
- The exact error message shown in your Search Atlas dashboard
- Which caching plugin(s) or managed hosting provider you are using
- Which OTTO pixel installation method you used (manual script, WordPress plugin, or other)
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.