Fix OTTO Script Detection on White-Label WordPress

Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🧩 Why This Happens

When the OTTO script is installed on a white-label WordPress site, the script may register against the wrong domain. As a result, the Site Auditor cannot verify ownership and throws an incorrect domain error — even if the snippet appears to be in the right place in your page source.

This is a known conflict specific to white-label WordPress sites. If you are experiencing this error, contact our support team so they can investigate the domain mapping and guide you to the correct setup method for your specific configuration.

✅ General Troubleshooting Steps

While support reviews your case, you can try the following steps to rule out common causes.

  1. Log in to your Search Atlas account and navigate to your OTTO setup for the affected site.
  2. Confirm that the OTTO script or plugin installed on your WordPress site corresponds to the correct site in your Search Atlas account. Mismatches between sites are a common cause of domain errors on white-label setups.
  3. Log in to your WordPress admin dashboard (e.g., yoursite.com/wp-admin) and check whether OTTO is connected via a plugin or a manually placed script snippet. Note which method is in use — your support agent will need this information.
  4. If your site uses caching plugins (e.g., WP Rocket, W3 Total Cache, LiteSpeed Cache), clear all caches and purge your CDN cache if applicable, then check whether the error persists.
  5. If your site uses a page builder (such as Elementor or Divi) that injects custom scripts, verify that only one instance of the OTTO script is present on the site. Duplicate or conflicting script instances can interfere with detection.
  6. After making any changes, return to your Search Atlas account and trigger a fresh check for your site, then allow a few minutes for the connection status to refresh.

⚠️ Important Notes for White-Label Sites

  • If you manage multiple white-label client sites, confirm that each site is connected to its own corresponding site entry in Search Atlas. Do not share credentials or tokens across different domains.
  • If the error persists after the steps above, contact Search Atlas support with details about your white-label configuration so the team can identify the correct resolution for your setup.