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