## **🔍 Overview**

OTTO SEO makes on-page changes by injecting optimised content directly into your site. On platforms like WordPress and Shopify, OTTO connects at the source level — meaning edits land in the actual page content and persist reliably. On **Webflow**, this source-level integration is not currently available, which limits what OTTO can do out of the box.

This article explains why that limitation exists, what OTTO can still accomplish on Webflow, and how a **Cloudflare Worker** can serve as a practical workaround to extend OTTO's reach.

## **⚙️ Why Webflow Has Client-Side Limitations**

OTTO's pixel operates client-side on Webflow, meaning it runs in the visitor's browser after the page has already loaded from Webflow's servers. This creates two key constraints:

- **No source-level writes:** OTTO cannot push changes directly into Webflow's CMS or page structure the way it can on WordPress or Shopify.
- **Rendering dependency:** Changes injected client-side may not be visible to all search engine crawlers, since some crawlers do not fully execute JavaScript before indexing.

As a result, certain OTTO optimisations — such as rewriting heading tags, updating meta content at render time, or modifying body copy — have limited or no effect on Webflow sites when relying solely on the pixel.

## **🗺️ Is a Source-Level Webflow Integration on the Roadmap?**

A native source-level fix for Webflow — comparable to the WordPress or Shopify integrations — is **not currently on the active roadmap**. Webflow's closed hosting architecture does not expose the same server-side hooks that other CMS platforms provide, making a direct equivalent technically complex to deliver.

We continue to evaluate platform integrations based on customer demand and technical feasibility. If this is important to your workflow, please share your feedback through the chat widget (details at the bottom of this article) so our team can log it as a feature request.

## **🚀 Cloudflare Worker: The Recommended Workaround**

If your Webflow site is proxied through **Cloudflare**, you can use a **Cloudflare Worker** to intercept and modify page HTML before it is delivered to the browser or crawler. This approach effectively moves OTTO's changes server-side, giving you similar behaviour to a native CMS integration.

Here is how the solution works at a high level:

1. **Your domain is proxied through Cloudflare** — traffic passes through Cloudflare before reaching visitors.
2. **A Cloudflare Worker is deployed** on your zone — this is a lightweight script that runs at Cloudflare's edge network.
3. **The Worker fetches OTTO's optimised output** and injects it into the HTML response before the page is served, making the changes visible to crawlers and browsers alike.
4. **Search engines receive fully rendered, optimised HTML** — no JavaScript execution required on their end.

## **✅ What the Cloudflare Worker Approach Enables**

- Meta title and description updates that are crawler-visible
- Heading tag modifications applied at the response level
- Body copy changes that do not rely on JavaScript rendering
- Behaviour closer to a source-level integration without requiring Webflow CMS access

## **📋 Prerequisites Before You Begin**

- Your Webflow site's domain must be **proxied through Cloudflare** (orange cloud enabled in your Cloudflare DNS settings).
- You need access to a Cloudflare account with **Workers enabled** (available on the free plan and above).
- Your OTTO pixel must already be installed on your Webflow site. To verify, go to **Left sidebar → OTTO SEO → Installation Guide** and confirm the pixel is active.

## **🛠️ Setting Up the Cloudflare Worker**

The exact Worker script will depend on how your OTTO configuration is structured. Follow these steps to get started:

1. Log in to your **Cloudflare dashboard** and select the zone (domain) connected to your Webflow site.
2. Navigate to **Workers & Pages** and create a new Worker.
3. Contact the Search Atlas support team (see below) to receive the **Worker script template** tailored to your OTTO site configuration. Our team will provide the script and your site-specific parameters.
4. Paste the script into the Worker editor and **deploy** it.
5. Add a **Worker Route** that maps the Worker to your domain (e.g., `yourdomain.com/*`).
6. Return to **Left sidebar → OTTO SEO → Overview** in Search Atlas and run a new **Scan** to verify that OTTO's changes are now being picked up correctly.

## **⚠️ Important Considerations**

- The Cloudflare Worker approach requires ongoing maintenance if your Cloudflare or Webflow configuration changes.
- Worker execution adds a small amount of latency at the edge — this is typically negligible but worth monitoring via Cloudflare's analytics.
- This workaround does not give OTTO write access to your Webflow CMS; it only modifies the HTML delivered to the end user and crawler at the network edge.

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