# **🔍 Why Your OTTO Pixel May Show 'Not Installed Correctly'**

After adding the OTTO pixel to your Squarespace site, the verification check may still return a **not installed correctly** status. This is a common issue and is almost always caused by one of a few specific configuration mistakes in Squarespace's header injection settings. This article walks you through every step to confirm your pixel is placed and verified correctly.

# **⚙️ How the OTTO Pixel Verification Works**

When you click **Verify** inside Search Atlas, OTTO sends a request to crawl your live Squarespace site and look for your unique pixel code in the page source. If the pixel is missing, blocked, or placed in the wrong location, verification will fail. It does **not** check your Squarespace editor — it checks your published, live site.

# **✅ Step-by-Step: Correct Pixel Installation in Squarespace**

1. Log in to your **Squarespace** account and open your site editor.
2. In the left sidebar, go to **Settings** → **Advanced** → **Code Injection**.
3. Paste your OTTO pixel snippet into the **Header** field only. Do not place it in the Footer or any other field.
4. Click **Save** in Squarespace before returning to Search Atlas.
5. In Search Atlas, navigate to **OTTO SEO** in the left sidebar, then open **SEO Automation** (URL: **/seo-automation-v3**).
6. Locate your connected site, then click **Verify** to re-run the installation check.

# **🚫 Common Reasons Verification Fails**

- **Page not published:** Squarespace only injects header code on published pages. If your site is in trial mode or password-protected, the crawler cannot access the pixel.
- **Password protection enabled:** A site-wide or page-level password blocks the OTTO crawler. Temporarily disable password protection, verify the pixel, then re-enable it.
- **Changes not saved:** Squarespace requires an explicit Save after adding code. Navigating away without saving discards the pixel.
- **Pixel placed in the wrong field:** Placing the snippet in the **Footer** or a page-specific injection area instead of the global **Header** field can cause verification to fail.
- **Duplicate or edited pixel code:** Copy the pixel directly from Search Atlas each time. Do not retype it or modify any characters — even a single extra space can break detection.
- **Caching delay:** Squarespace may cache pages for a few minutes after saving. Wait 2–3 minutes after saving, then click Verify again.

# **🔎 How to Confirm the Pixel Is Live on Your Site**

Before clicking Verify in Search Atlas, manually confirm the pixel is visible in your published site's source code:

1. Open your live Squarespace site in a browser (not the editor).
2. Right-click anywhere on the page and select **View Page Source**.
3. Press **Ctrl+F** (or **Cmd+F** on Mac) and search for **otto** or the first few characters of your pixel snippet.
4. If you can find the pixel in the source code, your installation is correct — return to Search Atlas and click **Verify**.
5. If you cannot find the pixel, revisit the Code Injection steps above and ensure the snippet was saved in the Header field.

# **💡 Tips for a Smooth Verification**

- Always copy your pixel code fresh from the Search Atlas dashboard to avoid stale or corrupted snippets.
- Use an incognito or private browser window when viewing your page source to avoid cached versions.
- If your Squarespace plan does not include **Code Injection** (available on Business plans and above), you will need to upgrade your Squarespace plan before the pixel can be installed.
- After a successful verification, avoid editing or removing the pixel code from Squarespace — doing so will disconnect OTTO from your site.

# **🆘 Still Showing 'Not Installed Correctly'?**

If you have followed every step above and verification still fails, there may be a plan-level restriction, a Squarespace-side caching issue, or a less common configuration conflict on your account. 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.