🧩 Why the Check and Scanner Can Disagree
The installation check confirms that a pixel string exists somewhere on your page. The diagnostic scanner goes further — it verifies that the pixel is placed in the correct location and will fire reliably on every page load. When you use a custom CMS or GoHighLevel (GHL), certain platform-specific behaviours can satisfy the basic check while still failing the deeper scan.
The three most common root causes are:
- Wrong placement location: The pixel is added to the body or footer instead of the
<head>section. - Widget or embed block used instead of raw code: Some CMS editors and GHL page builders wrap injected code inside a widget container, which delays or blocks the pixel from firing correctly.
- GHL-specific head injection misconfiguration: GHL has a dedicated Head Tracking Code field in funnel and site settings. Pasting the pixel anywhere else — such as a custom HTML element on the canvas — causes the scanner to flag it as incorrectly installed.
🗺️ Where to Find Your OTTO Pixel
Before troubleshooting, retrieve your unique pixel code from Search Atlas:
- Log in to Search Atlas and go to OTTO SEO in the left sidebar, then open SEO Automation (URL:
/seo-automation-v3). - Select the project you are working on.
- Open the OTTO panel and navigate to Pixel Settings.
- Copy the full pixel snippet shown there. Do not modify it.
🛠️ Step-by-Step Resolution — Custom CMS
- Access your theme or template editor. Every custom CMS exposes a way to inject code into the global
<head>tag — look for settings labelled Head Code, Custom Scripts, or Site Header. - Remove any existing OTTO pixel placements from page-level editors, footer sections, or widget blocks before proceeding.
- Paste the pixel snippet directly into the global head injection field. It must sit as raw code — not inside a CMS text block, HTML widget, or shortcode wrapper.
- Save and publish your changes so they go live across all pages.
- Wait 2–3 minutes, then return to OTTO SEO V3 → OTTO → Pixel Settings and run the diagnostic scanner again.
🟡 Step-by-Step Resolution — GoHighLevel (GHL)
- Open your GHL account and navigate to the site or funnel where OTTO should be active.
- For a Funnel: go to the funnel, click Settings (top-right gear icon), and locate the Head Tracking Code field.
- For a Website: go to Sites → Websites, open the site, click Settings, and find the Head Tracking Code field.
- Delete any OTTO pixel code placed elsewhere — including custom HTML elements on the page canvas or footer sections.
- Paste the full OTTO pixel snippet into the Head Tracking Code field only. This is the only GHL location the diagnostic scanner recognises as a valid installation.
- Save the settings and re-publish or re-deploy the funnel or website.
- Return to Search Atlas → OTTO SEO V3 → OTTO → Pixel Settings and run the diagnostic scanner to confirm the result is now passing.
✅ Quick Verification Checklist
- Pixel is placed in the global head section, not page-level or footer.
- No duplicate pixel instances exist across widgets, embeds, or canvas elements.
- The pixel code was pasted as raw HTML — not wrapped in a CMS block or builder element.
- For GHL: the pixel lives exclusively in the Head Tracking Code field in site or funnel settings.
- Changes were saved and published before re-running the scanner.
⚠️ Common Mistakes to Avoid
- Using a custom HTML element on the GHL canvas: This placement passes the basic check but always fails the diagnostic scanner.
- Installing the pixel on a single page only: OTTO requires the pixel to be present site-wide. Always use global head injection.
- Editing the pixel code: Any alteration to the snippet — even adding a space — can cause it to stop firing correctly.
💬 Still Need 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.