# **🔌 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.