🧭 Overview
The OTTO Pixel connects your website to Search Atlas so OTTO can monitor and automate SEO tasks. If your pixel shows as Not Installed or Duplicate Detected, this guide walks you through platform-specific considerations, UUID validation, and a verification checklist for multi-account setups.
🔑 Step 1: Retrieve Your Account-Specific Pixel Code
Each Search Atlas account has a unique pixel tied to its UUID. Using the wrong code—or reusing one across accounts—is the most common cause of detection errors.
- Log in to Search Atlas and navigate to the OTTO or SEO automation section of the platform.
- Select the specific account or project you are troubleshooting.
- Locate the OTTO Pixel snippet for that account and copy it exactly as displayed.
- Confirm the UUID string inside the snippet matches the account you are working on. The UUID is the alphanumeric identifier embedded in the pixel script URL.
- If you manage multiple accounts, repeat this process for each one individually—never share a single pixel across different accounts.
📍 Step 2: Understand Header Placement Requirements
The OTTO Pixel must be placed inside the <head> tag of every page, as high as possible before other scripts. Placement in the footer or body will cause unreliable detection and may trigger a Not Installed status even when the code is present.
- The pixel should load on all pages, not just the homepage.
- Avoid placing it inside conditional logic blocks that prevent it from firing on every page load.
- If a tag manager (such as Google Tag Manager) is used, ensure the tag is set to fire on All Pages with no exceptions.
🏗️ Step 3: Platform-Specific Installation Guidance
⚡ GoHighLevel (GHL)
GHL allows you to add custom scripts at the site or funnel level. Paste your OTTO Pixel snippet into your site's header script area so it fires on every page. Note that site-level scripts may not automatically apply to funnel pages—check each funnel's settings individually and add the pixel there as well if needed. Save and publish your changes, then allow some time before re-checking detection status in Search Atlas.
🔵 WordPress
On WordPress, the pixel must be inserted into the <head> section of every page. You can do this by editing your theme's header template directly, or by using a plugin that allows you to inject scripts into the header site-wide. Using a plugin is generally recommended for stability, as direct theme edits may be lost if the theme is updated or changed. Whichever method you use, verify the pixel is loading on all pages—not just the homepage—after installation.
🌸 Orchid CMS
Orchid CMS and similar platforms typically provide a global header code or custom script area in site settings. Paste your OTTO Pixel snippet into that header field so it applies across all pages. Consult your CMS documentation if you are unsure where the global header script area is located.
✅ Step 4: Verification Checklist
- Confirm the UUID in your pixel snippet matches the correct Search Atlas account.
- Verify the pixel is placed in the
<head>section, not the footer or body. - Check that the pixel fires on all pages, not just the homepage.
- For multi-account setups, ensure each site uses its own unique pixel—do not share snippets across accounts.
- After making changes, wait a few minutes and then recheck pixel status in Search Atlas.
- Use your browser's developer tools (View Source or Network tab) to confirm the pixel script is present in the page source.
🆘 Still Seeing Issues?
If you have followed all of the steps above and your pixel status still shows as Not Installed or Duplicate Detected, a support agent can investigate further. When reaching out, please have the following ready: your Search Atlas project or account name, the URL of the affected site, the UUID from your pixel snippet, and a description of which CMS platform you are using.
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.