Overview
When using GoHighLevel (GHL) as your website platform, two common OTTO issues can appear together: the OTTO pixel script is not detected after installation, and the schema markup feature shows an incomplete or failed deployment status. This article explains what to prepare and check for both issues, and how to get them resolved quickly with our support team.
Where to Find OTTO
In your Search Atlas dashboard, navigate to OTTO SEO using the left sidebar. Your OTTO settings, pixel script, and schema markup controls are all located within this section.
Issue 1: OTTO Pixel Not Detected in GoHighLevel
OTTO verifies that its pixel script is live on your site before activating automations. If the script appears to be installed in GHL but OTTO still shows it as undetected, common causes include:
- Caching layers serving an older version of your page that does not include the script.
- Script optimization or minification tools deferring or excluding the pixel before OTTO can read it.
- The script being placed in a section or block that does not render on all pages sitewide.
Steps to Try for Pixel Detection
- Copy your OTTO pixel script from OTTO SEO in your Search Atlas dashboard.
- In GoHighLevel, ensure the script is placed in a global location that injects into every page — not inside an individual page builder block, as these do not always render sitewide. Consult GoHighLevel's own documentation for the correct global script placement option in your account.
- If you use any caching or script optimization tools alongside GHL, purge all caches and check whether those tools are processing or excluding the OTTO pixel. You may need to configure those tools to leave the pixel script untouched.
- After making changes, return to OTTO SEO in Search Atlas and trigger a re-verification so OTTO re-crawls your site.
- To confirm the script is being output, open your site in a browser, right-click, and choose View Page Source. Search for your OTTO pixel script ID in the raw HTML. If it is absent, the script is not being rendered by GHL and the placement should be reviewed.
Issue 2: Schema Markup Showing Incomplete or Failed Deployment
If your OTTO schema markup feature shows an incomplete or failed deployment status in GoHighLevel, this is typically related to the same root causes as pixel detection — the schema deployment relies on the pixel being correctly detected first, and GHL-specific caching or script handling can interfere with the deployment process.
Steps to Try for Schema Markup Deployment
- Confirm that the OTTO pixel is successfully detected (see Issue 1 above) before troubleshooting schema deployment, as a failed pixel detection will block schema deployment.
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.