Search Atlas Help Center

⏱️ OTTO Pixel Installation Timeline and Cloudflare Setup

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

Camilo Aponte

Last updated on Sep 30, 2026

🔍 Overview

After you connect your Cloudflare token and install the OTTO pixel, there is a short waiting period before Search Atlas can confirm the pixel is live on your site. This article explains the expected timeline, what each status means, and the steps to take if OTTO has not been detected after the waiting period has passed.

⏳ How Long Does Detection Take?

Once your Cloudflare token is connected and the OTTO pixel has been deployed, allow up to 2 hours for the system to verify the pixel on your site. This delay is normal and is caused by the time Cloudflare needs to propagate changes across its global network.

  • 0–30 minutes: Token is being validated and the pixel deployment is queued.
  • 30 minutes–2 hours: Cloudflare is propagating the worker script. The OTTO status may still show as Not Found during this window.
  • After 2 hours: Detection should be complete. If OTTO still shows as Not Found, follow the troubleshooting steps below.

⚙️ How to Connect Your Cloudflare Token

  1. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation Projects) (URL: /seo-automation-v3).
  2. Select your website from the All Sites list.
  3. Choose Cloudflare as your installation method and click Connect Cloudflare Token.
  4. Log in to your Cloudflare account and generate an API token using the Edit Cloudflare Workers template plus a Zone:DNS:Edit row, which includes Zone:DNS:Edit, Zone:Zone:Read, Workers Scripts:Edit, Workers Routes:Edit, and Workers KV Storage:Edit permissions scoped to the correct zone (domain).
  5. Paste the token into Search Atlas and click Save & Deploy.
  6. Note the time of connection and wait up to 2 hours before checking the pixel status.

🛠️ Troubleshooting: OTTO Not Found After 2 Hours

If more than 2 hours have passed and OTTO still shows as Not Found, work through the following checks in order.

  1. Confirm the token has the correct permissions. Return to your Cloudflare dashboard, open API Tokens, and verify the token includes Zone:DNS:Edit, Zone:Zone:Read, Workers Scripts:Edit, Workers Routes:Edit, and Workers KV Storage:Edit for the correct zone. A token with missing or wrong-zone permissions will silently fail to deploy the worker.
  2. Check the correct zone is selected. If your site uses multiple Cloudflare zones (for example, a subdomain on a separate zone), ensure the token is scoped to the exact zone where your site lives.
  3. Verify the worker is live in Cloudflare. In your Cloudflare dashboard, go to Workers & Pages and confirm a worker named by Search Atlas appears in the list. If it is absent, the deployment did not complete.
  4. Re-save your token in Search Atlas. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation Projects), open your site, disconnect the existing token, and reconnect it. This triggers a fresh deployment attempt.
  5. Check for a Cloudflare route conflict. If another worker is already assigned to a route that covers your domain, the OTTO worker may be blocked. In Cloudflare, go to Workers & Pages → Routes and look for overlapping route patterns.
  6. Disable Cloudflare caching temporarily for a test. Open your Cloudflare dashboard, go to Caching → Configuration, and set Development Mode to On for 3 minutes, then recheck the OTTO status in Search Atlas. This forces Cloudflare to serve the latest version of your pages without cache.

✅ Confirming Successful Detection

When OTTO has been successfully detected, the status indicator in OTTO SEO → All Sites (SEO Automation Projects) will change from Not Found to Active. You will also see a green check mark next to your domain. At this point OTTO is live and will begin applying your SEO automations.

💡 Tips to Avoid Detection Delays

  • Always generate a new, dedicated API token for Search Atlas rather than reusing a token created for another tool. Shared tokens can have conflicting permission scopes.
  • Make sure your Cloudflare account plan supports Workers. Workers are available on the Free plan, but very high-traffic sites may require a paid plan for consistent execution.
  • Do not rotate or delete the Cloudflare token after connecting it. Search Atlas uses the token continuously to manage the worker. Deleting it will cause OTTO to go offline.

🆘 Still Need Help?

If you have completed all the steps above and OTTO is still not detected, 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.