Search Atlas Help Center

🛠️ Fix OTTO Script Not Recognized on WordPress

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

Camilo Aponte

Last updated on Sep 30, 2026

🔍 Overview

If you have installed the OTTO script on your white-label WordPress site but the Site Auditor still shows "not installed" or returns an "incorrect domain" error, this guide walks you through the most common causes and how to fix them.

⚠️ Common Causes of This Error

  • The domain registered in Search Atlas does not exactly match the URL of your WordPress site.
  • A legacy Search Atlas pixel is installed instead of the current OTTO pixel.
  • The script was added to the wrong location in the WordPress theme or a caching plugin is serving an old version of the page.
  • A security tool (such as Avast or a firewall plugin) is blocking or stripping the OTTO script before it loads.
  • The site uses Google Tag Manager (GTM) and the tag is not firing correctly on all pages.

✅ Step 1 — Verify the Domain in Search Atlas

  1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (URL: /seo-automation-v3).
  2. Open your OTTO project and locate the domain listed at the top of the project settings.
  3. Compare this domain exactly with the URL of your WordPress site — including whether it uses www or non-www, and http vs https.
  4. If there is any mismatch, update the domain in the project settings to match your live site URL precisely.

🔄 Step 2 — Replace Any Legacy Script

An older Search Atlas pixel will not be recognized by the current OTTO system. To get the correct, up-to-date script:

  1. Inside your OTTO project, click Connect OTTO or Get Script to copy the current pixel code.
  2. Log in to your WordPress admin dashboard.
  3. Go to Appearance → Theme File Editor (or use a header/footer plugin such as Insert Headers and Footers).
  4. Remove any existing Search Atlas or OTTO script that is already present.
  5. Paste the new OTTO script inside the section of every page.
  6. Save your changes.

🏷️ Step 3 — If You Are Using Google Tag Manager

Deploying the OTTO pixel through GTM requires the tag to fire on all pages, not just the homepage.

  1. In GTM, open the tag containing the OTTO script.
  2. Confirm the trigger is set to All Pages.
  3. Publish the GTM container to push the change live.
  4. Use GTM Preview mode to confirm the tag fires on multiple pages of your site, including internal pages.

🛡️ Step 4 — Check for Security Plugin or Antivirus Interference

Some security tools flag the OTTO pixel on white-label domains. To check whether this is happening:

  • Temporarily disable any WordPress security plugins (e.g., Wordfence, iThemes Security) and reload the page to see if the script is recognized.
  • If your visitors use Avast or similar antivirus software, the script may be blocked client-side — contact our team using the chat widget below for guidance on whitelisting the OTTO domain for your brand.
  • Re-enable your security plugins after testing.

🧹 Step 5 — Clear Caches and Re-verify

  1. Clear your WordPress caching plugin (e.g., WP Rocket, W3 Total Cache, LiteSpeed Cache).
  2. Clear any CDN cache (e.g., Cloudflare) by purging all files.
  3. Open your site in a private or incognito browser window and view the page source (Ctrl + U on Windows, Cmd + U on Mac).
  4. Search for the OTTO script in the source code to confirm it is present and unmodified.
  5. Return to your OTTO project in Search Atlas and click Verify Installation to trigger a fresh check.

📊 Step 6 — Run a New Site Audit

Once the script is confirmed in the page source, trigger a fresh audit to update the recognition status:

  1. Go to OTTO SEO → Site Audit → Overview (Website Overview) in the left sidebar.
  2. Open your project and click Recrawl Site.
  3. Wait for the crawl to complete — this may take a few minutes depending on site size.
  4. Check that the OTTO status now shows Active and that the domain error has cleared.

💡 Still Seeing the Error?

If the domain error or "not installed" status persists after completing all steps above, there may be a configuration issue specific to your white-label setup that requires a closer look. 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.