🔍 Overview

After installing the OTTO pixel through a Cloudflare Worker, the OTTO dashboard may still display a "Not Installed" status — even though the Worker deployed successfully and the pixel was working previously. This article explains the most common causes and the steps to resolve them.

⚙️ Why This Happens

The OTTO pixel verification system scans your live site to confirm the pixel is present and firing correctly. A "Not Installed" status after a Cloudflare Worker deployment is almost always caused by one of the following:

• Cloudflare API authorisation failure (cf_10000): The Worker was deployed but Search Atlas lost the API connection needed to confirm or maintain the installation. This surfaces as a silent failure — the deploy appears to succeed, but the pixel is not injected.
• Worker route not covering the correct URLs: The Cloudflare Worker route may be scoped to a path or subdomain that does not match the pages OTTO is scanning.
• Cached or stale scan result: OTTO's scanner checked the page before the Worker had fully propagated across Cloudflare's network (propagation can take a few minutes).
• Worker disabled or overridden: A Cloudflare configuration change (for example, a Page Rule, Cache Rule, or another Worker) may be intercepting requests before your OTTO Worker runs.
• Pixel key conflict: A previous pixel key installation was not cleanly removed, causing a conflict that blocks detection.

🚀 Step-by-Step Resolution

1. Check the Cloudflare API connection. In Search Atlas, go to OTTO SEO (left sidebar). Open your OTTO project settings and navigate to the Pixel Installation section. If you see a Cloudflare authorisation error or a cf_10000 code, re-authenticate by reconnecting your Cloudflare API token. Ensure the token has Zone:DNS:Edit, Zone:Zone:Read, Workers Scripts:Edit, Workers Routes:Edit, and Workers KV Storage:Edit permissions (the 'Edit Cloudflare Workers' template plus a Zone DNS Edit row) for the correct zone.
2. Verify the Worker is active in Cloudflare. Log in to your Cloudflare dashboard. Go to Workers & Pages and confirm the OTTO Worker is listed and shows a status of Active. Check that the Worker route pattern matches your full domain (for example, royallrides.com.au/*) and is not limited to a subdirectory.
3. Confirm no conflicting rules exist. In Cloudflare, review Page Rules and Cache Rules for your domain. Any rule that bypasses Workers or returns a cached response before the Worker executes will prevent the pixel from loading. Disable or reorder conflicting rules so the OTTO Worker runs first.
4. Remove and reinstall the pixel. If the issue persists, perform a clean reinstall. In OTTO's Pixel Installation section, delete the existing pixel key, wait 60 seconds, then generate a new key and redeploy via the Cloudflare Worker option. This clears any stale key conflict.
5. Trigger a fresh scan. After redeployment, wait at least 3–5 minutes for Cloudflare propagation, then return to the OTTO SEO section in Search Atlas and click Re-check Installation (or equivalent scan trigger). The status should update to Installed.
6. Test on a live page. Open a page on your domain in a private/incognito browser window. Right-click → View Page Source and search for the OTTO pixel snippet. If it is absent, the Worker is not injecting it — revisit steps 1–3.

📊 Impact on SEO Rankings

The OTTO pixel is required for OTTO to read your live site, apply on-page optimisations, and track ranking changes. While the pixel is undetected, no OTTO automations will execute on the site. This means approved changes — including title tags, meta descriptions, schema, and internal linking improvements — are not reaching your live pages, which directly limits ranking progress. Restoring pixel detection is the single most important fix before any other SEO work will take effect.

🛡️ Prevention Tips

• Avoid rotating or regenerating your Cloudflare API token without updating the credentials in Search Atlas at the same time.
• After any Cloudflare configuration change (zone settings, Cache Rules, new Workers), re-check the OTTO pixel status in the platform.
• If you use a third-party performance or security layer on top of Cloudflare (for example, an additional WAF or CDN), verify it is not stripping injected scripts.

💬 Still Need Help?

If you have followed the steps above and the pixel still shows as "Not Installed", our team can review your specific Cloudflare configuration and scan logs. 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.