Troubleshooting: Pixel on GoHighLevel & Other Builders

🛠️ Fix OTTO Pixel Not Installed on GoDaddy

🔍 Overview If your OTTO pixel shows as not installed after adding it to your GoDaddy website, the most common cause is an incorrect installation method or a misconfigured Google Tag Manager (GTM) setup. This article walks you through the correct process to get your pixel firing properly. ⚙️ Before You Begin Make sure you have the following ready before starting: - Access to your Search Atlas account (navigate to OTTO SEO via the left sidebar, then open SEO Automation, or go to /seo-automation-v3) - Admin access to your GoDaddy website - A published Google Tag Manager container connected to your GoDaddy site - Your OTTO pixel code snippet, copied directly from the OTTO dashboard 📋 Step 1 — Copy Your OTTO Pixel Code 1. Log in to Search Atlas and go to OTTO SEO in the left sidebar, then open SEO Automation. 2. Open the OTTO dashboard for the website you are setting up. 3. Locate the pixel installation section and copy the full pixel code snippet. Do not modify the code. 🏷️ Step 2 — Add the Pixel via Google Tag Manager Using GTM is the recommended method for installing the OTTO pixel on GoDaddy websites, as GoDaddy's native editor has limited support for custom scripts. 1. Log in to Google Tag Manager and select the container linked to your GoDaddy site. 2. Click Tags in the left menu, then click New. 3. Click Tag Configuration and choose Custom HTML as the tag type. 4. Paste your OTTO pixel code into the HTML field. Ensure the full snippet is included — do not wrap it in any additional tags. 5. Click Triggering and select All Pages so the pixel fires on every page load. 6. Name your tag (for example, OTTO Pixel) and click Save. 7. Click Submit in the top-right corner of GTM, add a version name, and click Publish. 🌐 Step 3 — Confirm GTM Is Active on Your GoDaddy Site The OTTO pixel will only fire if GTM itself is correctly installed on your GoDaddy site. Follow these steps to verify: 1. Log in to your GoDaddy account and open your website builder or WordPress admin panel. 2. Confirm your GTM container snippet (both the and portions) is present in your site's code. In GoDaddy Managed WordPress, use a plugin such as GTM4WP to insert both snippets correctly. 3. Visit your live website and use the Google Tag Assistant browser extension or GTM's built-in Preview mode to confirm the GTM container is loading on every page. ✅ Step 4 — Verify the OTTO Pixel Is Detected 1. Return to the OTTO dashboard in Search Atlas (OTTO SEO in the left sidebar → SEO Automation → your website). 2. Click the Check Installation or Verify Pixel button. 3. Allow up to 5 minutes after publishing your GTM container before checking, as propagation can take a short time. 4. If the pixel status changes to Installed, your setup is complete. ⚠️ Common Reasons the Pixel Shows as Not Installed - GTM container not published: Saving a tag in GTM is not enough — you must also click Submit and Publish to push changes live. - Incomplete GTM snippet on GoDaddy: Both the and GTM code snippets must be present. Missing the body snippet is a frequent cause of failures. - Wrong trigger set: If the trigger is not set to All Pages, the pixel may not fire on the page OTTO checks. - Modified pixel code: Any changes to the original OTTO pixel snippet can break detection. Always paste the code exactly as provided. - Caching: GoDaddy or a caching plugin may serve a cached version of your site. Clear all caches after publishing your GTM container. - Ad blocker or browser extension interference: Test verification in an incognito window with extensions disabled. 💡 Tips for GoDaddy Managed WordPress If your GoDaddy site runs on Managed WordPress, the easiest way to install GTM (and therefore the OTTO pixel) is to use the GTM4WP plugin. Once installed and configured with your GTM container ID, the plugin automatically places both required snippets in the correct positions — no manual code editing needed. 🆘 Still Need Help? If you have followed all the steps above and the OTTO pixel still shows as not installed, 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.

🛠️ Fix OTTO Pixel Detection Issues on GHL

🔍 Overview If you have installed the OTTO pixel on your GoHighLevel (GHL) website but the Search Atlas dashboard still shows it as not installed correctly, you are not alone. This is a known detection issue specific to how GHL renders pages, and it does not necessarily mean your pixel is missing. This article walks you through the steps to confirm your installation and resolve the detection flag so OTTO can deploy fixes on your site. ⚙️ Why This Happens on GHL GoHighLevel uses a custom page-rendering engine that can delay or alter how external scripts are loaded. OTTO's pixel verification system scans the page for the script at a specific moment during load. On GHL sites, the pixel may load slightly out of sync with that scan window, causing a false not installed status even when the code is present and firing correctly. ✅ Step 1 — Confirm the Pixel Is Present on Your Site 1. Open your GHL website in a browser and navigate to any published page. 2. Right-click anywhere on the page and select Inspect (or press F12) to open Developer Tools. 3. Go to the Elements tab and use Ctrl+F (Windows) or Cmd+F (Mac) to search for ottoseo or your unique pixel ID. 4. If the script tag appears in the HTML, your pixel is installed. Proceed to Step 2. 5. If the script tag does not appear, re-install the pixel by following the instructions in the OTTO onboarding flow under Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 🔧 Step 2 — Re-Install the Pixel in GHL Correctly To ensure the pixel loads as early as possible and is not blocked by GHL's rendering engine, follow these placement guidelines: - In your GHL account, go to Sites → Your Website → Settings → Header Tracking Code. - Paste the OTTO pixel script inside the section, not the footer. Head placement gives the script the best chance of firing before OTTO's verification scan runs. - Make sure the script is not wrapped in any conditional logic or tag manager delay rules that could postpone its execution. - Save your changes and publish the site. 🔄 Step 3 — Re-Trigger Pixel Verification in Search Atlas 1. Log in to Search Atlas and navigate to Left sidebar → OTTO SEO → All Sites (SEO Automation). 2. Locate your connected GHL website in the OTTO dashboard. 3. Click Verify Pixel or the re-check option next to the installation status indicator. 4. Wait up to 60 seconds for the scan to complete. 5. If the status updates to Installed, you are ready to deploy OTTO fixes. 💡 Step 4 — If the Status Still Shows Not Installed Some GHL configurations cache pages aggressively. Try the following before escalating: - Clear the GHL page cache from your site settings and republish all pages. - Test on a page that has been freshly published within the last 10 minutes to rule out stale cache. - Temporarily disable any third-party scripts or apps in GHL that might be blocking external JavaScript from loading. - Try verifying from a different browser or in an incognito window to rule out local caching on your end. 🚫 Common Mistakes to Avoid - Placing the pixel in the footer: Footer scripts load last and are most likely to be missed by the verification scan. - Using a tag manager with delays: Tag managers that fire scripts after a timer or scroll event will cause verification failures. - Installing the pixel on only one page: The OTTO pixel should be installed globally across all pages of your GHL site, not on a single landing page. - Duplicate pixel snippets: More than one instance of the pixel on the same page can cause conflicts. Ensure it appears only once in your header code. 📊 Confirming OTTO Is Active After Verification Once the pixel is verified, return to Left sidebar → OTTO SEO → All Sites (SEO Automation) and check that your site's OTTO status shows as Active. You should now be able to review and deploy recommended SEO fixes without any blocking warnings. If fixes still appear locked, try refreshing the page or logging out and back in to force the dashboard to update your site's verification state. 🆘 Still Need Help? If you have followed every step above and the pixel still shows as not installed, our team can review your specific GHL configuration directly. 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.

⚡ OTTO Pixel on GoHighLevel: Installation & Crawl Troubleshooting

🧭 Overview After installing the OTTO pixel on your GoHighLevel (GHL) site, you may see a message indicating the pixel has not been detected. In many cases, this is related to a slow or in-progress site crawl rather than a pixel installation error. If you are experiencing this issue, the steps below can help you identify what to check and when to reach out for support. ⚠️ Pixel Not Detected After Installation If the OTTO pixel is not being detected after you have installed it on your GoHighLevel site, this may be related to a slow crawl running in the background. You do not necessarily need to reinstall the pixel if you have already added it correctly. - A slow or stalled crawl may delay pixel detection confirmation. - If the crawl appears to be taking an unusually long time with no progress, this may require escalation to the support team. - Do not reinstall the pixel multiple times while waiting — this will not speed up detection. 📋 General Pixel Installation on GoHighLevel If you need to verify or redo your pixel installation on GoHighLevel, follow these general steps: 1. Locate your OTTO pixel snippet within the Search Atlas platform. 2. Log in to your GoHighLevel account and open the relevant sub-account. 3. Navigate to your site's settings and find the area where you can add tracking or header scripts. 4. Paste your OTTO pixel snippet into the appropriate field. 5. Save your changes and publish or re-publish your site so the updated code goes live. ✅ Before Escalating Before reaching out to support, confirm the following: - Pixel is installed: The OTTO pixel snippet has been added to your GoHighLevel site's script or tracking code area. - Site is published: You have saved and re-published your GoHighLevel site after adding the pixel. - Sufficient time has passed: You have waited a reasonable amount of time after installation before expecting pixel detection to update. - Crawl status: Check whether a crawl is still running or appears stalled — a slow crawl may be the cause of the delay. 🚨 When to Escalate If your pixel remains undetected after confirming the above steps, or if your crawl appears stuck with no progress for an extended period, please contact support. When escalating, have the following ready: your project or site name, the domain where the pixel is installed, and any error messages or status indicators you are seeing. 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.

🔧 Fix OTTO Pixel Installation Issues on Drupal

Overview If OTTO is not recognizing your pixel after installing it on a Drupal site, you are not alone. Drupal's caching layers, module conflicts, and theme structure can all interfere with pixel detection. This guide walks you through the most common areas to check when troubleshooting a pixel that is not being recognized. Before You Begin Make sure you have the following ready before troubleshooting: - Admin access to your Drupal site - Your OTTO pixel code, available inside your Search Atlas account - Access to your Drupal theme files or a module capable of injecting code into the page head Step 1 — Confirm Your Pixel Code Is Correct Start by verifying you are using the right pixel code for your site. 1. Log in to Search Atlas and locate your OTTO pixel snippet. It should be the complete script tag assigned to your specific site. 2. Copy the code fresh — do not rely on a previously saved copy that may be outdated. Step 2 — Place the Pixel Directly in the HTML Head A reliable method on Drupal is injecting the pixel code directly into the <head> section of your base theme, bypassing any third-party tag manager. 1. In your Drupal admin panel, navigate to your active theme's template files. 2. Open the base HTML template file for your theme. 3. Paste your OTTO pixel code immediately after the opening <head> tag. 4. Save the file. Important: If you previously installed the pixel through Google Tag Manager (GTM), consider removing it from GTM and placing it directly in the template instead. GTM loads asynchronously and may be affected by certain Drupal performance modules, which can cause detection failures. Step 3 — Clear All Drupal Caches Drupal aggressively caches page output, so changes to templates may not appear until caches are fully cleared. 1. Navigate to your Drupal admin panel and clear all site caches using the available cache-clearing option in your configuration settings. 2. If your hosting environment supports command-line tools, a full cache rebuild from the command line can ensure all layers are cleared. 3. If your site uses a CDN, purge the CDN cache as well to ensure visitors receive the updated page. Step 4 — Verify the Pixel Is Live on the Page After clearing caches, confirm the pixel is actually rendering in the browser. 1. Open your website in a browser and navigate to any page. 2. Right-click and select View Page Source. 3. Use Ctrl+F (or Cmd+F on Mac) to search for a unique string from your pixel code. 4. If the code appears in the source, the pixel is present on the page and OTTO should be able to detect it. If it does not appear, revisit Steps 1–3 above. 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.

🛠️ Fix OTTO Pixel Not Engaging on GoDaddy

🔍 Overview If you have installed the OTTO pixel on a GoDaddy website builder site but the dashboard still shows the pixel as not engaged, you are not alone. GoDaddy's template-based website builder applies extra layers of code management that can block or delay pixel activation. This article walks you through the most effective fixes so OTTO can start optimizing your site. ⚙️ Why This Happens on GoDaddy Templates GoDaddy's proprietary website builder (distinct from WordPress on GoDaddy hosting) restricts how custom scripts are loaded. Common reasons the OTTO pixel fails to engage include: - Script placement limitations: GoDaddy templates do not always support placing scripts in the <head> tag directly, causing the pixel to fire too late or not at all. - Caching layers: GoDaddy applies aggressive server-side and CDN caching that can serve stale pages without the pixel present. - Content Security Policy (CSP) restrictions: Some GoDaddy templates block third-party scripts by default. - Single-page template rendering: Certain GoDaddy themes render content dynamically, which prevents standard pixel triggers from firing correctly. ✅ Step-by-Step Troubleshooting 1. Verify the pixel code is copied correctly. Go to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3), open your OTTO project, and copy the full pixel snippet. Paste it into a plain-text editor and confirm there are no truncated characters or extra spaces. 2. Place the pixel in the correct location in GoDaddy. Log in to your GoDaddy account, open your website editor, navigate to Settings → Website Settings → Header Code (or equivalent in your template), and paste the full OTTO pixel snippet there. Avoid placing it only in the body or footer section. 3. Clear all GoDaddy caches. In your GoDaddy dashboard, locate the Cache or Performance settings and purge the cache entirely. Wait 5–10 minutes before rechecking pixel status in Search Atlas. 4. Disable any active CDN temporarily. If you have Cloudflare or GoDaddy's built-in CDN enabled, temporarily pause it to test whether the pixel engages. This helps identify whether caching is the root cause. 5. Check for Content Security Policy blocks. Using your browser's developer tools (press F12), open the Console tab and reload your website. Look for any errors mentioning refused to load script or Content Security Policy. If present, you will need to whitelist the OTTO script domain inside GoDaddy's CSP settings or contact GoDaddy support to adjust the policy. 6. Test in an incognito window. Open your website in a private/incognito browser tab to bypass local browser cache and confirm the pixel script is present in the page source (right-click → View Page Source and search for the OTTO pixel code). 7. Re-check pixel status in Search Atlas. Return to Left sidebar → OTTO SEO → SEO Automation (/seo-automation-v3), reload your OTTO project dashboard, and check whether the pixel status has updated to Engaged. Pixel status can take up to 15 minutes to refresh after a successful detection. 💡 Alternative: Use Google Tag Manager on GoDaddy If direct pixel installation continues to fail, deploying OTTO through Google Tag Manager (GTM) is a reliable workaround for GoDaddy template limitations: - Install the GTM container snippet into GoDaddy's Header Code section. - Inside GTM, create a new Custom HTML tag and paste the full OTTO pixel snippet. - Set the trigger to All Pages and publish the GTM container. - Return to Search Atlas and verify pixel engagement status after 10–15 minutes. GTM bypasses many of the script restrictions imposed by GoDaddy templates and is the recommended method for complex template environments. 🚫 Common Mistakes to Avoid - Do not paste the pixel snippet multiple times — duplicate instances can cause conflicts and prevent engagement. - Do not use GoDaddy's drag-and-drop HTML block widget as your only installation method, as these blocks are often excluded from the rendered <head> section. - Do not check pixel status immediately after installation — always allow at least 10–15 minutes and clear cache first. 🆘 Still Not Resolved? If you have completed all the steps above and the OTTO pixel still shows as not engaged, our team can investigate your specific GoDaddy template configuration. 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.

🔧 Fix OTTO Pixel Not Recognized on Drupal

🧭 Overview After installing the OTTO pixel on a Drupal site, Search Atlas may still show the code as unrecognized. Standard cache clearing alone is often not enough — Drupal requires a full cache flush to propagate header changes. This article walks you through every troubleshooting step to get your OTTO pixel recognized quickly. ✅ Before You Begin Confirm the following before troubleshooting: - You have admin access to your Drupal site and the Search Atlas platform. - Your OTTO pixel code has been copied exactly from Search Atlas — no extra spaces or characters. - You are editing the correct site in Search Atlas: navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar (URL: /seo-automation-v3) and confirm the domain shown matches your Drupal site. 📋 Step 1: Verify the Pixel Is in the Correct Location The OTTO pixel must be placed inside the tag of every page on your site, not in the body or footer. In Drupal, the recommended way to do this is through your active theme's html.html.twig file or a dedicated header block, depending on your theme setup. - Open your Drupal admin panel and go to Appearance → your active theme → Edit. - Locate the html.html.twig template (or equivalent header template). - Confirm the OTTO pixel code snippet appears immediately after the opening tag. - Save your changes. If you are using a module such as Head JS, Google Tag Manager, or a custom block to inject header scripts, ensure the OTTO pixel is placed directly in the template file, not inside GTM or any asynchronous script loader, as these can delay or block pixel recognition. 🚫 Step 2: Remove Any Conflicting GTM or Script Loader Code Google Tag Manager and similar tools load scripts asynchronously after the page has already started rendering. This can prevent Search Atlas from detecting the OTTO pixel reliably. - If you previously inserted the OTTO pixel inside a GTM container, remove it from GTM entirely. - Add the pixel code directly to your theme template as described in Step 1. - Double-check that no other plugin or module is moving or deferring scripts in the tag. 🗑️ Step 3: Flush All Drupal Caches (Critical Step) This is the most common reason the OTTO pixel remains unrecognized after installation. Drupal caches rendered HTML, Twig templates, and asset aggregations aggressively. A standard cache clear may not rebuild all layers. You must perform a full cache flush. Method A — Drupal Admin UI (Recommended): 1. Log in to your Drupal admin panel. 2. Go to Configuration → Development → Performance. 3. Click Clear all caches. 4. Wait for the confirmation message before proceeding. Method B — Drush Command Line (More Thorough): 1. Connect to your server via SSH. 2. Navigate to your Drupal root directory. 3. Run the command: drush cr (cache rebuild). This rebuilds all Drupal caches, including Twig compiled templates. 4. If you use a CDN or reverse proxy (such as Cloudflare, Varnish, or Nginx caching), purge the cache at that layer as well. Method C — Hosting-Level Cache: - If your hosting provider (e.g., Pantheon, Acquia, WP Engine for Drupal) has its own caching layer, log in to your hosting dashboard and purge or flush the site cache separately. This step is required even after running Drush. 🔍 Step 4: Verify the Pixel Is Live on Your Site After flushing all caches, confirm the pixel is visible in your page source before asking Search Atlas to re-verify: 1. Open your website in a browser. 2. Right-click anywhere on the page and select View Page Source. 3. Use Ctrl+F (or Cmd+F on Mac) to search for otto or the beginning of your pixel code snippet. 4. Confirm the code appears inside the section of the source. If the code does not appear in the page source, the template change was not saved correctly or a caching layer is still serving an old version of the page. Repeat Steps 1 and 3. 🔄 Step 5: Re-Verify in Search Atlas 1. In Search Atlas, go to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Locate your connected site and open its OTTO settings. 3. Click the Verify or Check Pixel button to trigger a fresh detection scan. 4. Allow up to two minutes for the verification to complete. If verification still fails after completing all steps above, your site may have a Content Security Policy (CSP) header blocking external scripts, or a module may be stripping unrecognized code from the tag. Check your Drupal security modules (such as Security Kit) for script restrictions. ⚠️ Common Mistakes to Avoid - Clearing cache without flushing: Drupal's "Clear cache" button does not always rebuild Twig templates. Always use Drush cr or the Performance page flush for header changes. - Inserting the pixel via GTM: GTM-loaded scripts are not reliably detected. Place the pixel directly in your theme template. - Forgetting CDN or proxy cache: Changes to your HTML will not be visible until the CDN cache is also purged. - Editing the wrong theme: Drupal may have a base theme and a sub-theme. Confirm you are editing the active sub-theme template. 💬 Need More 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.

🔌 Fix OTTO Pixel Not Engaged on GoDaddy

🧭 Overview If you have installed the OTTO pixel on a GoDaddy website builder template and the platform still shows the pixel as not engaged, standard WordPress troubleshooting steps will not apply to your setup. GoDaddy's website builder is a standalone drag-and-drop platform — it does not use plugins, theme files, or a WordPress dashboard. This article walks you through the correct fix for GoDaddy-hosted sites. ⚠️ Before You Begin Confirm the following before proceeding: - You are using GoDaddy Website Builder (also called GoDaddy Websites + Marketing), not a WordPress site hosted on GoDaddy. - You have already installed the OTTO pixel code in your GoDaddy site's header or footer settings. - The OTTO dashboard at OTTO SEO → All Sites (SEO Automation) (left sidebar → OTTO SEO → All Sites (SEO Automation)) still shows the pixel status as Not Engaged after several minutes. If you are using WordPress — even if it is hosted on GoDaddy — please refer to the standard OTTO pixel troubleshooting article instead. 🔍 Why This Happens on GoDaddy Templates GoDaddy's website builder handles custom code snippets differently from WordPress. When pixel code is pasted into the header or footer section, the builder can occasionally save a malformed or incomplete version of the script. This means the pixel fires incorrectly or not at all, even though it appears to be installed. The most reliable fix is to fully remove the existing pixel code and re-add it as a clean paste. 🛠️ Step-by-Step Fix: Delete and Re-Add the Pixel 1. Copy your OTTO pixel code. In Search Atlas, navigate to the left sidebar and select OTTO SEO → All Sites (SEO Automation). Locate your OTTO pixel code and copy the full script to your clipboard. Do not modify it. 2. Log in to GoDaddy. Go to godaddy.com, sign in, and open your Website Builder editor for the relevant site. 3. Open Website Settings. In the GoDaddy editor, click Settings (usually found in the left panel or top navigation), then select Website or SEO / Tracking depending on your GoDaddy plan version. 4. Find the existing pixel code. Look for a Header Code, Footer Code, or Custom Code field. You should see the OTTO pixel script already pasted there. 5. Delete the existing pixel code entirely. Select all text in the code field and delete it. Make sure the field is completely empty — do not leave any partial script tags or whitespace. 6. Save the empty field. Click Save or Apply to confirm the removal. This step is important; skipping it can cause the old code to persist. 7. Paste the pixel code fresh. Click back into the same code field and paste your OTTO pixel code directly from your clipboard. Do not retype it manually. 8. Save again. Click Save or Apply to store the new code. 9. Publish your site. In the GoDaddy editor, click Publish to push the changes live. The pixel will not be detectable until the site is published. 10. Verify in Search Atlas. Return to OTTO SEO → All Sites (SEO Automation) in Search Atlas and wait up to 5 minutes for the pixel status to refresh. It should now display as Engaged. ✅ Confirming the Pixel Is Active Once the steps above are complete, you can do a quick browser check to confirm the pixel is firing: - Visit your published GoDaddy site in a browser. - Right-click the page and select View Page Source. - Use Ctrl+F (or Cmd+F on Mac) to search for otto or the beginning of your pixel script. - If the script appears in the source, the pixel is correctly embedded and should register as engaged in Search Atlas within a few minutes. 🚫 Common Mistakes to Avoid - Not publishing after saving. GoDaddy saves changes to a draft state. The pixel is only live — and detectable — after you click Publish. - Pasting into the wrong field. Some GoDaddy plans show multiple code fields. Always paste into the global header or footer field, not a field tied to a single page, unless OTTO specifically requires per-page placement. - Editing rather than replacing. Modifying the existing code instead of deleting and re-pasting it can preserve hidden formatting errors. Always start with a clean, empty field. - Using WordPress troubleshooting steps. Plugin-based fixes, functions.php edits, and theme file changes do not apply to GoDaddy Website Builder and will not resolve this issue. 💬 Still Not Engaged After These Steps? If the pixel still shows as not engaged after completing all steps above, there may be a caching or account-level issue that requires a closer look. 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.

🛠️ Fix OTTO Pixel React Hydration Errors in Next.js

🔍 Overview The OTTO Pixel is a client-side script injection method that works well for traditional server-rendered or static sites. However, in Next.js and other React-based frameworks, the Pixel can cause React hydration errors and trigger repeated client-side API calls. This happens because the Pixel modifies the DOM after the initial server render, creating a mismatch between server-rendered HTML and what React expects on the client. The recommended solution for Next.js sites is to use the OTTO API integration, which fetches SEO data server-side before the page is rendered, completely avoiding DOM conflicts. ⚠️ Why the OTTO Pixel Causes Issues in Next.js React hydration works by attaching event listeners and state to a DOM that must exactly match what the server produced. When the OTTO Pixel injects meta tags or structured data into the DOM after hydration begins, React detects a mismatch and throws errors such as: - Hydration failed because the initial UI does not match what was rendered on the server - Repeated or duplicate API calls firing on every client-side navigation - SEO tags flickering or appearing inconsistently in page source Switching to the OTTO API integration resolves all of these issues by moving data-fetching to the server, so the HTML React receives on the client is already complete. 🚀 How the OTTO API Integration Works Instead of injecting a script tag into your page, the OTTO API integration lets your Next.js app call the OTTO API directly during server-side rendering (SSR) or static site generation (SSG). The API returns the SEO metadata for each page, which you render into your <head> before the HTML is sent to the browser. React then hydrates a page that is already complete — no DOM conflicts, no duplicate calls. ⚙️ Step-by-Step: Implementing the OTTO API Integration in Next.js 1. Remove the OTTO Pixel script tag from your _app.js, _document.js, or any layout component where it is currently injected. Removing it first prevents any conflicts during the migration. 2. Locate your OTTO UUID by navigating to Left sidebar → OTTO SEO → Installation Guide in the Search Atlas platform. Your UUID is displayed on that page and is required for all API requests. 3. Fetch SEO data server-side inside getServerSideProps (for SSR) or getStaticProps (for SSG) in each page file. Make a request to the OTTO API endpoint, passing your UUID and the current page path as parameters. The API response will contain the meta title, meta description, canonical URL, structured data, and any other SEO fields OTTO manages for that page. 4. Pass the API response as props to your page component. Keep the data shape flat and serialisable so Next.js can pass it through props without issues. 5. Render the SEO data into your <head> using Next.js's built-in next/head component (or your preferred head-management library). Because this happens on the server, the rendered HTML will already contain the correct meta tags before React hydrates. 6. Verify the integration by viewing the page source (not the browser inspector) and confirming the OTTO-managed meta tags appear in the raw HTML. Also check your browser console for any remaining hydration warnings. 7. Re-scan your site in Search Atlas by navigating to Left sidebar → OTTO SEO → Site Audit → Overview (Website Overview) and clicking Recrawl Site. This confirms OTTO can read the tags from your live pages and that the installation status updates correctly. 💡 Tips for a Smooth Migration - Handle API errors gracefully. Wrap your OTTO API call in a try/catch block and fall back to default meta values if the request fails, so a temporary API issue never breaks your pages. - Cache responses for SSG pages. If you use getStaticProps with revalidate, the OTTO API is only called during build or revalidation — not on every visitor request — which keeps performance fast. - Use a shared fetch utility. Create a single helper function (e.g., fetchOttoSeo(uuid, path)) that all your page files import. This avoids duplicating fetch logic and makes future updates easier. - Do not include the Pixel and the API integration at the same time. Running both simultaneously will cause duplicate tags and may trigger the same hydration conflicts you are trying to fix. - Dynamic routes (e.g., /blog/[slug]) should pass the resolved path string to the API — not the Next.js route pattern — so OTTO can match it to the correct page record. ✅ Confirming the Fix After completing the integration, confirm the following: - No hydration errors appear in the browser console on first load or client-side navigation. - Meta tags are visible in the raw page source before JavaScript executes. - The OTTO installation status in Left sidebar → OTTO SEO → Site Audit → Overview (Website Overview) shows as active and scanning correctly. - Network requests show a single server-side call to the OTTO API per page render — not repeated client-side calls. 💬 Need More 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.

🛠️ Fix OTTO Pixel Detection and GHL Integration Pricing

🔍 Overview Two common questions arise when managing your OTTO SEO setup: why the OTTO pixel shows as not installed even after a successful installation, and how pricing differs between a GoHighLevel (GHL) integration and a direct Search Atlas plan. This article walks you through both topics step by step. ⚙️ Why the OTTO Pixel Shows 'Not Installed' After placing the OTTO pixel on your website, the platform may still display a not installed status. This is almost always caused by one of the following reasons: - The pixel code was added to only some pages rather than site-wide (e.g., in a footer or header that does not load on every page). - A caching layer — from your hosting provider, CDN, or a caching plugin — is serving an older version of the page that does not yet include the pixel. - The pixel was placed inside a conditional block or tag manager rule that prevents it from firing on every visit. - The verification check was run immediately after installation before the platform had time to detect it. 🛠️ How to Reinstall or Verify the OTTO Pixel 1. In the left sidebar, navigate to OTTO SEO and open SEO Automation (URL: /seo-automation-v3). 2. Locate your website and open its OTTO SEO dashboard. 3. Find the Pixel Installation section and click Get Pixel Code to copy the latest snippet. 4. Paste the snippet inside the tag of your website's global template so it loads on every page — not just the homepage. 5. If you use a caching plugin (e.g., WP Rocket, W3 Total Cache) or a CDN (e.g., Cloudflare), purge all caches immediately after saving the change. 6. Return to the OTTO SEO dashboard and click Verify Installation. Wait up to five minutes for the status to update. 7. If the status still shows not installed after five minutes, open an incognito browser window, visit your website, then re-run the verification check. If you manage the site through a page builder (e.g., Elementor, Divi) or a third-party tag manager, make sure the pixel fires on all pages and is not limited to a specific trigger or audience rule. 💡 Common Installation Platforms — Quick Tips - WordPress: Use a header/footer plugin or paste the snippet directly into your theme's header.php file inside the section. - Shopify: Add the pixel under Online Store → Themes → Edit Code → theme.liquid inside the tag. - GoHighLevel (GHL) Sites: Go to your site settings in GHL, open the Tracking Code or Header Scripts field, and paste the pixel there. - Webflow / Wix / Squarespace: Use each platform's built-in custom code or header injection settings to add the snippet globally. 📊 GHL Integration Pricing vs. Direct Search Atlas Plan Search Atlas offers two ways to access the platform, and the pricing structure differs between them. - Direct Search Atlas Plan: You subscribe and pay Search Atlas directly. You have access to all plan features at the standard published rate and manage billing entirely within your Search Atlas account. - GHL (GoHighLevel) Integration: Access is provisioned through your GHL account or sub-account. Pricing for this integration is set at the GHL agency or marketplace level and may differ from the direct plan rates. Your Search Atlas subscription is tied to the GHL connection. Because GHL integration pricing is managed at the agency or reseller level, the exact rate depends on your specific GHL setup. For a precise quote or to compare costs for your account, please reach out via the chat widget so our team can review your configuration directly. 🔄 Will My Account Need to Be Disconnected or Reconnected? In most cases, switching between a GHL integration and a direct plan does not require disconnecting and reconnecting your account. However, there are scenarios where a reconnection step is needed: - If you are moving from a GHL sub-account to a standalone Search Atlas account (or vice versa), your billing source will change and a reconnection may be required. - If your GHL integration was set up under a different email or organisation than your direct plan, accounts may need to be merged or migrated by the support team. Before making any changes to your plan or integration, contact our team first so we can confirm the safest path and prevent any interruption to your OTTO SEO data or pixel tracking. 🚀 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.

🔌 Fix OTTO Pixel Installation on GoHighLevel

🧭 Overview If you have added the SearchAtlas OTTO tracking pixel to your GoHighLevel (GHL) site but the Search Atlas dashboard still shows the pixel as undetected — or you are seeing a JSON parsing error — the issue is almost always caused by how GHL handles custom code blocks. This article walks you through the correct installation method and the most common failure points. 📋 Before You Begin Confirm the following before troubleshooting: - You have access to your GoHighLevel funnel or website builder as an admin. - You have your OTTO pixel snippet ready. To find it, go to OTTO SEO in the left sidebar, open SEO Automation (URL: /seo-automation-v3), open your OTTO workspace, and copy the pixel script from the tracking setup panel. - The site is published and publicly accessible — the dashboard cannot detect the pixel on unpublished pages. ⚠️ Why GHL Installations Commonly Fail GoHighLevel uses a block-based editor that processes custom code differently from standard HTML page builders. Three failure points account for almost all detection problems: - Wrong placement location: Pasting the script into a content block body instead of the dedicated Header Tracking Code field causes the script to be wrapped in additional markup, which breaks JSON parsing. - JSON parsing error: GHL sometimes auto-encodes quotation marks inside custom code blocks. When the pixel script contains JSON-formatted configuration data, these encoded characters corrupt the payload and produce a JSON parsing error in the browser console. - Script added to a single page only: Adding the script to one page's settings instead of the site-wide header means the pixel fires inconsistently, causing intermittent or zero detection in the dashboard. ✅ Correct Installation Method Follow these steps exactly to install the OTTO pixel site-wide in GoHighLevel: 1. Log in to GoHighLevel and open the Sites section from the left menu. 2. Select the website or funnel where you want to install the pixel. 3. Click Settings (the gear icon) for that site — do not open an individual page editor. 4. Scroll down to the Header Tracking Code field. This is the only field that injects code cleanly into the <head> tag without encoding characters. 5. Paste your OTTO pixel snippet directly into the Header Tracking Code field. Do not wrap it in any additional tags. 6. Click Save and then Republish the site. 7. Wait 2–3 minutes, then return to OTTO SEO in the left sidebar in Search Atlas, open SEO Automation, and refresh the OTTO workspace to check detection status. 🚫 What to Avoid - Do not paste the pixel script into a custom HTML or code content block inside the page editor. GHL re-encodes quotes in these blocks and will break the script. - Do not use the Footer Tracking Code field for the OTTO pixel. Some GHL themes render the footer after the main content loads, which can cause the pixel to fire too late or not at all on fast-loading pages. - Do not add the script only to individual page settings. Always use the site-level Header Tracking Code field for consistent, site-wide detection. 🔍 Verifying the Pixel Is Firing Correctly After republishing, verify the installation using your browser before checking the Search Atlas dashboard: 1. Open your published GHL site in Google Chrome. 2. Right-click anywhere on the page and select Inspect, then open the Network tab. 3. Reload the page and filter requests by typing otto or your pixel domain in the search bar. 4. Confirm a network request is being made and that the response status is 200. 5. Open the Console tab and check that there are no JSON parsing errors. If a JSON error still appears, the script was most likely pasted into a content block rather than the Header Tracking Code field — repeat the installation steps above. 🛠️ Still Seeing a JSON Parsing Error? If you followed the steps above and the JSON parsing error persists, check these additional causes: - Conflicting scripts: A third-party script on the same page may be interfering. Temporarily disable other custom scripts in the Header Tracking Code field to isolate the conflict. - Caching: GoHighLevel caches published pages aggressively. Clear the site cache from the GHL Settings panel and hard-reload the page in your browser (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac). - Pixel snippet modified: Ensure the pixel snippet is copied exactly as provided in the Search Atlas dashboard. Any manual edits — including added line breaks or extra spaces — can invalidate the JSON structure. 💬 Need More 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.

🛠️ Fix OTTO Pixel Mobile Navigation Issues in GoHighLevel

🔍 Overview When the OTTO Pixel script is installed on a GoHighLevel (GHL) website, some customers notice that the mobile navigation bar disappears or stops working on the homepage. This happens because GoHighLevel's script loader can execute the OTTO Pixel asynchronously in a way that interferes with the page's navigation rendering. The fix is straightforward: adding the data-cfasync attribute to the OTTO Pixel script tag tells the page to handle the script correctly and prevents it from blocking or disrupting mobile navigation elements. ⚙️ Why This Happens GoHighLevel uses Cloudflare Rocket Loader to optimise page performance. Rocket Loader defers JavaScript execution to speed up load times. However, when it processes the OTTO Pixel script without proper instructions, it can interfere with scripts that control navigation menus — particularly on mobile viewports. Adding data-cfasync="false" to the OTTO Pixel script tag tells Cloudflare's Rocket Loader to skip deferring that specific script. This ensures the pixel fires correctly without disrupting other page elements like the navigation bar. 🚀 How to Fix the Issue 1. Log in to your GoHighLevel account and open the website or funnel where the OTTO Pixel is installed. 2. Navigate to the page settings or the custom code/header script section where your OTTO Pixel script tag is currently placed. 3. Locate the existing OTTO Pixel tag. It will look similar to this: ​ Before (original script tag): After (corrected script tag): 1. Add data-cfasync="false" as an attribute directly inside the opening tag, before the src attribute. 2. Save your changes and publish the page. 3. Open the page on a mobile device or use your browser's mobile preview mode to confirm the navigation bar is displaying and functioning correctly. ✅ Where Exactly to Place the Attribute The data-cfasync="false" attribute must be placed inside the opening script tag of the OTTO Pixel — not in a separate tag, not above or below it. See the correct placement below: If your OTTO Pixel script is an inline script (with the JavaScript code written directly between the tags rather than loaded from a URL), place the attribute the same way in the opening tag: 📊 Verify Your OTTO Pixel Is Still Active After making this change, confirm that the OTTO Pixel is still tracking correctly: - Go to Search Atlas and navigate to OTTO SEO in the left sidebar, then open SEO Automation inside it (or visit /seo-automation-v3). - Open the OTTO SEO dashboard for your connected website. - Check that the pixel status shows as Active or Connected. - If the status does not update within a few minutes, hard-refresh the page and check again. 💡 Tips to Avoid This Issue - Always add data-cfasync="false" to the OTTO Pixel tag at the time of installation on any GoHighLevel site. - If you manage multiple GHL sites with OTTO Pixel installed, audit each one to confirm the attribute is present. - Test your pages on mobile after any script changes to catch navigation issues early. - Rocket Loader is enabled by default on most Cloudflare-connected sites — this fix applies any time you see navigation disruption after adding a new script. 🆘 Still Seeing Issues? If your mobile navigation is still broken after adding the data-cfasync="false" attribute, or if the OTTO Pixel status is not showing as active, 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.

🔧 Fix OTTO Pixel Navigation Bar Conflicts in GoHighLevel

🧭 Overview When you install the OTTO Pixel on a GoHighLevel (GHL) site, the mobile navigation bar can disappear or become unresponsive. This happens because the OTTO Pixel script can interfere with GoHighLevel's built-in CSS cascade, z-index stacking, or DOM rendering order. This article explains the verified root causes and gives you exact steps to fix the conflict. ⚠️ Why This Happens There are three common reasons the navigation bar disappears after adding the OTTO Pixel to a GoHighLevel site: - CSS cascade conflict: The OTTO Pixel script loads external stylesheets or inline styles that override GoHighLevel's navigation CSS, causing the nav bar to render hidden or behind other elements. - Z-index conflict: GoHighLevel navigation components rely on specific z-index values. If the OTTO Pixel introduces a stacking context at a higher z-index, the nav bar is visually obscured even though it still exists in the DOM. - DOM manipulation timing: If the OTTO Pixel script executes before GoHighLevel finishes building the navigation element, it can remove or alter nodes the nav bar depends on, causing it to disappear on mobile viewports where rendering order is stricter. 📍 Where to Place the OTTO Pixel Script in GoHighLevel Correct placement is the single most important fix. Follow these steps exactly: 1. Log in to your GoHighLevel account and open the site or funnel where the issue occurs. 2. Go to Settings → Custom Code (or Site Settings → Header Tracking Code, depending on your GHL version). 3. Locate the Header code block — this is where the OTTO Pixel must be placed. 4. Paste the OTTO Pixel script as the last item inside the header code block, after any existing scripts or meta tags. Placing it last prevents it from interfering with GoHighLevel's own script initialization order. 5. Save and publish your changes. 6. Test on a mobile device or using your browser's mobile emulation tool to confirm the navigation bar is visible and functional. Do not place the OTTO Pixel in the body or footer code blocks. Body and footer placement increases the risk of DOM manipulation conflicts because GoHighLevel builds navigation components earlier in the render cycle. 🏷️ Adding the data-cfasync Attribute The data-cfasync="false" attribute tells Cloudflare's Rocket Loader to skip asynchronous processing of the OTTO Pixel script. Without it, Rocket Loader can delay or reorder script execution, which worsens DOM timing conflicts on GoHighLevel pages. Add the attribute directly inside the opening script tag of the OTTO Pixel, like this: - Find the OTTO Pixel script tag in your GoHighLevel header code block. - Change to . - If your OTTO Pixel is an inline script (no src attribute), add the attribute the same way: . - Save and republish the site. Important: The data-cfasync="false" attribute must be placed inside the opening script tag itself, not as a separate tag or comment. Placing it anywhere else will have no effect. 🔍 Diagnosing a Z-Index or CSS Conflict If the navigation bar is still missing after correct script placement and adding the data-cfasync attribute, a z-index or CSS conflict may still be present. Use these steps to investigate: 1. Open your browser's developer tools (right-click the page and select Inspect). 2. Use the element selector to click on the area where the navigation bar should appear. 3. In the Styles panel, look for any CSS rule applying z-index, display: none, visibility: hidden, or opacity: 0 to the navigation element. 4. Check whether any of those overriding rules originate from a script or stylesheet loaded after GoHighLevel's core styles. 5. If you find a conflicting rule, note the CSS selector and contact our support team with that information so our team can advise on a targeted fix. ✅ Quick Checklist Before Escalating - OTTO Pixel script is placed last inside the GoHighLevel header code block. - data-cfasync="false" is added inside the opening script tag. - No duplicate OTTO Pixel scripts exist in body or footer code blocks. - Site has been saved and published after changes (not just saved). - Navigation issue has been tested on an actual mobile device, not just desktop. - Browser cache has been cleared before retesting. 🔗 Finding the OTTO Pixel in Search Atlas To locate your OTTO Pixel code in Search Atlas, go to Left sidebar → OTTO SEO, then open SEO Automation (URL: /seo-automation-v3). From there, open your connected project and navigate to the OTTO settings to find your unique pixel snippet. 💬 Still Need Help? If you have confirmed all checklist items above and the navigation bar is still not displaying correctly, our team will need to review your specific GoHighLevel HTML structure and script configuration. 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.

🛠️ Fix OTTO Pixel & Slow Crawl on GoHighLevel

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

🔧 OTTO Pixel & Schema Markup Troubleshooting in GoHighLevel

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 1. Copy your OTTO pixel script from OTTO SEO in your Search Atlas dashboard. 2. 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. 3. 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. 4. After making changes, return to OTTO SEO in Search Atlas and trigger a re-verification so OTTO re-crawls your site. 5. 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 1. 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.

🔧 Fix OTTO Pixel Installation on GoDaddy with GTM

🧭 Overview When you add the OTTO pixel to a GoDaddy website through Google Tag Manager (GTM), the pixel may still show as Not Installed inside Search Atlas. This happens because GoDaddy's website builder loads GTM inside an iframe, which isolates the pixel from the top-level page that OTTO monitors. This article explains why this occurs and walks you through the correct fix. ⚠️ Why GoDaddy's GTM Integration Causes This Problem GoDaddy's built-in Google Tag Manager connection injects the GTM container inside an iframe rather than directly into the of your page. OTTO's pixel verification checks the top-level document, so a pixel that fires only inside an iframe is invisible to the status checker and will always appear as not installed. This is a GoDaddy platform limitation, not a bug in OTTO or GTM. The solution is to place the OTTO pixel script directly in your page's HTML, bypassing the iframe entirely. 📋 Before You Start - You are logged in to your GoDaddy account and have access to the website editor. - You have access to the OTTO or OTTO SEO section in Search Atlas where your pixel snippet is available. - You have your unique OTTO pixel snippet copied and ready (see the step below). 📎 Step 1 — Copy Your OTTO Pixel Snippet 1. In Search Atlas, navigate to the section where your OTTO pixel code is provided for your project. 2. Select the project connected to your GoDaddy website. 3. Locate your pixel snippet and copy it to your clipboard or a text editor — you will paste it shortly. 🛠️ Step 2 — Add the Pixel Directly to Your GoDaddy HTML Because GTM runs inside an iframe on GoDaddy, you must inject the pixel script directly into the page HTML. The exact location of the custom code option varies by GoDaddy plan, but generally you should look for a way to add custom code or header code to your site's settings: 1. Open the GoDaddy Website Builder and enter the editor for your site. 2. Look in your site settings for an option that allows you to add custom code or scripts to the header of your pages. 3. Paste your OTTO pixel snippet into that field so it loads in the of every page. 4. Save and publish your changes. Important: If your GoDaddy plan does not provide a header code field, check whether GoDaddy offers an HTML element or custom section block inside the page editor, and place the pixel snippet as close to the top of the page as possible. 🚫 Avoiding Duplicate Pixel Detection If you previously attempted to install the pixel through GoDaddy's built-in GTM connection and you are now adding it directly to the HTML, you must remove one of the two installations to avoid duplicate pixel detection. Keep only the direct HTML installation, as this is the one that OTTO can reliably verify. ✅ Step 3 — Verify the Pixel Is Detected After saving and publishing, return to Search Atlas and check the pixel status for your project. It may take a few minutes for the status to update. If the pixel now shows as installed, the direct HTML method has worked correctly. 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.

🍞 Fix OTTO Pixel Detection Issues on Toast Websites

🔍 Why This Happens on Toast Websites Toast is a closed restaurant-focused website platform with its own internal caching layer and strict script-loading rules. Standard troubleshooting steps — such as clearing your browser cache or repositioning a script tag — do not apply here. When OTTO Pixel stops being detected on a Toast website, the root cause is almost always one of the following: - Residual OTTO Pixel code left over from a previous install - Toast's internal cache serving an outdated version of your site - A Google Tag Manager (GTM) container conflicting with the direct pixel install Follow the steps below in order. Skipping steps or repeating the install without completing the full removal process is the most common reason reinstallation fails. 🗑️ Step 1 — Completely Remove Existing OTTO Pixel Code from Toast Before adding any new code, you must ensure no previous version of the OTTO Pixel remains on your Toast site. 1. Log in to your Toast account and navigate to your website settings. 2. Open the section where custom scripts or tracking codes are managed (sometimes labeled Header Scripts, Custom Code, or Advanced Settings). 3. Locate every instance of OTTO Pixel code. This includes any snippet containing your OTTO tracking ID or references to the OTTO script URL. 4. Delete all instances completely. Do not leave any partial snippets behind. 5. Save your changes. Important: If you installed OTTO Pixel more than once during previous troubleshooting attempts, there may be duplicate entries. Check the custom code area thoroughly before proceeding. 🏷️ Step 2 — Remove Google Tag Manager if Present If you previously installed OTTO Pixel through a Google Tag Manager (GTM) container, or if GTM is active on your Toast site alongside a direct OTTO Pixel install, this conflict will prevent detection. 1. Check your Toast custom code area for any GTM snippet (it will reference googletagmanager.com). 2. If GTM is present and was used to fire the OTTO Pixel, remove the GTM container snippet from Toast entirely, or pause the OTTO Pixel tag inside GTM so it is not firing. 3. Choose one installation method only: either a direct OTTO Pixel snippet in Toast, or via GTM — never both at the same time. 4. Save all changes. If you intend to use GTM as your installation method, ensure the GTM container is published with the OTTO Pixel tag active before moving to the cache-clearing step. 🧹 Step 3 — Clear Toast's Internal Cache Toast caches your website at the platform level. Clearing your browser cache alone will not update what Toast serves to visitors or to OTTO's detection system. 1. Inside your Toast dashboard, locate the Publish or Save & Publish option for your website. 2. Trigger a full republish of your site. On some Toast plans this is labeled Force Refresh or Clear Cache. 3. If you do not see a dedicated cache-clearing option, saving any minor change to your site (such as editing a word in a paragraph, then reverting it) and republishing will force Toast to regenerate your pages. 4. Confirm the publish completed successfully before continuing. ➕ Step 4 — Reinstall the OTTO Pixel 1. In Search Atlas, go to OTTO SEO in the left sidebar (URL: /seo-automation-v3). 2. Locate your OTTO Pixel snippet for the relevant project. 3. Copy the snippet in full. 4. Return to your Toast custom code area and paste the snippet once into the correct field (typically the Header section). 5. Save and republish your Toast site. ⏳ Step 5 — Wait 20+ Minutes Before Testing Detection After republishing, Toast requires time to propagate changes across its network. Attempting to verify OTTO Pixel detection immediately after reinstallation is one of the most common sources of confusion — the pixel will appear undetected even when the install is correct. - Wait a minimum of 20 minutes after your final publish before running a detection check. - When you are ready to test, open your live Toast website URL in a private or incognito browser window to avoid cached responses from your own browser. - Return to Search Atlas and trigger the OTTO Pixel verification check from the OTTO SEO section. ✅ Quick Checklist Before Contacting Support - All previous OTTO Pixel code removed from Toast custom code fields - GTM conflict resolved — one installation method only - Toast internal cache cleared via a full republish - Fresh OTTO Pixel snippet pasted once into the Header section - Site republished and at least 20 minutes have passed - Detection tested from a private browser window on the live site URL 💬 Still Not Detected? If you have completed every step above and OTTO Pixel is still not being detected, there may be a Toast account-level restriction or a platform update affecting script loading. 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.

🔌 Fix OTTO Pixel Not Detected on Dealer.com Sites

🧭 Overview If your OTTO Pixel shows a Not Installed status on a site hosted on the Dealer.com CMS, this is a known integration issue. Unlike most platforms, Dealer.com sites can cause the OTTO Pixel to silently disconnect after initial setup — even when the pixel code appears to be present on the site. Clearing cache or verifying the installation method will not resolve this issue. The only confirmed fix is to delete the existing pixel and reinstall it from scratch using the steps below. ⚠️ Why This Happens Dealer.com's CMS manages third-party scripts in a way that can break the connection between Search Atlas and an installed OTTO Pixel over time. When this disconnection occurs, Search Atlas can no longer verify the pixel's presence — even if the script tag is still visible in the site's source code. This causes the pixel status to display as Not Installed inside the platform. This behaviour is specific to Dealer.com-hosted sites and is not caused by browser caching, bot-blocking settings, or incorrect installation methods. ✅ How to Fix It — Delete and Reinstall the Pixel 1. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3) to open your OTTO dashboard. 2. Locate the affected site — in this example, www.polestarfortlauderdale.com — and open its OTTO settings. 3. Find the existing OTTO Pixel entry for this site and delete it. Do not attempt to re-save or update the existing pixel — it must be fully removed. 4. Once deleted, generate a new OTTO Pixel for the same site from within the OTTO SEO section. 5. Copy the new pixel script provided by Search Atlas. 6. Log in to your Dealer.com account and navigate to the section where third-party scripts or tracking codes are managed (typically under Site Settings or Integrations). 7. Remove any previously installed OTTO Pixel script from Dealer.com. 8. Paste the new pixel script into Dealer.com and save your changes. 9. Return to Search Atlas and allow time for the pixel status to update to Installed. Automatic checks run every 15 minutes for projects under 2 hours old, hourly from 2–24 hours, every 6 hours from 1–7 days, and stop after 7 days. 🔍 How to Confirm the Fix Worked - After the next automatic check, return to OTTO SEO → All Sites (SEO Automation) in the left sidebar and check the pixel status for your site. - The status should now display as Installed. - If you want to verify the pixel is firing independently, use a browser extension such as Google Tag Assistant or inspect the page source to confirm the new script is present. 🚫 What Not to Try on Dealer.com Sites The following steps are standard pixel troubleshooting actions that will not resolve this specific Dealer.com disconnection issue: - Clearing browser or server-side cache - Switching between manual and tag-manager installation methods - Checking or adjusting bot-access or crawler settings - Re-saving the existing pixel without deleting it first If you apply any of the above steps without completing the full delete-and-reinstall process, the pixel will continue to show as Not Installed. 📋 Quick Reference — Dealer.com Pixel Fix - Affected platform: Dealer.com CMS - Symptom: OTTO Pixel status shows Not Installed despite pixel code being present - Root cause: Dealer.com script handling causes pixel disconnection after installation - Resolution: Delete existing pixel in Search Atlas, generate a new one, reinstall in Dealer.com - Time to verify: Depends on project age — every 15 minutes (under 2 hours old), hourly (2–24 hours), every 6 hours (1–7 days), no automatic checks after 7 days 💬 Still Need Help? If you have completed the delete-and-reinstall process and the pixel still shows as Not Installed after the expected check interval for your project's age, or if you need guidance navigating Dealer.com's script management interface, 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.

🛠️ Troubleshoot OTTO SEO Pixel on GHL

🔍 Overview After installing the OTTO SEO Pixel on a GoHighLevel (GHL) site, the Search Atlas dashboard should confirm the connection within about 15 minutes. If your dashboard still shows the Pixel as disconnected after 20 or more minutes, one of the common issues below is usually the cause. Work through each section in order until the Pixel shows as Connected. ✅ Before You Begin Confirm you have the following ready before troubleshooting: - Access to the GoHighLevel site builder for the website you are connecting. - Your OTTO SEO Pixel snippet — found in Search Atlas by navigating to OTTO SEO in the left sidebar, then opening SEO Automation inside it (URL: /seo-automation-v3), then selecting your project and opening the Pixel setup step. - A way to clear your browser cache and cookies. 🧩 Step 1 — Verify the Pixel Snippet Is Copied Correctly An incomplete or altered snippet is the most common reason the Pixel does not connect. 1. Go to OTTO SEO in the left sidebar of Search Atlas, then open SEO Automation inside it. 2. Open your project and locate the Pixel snippet in the setup panel. 3. Click Copy directly from the panel — do not retype or manually select the code, as this can introduce hidden characters. 4. Paste the snippet into a plain-text editor (such as Notepad or TextEdit) and confirm it starts with <script> and ends with </script> with no extra characters before or after. 📋 Step 2 — Confirm Placement in GHL The Pixel must be placed in a location that loads on every page of your site. In GoHighLevel, the correct location is the site-wide Header Tracking Code field. 1. Log in to GoHighLevel and open the Sites section. 2. Select the website you are connecting to OTTO SEO. 3. Click Settings (the gear icon) for that site. 4. Scroll to the Header Tracking Code field. 5. Paste the OTTO SEO Pixel snippet here. If other scripts are already present, paste the OTTO snippet on a new line after them — do not replace existing code. 6. Click Save and then Publish the site to push the change live. Important: Adding the snippet only to an individual page footer or a single funnel step will not satisfy the Pixel check. It must be in the site-wide header settings. 🌐 Step 3 — Confirm the Site Is Published and Publicly Accessible The Search Atlas system verifies the Pixel by scanning your live site URL. If the site is in draft mode or password-protected, the scan will fail. - Open your site's public URL in a private or incognito browser window to confirm it loads without a login prompt or "coming soon" page. - In GoHighLevel, ensure the site status is set to Published, not Draft. - If you use a custom domain, confirm DNS has fully propagated and the domain resolves correctly. 🔎 Step 4 — Manually Verify the Pixel Is Firing You can confirm the snippet is live on your site before waiting for the dashboard to update. 1. Open your site's public URL in a browser. 2. Right-click anywhere on the page and select View Page Source. 3. Use Ctrl + F (or Cmd + F on Mac) to search for ottoseo or the unique ID from your Pixel snippet. 4. If the snippet does not appear in the source, return to Step 2 and re-check your GHL settings. 5. If the snippet does appear, proceed to Step 5. ⏱️ Step 5 — Trigger a Manual Recheck in Search Atlas Once the snippet is confirmed live, prompt Search Atlas to re-scan your site. 1. Navigate to OTTO SEO in the left sidebar, then open SEO Automation inside it (URL: /seo-automation-v3). 2. Open your project and go to the Pixel setup step. 3. Click the Verify / Recheck button if available, or save your project settings to trigger a fresh scan. 4. Wait up to 15 minutes and refresh the page. The status should update to Connected. ⚠️ Common Mistakes to Avoid - Adding the snippet to only one page: The Pixel must load site-wide. Use the Header Tracking Code field in GHL site settings, not a single page. - Not publishing after saving: In GHL, saving alone does not push changes live. Always click Publish. - Using the wrong project's Pixel: Each OTTO SEO project generates a unique snippet. Make sure the snippet matches the project you are trying to connect. - Browser cache showing old source: If you recently added the snippet and the page source still looks old, hard-refresh with Ctrl + Shift + R (or Cmd + Shift + R on Mac) or use incognito mode. 💬 Still Not Connected? If you have followed all the steps above and the Pixel still shows as disconnected, our support team can review your specific setup directly. 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.

🔧 OTTO Pixel Troubleshooting for GoHighLevel Websites

🧭 Overview If you are using a GoHighLevel (GHL) website and OTTO is showing a "pixel not installed correctly" warning, you are not alone. This error is a known platform-specific display issue. The standard WordPress or Shopify troubleshooting steps do not apply here. This article walks you through the GHL-specific workaround that resolves the error and lets you deploy OTTO fixes without interruption. ⚠️ Why This Happens on GHL GoHighLevel manages scripts and tracking pixels differently from other website platforms. Even when the OTTO pixel is correctly placed in your GHL site settings, the Search Atlas system may still flag it as undetected due to the way GHL renders and caches custom scripts. This is a verification display issue — not a problem with your pixel code itself. ✅ Before You Begin Confirm the following before applying the workaround: - You have access to your GHL site's Settings and the Header Tracking Code field. - You have already copied your unique OTTO pixel snippet from Search Atlas. - You are logged in to Search Atlas and have navigated to OTTO SEO in the left sidebar, then opened SEO Automation inside it (URL: /seo-automation-v3) to access your OTTO dashboard. 🛠️ GHL-Specific Workaround (Step-by-Step) 1. Copy your OTTO pixel snippet. In Search Atlas, go to OTTO SEO in the left sidebar, then open SEO Automation inside it. Locate your OTTO pixel code and copy the full snippet to your clipboard. 2. Open your GoHighLevel account. Navigate to the website or funnel where OTTO is being deployed. 3. Access site tracking settings. In GHL, go to Sites → Your Website → Settings → Tracking Code (or Header Tracking Code, depending on your GHL version). 4. Paste the OTTO pixel snippet. Paste the full pixel code into the header tracking field. Make sure no extra characters or line breaks are added before or after the snippet. 5. Save and publish the changes. Click Save, then republish your GHL site so the script is pushed live to all pages. 6. Return to Search Atlas and trigger a manual recheck. In your OTTO dashboard (go to OTTO SEO in the left sidebar, then open SEO Automation inside it), locate the pixel verification section and click Recheck or Verify Pixel. Allow up to about 15 minutes for the system to detect the pixel across your GHL domain, since automatic checks run every 15 minutes for new projects. 7. Proceed with deploying OTTO fixes. Once the pixel status updates to confirmed, all OTTO fix deployment options will become available. If the status display still shows a warning but your pixel is live, you can proceed — the underlying detection is functional. 🔁 One-Time Application — Important Note This workaround only needs to be completed once per GHL website. After the pixel is correctly placed in the GHL tracking code field and verified, you will not need to repeat these steps unless you create a new site, switch domains, or reset your GHL site settings. Do not reinstall or duplicate the pixel snippet, as multiple instances of the same pixel code can cause tracking conflicts. ❓ Frequently Asked Questions - The pixel status still shows an error after following these steps. What should I do? Wait about 15 minutes and trigger the recheck again. GHL sites can have a short cache delay before newly added scripts are detectable. If the issue persists after two rechecks, contact support using the chat widget below. - Can I use the WordPress or Shopify pixel instructions instead? No. Those instructions reference plugin-based or theme-based installation methods that do not exist in GHL. Always use the steps in this article for GoHighLevel websites. - Will this affect my other GHL tracking scripts? No. Adding the OTTO pixel to the header tracking field in GHL does not interfere with Google Analytics, Facebook Pixel, or other scripts already installed there. - My GHL site uses funnels, not a standard website. Does this still apply? Yes. For GHL funnels, navigate to the individual funnel settings and add the pixel to the Funnel Settings → Tracking Code field using the same steps above. 💬 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.

🛠️ Fix OTTO Pixel Detection on Toast Websites

🔍 Overview The OTTO Pixel is a small tracking script that allows OTTO SEO to monitor and automate optimizations on your website. When connected to a Toast website, the pixel can occasionally lose its connection or stop being detected — even if it was working before. This article explains why this happens and walks you through the steps to restore detection successfully. ⚠️ Why the OTTO Pixel Stops Being Detected Toast websites use a proprietary content management system that can overwrite or reset third-party scripts in the following situations: - A Toast platform update or template refresh was applied to your site. - You edited or republished your site through the Toast dashboard, which can clear injected scripts. - The script was added to a section of the page that Toast does not persist between sessions or publishes. - Browser caching caused Search Atlas to check a stale version of the page during detection. Because Toast manages its own code environment, standard reinstallation steps may appear to succeed but the pixel can still fail detection if placed in the wrong location. ✅ How to Correctly Reinstall the OTTO Pixel on a Toast Website 1. Get your OTTO Pixel snippet. In Search Atlas, go to OTTO SEO in the left sidebar and open SEO Automation (or navigate to /seo-automation-v3). Open your OTTO project and locate the pixel installation section. Copy your unique pixel code snippet. 2. Log in to your Toast website dashboard. Navigate to the section that controls custom code or scripts — this is typically found under Settings → Custom Code or a similar menu in your Toast admin panel. 3. Remove any previously installed pixel snippets. Before adding a fresh copy, delete all existing instances of the OTTO Pixel from your Toast site. Having duplicate or stale versions is a common cause of detection failures. 4. Paste the pixel in the section only. Toast websites retain third-party scripts most reliably when they are placed in the global section, not in the body or footer. Confirm you are pasting into the head-level custom code field. 5. Save and publish your changes. Make sure to fully publish or go live with the update — saving as a draft will not make the script visible to Search Atlas for detection. 6. Clear your browser cache and any site-level cache. After publishing, clear your browser cache. If Toast offers a cache-clearing option in the dashboard, use it as well. 7. Trigger pixel detection in Search Atlas. Return to your OTTO project under OTTO SEO → SEO Automation (/seo-automation-v3) and run the pixel detection check. For new projects, automatic checks run every 15 minutes, so detection is normally confirmed within about 15 minutes. 💡 Tips to Prevent Future Detection Loss - Avoid republishing your entire Toast site unless necessary — full republishes can reset custom code fields. - Check your pixel after any Toast platform update. Toast occasionally pushes automatic updates that may clear injected scripts. Make it a habit to verify detection after any changes to your site. - Only install the pixel once. Multiple copies of the pixel snippet can cause conflicts and failed detection. Always verify no duplicates exist before adding a new one. - Use the placement every time. Footer or body placements are less reliable on Toast and may not be detected consistently. 🔎 How to Verify the Pixel Is Live on Your Site Before triggering detection in Search Atlas, you can manually confirm the pixel is present on your Toast website: 1. Open your live website URL in a browser. 2. Right-click anywhere on the page and select View Page Source. 3. Use Ctrl+F (or Cmd+F on Mac) to search for otto or a unique portion of your pixel snippet. 4. If the snippet appears in the source, the pixel is live. If it does not appear, return to your Toast dashboard and repeat the reinstallation steps above. 🆘 Still Not Being Detected? If you have followed all the steps above and the OTTO Pixel is still not being detected on your Toast website, our team can investigate further. 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. Additional Notes If you previously installed OTTO Pixel through a Google Tag Manager (GTM) container, or if GTM is active on your Toast site alongside a direct OTTO Pixel install, this conflict will prevent detection. Check your Toast custom code area for any GTM snippet (references googletagmanager.com) and remove it.

🔌 Troubleshoot OTTO SEO Pixel Not Connecting in GHL

🧭 Overview After installing the OTTO SEO Pixel in GoHighLevel (GHL), your dashboard should show the pixel as Connected within about 15 minutes on a new project. If it has been longer than that and the status still shows as unconnected, this guide will walk you through the most common causes and how to fix them. ⚡ Key Things to Know Before You Start - The OTTO SEO Pixel only needs to be installed on one page of your GHL site — it does not need to be added to every page. - Connection confirmation typically happens within about 15 minutes after a correct installation on a new project, since Search Atlas automatically checks new projects every 15 minutes. - If you prefer a visual walkthrough, a Loom video guide is available — see the section below. 🔍 Step 1 — Verify the Pixel Code Is Correctly Placed 1. In GHL, open the page where you added the pixel code. 2. Go to the page's Settings and locate the Header Tracking Code or Custom Code field. 3. Confirm the full OTTO SEO Pixel snippet is pasted there — it must be complete, with no characters missing or added. 4. Make sure the code is placed inside the section, not the body or footer. 🌐 Step 2 — Confirm the Page Is Published and Live 1. Check that the page where you added the pixel is published, not saved as a draft. 2. Open the live URL of that page in your browser. 3. Right-click the page and select View Page Source. 4. Use Ctrl + F (or Cmd + F on Mac) to search for otto or your pixel ID — it should appear in the source code. 5. If you do not see it, the page may not have saved correctly. Re-paste the code, save, and republish. 🔄 Step 3 — Refresh the OTTO SEO Dashboard 1. In Search Atlas, navigate to OTTO SEO using the left sidebar. 2. Open your OTTO SEO project and go to the pixel connection section. 3. Click Check Connection or refresh the page to prompt a new verification check. 4. Wait a few minutes after refreshing before checking the status again. Note that automatic checks run every 15 minutes for projects under 2 hours old, every hour from 2–24 hours old, every 6 hours from 1–7 days old, and stop after 7 days. 🛠️ Step 4 — Use the Alternative Installation Method If the standard installation is not working, try the alternative method shown in the Loom video guide: 1. In your OTTO SEO pixel setup screen, look for the link labeled Watch Loom Video or Video Walkthrough. 2. Follow the video steps exactly — the video demonstrates an alternative way to embed the pixel in GHL that avoids common copy-paste errors. 3. After completing the steps in the video, republish the page and return to your dashboard to recheck the connection status. 🚫 Common Mistakes to Avoid - Adding the pixel to multiple pages: You only need it on one page. Adding it to many pages will not speed up detection and may cause conflicts. - Placing the code in the wrong field: In GHL, use the Header Tracking Code field specifically — avoid the body or footer code fields. - Checking too soon: Allow at least 15 minutes after a fresh installation before declaring it failed, since that's how often new projects are automatically checked. - Browser caching: If you are testing the live page, use an incognito window or clear your cache to ensure you are seeing the latest published version. ✅ How to Confirm the Pixel Is Working - The status in your OTTO SEO dashboard changes from Not Connected to Connected. - You can see the pixel ID in the page's HTML source code when you view the published page. - OTTO SEO begins populating data for that website within your project. 💬 Still Need Help? If you have followed all steps above and the pixel is still not showing as connected, 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.

🛠️ OTTO Pixel Not Detected on Dealer.com Sites

🔍 Overview If your site runs on the Dealer.com CMS and the OTTO Pixel shows as not installed inside Search Atlas, this is a known platform-specific detection issue. It does not necessarily mean the pixel is missing from your site — it means Search Atlas cannot verify it through its standard detection method due to how Dealer.com renders and serves its pages. ⚙️ Why This Happens Dealer.com is an automotive-focused CMS that uses a heavily managed hosting and rendering environment. This setup can prevent external tools from reading page source code in the standard way. As a result, even when the OTTO Pixel script is correctly placed on your site, Search Atlas may still report its status as not detected. Common reasons the pixel goes undetected on Dealer.com sites include: - Deferred or async script loading: Dealer.com often loads third-party scripts after the initial page render, which can cause detection checks to miss the pixel entirely. - Restricted page source access: Dealer.com's infrastructure may block or limit external crawlers from reading the full HTML output of a page. - Tag Manager conflicts: If the pixel is deployed via a Tag Manager container rather than hardcoded into the page template, it may not appear during a standard source scan. - CDN or proxy caching: Dealer.com uses content delivery networks that may serve cached versions of pages without the pixel present in every response. ✅ How to Confirm the Pixel Is Actually Installed Before escalating, verify the pixel is live on your site using these steps: 1. Open your site in a browser (e.g., www.polestarfortlauderdale.com). 2. Right-click anywhere on the page and select Inspect (or press F12) to open browser DevTools. 3. Go to the Sources or Network tab and search for otto or your unique pixel ID. 4. Alternatively, use the Elements tab and press Ctrl+F (or Cmd+F on Mac) to search for the pixel script tag. 5. If the script appears, the pixel is installed correctly — the issue is limited to how Search Atlas detects it remotely. 🚀 Steps to Request Manual Pixel Verification Because automated detection may not work reliably on Dealer.com sites, Search Atlas supports a manual verification process. Follow these steps: 1. Log in to Search Atlas and navigate to OTTO SEO in the left sidebar, then open SEO Automation inside it (or go to /seo-automation-v3). 2. Locate the OTTO Pixel status for your site and take a screenshot showing the not detected status alongside your domain name. 3. Open the chat widget in the bottom-right corner of the platform and type human teammate. 4. Share your domain, the screenshot, and confirmation that your site uses Dealer.com as the CMS. 5. Our team will manually confirm pixel activity on the backend and update your account status accordingly. 💡 Best Practices for Dealer.com Pixel Installation To give the OTTO Pixel the best chance of being detected automatically in future scans, work with your Dealer.com account representative to ensure: - The pixel script is placed in the section of every page template, not just the homepage. - The script loads synchronously where possible, rather than being deferred or set to async-only. - If using Google Tag Manager, confirm the GTM container itself fires on all pages and that the OTTO Pixel tag has no restrictive trigger conditions. - Any cookie consent or privacy tools are configured to allow the pixel to load for users who accept analytics cookies. 🙋 Still Seeing Issues? If you have confirmed the pixel is on the page but Search Atlas still reports it as undetected after following the steps above, our support team can investigate further. 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. Additional Notes The only confirmed fix is to delete the existing pixel and reinstall it from scratch. Delete the existing OTTO Pixel entry (do not re-save/update it), generate a new pixel, remove the old script from Dealer.com, paste the new script, and allow about 15 minutes for status to update on a new project (automatic checks run every 15 minutes for projects under 2 hours old).

🛠️ Fix Search Atlas Script Not Working on GoHighLevel

🔍 Overview If you have added the Search Atlas script to your GoHighLevel (GHL) website but OTTO is not detecting it, the most common cause is a Cloudflare security rule that blocks the Search Atlas crawler before it can verify the script. This article walks you through diagnosing and fixing the issue so OTTO can successfully connect to your site. ⚠️ Common Symptoms - You added the Search Atlas script to your GHL site but OTTO still shows the site as undetected or not connected. - The Installation Guide shows the script as missing even though you can see it in your GHL settings. - You notice two script tags on your site — this is normal GHL behavior and is not a duplicate error. 🧩 Why This Happens Cloudflare's bot protection can treat the Search Atlas crawler as an unwanted bot and block its requests. When the crawler is blocked, it cannot reach your page to confirm the script is present, so OTTO never registers a successful connection. The fix is to whitelist the Search Atlas crawler in your Cloudflare settings so it can access your site freely. ✅ How to Fix It 1. Log in to your Cloudflare dashboard for the domain connected to your GoHighLevel site. 2. Navigate to your security or bot management settings. The exact location depends on your Cloudflare plan, but look for sections related to bot protection, firewall rules, or IP access rules. 3. Add a whitelist rule that allows the Search Atlas crawler. Create an allow rule for the Search Atlas crawler user agent or IP range. If you are unsure of the exact crawler details, contact our support team using the instructions at the bottom of this article and a teammate will provide them. 4. Save your changes and allow a few minutes for the rule to propagate. 5. Trigger a new scan in Search Atlas. Return to your Search Atlas account and run a fresh scan on your site so OTTO can attempt to detect the script again. 6. Check the installation status. Confirm in your Search Atlas account whether the script is now detected and the site shows as connected. 📋 Additional Notes - Two script tags on your GHL site is expected. GoHighLevel sometimes renders the script tag more than once. This is standard GHL platform behavior and does not indicate a problem with your installation. - CMS detection may show as "Custom CMS" instead of "GoHighLevel." Our engineering team is actively working on improving GoHighLevel fingerprinting so the CMS is recognised correctly. This does not affect OTTO's ability to optimise your site once the script is connected. - If your site uses a third-party proxy or additional anti-bot service beyond Cloudflare, the same principle applies — the Search Atlas crawler must be permitted through any layer that sits in f

🚀 Installing OTTO Pixel on Next.js Without Errors

Overview OTTO supports two installation methods: direct pixel installation and Google Tag Manager (GTM) deployment. This article explains how to implement either method in a Next.js project so you do not encounter React hydration errors or performance issues. Why Hydration Errors Happen React hydration errors occur when the HTML rendered on the server does not match what React expects to render on the client. The OTTO pixel is a client-side script. If it runs during server-side rendering (SSR), it can reference browser-only globals such as window or document that do not exist in the Node.js environment, causing a mismatch. The fix is to ensure the pixel only ever runs in the browser, after the component has mounted. Supported OTTO Integration Methods - Direct pixel installation — Embed the OTTO pixel script directly in your Next.js project using a client-side-safe approach. - Google Tag Manager — Deploy the OTTO pixel through a GTM container tag, which fires only in the browser environment. If you are unsure which method fits your setup, contact the Search Atlas support team and they will help you choose the right approach. How to Find Your OTTO Pixel Code Log in to your Search Atlas account and locate your site-specific OTTO pixel snippet inside your project settings. If you are unsure where to find your pixel code, contact our support team and they will guide you to the correct screen. Method 1: Direct Pixel Installation Using useEffect The safest way to load the OTTO pixel directly in a Next.js project is to use the useEffect hook, which only runs in the browser after the component has mounted. This prevents any server-side execution. 1. Create or open a layout or page component where you want the pixel to load globally (for example, _app.js in the Pages Router, or your root layout.js in the App Router). 2. Import useEffect from React at the top of the file: import { useEffect } from 'react'; 3. Inside the component, add a useEffect block that creates a script element and appends it to the document body: - Create the script tag: const script = document.createElement('script'); - Set the src to your OTTO pixel URL: script.src = 'YOUR_OTTO_PIXEL_URL'; - Set it to load asynchronously: script.async = true; - Append it: document.body.appendChild(script); 4. Make sure the dependency array is empty ([]) so it runs only once after the initial render. 5. Save the file, then open your browser's developer console and confirm no hydration errors appear and the pixel fires as expected. Method 1 Alternative: Using next/script Next.js provides a built-in Script component from next/script that handles client-safe loading automatically. 1. Import the Script component: import Script from 'next/script'; 2. Add the Script component to your layout or page, setting the strategy prop to afterInteractive or lazyOnload. Both strategies ensure the script only runs in the browser after the page is interactive: <Script src="YOUR\_OTTO\_PIXEL\_URL" strategy="afterInteractive" /> 3. Verify in the browser developer console that no hydration errors appear and that the pixel fires correctly. Method 2: Installing via Google Tag Manager If you prefer to manage the OTTO pixel through GTM, the key is to load the GTM container itself in a browser-safe way within Next.js. 1. Retrieve your GTM container ID (formatted as GTM-XXXXXXX) from your Google Tag Manager account. 2. In your Next.js project, add the GTM snippet using the next/script Script component with strategy="afterInteractive" so it only runs in the browser. 3. Place the GTM <noscript> iframe fallback inside the <body> tag of your layout. 4. Inside GTM, configure your OTTO pixel as a Custom HTML tag set to fire on All Pages (or your preferred trigger). GTM tags fire in the browser by default, so no additional SSR guard is needed on the tag itself. 5. Publish your GTM container, then verify in the browser developer console and GTM Preview mode that the OTTO pixel fires without hydration errors. General Best Practices - Always load the OTTO pixel in a way that guarantees it only executes in the browser, not during server-side rendering. - If using GTM, ensure the GTM container tag is also loaded in a browser-safe manner within your Next.js project. - After installation, verify in your browser's developer console that no hydration errors appear and that the pixel fires as expected. Getting Help With Your Next.js Integration Because Next.js projects vary in structure (Pages Router vs. App Router, SSR vs. static export), the correct way to integrate the OTTO pixel depends on your specific setup. If you need tailored guidance, please reach out to our support team. Share details about your Next.js version and rendering approach so the team can advise you on the right integration method. If we were unable to resolve your issue, please contact our support team and we will be happy to help.

🛠️ Fix OTTO Pixel Wrong Domain Error on GoHighLevel

🔍 What This Error Means The wrong domain error appears when the OTTO Pixel installed on your GoHighLevel site does not match the project domain registered in OTTO. When the domains do not match, OTTO cannot verify the connection, and Atlas Brain is blocked from deploying your SEO fixes. The most common cause on GoHighLevel is using a White Label (WL) pixel when your OTTO project expects a Search Atlas (SA) pixel, or the reverse. 💡 WL Pixel vs SA Pixel OTTO offers two versions of the Pixel, and they are not interchangeable. Installing the wrong one is the leading cause of this error. - SA Pixel (Search Atlas): The standard pixel issued to accounts that use Search Atlas branding. - WL Pixel (White Label): The pixel issued to accounts running on a White Label or agency-branded domain. Your OTTO project will only validate the pixel type that matches your account configuration. If your project is set up as White Label, you must deploy the WL pixel; if it is a standard Search Atlas project, you must deploy the SA pixel. ⚙️ Why the Error Happens on GoHighLevel GoHighLevel lets you add custom code through site or funnel settings, so it is easy to paste a pixel that belongs to a different domain or a different pixel type. The error is usually triggered by one of these issues: - The WL pixel was installed on a project expecting the SA pixel, or the SA pixel was installed on a White Label project. - The pixel was copied from a different OTTO project or domain. When the pixel actually belongs to a different OTTO account or project, OTTO may report it as a wrong_uuid / account mismatch rather than a simple domain mismatch—in that case the fix is to copy the pixel from the correct project under the correct account. - The domain in OTTO includes www or https:// while the live GoHighLevel site uses a different format. - The pixel was added to a staging or preview URL instead of the published domain. 🛠️ How to Fix It Step by Step 1. Open OTTO and select the affected project. 2. Confirm the exact domain listed in the project settings. Note whether it uses www and the correct protocol. 3. Identify whether your project is a Search Atlas or White Label project. This determines which pixel you need. 4. Copy the correct pixel code directly from your OTTO project. Always copy a fresh version rather than reusing an older snippet. 5. In GoHighLevel, go to Sites, then open the relevant funnel or website, and navigate to the settings where custom code or tracking code is added. 6. Remove any existing OTTO pixel to avoid duplicate or conflicting installs. 7. Paste the correct pixel into the header or tracking code section, then save and publish. 8. Make sure the published domain matches the domain registered in OTTO exactly. ✅ Verify the Fix After publishing, return to OTTO to confirm the connection is healthy. 1. Open your OTTO project and check the pixel status. 2. Wait a few minutes for OTTO to re-scan the live site. 3. Confirm the wrong domain error has cleared and the pixel shows as verified. 4. Check that Atlas Brain can resume deploying your SEO fixes. If the status does not update right away, clear your cache or open the live domain in a private browser window to ensure the published pixel is loading. In rare cases the pixel can show as detected and verified while the project still does not move out of an unactivated state. If the wrong domain error has cleared and the pixel is verified but your project stays unactivated, this is a separate condition from the domain mismatch—start a live chat so our team can review and activate the project on their end. 🚀 Tips to Prevent Future Errors - Always copy the pixel from the specific OTTO project it belongs to. - Match the pixel type to your account: WL pixel for White Label projects, SA pixel for Search Atlas projects. - Keep the domain format in OTTO identical to your live GoHighLevel domain. - Install the pixel on the published site, not a preview or staging URL. - Remove old pixels before adding a new one. ⚠️ Known Issues to Be Aware Of - GoHighLevel detected as “Custom CMS”: OTTO can sometimes label a GoHighLevel site as a Custom CMS instead of GHL during detection. This is a known issue that has been logged with our engineering team and is currently scheduled for development, so if you see this label, follow the manual pixel steps above rather than relying on automatic CMS detection. - WL pixel blocked by antivirus: On some white-label domains, the OTTO pixel script was previously flagged as phishing by tools such as Avast and VirusTotal, which could stop the pixel from loading. This issue has been resolved—make sure your security software and definitions are up to date if a WL pixel still appears blocked. - Pixel/UUID not detected behind Cloudflare: If your GoHighLevel domain is proxied through Cloudflare, the pixel or UUID may fail to be detected even after a successful deployment. This was a known issue that has since been resolved—if you still encounter it, copy a fresh pixel from your OTTO project, republish, and allow a few minutes for OTTO to re-scan. - WL pixel on White Label domain aliases: For White Label domains that use domain aliases, our engineering team is currently working on routing the OTTO pixel traffic through a CDN to improve detection reliability. This work is in development, so if a WL pixel on an aliased domain still fails to validate, copy a fresh pixel, republish, and contact support if the error persists. 💬 Still Need Help? If you have confirmed the correct pixel type and matching domain but the error continues, our team can review your specific setup. If you need further assistance, click the chat icon in the bottom-right corner of the platform to start a live chat with a member of our team.