🧭 Overview

Connecting OTTO SEO to a Webflow site requires a specific installation method. Because Webflow restricts how custom code is injected, using the wrong method — or mixing two methods — creates a conflict that blocks both OTTO activation and Google Search Console (GSC) verification. This article explains why this happens and how to fix it.

⚠️ Why the Conflict Happens

OTTO can be connected to your site in two ways:

• Google Tag Manager (GTM) — the pixel fires through an existing GTM container.
• JavaScript Pixel — the pixel is pasted directly into your site's code.

Webflow sites frequently have both GTM and a custom code section active at the same time. If the OTTO pixel is present in both locations, the duplicate tags conflict with each other. This causes OTTO to fail its site verification check and prevents GSC from confirming site ownership, even if you have followed the setup video exactly.

🔍 How to Diagnose the Conflict

1. In your browser, open your Webflow site and press Ctrl + U (or Cmd + U on Mac) to view the page source.
2. Press Ctrl + F and search for your OTTO pixel ID or the Search Atlas script tag.
3. If the pixel appears more than once in the source, you have a duplicate conflict.
4. Also check whether a GTM container script (GTM-XXXXXXX) is present — this confirms GTM is active on the page.

🛠️ How to Fix the Conflict

You must choose one installation method and remove the other completely. We recommend the method that matches how your site is already set up.

Option A — Use GTM only (recommended if GTM is already on your site):

1. Log in to your Google Tag Manager account.
2. Open the container for your Webflow site.
3. Create a new Custom HTML tag and paste the OTTO JavaScript pixel inside it.
4. Set the trigger to All Pages and publish the container.
5. Go to your Webflow Designer, open Site Settings → Custom Code.
6. Delete any Search Atlas or OTTO script tags from the Head Code and Footer Code fields.
7. Save and publish your Webflow site.

Option B — Use the JavaScript Pixel only (recommended if you do not use GTM):

1. Go to your Webflow Designer, open Site Settings → Custom Code.
2. Paste the OTTO JavaScript pixel into the Head Code field.
3. Make sure the same pixel is not also firing through GTM. Open GTM and delete or pause any existing OTTO/Search Atlas tags.
4. Save and publish your Webflow site.

📊 Reconnect OTTO and Verify GSC

After cleaning up the duplicate, complete the reconnection in Search Atlas:

1. In the left sidebar, go to OTTO SEO and open SEO Automation (URL: /seo-automation-v3).
2. Select your project and open the OTTO SEO settings.
3. Click Verify Site. OTTO will re-check for the pixel on your live Webflow URL.
4. Once OTTO verification passes, return to Google Search Console and run the ownership verification again. GSC reads the same pixel tag, so it should now confirm successfully.

Important: Always click Publish in Webflow after making any custom code changes. Webflow does not push code changes to your live site until you publish — this is the most common reason verification appears to fail even after following the steps above.

✅ Quick Checklist Before You Verify

• The OTTO pixel appears exactly once in your live page source.
• You are using only one installation method (GTM or JavaScript, not both).
• Your Webflow site has been published after the code change.
• You are verifying the exact URL added to your Search Atlas project (www vs. non-www matters).
• Your GTM container is published, not just saved, if you are using the GTM method.

💬 Still Need 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.