Search Atlas Help Center

🔌 Connect OTTO to Your Webflow Site Successfully

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🧭 Overview

Connecting OTTO to a Webflow site is different from a WordPress setup. Webflow does not support plugins, so you must add the OTTO tracking code manually — either through Google Tag Manager (GTM) or a JavaScript Pixel embedded directly in your site settings. Using both methods at the same time is the most common cause of connection failures on Webflow.

This article walks you through the correct setup, explains how to identify and fix the GTM vs. JavaScript Pixel conflict, and covers Google Search Console (GSC) connection troubleshooting specific to Webflow.

⚙️ How to Access OTTO

In Search Atlas, open the left sidebar and click OTTO SEO. From the OTTO SEO dashboard, select or create the project you want to connect, then follow the steps below.

🚦 Choose One Connection Method Only

Before you add any code to Webflow, decide which method you will use. Installing both causes a conflict that prevents OTTO from verifying your site.

  • Google Tag Manager (GTM): Best if you already use GTM on your site or manage multiple tracking scripts. You add one GTM container snippet to Webflow and fire the OTTO pixel as a tag inside GTM.
  • JavaScript Pixel (direct embed): Best if you do not use GTM. You paste the OTTO script directly into your Webflow site settings under the custom code section.

Pick one method and make sure the other is completely removed before testing the connection.

📋 Method 1 — Connect via JavaScript Pixel (Direct Embed)

  1. In Search Atlas, go to OTTO SEO and open your project's OTTO connection settings. Copy the OTTO JavaScript Pixel snippet provided.
  2. In Webflow, open your project and go to Site Settings → Custom Code.
  3. Paste the OTTO snippet into the Head Code field.
  4. Click Save Changes, then publish your Webflow site.
  5. Return to Search Atlas and click Verify Connection in the OTTO setup panel.

Important: If you previously added OTTO through GTM, remove that GTM tag before publishing. Having the pixel fire from both GTM and the direct embed will cause a duplicate-signal conflict and the verification will fail.

📋 Method 2 — Connect via Google Tag Manager

  1. In Search Atlas, go to OTTO SEO and open your project's OTTO connection settings. Copy the OTTO JavaScript Pixel snippet.
  2. In your GTM workspace, create a new tag. Set the tag type to Custom HTML and paste the OTTO snippet into the HTML field.
  3. Set the trigger to All Pages and save the tag.
  4. In Webflow, go to Site Settings → Custom Code and confirm the GTM container snippet (the one starting with GTM-) is present in the Head Code field. This is your GTM container only — do not add the OTTO pixel snippet here as well.
  5. Publish your Webflow site, then submit and publish your GTM container.
  6. Return to Search Atlas and click Verify Connection in the OTTO setup panel.

🔍 Diagnosing the GTM vs. JavaScript Pixel Conflict

If OTTO still shows as unverified after following either method, a dual-installation conflict is likely the cause. Check for it by following these steps:

  1. In Webflow, go to Site Settings → Custom Code and review the Head Code and Footer Code fields. If you see both a GTM container snippet and a standalone OTTO JavaScript snippet, you have a conflict.
  2. Inside GTM, open your container and search for any existing OTTO or Search Atlas tags. If you find one there while also having the pixel in Webflow's custom code, that confirms the conflict.
  3. Remove the version you are not using, publish your Webflow site (and your GTM container if applicable), then click Verify Connection again in Search Atlas.

🔗 Fixing the GSC Connection on Webflow

If your Google Search Console property is not connecting, this is usually a separate verification issue unrelated to the OTTO pixel conflict. Follow these steps:

  1. In Google Search Console, confirm you have added a property for your Webflow domain and that verification is complete. Webflow users most commonly verify via the HTML tag method or the Google Analytics integration.
  2. In Search Atlas, go to your project settings and reconnect GSC by selecting your verified property from the dropdown. If your property does not appear, click Reconnect Google Account and re-authorise access.
  3. Make sure the Google account you used to connect GSC in Search Atlas is the same account that owns the GSC property. A mismatch here will prevent the property from appearing.
  4. After confirming the property is visible and selected, save your project settings and allow up to 15 minutes for data to populate.

✅ Quick Checklist Before Contacting Support

  • Only one OTTO connection method (GTM or JavaScript Pixel) is active — not both.
  • Your Webflow site has been published after any code changes.
  • Your GTM container has been submitted and published if using the GTM method.
  • Your GSC property is fully verified in Google Search Console.
  • The Google account connected in Search Atlas matches the GSC property owner.
  • You clicked Verify Connection in the OTTO panel after completing all changes.

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