# **🧭 Overview**

When title tags, meta descriptions, and headings are marked as deployed in the Search Atlas dashboard but are not showing up on your live website, the most common cause is an incomplete OTTO script or UUID installation. This means the script is either missing from certain pages, installed incorrectly, or not firing properly on your platform. This article walks you through diagnosing and fixing the issue across WordPress, Shopify, Webflow, and custom-built websites.

# **🔍 Step 1 — Confirm the Issue Is Script-Related**

Before diving into platform-specific steps, verify that the OTTO script is the root cause:

1. Go to **Left sidebar → OTTO SEO → All Sites (SEO Automation)** (URL: **/seo-automation-v3**).
2. Open the OTTO project for your website and check which pages show deployed changes.
3. Visit one of those pages in your browser, right-click the page, and select **View Page Source**.
4. Use **Ctrl+F** (or **Cmd+F** on Mac) to search for **otto** or your unique **UUID** string.
5. If the script is not found in the page source, the script is missing from that page.
6. Repeat this check on two or three additional pages to determine whether the problem is isolated to specific pages or affects your entire site.

**Important:** A partial installation — where the script exists on some pages but not others — is the most frequent reason deployed changes appear only on part of your website.

# **🟦 WordPress**

If your site is built on WordPress, the OTTO script should be loaded globally via a plugin or your theme. A partial installation usually means the script was added to only one template or page.

1. Log in to your WordPress admin dashboard.
2. Navigate to **Appearance → Theme File Editor** or open your active theme's **header.php** file.
3. Confirm the OTTO script tag with your UUID appears inside the **<head>** section.
4. If you used a plugin such as **Insert Headers and Footers** or **WPCode**, open that plugin and verify the script is set to load on **All Pages**, not just the front page or specific post types.
5. Clear any caching plugins (e.g., WP Rocket, W3 Total Cache) and visit your site again to recheck the page source.

# **🟩 Shopify**

On Shopify, the OTTO script must be placed in the theme layout file so it loads across every page of your store.

1. In your Shopify admin, go to **Online Store → Themes → Edit Code**.
2. Open the **theme.liquid** file (or your active layout file).
3. Confirm the OTTO script tag with your UUID is placed inside the **<head>** tags, not inside a section or block file.
4. If the script is in a section file, it will only load on pages that include that section — move it to **theme.liquid**.
5. Save the file, then use Shopify's Preview mode to check the page source on your homepage, a product page, and a collection page.

# **🟪 Webflow**

In Webflow, scripts added at the page level only affect individual pages. The OTTO script must be added at the site level to deploy across all pages.

1. Open your project in the **Webflow Designer**.
2. Go to **Project Settings → Custom Code**.
3. Paste the OTTO script tag with your UUID into the **Head Code** field under the **Site-wide** section — not under any individual page settings.
4. Click **Save Changes** and publish your site.
5. If you previously added the script under a specific page's custom code, remove it from there to avoid duplicate or conflicting instances.

# **⚙️ Custom or Other Platforms**

For websites built on custom frameworks, static site generators, or other CMS platforms, the goal is the same: ensure the OTTO script loads in the **<head>** of every page.

1. Locate the global layout or master template file for your platform — this is typically named **layout.html**, **base.html**, **\_layout.liquid**, or similar.
2. Paste the full OTTO script tag with your UUID inside the **<head>** element of that file.
3. If your platform uses a build process (e.g., Next.js, Gatsby, Hugo), redeploy or rebuild the site after adding the script.
4. For static HTML sites, you must add the script to the **<head>** of every individual HTML file, or consolidate pages into a shared template.
5. After updating, verify the script appears in the source of at least three different page types on your live site.

# **✅ Step 2 — Re-Verify in Search Atlas After Fixing**

1. Once the script is confirmed present across your pages, return to **Left sidebar → OTTO SEO → All Sites (SEO Automation)** (URL: **/seo-automation-v3**).
2. Open your OTTO project and trigger a re-scan or refresh the deployment status for the affected pages.
3. Allow up to 15 minutes for changes to propagate, then revisit your live pages and check the title tags, meta descriptions, and headings directly in the page source.
4. You can also use the **Website Studio** (**Left sidebar → Website Studio**, URL: **/website-studio**) to review on-page SEO element status after redeployment.

# **⚠️ Common Mistakes to Avoid**

- **Adding the script at page level instead of site level** — always use a global template or layout file.
- **Incorrect UUID** — copy the UUID exactly from your OTTO project settings; extra spaces or characters will break the connection.
- **Caching** — cached versions of pages may hide a freshly added script; always clear your cache before re-testing.
- **Multiple script instances** — having the script in both a global template and individual pages can cause conflicts; keep only one instance.

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