Search Atlas Help Center

🛠️ Fix OTTO Pixel Not Installed Correctly Error

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🔍 Why You're Seeing This Error

The "OTTO Pixel is not installed correctly" message appears when Search Atlas cannot detect your OTTO Pixel firing on your website. This can happen even if you have the WordPress plugin installed and your GTM container published. The most common causes are a conflict between two installation methods, an unpublished GTM tag, or a firing trigger that hasn't been configured correctly.

⚙️ How the OTTO Pixel Can Be Installed

There are two supported ways to install the OTTO Pixel. You should use only one method — running both at the same time will cause conflicts and trigger the error.

  • Method 1 — WordPress Plugin: The OTTO Pixel snippet is injected directly into your site via the Search Atlas WordPress plugin.
  • Method 2 — Google Tag Manager (GTM): You add the OTTO Pixel as a custom HTML tag inside GTM and publish the container.

If you installed the WordPress plugin and also added the pixel code inside GTM, disable one of them before proceeding.

🛠️ Step-by-Step: Verify Your GTM Installation

If you are using GTM as your installation method, follow these steps carefully.

  1. Confirm the WordPress plugin is not also injecting the pixel. In your WordPress dashboard, go to the Search Atlas plugin settings and check whether the pixel output is enabled. If it is, disable it so GTM is the only active method.
  2. Check your GTM tag is set up correctly. Log in to your GTM account, open the correct container for your website, and locate the OTTO Pixel tag. Make sure the pixel code is pasted in full inside a Custom HTML tag — not a different tag type.
  3. Verify the trigger fires on all pages. Open the tag in GTM and check the trigger assigned to it. It should be set to All Pages (Page View trigger). If no trigger is assigned, the tag will never fire.
  4. Publish the GTM container. Click Submit in the top-right corner of GTM and then Publish to push the latest version live. Saving a tag without publishing means the change is not yet active on your site.
  5. Use GTM Preview mode to confirm the tag fires. Click Preview in GTM, enter your website URL, and navigate to any page. In the Tag Assistant panel, confirm the OTTO Pixel tag shows a status of Fired. If it shows Not Fired or does not appear at all, revisit the trigger configuration in step 3.

🛠️ Step-by-Step: Verify Your WordPress Plugin Installation

If you are using the WordPress plugin as your installation method (without GTM), follow these steps.

  1. Confirm the plugin is active. In your WordPress dashboard, go to Plugins → Installed Plugins and verify that the Search Atlas plugin status shows Active.
  2. Check the pixel is configured inside plugin settings. In WordPress, go to Search Atlas → Settings and confirm the OTTO Pixel UUID field is populated and saved.
  3. Remove any duplicate pixel code from GTM. If the OTTO Pixel tag also exists inside a GTM container, remove or pause it and re-publish the container so it is no longer firing.
  4. Clear your site cache. If you use a caching plugin such as WP Rocket, W3 Total Cache, or a CDN like Cloudflare, purge all caches so the latest version of your pages is served to visitors and to Search Atlas during verification.

✅ Re-Run the Pixel Verification in Search Atlas

Once you have completed the steps above, return to Search Atlas and re-trigger the pixel check.

  1. In the left sidebar, navigate to OTTO SEO and open SEO Automation (URL: /seo-automation-v3).
  2. Locate your OTTO project and open its settings.
  3. Find the Pixel Installation section and click Verify Installation or the equivalent re-check button.
  4. Wait a few seconds for the check to complete. If the pixel is detected correctly, the error message will be replaced with a green confirmation status.

💡 Quick Troubleshooting Checklist

  • Only one installation method is active — plugin or GTM, not both.
  • GTM container has been published (not just saved).
  • GTM tag trigger is set to All Pages.
  • GTM Preview mode confirms the tag Fired.
  • WordPress plugin is Active and pixel output is enabled in settings.
  • Site cache and CDN cache have been purged.
  • No ad blocker or browser extension is interfering during your own verification test.

💬 Still Seeing the Error?

If you have followed all the steps above and the pixel is still not verifying, there may be a theme conflict, a custom caching layer, or an advanced GTM configuration causing the issue. 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.