Pixel Installation: Webflow, GoDaddy & Other Builders

⚡ OTTO Pixel Slowdown on Duda Sites

🔍 OTTO Pixel Privacy, History, and Webflow Integration

Overview OTTO SEO automates on-page optimizations through a lightweight pixel and a no-code deployment system. This article covers the three most common questions customers ask about the OTTO pixel: what data it collects, how to review past deployments, and how OTTO behaves on Webflow sites. Note: The specific UI labels and panel names within OTTO may vary depending on your account version. If you cannot locate a section described below, reach out to our support team for the exact location in your account. What Data Does the OTTO Pixel Collect? The OTTO pixel is a small JavaScript snippet added to your website that allows OTTO to read page structure and apply SEO changes. Questions about exactly what data the pixel collects and how it is handled are best directed to our support team, who can provide details specific to your account and compliance requirements. If you have specific compliance questions about data handling, contact our support team for details relevant to your use case. How to View Previously Deployed Changes OTTO maintains a record of changes deployed to your site. To find this history, navigate to OTTO SEO → All Sites (SEO Automation) → your project → Deployment History. From there you should be able to see which pages were affected and when changes were made. If you need to undo a specific optimization, look for a toggle or option adjacent to the individual change entry. If you are unable to locate the deployment history within your project view, our support team can walk you through the exact steps for your account. OTTO and Webflow: What to Expect OTTO works with Webflow sites by injecting changes through the pixel. If you are seeing unexpected behavior or have questions about how OTTO interacts with your specific Webflow setup, our support team can review your project and advise on next steps. 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.

Install OTTO Pixel on Cloudflare and Custom CMS

🧭 Overview The OTTO pixel allows Search Atlas to crawl and optimize your site automatically. If your site is protected by Cloudflare, its bot protection may block Search Atlas bots by default — preventing the pixel from working correctly. This article walks you through how to whitelist Search Atlas bots in Cloudflare and how to install the OTTO pixel on a custom CMS using Google Tag Manager (GTM). ⚠️ Why Cloudflare May Block the OTTO Pixel Cloudflare's bot management and firewall features are designed to block unrecognized automated traffic. Search Atlas crawlers may be blocked before the pixel can fire, which can result in the pixel appearing unverified inside OTTO even after installation. ✅ Step 1 — Whitelist Search Atlas Bots in Cloudflare To allow Search Atlas crawlers through Cloudflare's firewall, you need to create a firewall rule (or WAF custom rule) that bypasses bot protection for Search Atlas user agents and/or IP ranges. 1. Log in to your Cloudflare dashboard and select the domain where OTTO is installed. 2. Locate the firewall or WAF rules section for your plan — the exact menu path may vary depending on your Cloudflare plan version. 3. Create a new custom rule named something like Allow Search Atlas Bots. 4. Configure the rule to match Search Atlas traffic by user agent and/or by any IP addresses that Search Atlas has provided to you, then set the action to allow or bypass bot protection for matching requests. 5. Save and deploy the rule. If your Cloudflare plan includes additional bot protection features, you may also need to review those settings to ensure verified or allowlisted bots are not being challenged. Refer to Cloudflare's official documentation for the exact steps that apply to your plan. 📦 Step 2 — Install the OTTO Pixel via Google Tag Manager If your CMS does not allow direct theme file editing (e.g., some hosted or headless platforms), use Google Tag Manager to deploy the OTTO pixel. 1. Log in to Search Atlas and locate your unique OTTO pixel code snippet within your OTTO settings area. 2. Log in to Google Tag Manager and open the container for your site. 3. Create a new tag using the Custom HTML tag type. 4. Paste the OTTO pixel code snippet into the HTML field. 5. Set the trigger so the pixel fires on every page load (e.g., an All Pages trigger). 6. Name the tag and publish your GTM container to make the pixel live. 🔍 Step 3 — Verify the Pixel Is Working After completing both steps, return to Search Atlas and check whether the OTTO pixel status updates to verified. If the pixel remains unverified, confirm that your Cloudflare allowlist rule is active and that GTM has been published with the correct trigger 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.

🔌 Install OTTO Pixel in Webflow Custom Code

🧭 Overview The OTTO Pixel is a tracking script that allows OTTO to audit and automate SEO changes on your website. When using Webflow, the script must be added through Webflow's built-in custom code feature. If the pixel is not being recognized after installation, our support team can walk you through the exact steps required for your account setup. ✅ Before You Begin - Confirm you have the necessary access level in Webflow to add custom code to your project. - Make sure your Webflow site is published before expecting the pixel to be detectable — unpublished changes are not visible to external scanners. - Have your OTTO Pixel script ready to copy from within Search Atlas. 📋 General Installation Process The general process for installing the OTTO Pixel in Webflow involves the following steps. Because the exact UI labels and navigation paths in both Search Atlas and Webflow may vary depending on your account type and platform version, contact our support team if you are unsure where to find a specific setting. 1. Log in to Search Atlas and locate your unique OTTO Pixel script. Copy it to your clipboard. 2. Log in to your Webflow project and navigate to the area where custom code can be added to your site. 3. Paste the OTTO Pixel script into the appropriate custom code area for site-wide scripts. 4. Save your changes and republish your Webflow site so the script appears on your live pages. 5. Return to Search Atlas and initiate a pixel detection or site scan for your website. 🛠️ If the Pixel Is Still Not Recognized If the pixel is not detected after following the steps above, common things to check include: - Site not republished: Changes in Webflow only go live after you explicitly publish the site. Verify the site was republished after pasting the script. - Script placement: Ensure the script was added to a site-wide location rather than a single page, unless OTTO only needs to track a specific page. - Correct script copied: Confirm the script you pasted matches the one shown in Search Atlas for the correct website/project. If you have worked through these checks and the pixel is still not recognized, please have the following ready when you contact support: your Search Atlas project or website name, the Webflow site URL, and any error or status message shown in Search Atlas. 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 Data, Deployment History & Webflow

🛰️ What Data Does the OTTO Pixel Collect? The OTTO pixel is a lightweight tracking script you place on your website. It collects anonymised, session-level behavioural data to help OTTO understand how visitors interact with your pages. Specifically, it captures: - Page views and URL paths — which pages are visited and in what order. - Scroll depth — how far down a page a visitor scrolls. - Click events — interactions with links, buttons, and navigation elements. - Session duration — time spent on individual pages and across the full session. - Device and browser type — general environment data (e.g. mobile vs desktop, browser family). - Referral source — the channel or URL that brought the visitor to your site. The OTTO pixel does not collect personally identifiable information (PII) such as names, email addresses, or payment details. No individual user profiles are created. All data is processed solely to inform OTTO's on-page SEO recommendations and to measure the impact of deployed changes on engagement signals. 📋 How to View Previously Deployed Changes in OTTO OTTO keeps a full log of every change it has applied to your site so you can audit, review, or roll back at any time. 1. In the left sidebar, navigate to OTTO SEO, then open All Sites (SEO Automation). 2. Open the OTTO project you want to review. 3. Click the Deployment History tab near the top of the project dashboard. 4. You will see a chronological list of all deployed actions, each showing the date and time, the page or element affected, the type of change (e.g. title tag update, meta description, schema injection), and the deployment status (Active, Rolled Back, or Pending). 5. Click any entry to expand the full details, including the before and after values for that change. 6. To revert a specific change, click Roll Back next to the relevant entry and confirm the action. Deployment history is retained indefinitely for your project so you always have a complete record of what OTTO has modified. 🌐 Will OTTO Changes Be Visible in Webflow Developer Mode? This depends on how OTTO deploys changes to your Webflow site. JavaScript-injected changes (default method): OTTO deploys most SEO updates — such as meta tags, structured data, and canonical tags — by injecting them via the OTTO pixel script at page load. These changes are applied to the rendered DOM and are not written back into the Webflow Designer or CMS. As a result, they will not be visible in Webflow's Designer, Editor, or developer mode panels. However, they are fully visible to search engine crawlers and in your browser's View Page Source or Inspect Element tools on the live site. Direct CMS integration (if enabled): If you have connected OTTO to your Webflow site via the native CMS integration, certain content-level changes may be written directly to Webflow CMS fields. In this case, those specific changes will appear inside Webflow's Editor and CMS collections. Check your OTTO project settings under Integrations to confirm which deployment method is active for your Webflow site. Key takeaway: Always verify OTTO changes by viewing your live page source rather than relying on Webflow's Designer view, unless you are using the direct CMS integration. ✅ Quick Reference Summary - OTTO pixel collects: anonymised behavioural data only — no PII. - Deployment history: found in OTTO SEO → All Sites (SEO Automation) → your OTTO project → Deployment History tab. - Webflow Designer visibility: changes are not visible in Designer by default; use View Page Source on the live site to confirm. 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.

🤖 Install OTTO on HubSpot via Custom JavaScript

🧭 Overview If your website runs on HubSpot, you cannot use the Cloudflare integration to install OTTO. Instead, you will add the OTTO script directly to your HubSpot site's custom header HTML. This article walks you through every step, from copying your script to confirming OTTO is active. ⚙️ Before You Begin - You must have Admin or Super Admin access in your HubSpot account. - Your Search Atlas account must have an active OTTO seat assigned to the property you want to manage. - Make sure your website domain in Search Atlas matches the domain you are managing in HubSpot. 📋 Step 1: Copy Your OTTO Script from Search Atlas 1. Log in to Search Atlas and go to OTTO SEO → Installation Guide in the left sidebar. 2. Locate the property for machmanufacturing.io in your property list. 3. Click Activate OTTO or open the OTTO settings for that property. 4. On the Installation Guide page, click Copy Script. The script is a short <script> tag unique to your property. 🛠️ Step 2: Add the Script to HubSpot Site Header 1. Log in to your HubSpot account. 2. In the top navigation, click the Settings gear icon. 3. In the left sidebar, go to Website → Pages. 4. Select the tab for the site you want to update (for example, machmanufacturing.io). 5. Scroll down to the Site Header HTML section. 6. Paste your copied OTTO script into the text area. Place it just before the closing </head> tag if you see existing code, or simply paste it into the empty field. 7. Click Save at the bottom of the page. Important: The Site Header HTML field in HubSpot applies the script globally across all pages on your site. You do not need to add it page by page. 🔍 Step 3: Verify the Installation After saving, use the following methods to confirm OTTO is installed correctly. - Check in Search Atlas: Return to OTTO SEO → Installation Guide in Search Atlas for machmanufacturing.io. Look for a green Connected or Active status indicator. It can take up to 15 minutes for the status to update after you save the script in HubSpot. - Inspect your live site: Open your website in a browser, right-click anywhere on the page, and select View Page Source. Use Ctrl + F (or Cmd + F on Mac) to search for otto or the script tag you pasted. If it appears in the source, the script is live. - Use browser developer tools: Open your browser's developer tools with F12, go to the Network tab, reload the page, and filter requests by otto or your script's domain. A successful request with a 200 status confirms the script is loading. ⚠️ Common Issues and Fixes - Status still shows "Not Connected" after 15 minutes: Double-check that you saved the settings in HubSpot and that the script appears in your live page source. If the script is missing from the source, repeat Step 2. - Script is in the source but OTTO is not activating: Confirm the script you copied belongs to the correct property (machmanufacturing.io) and has not been modified after copying. - HubSpot Site Header HTML field is greyed out: You may not have the correct permissions. Ask your HubSpot Super Admin to make the change or to grant you the necessary access level. - Changes not appearing on the live site: HubSpot may be serving a cached version. Try a hard refresh with Ctrl + Shift + R (or Cmd + Shift + R on Mac), or check back after a few minutes. ❓ Frequently Asked Questions - Do I need Cloudflare to use OTTO? No. Cloudflare is one installation method, but it is not required. The custom JavaScript method described in this article works independently of Cloudflare. - Will this affect my HubSpot site performance? The OTTO script is lightweight and asynchronous. It loads without blocking your page content. - Can I add the script to only specific pages? OTTO requires site-wide installation to function correctly. Adding it only to selected pages will prevent it from working as intended. 💬 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.

🛠️ Install OTTO Pixel on Your GoDaddy Website

🔍 What This Guide Covers The OTTO pixel connects your GoDaddy website to Search Atlas so OTTO can track performance and apply SEO improvements automatically. This guide walks you through the full installation process using GoDaddy's built-in tools — no coding experience required. 📋 Before You Begin Make sure you have the following ready before you start: - Access to your Search Atlas account - Your GoDaddy account login credentials - Your GoDaddy website open in a separate browser tab 🔑 Step 1: Copy Your OTTO Pixel Code 1. Log in to Search Atlas. 2. In the left sidebar, click OTTO SEO → All Sites (SEO Automation). 3. Select your website project from the list, or create a new one if you have not added your site yet. 4. Inside the project, locate the OTTO Pixel section. You will see a short snippet of code. 5. Click the Copy button next to the pixel code. Keep this tab open — you will need the code in a later step. 🌐 Step 2: Log In to GoDaddy and Open Your Website Editor 1. Open a new browser tab and go to godaddy.com. 2. Click Sign In in the top-right corner and enter your GoDaddy credentials. 3. From your GoDaddy dashboard, click My Products. 4. Find your website and click Manage next to it. 5. Click Edit Website to open the GoDaddy website builder. 📝 Step 3: Add the Pixel Code Using GoDaddy's Header Settings GoDaddy's website builder lets you paste code into a global header section. This is the easiest and recommended method for beginners because it automatically applies the pixel to every page on your site. 1. Inside the GoDaddy website editor, click the Settings icon. This is usually represented by a gear icon in the left or top menu. 2. Look for an option called Website Settings, SEO, or Advanced. The exact label depends on your GoDaddy plan and template. 3. Find the field labelled Header Code, Custom Code, or Tracking Code. 4. Click inside that field and paste the OTTO pixel code you copied in Step 1. 5. Click Save or Apply to confirm your changes. 6. Publish your website by clicking the Publish button so the pixel goes live. 🛒 Step 3 (Alternative): GoDaddy Managed WordPress Sites If your GoDaddy website runs on WordPress, follow these steps instead of the instructions above: 1. From your GoDaddy dashboard, open your WordPress Admin panel. 2. In the WordPress left sidebar, go to Appearance → Theme File Editor. 3. On the right side of the screen, find and click the file named header.php. 4. Locate the closing </head> tag in the file. It will look exactly like that. 5. Paste your OTTO pixel code on the line directly above the </head> tag. 6. Click Update File to save. The pixel is now live on your site. Not sure which version you have? If you see a WordPress dashboard after clicking Manage, you have a WordPress site. If you see a drag-and-drop visual editor, use the standard steps in Step 3 above. ✅ Step 4: Verify the Pixel Is Working 1. Return to Search Atlas and navigate back to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Open your website project and go to the OTTO Pixel section. 3. Click Verify Pixel or Check Connection. Search Atlas will confirm whether the pixel is detected on your site. 4. If the pixel is detected, you will see a green confirmation message. OTTO is now connected and will begin tracking your site. 5. If verification fails, double-check that you published your GoDaddy site after saving the code, then try verifying again after a few minutes. ⚠️ Common Issues and Quick Fixes - Pixel not detected after verification: Make sure you clicked Publish in GoDaddy after saving the code. Unpublished changes are invisible to external tools. - Cannot find the Header Code field in GoDaddy: The field name varies by template. Try checking under Settings → SEO, Settings → Advanced, or Pages → Website Header. - Code disappeared after saving: Some GoDaddy templates strip certain characters. Paste the code again, then immediately click Save and Publish without making other edits first. - GoDaddy Managed WordPress — cannot find Theme File Editor: Your WordPress theme or user role may restrict access. Contact GoDaddy support to enable theme editing for your account. 💬 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.

🔗 Integrating Next.js Static Sites into Search Atlas

🧭 Overview Search Atlas connects to your website primarily through your public URL, which means static sites built with Next.js are generally supported — whether you use Static Site Generation (SSG), Incremental Static Regeneration (ISR), or a fully exported static build via next export. No server-side rendering is required for integration. This article covers two aspects of the original topic: connecting your Next.js site to Search Atlas and compliance certification questions that may arise during or after that process. ✅ Before You Begin Make sure the following are in place before connecting your Next.js site: - Your site is deployed and publicly accessible via a live domain (e.g., https://yoursite.com). - You have admin or owner access to your Search Atlas workspace. - You have access to your site's codebase or hosting platform if any verification steps are required. 🚀 Step 1 — Add Your Site to Search Atlas Log in to your Search Atlas account and locate the option to add a new site within your workspace. Enter your full domain URL (include https://) and proceed through the prompts shown in the platform. 🔍 Step 2 — Verify Site Ownership Search Atlas will present you with a verification method during the site setup flow. Follow the on-screen instructions provided at that step to confirm ownership of your domain. The exact verification options available to you will be displayed within the platform during setup. For Next.js sites, a common approach is to place any required verification code inside your project's <head> section — for example in pages/_document.js (Pages Router) or your root layout.tsx (App Router) — and then redeploy your site before confirming in Search Atlas. 🗺️ Step 3 — Submit Your Sitemap Next.js does not generate a sitemap automatically in all configurations. Once your site is added, submit your sitemap so Search Atlas can crawl your full page inventory: 1. Confirm your sitemap is publicly accessible (e.g., at https://yoursite.com/sitemap.xml). If you do not yet have one, the next-sitemap package is a common solution for Next.js projects. 2. In Search Atlas, locate the sitemap submission option within your site's settings in the platform. 3. Enter your sitemap URL and submit it. 📋 Compliance Certifications If your question involves compliance certifications (for example, questions about whether Search Atlas holds SOC 2, GDPR, or similar certifications, or whether your site's integration meets certain compliance requirements), this is handled on a case-by-case basis by the Search Atlas team. There are no self-serve compliance certificate downloads available in the platform at this time. When escalating a compliance certification question, please have the following ready: - The specific certification or compliance standard you are asking about (e.g., SOC 2 Type II, GDPR, ISO 27001). - Your company name and Search Atlas workspace details. - Any deadline or legal context that applies to your request. 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.

🔧 Install OTTO Pixel on GoDaddy Website Builder

🧭 Overview GoDaddy Website Builder (also called GoDaddy Websites + Marketing) does not allow you to paste code directly into the <head> section of your site. This is a platform limitation — not an issue with your OTTO pixel. This article walks you through the correct workaround so the pixel installs and verifies successfully. ⚠️ Before You Start - Make sure OTTO is activated for your project inside Search Atlas. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (or navigate to /seo-automation-v3) and confirm your site is connected. - Copy your unique OTTO pixel code from the OTTO dashboard. You will need it in the steps below. - Note: GoDaddy Website Builder is different from a WordPress site hosted on GoDaddy. If you have WordPress, you can paste the pixel into the <head> directly or use a plugin. 🛠️ Method 1 — Use GoDaddy's Built-In Tracking Code Field GoDaddy Website Builder has a dedicated field for third-party tracking codes. This is the recommended path for OTTO pixel installation. 1. Log in to your GoDaddy account and open your Website Builder editor. 2. In the editor, click Settings (the gear icon, usually in the top navigation bar). 3. Select Website Settings, then choose the GoDaddy Insight / Analytics or Tracking Codes tab. The exact label may vary depending on your GoDaddy plan. 4. Paste your full OTTO pixel code into the tracking code field. 5. Click Save, then Publish your site to push the changes live. Once published, GoDaddy injects this code into the <head> automatically on every page. You do not need to add it page by page. 🛠️ Method 2 — Use a GoDaddy HTML Section Block If your GoDaddy plan does not include a tracking code field, you can use an HTML section block as an alternative. This places the pixel in the page body rather than the head, which is still functional for OTTO tracking. 1. Open your Website Builder editor and navigate to the page you want to track. 2. Click Add Section and search for an HTML block or Custom Code block. 3. Drag the block to the very top of the page, above all other content. 4. Paste your OTTO pixel code inside the HTML block. 5. Repeat for any additional pages you want to track, or check if your theme supports a global footer/header section where you can add it once. 6. Click Save and Publish. Important: Placing the pixel in the page body instead of the <head> may cause a short delay in tracking page events. OTTO will still receive data, but the pixel fires slightly later in the page load sequence. This is expected behaviour for this method. ✅ How to Verify the Pixel Is Working 1. After publishing, wait 10–15 minutes before checking pixel status. 2. In Search Atlas, go to OTTO SEO → All Sites (SEO Automation) in the left sidebar and open your site's OTTO dashboard. 3. Look for a green Pixel Active indicator. If it shows as pending, wait up to 24 hours — GoDaddy's CDN can take time to fully propagate published changes. 4. Visit your live website in a browser, then return to OTTO and refresh the dashboard. An active pixel will register your visit as a confirmed signal. Do not run browser-based head-section diagnostics on a GoDaddy Website Builder site. Because GoDaddy manages the code injection on their servers, standard inspect-element checks may not show the pixel in the expected location. The OTTO dashboard confirmation is the reliable verification method. ⏱️ GTag and Data Population Timeline If OTTO is also collecting Google Tag (GTag) data alongside the pixel, keep these timelines in mind: - Pixel confirmation: 10 minutes to 24 hours after publishing. - First GTag data in Reports: Allow 48–72 hours after pixel activation. Go to Reports in the left sidebar (or /report-builder/projects-list) to view incoming data once it populates. - If no data appears after 72 hours, revisit the steps above and confirm your site was published — saving in the editor alone is not enough. ❓ Common Issues - I don't see a Tracking Codes tab in Settings. This field is available on most GoDaddy Websites + Marketing paid plans. If you are on a free or legacy plan, use Method 2 (HTML block) instead. - The pixel shows as inactive after 24 hours. Confirm the site was published after you saved the pixel code. Unpublished changes are not visible to OTTO. - I have multiple pages and Method 2 is time-consuming. Check if your GoDaddy theme includes a global header or footer section — adding the pixel there once will apply it site-wide. 💬 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.

🔌GHL OTTO Pixel Installation Guide

🔌 GHL OTTO Pixel Installation Guide This guide outlines the validated implementation to install the OTTO Pixel on websites built with GoHighLevel (GHL) (e.g., via Ideation), ensuring that OTTO's diagnostic tool successfully detects the pixel. ⚠️ This method has been tested across multiple client sites and is currently the most reliable approach. 📄 Step 1: Create a New Project Start inside your Search Atlas dashboard. - Left Sidebar → OTTO SEO → All Sites → + Create (top-right) - Follow the Setup Steps. 🌐 Step 2: Select or Add Your Website - Enter your full URL (e.g., https://yourdomain.com). - Wait for the green verification check mark confirming the domain. - Then click Continue. 📝 Step 3: Set up Fields (Optional) You will see fields for Business Information, Address, and Social Profiles. - These fields are optional for Pixel installation. - You may complete them now or later. Click Continue to proceed. 📎 Step 4: Copy Your OTTO Pixel Script Inside the Installation Guide: - Select Go High Level (GHL) from the CMS list. - Click the Video Guide Card, then scroll to Pixel Code. - Click Copy to copy your OTTO Pixel <script>. - (Optional) Click Email My Developer to send the snippet. - Click Step by step for detailed GHL instructions. - Click Continue in the bottom right corner. Stop here — now switch to your Go High Level (GHL) dashboard to insert the script before returning to Search Atlas. ⚠️ Important: Use the Correct (White-Label) Pixel Variant If your OTTO project uses a white-label/custom API endpoint (e.g., https://search.yourdomain.com/), make sure you copy the white-label version of the JavaScript pixel — not the default one that gathers data via dashboard.searchatlas.com. Using the wrong (non-white-label) pixel can cause the OTTO project to intermittently display the wrong domain across site accounts and may require daily manual scans to temporarily correct the issue. Confirm the script you copy references your project's correct API endpoint before installing it. 🛠️ Step 5: Open the Website Inside GHL and Install the Script - In the Home page editor, click the + icon at the top left corner of the page. - Scroll down to the Custom category in the element list. - Locate the Code box. - Drag and drop this Code block into the header area of your homepage layout. - Paste the OTTO Pixel <script> tag into that HTML block. - After inserting the script, mark the section as a Global Section. This ensures it loads across all pages using this section. - When saving: a modal titled “Section Changes Made” will appear. Confirm that you're applying changes to the Global Section. - Click Save. 🔍 This step is crucial — it ensures the OTTO Pixel script loads site-wide and can be detected by the diagnostic tool. ⚠️ Important clarification: The “header section” does not mean the top of the visible page (above your logo, banner, or navigation). It refers to the technical header area — the upper structural section of your layout where global scripts are placed. 🚀 Step 6: Activate in Search Atlas Once OTTO completes the initial setup for your project, your website appears inside the OTTO SEO (📊) Automation dashboard. Click on your project. Then you'll see: - Your domain name at the top (e.g., https://yourdomain.com). - Below it, your SEO performance metrics, including: - Healthy Pages (pages scanned so far) - OTTO Grader (overall site health score) - Content, Authority, Technicals, UX Signals (the four SEO pillar indicators) - On the right side of the site row, you'll see a red status label such as “Not Installed” or “OTTO Not Detected” until the pixel is verified. 🧰 Troubleshooting: Wrong Domain Displayed in OTTO Project Symptom: Your OTTO project intermittently shows the wrong domain (e.g., another client's domain appears in your site account), and only a manual daily scan temporarily resolves it. Cause: The installed JavaScript pixel is the non-white-label version, which gathers OTTO API data from dashboard.searchatlas.com instead of your project's correct (white-label) API endpoint (e.g., https://search.yourdomain.com/). Fix: 1. Remove the existing pixel from your GHL site's header. 2. Return to Search Atlas and copy the correct white-label JavaScript pixel tied to your project's API endpoint. 3. Reinstall it in the GHL header as a Global Section (see Step 5). 4. Save and confirm the change applies globally. Once the correct pixel is installed and detected, the wrong-domain issue should not recur and daily manual scans will no longer be required.