This guide will walk you step-by-step through adding the OTTO Pixel to your site using Google Tag Manager (GTM). You’ll know exactly where to click and what to look for — no previous experience required.
📄 Step 1: +Create a new project.
📄 Step 1: +Create a new project.
Start inside your Search Atlas dashboard.
Left Sidebar → AI SEO → All Sites → + Create (top-right)
Follow the Setup Steps.
🌐 Step 2: Select or Add Your Website
🌐 Step 2: Select or Add Your Website
Enter your full URL (e.g., https://yourdomain.com).
• Wait for the green verification check mark confirming the domain.
• Then click "Continue".
📝 Step 3: Set up Fields (Optional).
📝 Step 3: Set up Fields (Optional).
You will see fields for Business Information, Address, and Social Profiles.
• These fields are optional for Pixel installation.
• You may complete them now or later.
Click "Continue" to proceed.
📎 Step 4: Copy Your OTTO Pixel Script.
📎 Step 4: Copy Your OTTO Pixel Script.
Inside the Installation Guide:
• Select "Google Tag Manager" from the CMS list.
Click the Video Guide Card, then scroll to Pixel Code and copy it.
Click "Step by step" for detailed GTM instructions (See the next step before clicking continue!).
Click "Continue" to proceed.
🛠️ Step 5: Install the OTTO Pixel Script in GTM.
🛠️ Step 5: Install the OTTO Pixel Script in GTM.
Log in to your Google Tag Manager account at https://tagmanager.google.com.
On the left menu, click Tags.
In the top right corner of the Tags page, click the New button (white box with a plus sign).
4. A new panel will slide in from the right — at the top, give your tag a name (e.g., "Search Atlas Tracking").
5. Under the tag options, scroll down to Custom and choose Custom HTML as the tag type.
6. Copy and paste the Search Atlas script into the HTML field, ensuring that all necessary parameters, such as your unique app token, are correctly inserted.
7. Under Triggering, select All Pages so the script runs across your entire site. Then, click Save to apply the changes.
8. Go to the top right and select the submit button. A sidebar will appear, click Publish and a Name if you wish, if not, click SKIP. The tag will be published.
9. Test the Pixel
In GTM, click Preview (top right).
Enter your website URL, and click Connect.
Your site will open in a new tab.
Go back to GTM — under Output, look for Tag Fired with your pixel’s name.
Challenges with React.js and Custom Websites
It's worth noting that React.js or custom websites like Bolt.new can sometimes encounter script-related installation conflicts, including base64-related token errors. For these cases, Google Tag Manager (GTM) provides a streamlined alternative for including the Search Atlas Pixel, bypassing direct script injection issues.
🚀 Step 6: Activate in SearchAtlas.
🚀 Step 6: Activate in SearchAtlas.
Once OTTO completes the initial setup for your project, your website appears inside the OTTO SEO (📊) Automation dashboard. You need to click on your project.
Then you'll see:
• Your domain name at the top (e.g., https://yourdomain.com).
• Below it, your SEO performance metrics, including:
– Healthy Pages (pages scanned so far)
– OTTO Grader (overall site health score)
– Content, Authority, Technicals, UX Signals (the four SEO pillar indicators)
On the right side of the site row, you’ll see:
• A red status label such as “Not Installed” or “OTTO Not Found.”
→ This means the OTTO Pixel has not been verified yet.
• A Scan button
→ Used to run OTTO’s Installation Diagnostics.
• A yellow/orange Disengaged toggle
→ Indicates OTTO is inactive until Pixel verification succeeds.
Next Steps
1️⃣ Click Engage OTTO.
This enables the site for testing and prepares the system to check your Pixel connection.
2️⃣ Click Scan.
This opens the Installation Diagnostics modal.
Your domain (e.g., https://yourdomain.com) will appear automatically in the field.
3️⃣ Verify the domain, then click Run Diagnostics.
OTTO will begin scanning your site for the installed Pixel.
During this stage, you’ll see the message:
“Running Diagnostics…
We’re checking the selected page for any OTTO implementation issues.
This might take a few seconds — hang tight!
A detailed report will be ready shortly.”
This confirms that OTTO is checking your site for the Pixel across your environment. The scan may take a couple of minutes — this is normal.
⏳ If the status remains red after the scan:
Wait 3–5 minutes to allow the Pixel to propagate across your domain fully. Then refresh the OTTO SEO dashboard — the status should update once the Pixel is detected.
That’s it! The OTTO Pixel is now live on your GHL site, powering automated insights and performance boosts for your SEO strategy. Make sure to revisit the diagnostics panel anytime to ensure your tracking is running smoothly.
🔎 Understanding Your OTTO Installation Diagnostics Results
After you click Scan → Run Diagnostics, OTTO inspects your website to verify Pixel installation, detect duplicates, confirm UUID validity, and validate deployed SEO fixes.
Below is what each possible status means and what you should do next:
❌ 1. “OTTO not detected.”
❌ 1. “OTTO not detected.”
What does it mean:
OTTO couldn’t find your Pixel script in the live HTML for the scanned URL.
Why does it happen:
Pixel not installed
Pixel added to the wrong theme/template
Installed on staging but not production
Installed on a different domain variant (www vs non-www / http vs https)
What to do:
Reinstall the Pixel using the correct installation guide, then wait 3–5 minutes for the status to update after saving changes.
❌ 2. “Your script is using an incorrect UUID.”
❌ 2. “Your script is using an incorrect UUID.”
What does it mean:
A Pixel exists, but the UUID doesn’t match the one assigned to your site.
Why does it happen:
Pixel copied from another project
Duplicate site setup
Wrong script was pasted into the template
Old Pixel copied before regenerating a new one
What to do:
Replace the script with the correct Pixel UUID from your Installation Guide.
Then wait up to 3 minutes for OTTO to re-check the installation.
⚠️ 3. “Duplicate Installation Detected.”
⚠️ 3. “Duplicate Installation Detected.”
What does it mean:
OTTO found more than one Pixel on your site.
Possible duplicates:
JavaScript Integration duplicated
WordPress Plugin + JavaScript script at the same time
Multiple manual Pixels installed across templates
Pixel is installed in both global and page-level injectors
What to do:
Remove the extra instances and leave only one valid Pixel.
Once fixed, wait 3 minutes for the system to update.
🟡 4. “OTTO is disengaged.”
🟡 4. “OTTO is disengaged.”
What does it mean:
Your Pixel may be installed, but OTTO is not turned on for this site.
What to do:
Return to the OTTO dashboard → click Engage OTTO → re-run Scan → Run Diagnostics.
🟢 5. “Deployed Fixes Verification — OK”.
🟢 5. “Deployed Fixes Verification — OK”.
What does it mean:
OTTO confirms that on-page fixes (meta tags, headings, titles, etc.) have been properly deployed and rendered in the live HTML.
This means everything is functioning normally.
⚠️ 6. “Some deployments were not identified in our scan.
⚠️ 6. “Some deployments were not identified in our scan.
What does it mean:
At least one of the fixes OTTO attempted to deploy did not appear in your rendered HTML during the verification pass.
Why does it happen:
Cache not cleared
CDN is still serving an old version
Fix deployed but not published
Plugin conflict (WordPress only)
JavaScript rendering delay
What to do:
Click View Issue to see which page or tag failed → then re-run Scan after clearing cache.
🟣 7. The Purple Banner (First-Time Installations).
🟣 7. The Purple Banner (First-Time Installations).
If this is your first Pixel installation, you may also see:
“Site processing is still in progress.”
“Waiting for data…”
“No crawl data available yet.”
“Pixel detected — awaiting first scan results.”
This is normal.
OTTO’s first crawl can take up to 24 hours, depending on site size and CMS.
If more than 24 hours pass → go to
Scan → Run Diagnostics → Re-run Crawl.
🧭 Summary of What Your Results Mean.
🧭 Summary of What Your Results Mean.
Message | Meaning | Action |
❌ OTTO not detected | Pixel missing | Install + Publish + rescan |
❌ Incorrect UUID | Wrong script | Replace Pixel + Publish |
⚠️ Duplicate Pixel | More than one Pixel | Remove duplicates |
🟡 OTTO disengaged | Pixel found but inactive | Engage OTTO |
🟢 Fixes Verified | Working correctly | No action |
⚠️ Fixes Missing | Fixes not in HTML | Clear cache + rescan |
🟣 Processing banner | First crawl running | Wait or Re-run Crawl |
🛟 Troubleshooting if OTTO Shows “Not Engaged.”
🛟 Troubleshooting if OTTO Shows “Not Engaged.”
✅ Check that you pasted the correct OTTO Pixel script into GTM.
✅ Confirm the trigger is set to All Pages.
✅ Make sure you have published the container in GTM after saving.
✅ Wait 3–5 minutes, then refresh your Search Atlas dashboard.
✅ If it still says “Not Engaged”, click Enable again in Search Atlas.
Alternative Installation Method
If GTM is not suitable for your setup, consider directly placing the pixel code in your site’s <head> tag. Ensure it is correctly added to all required pages and follow installation instructions provided by Search Atlas.
✅ You’re all set!
Your OTTO Pixel is now connected to your site through Google Tag Manager and will run on every page you’ve selected.
💡 Pro Tip: Whenever you make changes to your GTM tags or triggers, remember to republish the container so OTTO can continue tracking and optimizing your site without interruption.
If you still see “Not Engaged” in your Search Atlas dashboard after following the steps and troubleshooting, recheck your GTM setup or contact our support team with your site’s UUID and script code handy — this will help us assist you faster.
For unique site setups like React.js frameworks or builders such as Bolt.new, our support team is equipped to provide specialized assistance. Remember to include your site's UUID and pixel script when contacting support for quicker resolution.