Overview

When you upgrade your Search Atlas plan or configure a whitelabel subdomain, your Otto pixel becomes tied to a new URL environment. Any previously installed pixels are no longer valid for that domain, which causes "Otto not deployed" and "Access forbidden" errors across your projects. The fix requires you to regenerate your Otto pixel inside the platform and redeploy it to each site under your new whitelabel subdomain.

When Pixel Regeneration Is Required

You must regenerate and redeploy your Otto pixel any time one of the following changes occurs:

• You upgrade to a new Search Atlas plan
• You set up or change a whitelabel subdomain
• You transfer projects to a different whitelabel environment
• Your current pixel was generated before your whitelabel subdomain was fully activated

In all of these cases, the old pixel references the previous domain and will not authenticate correctly against the new whitelabel URL, triggering the errors you are seeing.

Step 1 — Confirm Your Whitelabel Subdomain Is Active

Before regenerating your pixel, make sure your subdomain is fully propagated and reachable.

1. Open a browser and navigate to your whitelabel subdomain.
2. Confirm the Search Atlas login screen loads without errors. If it does not load, your DNS records may still be propagating — allow sufficient time after initial setup for propagation to complete.
3. Log in through your whitelabel subdomain URL, not through the default Search Atlas domain. All steps below must be completed while logged in via your whitelabel URL to ensure the pixel is generated for the correct environment.

Step 2 — Regenerate Your Otto Pixel

1. Log in to the platform via your whitelabel subdomain URL.
2. Navigate to OTTO SEO → All Sites (SEO Automation).
3. Select the project that is showing "Otto not deployed."
4. Locate the pixel or deployment option within the project and use the available control to generate a new pixel script. The platform will produce a fresh pixel tied to your active whitelabel subdomain.
5. Copy the full pixel code snippet that appears. Do not close this screen until you have successfully installed the code in the next step.

Step 3 — Redeploy the Pixel to Your Site

1. Log in to the WordPress admin panel (or your site's CMS) for the project you are working on.
2. Navigate to the location where your previous Otto pixel was installed. This is typically inside a header script field, a dedicated Otto plugin settings page, or a custom code snippet area.
3. Replace the old pixel code with the new pixel code you copied in Step 2.
4. Save your changes and clear any site or server caches.
5. Return to the platform and verify that the project now shows Otto as deployed. If it still shows an error, wait a few minutes and refresh the page before troubleshooting further.

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.