🧭 Overview
If you have installed the Search Atlas WordPress plugin and entered your UUID but still see a "UUID not correct" error, your white-label domain configuration is likely the cause. Standard plugin installations validate the UUID against the default Search Atlas dashboard URL. When your account uses a custom white-label domain — such as dashboard.hearingassetadvisors.com — the plugin needs additional configuration to recognize that domain as a trusted source. This article walks you through every fix.
🔍 Why White-Label Domains Cause UUID Errors
The OTTO pixel plugin validates your UUID by communicating with the Search Atlas dashboard. If your account is accessed through a white-label domain, the plugin must be told which domain to trust. Without this, the handshake between your WordPress site and the dashboard fails, producing a UUID validation error even when the UUID itself is perfectly correct.
- The UUID displayed inside a white-label dashboard is the same UUID used platform-wide — no separate UUID is issued.
- The error is not caused by a wrong UUID; it is caused by a domain mismatch during validation.
- Resolving the mismatch requires configuring the plugin settings under Search Atlas → Settings or inserting the pixel script manually.
✅ Step 1 — Verify Your UUID Is Copied Correctly
Before changing any settings, confirm the UUID itself is error-free.
- Log in to your dashboard through your white-label domain (for example, dashboard.hearingassetadvisors.com).
- Navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar.
- Locate your OTTO pixel UUID. It is a long alphanumeric string with hyphens.
- Click the copy icon next to the UUID — do not type it manually.
- Paste it into a plain-text editor and confirm there are no leading spaces, trailing spaces, or line breaks.
- Re-enter this clean UUID in the WordPress plugin settings and save.
If the error persists after this step, continue to Step 2.
⚙️ Step 2 — Enable the White-Label Domain in Plugin Settings
The Search Atlas WordPress plugin includes a setting that allows you to declare your white-label domain so UUID validation routes correctly.
- In your WordPress admin panel, go to Search Atlas → Settings in the sidebar.
- Locate the field labelled Dashboard Domain or Custom Domain (exact label may vary by plugin version).
- Enter your full white-label domain including the subdomain, for example: dashboard.hearingassetadvisors.com.
- Save the settings.
- Return to the UUID field, re-paste your UUID, and save again.
- Reload the page and check whether the validation error has cleared.
If your plugin version does not show a Dashboard Domain field, proceed to Step 3.
🔗 Step 3 — Enable Metasync in the Plugin
Metasync is the background sync feature that links your WordPress site to the Search Atlas platform. It must be active for UUID validation to work under a white-label domain.
- In your WordPress admin panel, open Search Atlas → Settings in the sidebar.
- Find the toggle labelled Metasync or Enable Metasync.
- Switch it to On or Enabled.
- Save your settings.
- Wait up to two minutes, then reload the plugin settings page to confirm the UUID now shows as verified.
📋 Step 4 — Insert the Pixel Script Manually (Alternative Method)
If the plugin-based UUID entry continues to show errors, you can bypass it entirely by inserting the full OTTO pixel script directly into your WordPress site's code. This method works regardless of white-label domain configuration.
- Log in to your dashboard through your white-label domain.
- Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar.
- Find the OTTO pixel section and click Copy Script or Get Pixel Code. This copies the complete tag including your UUID already embedded inside it.
- In your WordPress admin panel, go to Appearance → Theme File Editor, or install a plugin such as Insert Headers and Footers if you prefer not to edit theme files directly.
- Paste the copied script into the section of your site. If using Insert Headers and Footers, paste it in the Scripts in Header field.
- Save the changes.
- Visit your website, right-click the page, and select View Page Source. Search for your UUID to confirm the script is present in the page HTML.
Once the script is live in your page source, the OTTO pixel is active. You do not need the plugin's UUID field to show a green checkmark for tracking to function when the script is inserted manually.
🌐 Does Your White-Label Domain Affect Pixel Tracking?
Your white-label domain affects the validation step inside the plugin UI, but it does not change what the pixel collects or how OTTO processes your site data. Once the pixel script is live on your pages — whether via the plugin or manual insertion — all tracking and OTTO automation works exactly as it does for standard installations. The white-label domain is purely a branding layer for your dashboard access.
🛠️ Quick Troubleshooting Checklist
- UUID copied with extra spaces? Re-copy using the copy icon, not manual selection.
- Plugin Dashboard Domain field filled in? Enter your full white-label domain.
- Metasync enabled? Toggle it on and save.
- Plugin version outdated? Update the Search Atlas plugin to the latest version from the WordPress plugin repository.
- Script inserted manually but UUID not in page source? Clear your caching plugin and CDN cache, then re-check.
- Firewall or security plugin blocking the script? Whitelist the Search Atlas pixel domain in your security plugin settings.
💬 Need More Help?
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.