🔍 Overview

The OTTO pixel connects your website to Search Atlas so OTTO SEO can read your site's data and apply optimisations. On WordPress, the most common setup issues are an incorrectly entered UUID, a misconfigured plugin installation, or a white-label domain that interferes with pixel verification. This article walks you through the correct setup process and explains how to resolve each of these issues.

⚙️ Step 1 — Find Your OTTO Pixel UUID

Before touching WordPress, make sure you have the correct UUID from Search Atlas.

1. Log in to Search Atlas and navigate to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3).
2. Select the project you are connecting.
3. Open the OTTO Pixel or Connect Site section.
4. Copy the full UUID — it is a long alphanumeric string. Copy it directly from the platform to avoid typos.

Important: The UUID is unique to each project. If you manage multiple sites, confirm you are copying the UUID that belongs to the exact domain you are configuring.

🔌 Step 2 — Install the Pixel Using the WordPress Plugin

Search Atlas provides a dedicated WordPress plugin that inserts the OTTO pixel automatically when you enter your UUID. Follow these steps precisely.

1. In your WordPress admin dashboard, go to Plugins → Add New → Upload Plugin, upload the Search Atlas plugin .zip file provided by Search Atlas, then install and activate the plugin.
2. After activation, go to the Search Atlas top-level menu in the WordPress admin sidebar and open Settings.
3. Paste your UUID into the OTTO Pixel UUID field. Do not add extra spaces, quotation marks, or any other characters around it.
4. Save your settings.

Once saved, the plugin automatically injects the pixel script into every page of your site. You do not need to manually copy or paste the full script code anywhere — the plugin handles this for you. If you have been manually inserting script code, remove those manual insertions to avoid duplication conflicts.

✅ Step 3 — Verify the Pixel Is Firing Correctly

After saving, return to Search Atlas and use the pixel verification tool to confirm the connection.

1. Navigate back to OTTO SEO → SEO Automation → your project → OTTO Pixel section.
2. Click Verify Pixel or Check Connection.
3. If verification passes, your setup is complete.
4. If you still see a "UUID not correct" error, continue to the troubleshooting steps below.

⚠️ Troubleshooting: "UUID Not Correct" Error

If the platform still reports that the UUID is not recognised after following the steps above, work through the following checks in order.

• Re-copy the UUID: Select all text in the UUID field in Search Atlas, copy it fresh, clear the WordPress plugin field completely, and paste again. A single wrong character will cause verification to fail.
• Check for caching: WordPress caching plugins (WP Rocket, W3 Total Cache, LiteSpeed Cache, etc.) can serve a cached version of your pages that does not yet include the pixel. Clear all caches after saving the plugin settings, then re-run verification.
• Check for conflicting scripts: If you previously inserted the OTTO script manually into your theme's functions.php, a header/footer plugin, or Google Tag Manager, remove those manual copies. Duplicate or malformed script instances will cause verification errors.
• Confirm the plugin is active: Go to Plugins → Installed Plugins and confirm the Search Atlas plugin status shows Active. An inactive plugin will not inject any code.
• Check your domain matches the project: In Search Atlas, confirm the domain listed under the project exactly matches the live URL of your WordPress site, including whether it uses www or not.

🌐 White-Label Domain Conflicts

If your Search Atlas account is accessed through a white-label domain (for example, a custom URL like dashboard.youragency.com that points to the Search Atlas platform), this affects only the interface URL you use to log in — it does not affect how the OTTO pixel functions on your client's website.

However, there are two scenarios where a white-label domain can indirectly cause issues.

• Pixel script source URL: In some configurations, the pixel script may reference the Search Atlas origin domain. If your white-label setup involves custom DNS routing or SSL termination that blocks outbound requests, the pixel call may fail. Confirm with your hosting or DNS provider that your white-label domain correctly passes through all traffic to the Search Atlas platform without blocking script requests.
• UUID copied from the wrong environment: If you have both a white-label dashboard and the main Search Atlas dashboard open, ensure you copy the UUID from the same environment where the project is registered. UUIDs are consistent across both interfaces, but double-checking removes any doubt.

In most cases, a white-label domain configured correctly as a DNS CNAME or proxy to the Search Atlas platform will not interfere with pixel verification. If you have confirmed all the steps above and the error persists, the issue is most likely a caching layer or a duplicate script conflict rather than the white-label domain itself.

📋 Quick-Reference Checklist

• UUID copied directly from OTTO SEO → SEO Automation → project → OTTO Pixel with no extra characters
• Search Atlas WordPress plugin installed and Active
• UUID pasted into the plugin settings and saved
• No manual script copies in theme files, header/footer plugins, or Tag Manager
• All WordPress caches cleared after saving
• Project domain in Search Atlas matches the live site URL exactly
• White-label domain DNS/proxy confirmed as passing through traffic correctly

💬 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.