🔍 Overview

Two common issues arise when connecting OTTO SEO to a GoHighLevel (GHL) site: the OTTO pixel not being detected after installation, and the site crawl taking an unusually long time (three hours or more). This article walks you through the most effective fixes for both problems.

⚙️ How to Access OTTO SEO

To get started, navigate to OTTO SEO in the left sidebar of your Search Atlas dashboard, then open SEO Automation inside it (URL: /seo-automation-v3). Select the property connected to your GoHighLevel site and proceed from there.

📋 Part 1: OTTO Pixel Not Being Detected

If OTTO reports that the pixel has not been found, the most common causes are an incorrect placement of the pixel code or a caching layer that is serving an outdated version of your page. Follow these steps in order:

1. Copy the pixel code exactly. In the OTTO SEO dashboard, open your connected property and locate the pixel snippet. Copy the entire code block without adding or removing any characters.
2. Paste into the GoHighLevel header. In your GHL account, go to Sites → Your Website → Settings → Custom Code and paste the pixel into the Header section. Do not place it in the footer, as OTTO requires the pixel to load early in the page lifecycle.
3. Save and publish your changes. Click Save and then republish your site inside GoHighLevel. Changes that are saved but not published will not appear on the live page.
4. Clear GoHighLevel's cache. Navigate to Sites → Your Website → Settings and use the Clear Cache option if available in your plan. If your site sits behind Cloudflare or another CDN, purge the cache there as well.
5. Trigger a re-detection in OTTO. Return to the OTTO SEO dashboard, open the property settings, and click Re-check Pixel (or Verify Installation). Allow up to five minutes for the check to complete.
6. Confirm with a live page inspection. Open your GoHighLevel site in a browser, right-click, select View Page Source, and search for your OTTO pixel ID. If the snippet is visible in the source, the pixel is live and OTTO should detect it on the next check.

If the pixel ID appears in the source but OTTO still reports it as undetected, the page may be behind a login wall or a password-protection layer that prevents OTTO's crawler from reading it. Temporarily disable any password protection, run the pixel check, and then re-enable it.

🐢 Part 2: Site Crawl Running for 3+ Hours

A slow or stalled crawl on a GoHighLevel site is usually caused by one of the following: a very large number of pages, JavaScript-heavy rendering, crawl-blocking rules, or server rate limiting. Try the steps below to resolve it:

1. Check your robots.txt file. In a browser, visit yourdomain.com/robots.txt. If you see a Disallow: / rule or a rule blocking all bots, GoHighLevel's default settings may be restricting the crawler. Update your robots.txt inside GHL under Sites → Settings → SEO to allow crawling.
2. Reduce the crawl scope (if available). In the OTTO SEO dashboard, check whether you can limit the crawl to specific folders or page types. Crawling only your most important pages first will return faster results.
3. Disable JavaScript-only page features during the crawl window. OTTO's crawler can time out on pages that rely heavily on client-side JavaScript to load content. Where possible, ensure critical content is available in the raw HTML.
4. Pause and restart the crawl. If the progress bar has not moved for more than 30 minutes, cancel the current crawl from the OTTO SEO dashboard and start a new one. Transient server timeouts are often resolved simply by re-initiating the process.
5. Check GoHighLevel server status. Occasionally GHL experiences platform slowdowns that affect crawl speeds. Visit the GoHighLevel status page to confirm there are no active incidents.
6. Avoid crawling during peak hours. If your site is under heavy traffic, scheduling the crawl for off-peak hours (early morning or overnight) can significantly reduce completion time.

✅ Quick-Reference Checklist

• Pixel pasted into GHL Header section, not footer
• Site saved and published after adding the pixel
• Cache cleared in GHL and any connected CDN
• robots.txt allows crawler access
• Crawl restarted if stalled for more than 30 minutes
• JavaScript-heavy redirects or splash pages temporarily bypassed

💬 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.