Use this guide to manually inspect and validate your OTTO pixel on any platform — WordPress, Shopify, Wix, Webflow, GoHighLevel, Lovable, and custom-coded sites. A missing, duplicated, or UUID-mismatched pixel prevents OTTO from crawling, activating, and deploying on-page optimisations.

# **🛠️ Step 1: Run the Official Diagnostic Scan (Always Do This First)**

The Diagnostic Scan confirms:

- Pixel presence
- Correct UUID
- Duplicate installs
- Engagement status
- Partial installs
- Improper placement

## **Navigate to the Diagnostic Scan**

**OTTO SEO → All Sites → select your site → click Scan → click Run Diagnostics Scan**

You can scan:

- The homepage
- Any specific URL
- Recently added pages
- Subdomains

**Important:** Diagnostics confirms whether the pixel is detected. It does not confirm whether the pixel fires — that requires manual browser inspection in Step 3.

**Known limitation (as of May 2026):** OTTO may display as installed even when the project UUID does not match the UUID embedded on the site. If OTTO reports a `wrong_uuid` status or shows the feature as not connected, the live site likely contains a stale UUID from a previous project — even if you recently installed a new snippet. Proceed to Step 3 to verify the UUID in the script tag matches the UUID in your current OTTO project dashboard. If they differ, follow the fix in the **UUID Mismatch** section below.

# **🌐 Step 2: Open the Website in a Clean Environment**

To avoid login-based suppression or cached versions, access the site using:

- Incognito / Private Mode
- All browser extensions disabled
- The exact domain variant configured in Search Atlas: `https` vs `http`, `www` vs non-www, correct subdomain, no staging URLs

OTTO cannot detect a pixel installed on a different domain variant. You now have a clean session that reflects exactly what OTTO's crawler sees.

# **🔎 Step 3: Inspect the Pixel in DevTools (Manual Validation)**

## **Open DevTools**

Right-click anywhere on the page → **Inspect** → open the **Elements** panel.

## **Search the Page for OTTO Code**

Press **CTRL + F** (Windows) or **CMD + F** (Mac), then search for:

- `sa-dynamic-optimization`
- `searchatlas`
- `data-uuid`

## **Expected Pixel Locations**

- Inside the `<head>`
- Injected dynamically in the `<body>` on render

Both locations are valid depending on your CMS.

**Note on rendering layers:** Browser DevTools and Google's URL Inspection tool confirm JS-rendered output. Some OTTO edge-level changes (e.g., H1 deployments) may not appear in raw HTML fetched by AI crawlers or non-JS bots (ChatGPT, Perplexity, Claude). To verify raw HTML output, use `curl` or a server-side fetch tool and inspect the response body directly.

If you find the script tag, the pixel is present in the rendered DOM.

# **✅ Step 4: Confirm the Pixel Structure**

The OTTO Pixel always includes two components. Verify both are present.

## **A. The Loader Script**

`<script src="https://cdn.searchatlas.com/otto/loader.min.js" data-noptimize></script>`

Verify all of the following are intact:

- `id="sa-dynamic-optimization-loader"` present on the script tag
- Correct UUID in the `data-uuid` attribute — must match the site's current project in Search Atlas
- CDN path intact with no corruption from minifiers
- Both attributes present: `data-noptimize` and `data-cfasync="false"`

## **B. The Base64 Script Block (Core Logic)**

Search Atlas injects a Base64-encoded script block that initialises OTTO's core tracking and optimisation logic. Verify the block is present and not truncated — a partial or corrupted block prevents OTTO from activating even when the loader script is correctly placed.

# **🔑 Fix a UUID Mismatch on a Lovable-Hosted Site**

If OTTO reports a `wrong_uuid` status or shows the feature as not connected on a Lovable-hosted site, the most common cause is a stale script tag from a previous project still embedded in `index.html`. Follow these steps to replace it.

1. Open your project at [lovable.dev](https://lovable.dev) and sign in.
2. Click **Code editor** in the left sidebar.
3. Navigate to the **public/** folder and open **index.html**.
4. Search the file for the existing OTTO script tag — search for `searchatlas` or `sa-dynamic-optimization`.
5. Delete the old script tag entirely.
6. In Search Atlas, go to **OTTO SEO → All Sites → select your site → OTTO Pixel** and copy the current pixel snippet.
7. Paste the new snippet into `index.html` inside the `<head>` tag.
8. Save and commit — Lovable automatically redeploys on save.

After the redeploy completes, return to Search Atlas and run the Diagnostic Scan again to confirm OTTO detects the correct UUID.

**Alternative:** If you have a previously verified project that already has the correct UUID embedded on the live site, switch to that project in Search Atlas under **OTTO SEO → All Sites** instead of updating the pixel.

# **⚠️ Common UUID Mismatch Causes (All Platforms)**

If OTTO reports a UUID mismatch or `wrong_uuid` status on any platform, check these common causes:

- A previous OTTO project's pixel snippet was never removed before installing a new one.
- A page builder or caching plugin preserved the old script tag after you updated it.
- The snippet was installed on a staging environment instead of the production domain.
- The UUID in the pixel does not match the current project — compare the `data-uuid` value visible in DevTools against the UUID shown in your OTTO project dashboard in Search Atlas.

The issue is resolved when the Diagnostic Scan shows the UUID matches and OTTO status changes to connected.

**🎯 You now know how to inspect, validate, and fix your OTTO pixel on any platform, including Lovable-hosted sites. If OTTO still reports a UUID mismatch after following these steps, contact Search Atlas support with your project UUID and domain so the team can diagnose the issue directly.**