## **🔍 Overview**

OTTO SEO connects to your website through a JavaScript pixel that is installed on your pages. On some platforms, OTTO can write changes directly to your page content at the source level — meaning edits land inside the actual CMS and persist as real content updates. On **Webflow**, this deeper integration is not yet available.

This article explains what that means for your site, why the limitation exists, and what the current situation looks like.

## **⚙️ How the OTTO Pixel Works on Webflow**

When you install OTTO on a Webflow site, the pixel is injected as a client-side JavaScript snippet. This means OTTO can:

- Read and analyse your page content
- Surface SEO recommendations and audit findings
- Apply certain on-page changes via the browser at render time

However, because the pixel operates client-side, it cannot write changes back into Webflow's CMS or Designer. Any modifications OTTO applies are rendered in the browser layer — they are not stored as permanent edits inside your Webflow project.

## **🚧 Why a Source-Level Fix Is Not Yet Available**

Webflow uses a closed Designer environment and a separate CMS API that requires a different integration approach — one that goes beyond what a client-side pixel can do on its own. Bridging OTTO's automation engine with Webflow's CMS API at a source level is a significant technical undertaking, and this capability is not currently available.

## **📊 What This Means for Your Webflow Site Right Now**

If you are running OTTO on a Webflow site, here is what you can expect:

- **SEO audits and recommendations** work fully — OTTO will scan your site and surface issues through the standard audit workflow.
- **Client-side optimisations** applied by the pixel are active while the pixel is loaded, but are not written into Webflow's source content.
- **Manual implementation** is currently required — to make OTTO's recommendations permanent, you or your team will need to apply the suggested changes directly inside the Webflow Designer or CMS editor.

## **🛠️ Interim Workaround: Applying OTTO Recommendations Manually in Webflow**

While native CMS-write is unavailable, you can still action every OTTO recommendation by following these steps:

1. **Run an OTTO audit** on your Webflow site. Navigate to OTTO SEO → Site Audit in the left sidebar, select your project, and open the Audit or Recommendations panel to see a prioritised list of issues.
2. **Export or note the specific recommendations** — for example, missing meta titles, meta descriptions, heading structure issues, or alt-text gaps. OTTO surfaces the exact field and suggested value for each finding.
3. **Log in to your Webflow project** and open the page or CMS Collection that contains the flagged content.
4. **For static pages:** Open the page in the Webflow Designer, click the relevant element or use the SEO settings panel (Page Settings → SEO tab) to update meta title, meta description, Open Graph fields, or on-page content as recommended by OTTO.
5. **For CMS Collection items:** Go to your Webflow CMS editor, open the relevant Collection, and edit the individual item fields (e.g., SEO Title, Meta Description, or custom fields) to match OTTO's suggested values.
6. **Publish your Webflow site** after making changes so that updates go live and are reflected when OTTO re-scans the page.
7. **Re-run the OTTO audit** to confirm the issues are resolved and track your progress over time.

Repeating this workflow for each audit cycle allows you to systematically implement OTTO's recommendations even without automated CMS-write support.

## **🗺️ Roadmap Status**

A native, source-level Webflow integration — one that writes changes directly into your Webflow CMS — is **not available at this time**. There is no confirmed delivery date for this capability.

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.