Search Atlas Help Center

🛠️ OTTO Pixel Troubleshooting Guide

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

Camilo Aponte

Last updated on Sep 30, 2026

If OTTO shows "Not Installed," "Not Detected," or is not firing, this guide covers every known root cause and fix — from incomplete setup and crawler blocks to caching conflicts and script placement errors.

⚠️ Error States This Guide Resolves

  • "OTTO Not Installed"
  • "OTTO Not Detected"
  • "Missing crawl data"
  • Pixel not firing
  • No deployments verified

🔍 Root Causes

Almost all OTTO detection failures trace back to one of these causes:

  • Incomplete project setup (installation wizard not completed)
  • Caching or minification interference
  • Incorrect script placement
  • Duplicate pixel installations
  • Blocked Search Atlas crawler
  • Site performance / slow server response time

🧭 Universal Troubleshooting Steps

Work through Steps 1–6 in order. Most OTTO detection failures are resolved by Step 2 or earlier.

⏳ Step 0 — Give a Brand-New Install a Few Minutes First

If you just finished installing the pixel and OTTO still shows "Not Installed" or "Not Detected," this is very often a short detection delay — caused by cache/CDN propagation or the page needing a moment before our scanner re-checks it — rather than a broken install.

  • Wait a few minutes after installing, clear your site's cache (and your browser cache), then re-run the diagnostic scan.
  • If the status still shows "Not Installed" after that, continue with Steps 1–6 below, which cover the confirmed root causes: incomplete setup, crawler blocking, caching, script placement, duplicate installs, and slow server response.

Note: Pixel detection and your project's Site Audit crawl are separate systems. A Site Audit crawl still running in the background does not block or delay your OTTO pixel status.

✅ Step 1 — Check for Incomplete Project Setup

If your site shows "Not Installed" despite the OTTO pixel visibly firing, the project was likely added to OTTO but the setup wizard was never completed. This most commonly surfaces on Duda-hosted sites but can occur on any platform. Regardless of your CMS, an incomplete wizard creates a false "Not Installed" status even when the pixel is live and firing correctly.

  1. Go to OTTO and locate the affected project.
  2. If a Continue Installation button appears, click it to finish the setup wizard.
  3. Re-run the diagnostic scan once setup is complete.

The pixel status changes from "Not Installed" to "Detected" as soon as the setup wizard finishes.

Note: If you are using Classic View on the Search Atlas home page and cannot connect your website to an OTTO project (receiving an API 400 error), switch to the new default view and try again. This is a known interface-specific bug currently being resolved. If switching views does not help, contact support.

🛡️ Step 2 — Whitelist the Search Atlas Crawler

If your CDN or firewall blocks the Search Atlas user agent, OTTO cannot detect your pixel — even when it is installed correctly. This is the most critical step if Step 1 did not resolve the issue.

☁️ Cloudflare

Go to Cloudflare → Security → Bots and disable:

  • Bot Fight Mode
  • Super Bot Fight Mode

⚠️ Known Issue OTTO-1850 — OTTO Shows Inactive Despite a Validated Cloudflare API Token

Even when the Cloudflare API token shows as Connected in OTTO settings, a known detection bug may still report OTTO as inactive. Disconnect and reconnect the Cloudflare integration, then re-run the diagnostic scan.

⚠️ Known Issue OTTO-1931 — Deployed Changes Appear Then Revert

This is a known issue with the Cloudflare DNS integration. Reconnect the integration and re-deploy. If reverts continue, contact support and reference OTTO-1931.

⚠️ Known Issue OTTO-1943 — Updated H1 Visible in Google Search Console but AI Crawlers Still Show the Original

This is an edge-level deployment issue where the H1 does not deploy for non-JS bots, even though Googlebot (which renders JS) sees the updated H1. Contact support and reference OTTO-1943 for the backend fix.

☁️ Cloudflare Worker — Special Character Corruption

If characters like & or ' appear on your pages after engaging OTTO via Cloudflare, this was caused by a known OTTO Cloudflare Worker script-injection bug (SPE-666) that affected headings with nested HTML elements. The bug is resolved and the updated Cloudflare Worker script is live.

To apply the fix:

  1. Disengage OTTO.
  2. Go to Avatar → Settings → Integrations.
  3. Disconnect and reconnect your Cloudflare integration.
  4. Re-engage OTTO.

If encoding issues persist after reconnecting, contact support.

Webflow note: On Webflow sites, after disengaging OTTO to fix encoding corruption, the diagnostic tool may fail to re-detect the Cloudflare Worker installation. If this occurs, fully remove and re-add the Cloudflare integration from scratch rather than using the reconnect flow, then re-run the diagnostic scan.

🔒 WordFence

Go to WP Admin → WordFence → Firewall → Firewall Options → Allowlisted IPs/User Agents and add:

  • Search Atlas Bot (https://www.searchatlas.com/)

🚫 Stop Bad Bots Plugin

Go to WP Admin → Block Bad Bots → Settings → Settings tab and either disable Block All Bots, or add the allowed user agent:

  • Search Atlas Bot (https://www.searchatlas.com/)

🧹 Step 3 — Clear Cache and Disable Minification

Caching layers and JavaScript minification can prevent the OTTO pixel from loading correctly, or cause a previously detected pixel to stop firing.

  1. Clear your site's server-side cache (hosting control panel or caching plugin).
  2. Clear any CDN cache (e.g., Cloudflare → Caching → Purge Everything).
  3. If you use a WordPress caching plugin (WP Rocket, W3 Total Cache, LiteSpeed Cache, etc.), purge all cached files.
  4. If JavaScript minification or concatenation is enabled, temporarily disable it and re-run the OTTO diagnostic scan to confirm whether minification is the cause.
  5. Re-run the OTTO diagnostic scan after clearing all caches.

📌 Step 4 — Verify Script Placement

The OTTO pixel must be placed in the correct location in your page's HTML. Incorrect placement can prevent detection even when the script is present.

  • Place the OTTO pixel script inside the <head> tag, as high as possible.
  • Confirm the script is not inside a conditional block, a footer widget, or a section that renders after the page body.
  • On WordPress, check that no plugin is deferring or async-loading the OTTO script in a way that delays its execution.
  • Use your browser's developer tools (View Source or Elements panel) to confirm the OTTO script tag is present and in the <head>.

🔁 Step 5 — Check for Duplicate Pixel Installations

Multiple instances of the OTTO pixel on a single page can cause detection failures or conflicting signals.

  1. Use your browser's developer tools (Network or Elements panel) to search for multiple instances of the OTTO pixel script.
  2. If you find duplicates, remove all but one installation — typically keeping the one managed through OTTO's official integration or your CMS's <head> injection.
  3. Re-run the OTTO diagnostic scan after removing duplicates.

🐢 Step 6 — Check Site Load Time

If your server responds too slowly, the Search Atlas crawler may time out before completing its scan, causing OTTO optimizations to appear missing even when the pixel is installed correctly.

  1. Test your site's load time using PageSpeed Insights or a similar performance testing tool.
  2. If your server response time (TTFB) is consistently above 2–3 seconds, contact your hosting provider — a slow or timing-out server can prevent the crawler from completing a full scan.
  3. Re-run the OTTO diagnostic scan after any hosting or performance improvements.

🛍️ Shopify — Correct OTTO Pixel Installation

Manual OTTO pixel injection on Shopify can break themes and generate multiple errors if the script is pasted into the wrong location. Do not copy-paste the pixel script directly into Shopify's theme editor without following the correct steps.

  1. In your Shopify admin, go to Online Store → Themes → Edit Code.
  2. Open theme.liquid and locate the closing </head> tag.
  3. Paste the OTTO pixel script immediately before </head>.
  4. Save the file and verify the script appears in the page source before going live.

Avoid injecting the script into snippets, sections, or asset files that Shopify's pipeline compiles or reorders — this can conflict with the asset pipeline and trigger theme errors. If your theme already has 9 or more errors after injection, contact Search Atlas support for agent-assisted theme remediation.

🤖 AI-Builder and React-Based Sites — Deployments Engaged but Not Visible

On sites built with AI-powered or no-code builders (such as Lovable.ai) or custom React frameworks, OTTO deployments may appear as "Engaged" in the dashboard but never render on the live site. This occurs when the site's own client-side code — commonly a MutationObserver or hydration logic inside a component like Seo.tsx — intercepts and reverts OTTO's DOM changes after they are applied.

  1. Confirm that OTTO shows deployments as "Engaged" but changes are invisible on the live page.
  2. Ask your developer (or audit the framework source yourself) to search for MutationObserver, useEffect with DOM targeting, or hydration calls inside SEO-related components (e.g., Seo.tsx, Head.tsx).
  3. Any component that overwrites <title>, <meta>, or heading elements after page load can revert OTTO's changes. Remove or adjust the conflicting logic so it does not override third-party DOM modifications.
  4. Contact Search Atlas support if you need help identifying the conflicting component.

⚠️ Known Issue — Fatal Error on Divi / Elegant Themes WordPress Sites

If your Divi or Elegant Themes WordPress site goes down or displays a fatal PHP error after OTTO pixel installation (Call to undefined function et_theme_builder_decorate_page_resource_slug()), this is a known active bug in Otto_pixel_class.php:626. Open a support ticket immediately and include the Sentry reference WORDPRESS-METASYNC-2XGY so the team can prioritize and expedite the fix for your account.

🎯 After completing these steps, your OTTO pixel should detect successfully and deployments should begin verifying. If you are still seeing errors, contact Search Atlas support with your site URL and the specific error message — and reference any known-issue code above if it applies to your situation.

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.