Skip to main content

✅ Troubleshooting OTTO Pixel & Plugin Issues Across All Platforms

A step-by-step guide to help you identify, resolve, and validate the most common pixel installation and detection errors.

Updated yesterday

Installing the OTTO Pixel is the gateway to unlocking automated SEO optimization through Search Atlas. But what happens when you follow all the steps, and it still doesn’t work? Whether you're using WordPress, GTM, GHL, or another CMS, even minor misconfigurations can block OTTO from scanning your site or deploying fixes.

This guide is designed to walk you through the most common issues (and their solutions), so you can quickly validate your pixel setup and get OTTO working as expected. No technical background required — follow along platform by platform and you’ll be back on track in no time.

🧰 Universal Troubleshooting (Apply First)

🔁 Start here before platform-specific checks:

  • Before diving into platform-specific fixes, check these universal issues first:

    • Pixel not firing
      Open your browser’s DevTools → Network tab → reload the page → search for sa-dynamic-optimization.
      If it doesn’t appear, the installation may have failed, or CSP, caching, or CDN could block the script.

    • Duplicate Pixel installations
      Make sure you’re using only one installation method: plugin, GTM, or manual script. Duplicate scripts can prevent detection.

    • Script misplaced
      The script should be placed in <head>—or as early in the page load as possible. If it’s too late (e.g., bottom of <body>), it may not load in time to be detected.

    • OTTO is not enabled in the dashboard
      After installation, navigate to OTTO & Audit → All Sites in your Search Atlas dashboard and ensure the switch is set to “Enable OTTO.” Crawls can take time so that activation might be delayed.

    • Caching or minification plugins interfering
      Plugins like WP Rocket or NitroPack may delay or block the script. Add attributes like no-wp-rocket or nitro-exclude to the script tag.

🖥️ Platform-Specific Troubleshooting

🟩 WordPress (Plugin)

Common Issues:

  • The Search Atlas plugin isn't active, or the code wasn't saved.

  • Conflicts with other SEO plugins that alter <head>.

  • Caching plugins blocking script deployment.

Fixes:

  1. In WP Admin, go to Plugins and ensure Search Atlas SEO is active.

  2. In its settings, check 'Enable OTTO', paste the UUID, and click 'Save'.

  3. Clear your cache (e.g., WP Rocket, NitroPack).

  4. Use DevTools to confirm the script appears in <head>.

  5. Run the Pixel Diagnostic Scan on your Search Atlas dashboard and verify detection.

🟨 Google Tag Manager (GTM)

Common Issues

  • Tag type is incorrect (e.g., Image, iFrame instead of Custom HTML)

  • Trigger only fires on pageviews or specific events, delaying script load

  • GTM container was edited but not published

  • OTTO script is duplicated outside of GTM or in conflicting locations

  • Script loads too late in the page (fails early execution needed for OTTO detection)

Fixes

  1. In GTM, go to Tags > New > Tag Configuration, and choose Custom HTML

  2. Paste the entire OTTO Pixel script into the HTML field

  3. Under Triggering, select Initialization – All Pages to ensure the script loads before other page content

  4. Save, Submit, and Publish the GTM container

  5. Remove any OTTO scripts hardcoded in your site’s theme or elsewhere

  6. Go to your OTTO dashboard in Search Atlas and click Run Diagnostic Scan to confirm the pixel is detected

Note: Using the Initialization trigger ensures that the OTTO Pixel loads as early as possible in the page lifecycle — this is critical for proper detection.

🟦 GoHighLevel (GHL / Ideation)

Common Issues

  • The OTTO script was added to a single page instead of being applied globally

  • The Custom Code section wasn’t marked as a Global Section

  • Changes were made, but not saved or published

  • Script placement was too low in the header, delaying execution

How to Fix It

  1. Copy the full OTTO Pixel script from the Pixel Integration tab in Search Atlas

  2. In GoHighLevel, go to Sites > Pages > Edit Home Page

  3. Add a Custom Code block in the Header area, and paste the script

  4. Make sure to mark the section as Global so the script applies to all pages

  5. Save and publish the changes — confirm in the modal when prompted

  6. Return to your OTTO dashboard and click Run Diagnostic Scan

Note: To ensure proper detection, the OTTO Pixel script should load early — placing it at the top of a global header ensures this. Avoid placing the script in footers or page-specific sections.

🟪 Wix

Common Issues

  • The OTTO Pixel script was only applied to selected pages

  • The script was added in the wrong section (e.g., body or footer instead of head)

  • The script wasn’t set to load on every pageview

  • Site changes weren’t published after editing code settings

How to Fix It (Revised)

  1. In your Wix Editor, go to Settings > Custom Code

  2. Click + Add Code and paste the full OTTO Pixel script

  3. Apply the script to All Pages

  4. Set it to Load Code on Each Page Load

  5. Place the script in the Head section — this ensures early execution and accurate detection

  6. Save your changes and publish the site

  7. Open your OTTO dashboard in Search Atlas and click Run Diagnostic Scan

Note: For proper tracking, the OTTO script must be injected into the Head and applied across all pages, not just the homepage or individual subpages.

🟥 Shopify

Common Issues

  • The OTTO script was placed at the bottom of the <head> or near </head>, delaying or blocking execution

  • The script was pasted in the wrong file or outside the <head> tag

  • The theme.liquid file was not saved or published after editing

  • Conflicting scripts or multiple instances of the OTTO pixel were installed

  • The Shopify cache or browser cache wasn't cleared, preventing detection

How to Fix It

  1. In Shopify Admin, go to Online Store > Themes > Edit Code

  2. Open the theme.liquid file

  3. Locate the <head> tag

  4. Paste the OTTO Pixel script immediately after the opening <head> tag — it must be the first script loaded in the head section

  5. Save and publish your theme

  6. Clear your browser and site cache (or any CDN like Cloudflare if used)

  7. Open the OTTO dashboard in Search Atlas and click Run Diagnostic Scan

Note: Placing the script too low in the <head> or near </head> can prevent proper loading and block the OTTO scanner from detecting the pixel. Always place it at the very top of the <head>.

🟫 Other CMS (Webflow, Squarespace, etc.)

Common Issues (Limited CMS Platforms)

  • The OTTO Pixel script was placed in the <body> or in a section that only loads on specific pages

  • The CMS does not support direct injection into the true <head>

  • The script was applied locally instead of globally

  • Platform-specific limitations delay or block script execution

How to Fix It

  1. Go to your CMS Site Settings > Custom Code or look for a Header Code section

  2. Paste the full OTTO Pixel script in the Head section, and ensure it applies to All Pages

  3. If your CMS doesn’t allow full <head> access (e.g., Blocs, Carrd), place the script immediately after the first <meta> tag — this ensures early loading for pixel detection

  4. Save and publish globally across your site

  5. Clear your browser and platform cache

  6. Open your OTTO dashboard in Search Atlas and click Run Diagnostic Scan

  7. For best results, test in Incognito mode to confirm detection

Note: On restrictive CMS platforms, the key is to load the script as early as possible — as close to <head> as the platform allows.

✅ Final Steps & Diagnostic Scan

  1. Clear all caches.

  2. Open your site in an incognito browser window.

  3. Run the Pixel Diagnostic Scan from the OTTO dashboard—you should see:

    • ✅ Detected via JavaScript

    • ✅ No duplicate instances

    • ✅ Fixes deployed successfully

  4. If it fails, inspect DevTools for presence of:

    • id="sa-dynamic-optimization"

    • Valid data-uuid, src

    • Appropriate cache exclusion flags like no-wp-rocket

🔍 Post‑Installation Pixel Validation & Troubleshooting

❌ Commonly Missed Validation Steps (Now Covered)

1. Use DevTools to Confirm Pixel Load

Open Chrome DevTools → go to the Network tab → reload the page → search for:

csharpCopiarEditarsa-dynamic-optimization

✅ If present → the pixel is loading.
❌ If absent → the script isn’t running (check placement or CMS restrictions).

2. Check Script Location in HTML

Go to the Elements tab → confirm the <script> appears in the:

htmlCopiarEditar<head> <script id="sa-dynamic-optimization" ...>

❌ If it's inside <body> or too far down in <head>, it may load too late.

💡 Pro tip: Always place before closing </head> or high in the <head>.

3. Watch for Minification or Caching Conflicts

If using plugins like WP Rocket, NitroPack, or Cloudflare, they might:

  • Strip <script> attributes

  • Delay script execution

  • Cache old versions

Fix: Add one of the following to the <script> tag:

htmlCopiarEditardata-noptimize data-cfasync="false"

Or exclude from minification via plugin settings.

4. Validate with the OTTO Diagnostic Scan

In your Search Atlas dashboard:

  • Go to OTTO & Audit → All Sites

  • Click “Scan” on the warning banner

  • Wait for:

    • ✅ JavaScript Detected

    • ✅ No duplicate pixel found

    • ✅ Fixes deployed

If any are missing → the installation needs adjustment.

Installing the OTTO Pixel isn’t just about placing a line of code — it’s about unlocking the full power of AI-driven SEO. Whether you're using WordPress, Shopify, Wix, or a custom CMS, each step you take ensures OTTO can scan, optimize, and elevate your site’s visibility.

By following this troubleshooting guide, you’ve covered not just installation but the nuances that often trip up even experienced marketers. And if things still don’t go as planned, you're not alone — our support team is just a message away, ready to help you get every page firing with OTTO precision.

Related Articles
How to install OTTO Pixel
🔎 Where’s My OTTO SEO Pixel?
❓ What Is the OTTO Pixel and Why Do I Need It?
📍 How Do I Install the OTTO Pixel on My Website?
🚫 “Duplicate OTTO Pixel Detected” — how to find it, fix it, and prevent it (all platforms)
Did this answer your question?