🧭 Overview

If Search Atlas reports that Otto is not installed while you are also seeing a duplicate installation warning, there is a conflict between two sources of the Otto tracking code on your site. This usually happens when the Otto snippet has been added both manually (via a code snippet plugin or theme file) and through the official Otto WordPress plugin. This article walks you through diagnosing the conflict and reaching a clean, working installation.

🔍 Step 1: Check Otto's Status in Search Atlas

Before making any changes to your WordPress site, confirm what Search Atlas currently detects.

1. Log in to your Search Atlas account.
2. Navigate to the Otto or OTTO SEO section of the platform.
3. Review the Otto connection status shown on the page — it should indicate whether Otto is detected on your site.
4. Note the current status before proceeding, so you can confirm whether your changes resolve the issue.

⚠️ Step 2: Understand Why the Conflict Happens

A duplicate installation warning means Search Atlas has found more than one copy of the Otto tracking code firing on your site. Common causes include:

• The Otto WordPress plugin is active and the Otto code snippet was also pasted manually into your theme files.
• A code snippet plugin is injecting the Otto script separately from the official plugin.
• A previous plugin installation was deactivated but not deleted, leaving residual code behind.
• A caching layer is serving an old version of the page that still contains the old snippet.

🛠️ Step 3: Remove the Duplicate Code Source

You need to keep only one source of the Otto code — the official Otto WordPress plugin. Remove all other instances.

1. Log in to your WordPress admin panel.
2. Go to Plugins → Installed Plugins and check whether the Search Atlas plugin is listed and Active (you can access its settings via Search Atlas → Settings). If it is not active, activate it now before proceeding.
3. Check your theme files (via the Theme File Editor or an FTP/file manager client) for any manually added Otto tracking code or references to your Otto site key. Delete any such block and save the file.
4. Open any active code snippet plugins and search for snippets that include the Otto tracking script. Disable and delete those snippets.
5. If you use a page builder or a tool with custom header or footer code injection fields, check those fields and remove any Otto script you find there as well.

🔄 Step 4: Clear Your Site Cache

After removing the duplicate code, clear all caching layers to ensure Search Atlas re-evaluates a clean version of your pages.

1. Clear the cache in your WordPress caching plugin, if you use one.
2. Clear any server-side or CDN cache associated with your site.
3. Reload your website in a browser (using a hard refresh) to confirm the cached version is no longer served.

✅ Step 5: Verify the Otto Plugin Is Working

Once all duplicate sources have been removed and caches cleared, return to Search Atlas and check the Otto connection status again. It should now reflect a single, active installation. If the status has not updated, wait a few minutes and refresh the page, as detection may take a short time to propagate.

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.