Search Atlas Help Center

🔍 OTTO Pixel Not Detected Advanced Troubleshooting

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

Camilo Aponte

Last updated on Sep 30, 2026

🧭 Overview

After activating the OTTO WordPress plugin with your API key and UUID, Search Atlas Site Auditor must be able to crawl your site and confirm the pixel is present. If the auditor cannot reach your site — due to Cloudflare, a CDN, a firewall, or bot-blocking rules — it will report the pixel as undetected even when the plugin is installed and working correctly. Always check for server-side blocking first before revisiting plugin settings or caches.

🚧 Step 1 — Check for Cloudflare or CDN Bot Blocking

This is the most common and most overlooked cause of pixel detection failures. Cloudflare and similar CDNs can silently block the Search Atlas crawler before it ever reads your page source.

  1. Log in to your Cloudflare dashboard (or your CDN provider's dashboard).
  2. Go to Security → Events and filter by the last 24 hours. Look for blocked or challenged requests from Search Atlas crawlers.
  3. Go to Security → Bots and confirm that Bot Fight Mode or Super Bot Fight Mode is not set to block all automated traffic.
  4. Go to Security → WAF → Firewall Rules and check whether any rule blocks unknown bots, specific user agents, or high-frequency crawlers.
  5. If you find a blocking rule, create a WAF exception (allow rule) for the Search Atlas crawler, or temporarily set the security level to Essentially Off to test whether detection succeeds.
  6. After making changes, return to the Search Atlas platform and re-run the Site Audit to trigger a fresh detection check.

🔥 Step 2 — Check Server-Level Firewalls and Security Plugins

Even without Cloudflare, a server firewall or a WordPress security plugin can block the crawler at the hosting level.

  1. If you use a security plugin such as Wordfence, Sucuri, iThemes Security, or All-In-One Security, open its settings and review the blocked IP log or lockout log.
  2. Check whether your hosting provider's built-in firewall (common with WP Engine, Kinsta, SiteGround, and Cloudways) has flagged or rate-limited crawl traffic.
  3. Temporarily whitelist the Search Atlas crawler user agent (SearchAtlasBot) or disable aggressive bot-blocking rules for testing, then re-trigger the Site Audit.
  4. If your firewall requires specific IP ranges to be whitelisted, escalate to our support team with your site URL and firewall type so the current crawler IP list can be provided.

🤖 Step 3 — Verify robots.txt Is Not Blocking the Crawler

A Disallow rule in your robots.txt file can prevent the Site Auditor from accessing the pages where the pixel should be detected.

  1. Open a browser and navigate to https://yourdomain.com/robots.txt to view your current rules.
  2. Check for any Disallow: / rules or rules targeting all user agents (User-agent: *) that would block automated crawlers from accessing your site.
  3. If you find a blocking rule, either remove it or add a specific Allow entry for the Search Atlas crawler user agent (SearchAtlasBot).
  4. Save your updated robots.txt, then return to the Search Atlas platform and re-run the Site Audit.

🗄️ Step 4 — Clear Site and CDN Cache

After confirming no blocking rules are active, a stale cache may still serve an old version of your page that does not include the OTTO pixel script.

  1. In your WordPress admin, navigate to your caching plugin (e.g., WP Rocket, W3 Total Cache, LiteSpeed Cache) and click Clear All Cache.
  2. If you are using Cloudflare, log in to your dashboard, go to Caching → Configuration, and click Purge Everything.
  3. Ask your hosting provider to flush any server-side object or page cache if the above steps do not resolve the issue.
  4. Once all caches are cleared, re-run the Site Audit in Search Atlas to trigger a fresh crawl and detection check.

🔌 Step 5 — Confirm the OTTO Plugin Is Active and the Pixel Is Rendering

If blocking and cache issues have been ruled out, verify the plugin itself is correctly outputting the pixel on your live pages.

  1. Log in to your WordPress admin and go to Plugins → Installed Plugins. Confirm the Search Atlas plugin is Active (menu: Search Atlas → Settings).
  2. In the OTTO plugin settings, confirm your API key and UUID are saved correctly and match what is shown in your Search Atlas account.
  3. Open your homepage in a browser, right-click anywhere on the page, and select View Page Source. Search for otto or your UUID in the source code to confirm the pixel script is being output.
  4. If the pixel script is not visible in the page source, deactivate and reactivate the OTTO plugin, then check the page source again.
  5. After confirming the pixel is present in the source, return to Search Atlas and re-run the Site Audit.

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.