How to connect a Webflow site to Agent Analytics (via Cloudflare)

Agent Analytics works by reading the AI-bot visits recorded at your site's edge. Webflow, however, doesn't expose server logs or let you run server-side code.

A workaround is to place a free Cloudflare account in front of your Webflow site. Cloudflare sees every request (including AI crawlers), a lightweight OtterlyAI Worker records the AI-bot visits, and everything else passes straight through to Webflow untouched. Webflow officially supports this setup, it's known as "Orange-to-Orange", and it has no effect on your visitors or your site's performance.

This guide walks through the whole setup.

⚠️ Your Webflow site needs a paid Site plan — not a Workspace plan.

Webflow sells two different kinds of plan, and it's easy to buy the wrong one:

• Workspace plans (Starter, Freelancer, Agency) cover seats and collaboration. They do not allow custom domains.
• Site plans (Basic, Premium, Enterprise) are bought per site under Site settings → Plans, and are what unlock a custom domain.

Basic is enough if your site has no CMS collections. If it does, Webflow requires Premium.

You'll also need:

• Access to your domain's registrar (where you bought the domain), so you can change its nameservers.
• A free Cloudflare account. Create one at dash.cloudflare.com if you don't already have one.

Step 1 — Webflow: confirm the plan and add the domain

1. Open Site settings → Plans. The Website tab must show Basic, Premium or Enterprise as current. If it shows Starter (or only a Workspace plan), purchase a Site plan before continuing.
2. Open Site settings → Publishing.
3. Click Add a custom domain → Manually add domain. Enter yourdomain.com and accept adding www.yourdomain.com as well.
4. Click Make default on www.yourdomain.com.
   
   
5. Copy the _webflow TXT record value shown under "Verification required" — you'll need it in Step 2. Ignore the A record and the proxy-ssl.webflow.com CNAME; you won't use them.
   
   

Step 2 — Cloudflare: add the zone

1. In Cloudflare, click Add a domain, enter yourdomain.com, and choose the Free plan.
2. Review the imported DNS records. Delete any A or CNAME records for @ and www that point to your old host. Keep your MX and TXT records — they carry your email settings.
3. Add these three records:

   Type	Name	Value	Proxy status
   CNAME	@	cdn.webflow.com	Proxied 🟠
   CNAME	www	cdn.webflow.com	Proxied 🟠
   TXT	_webflow	one-time-verification=<value you copied in Step 1>	DNS only ⚪

   The orange cloud (Proxied) on the two CNAMEs is what routes traffic through Cloudflare; this is the "Orange" part of Orange-to-Orange, and it's what lets Agent Analytics see AI-bot visits.
4. Click Continue to activation and note the two nameservers Cloudflare assigns you, you'll need them in Step 3.

Step 3 — Registrar: switch nameservers

1. At your registrar, replace the current nameservers with the two Cloudflare gave you in Step 2. If DNSSEC is enabled, turn it off.
2. Back in Cloudflare, click Check nameservers. Activation usually takes a few minutes, occasionally a few hours.

Step 4 — Cloudflare: zone settings

1. SSL/TLS → Overview: set the encryption mode to Full (strict).
2. Security → Bots: turn Bot Fight Mode off.
3. AI Crawl Control: make sure no category is blocked.

⚠️ This is the most common reason Agent Analytics shows no data. Cloudflare blocks AI crawlers by default on new zones, and a blocked crawler never reaches your site or the OtterlyAI Worker, so it can't be counted. Confirm AI Crawl Control is not blocking anything before moving on.

Step 5 — Webflow: verify and publish

1. Once the Cloudflare zone shows Active, return to Webflow Site settings → Publishing and click Verify domain on both domains.
2. Click Publish, tick the production domains, and publish. The domains may keep showing an "Update needed" badge, this is expected with the Cloudflare proxy and can be ignored as long as the site loads.
3. Open https://www.yourdomain.com and confirm the site loads normally.

Step 6 — Cloudflare: create an API token for OtterlyAI - A full guide.

OtterlyAI needs a scoped API token to deploy and manage the Worker that records AI-bot visits.

1. Click your profile icon → API Tokens → Create Token → Custom token. Set these permissions:

   Scope	Permission	Access
   Account	Workers Scripts	Edit
   Zone	Workers Routes	Edit
   Zone	Zone	Read

   Under Zone Resources, include only yourdomain.com.
2. Continue to the summary, click Create Token, and copy the token. It is shown only once.

🔒 Treat this token like a password. Keep the permissions and zone scoped exactly as above — that's all OtterlyAI needs, and don't share or reuse it elsewhere. If it's ever exposed, delete it in Cloudflare and generate a new one.

Step 7 — OtterlyAI: connect

1. In OtterlyAI, open the brand report whose domain is yourdomain.com, then go to Agent analytics → Add data source. Choose Provider: Cloudflare, paste the token, click List zones, pick yourdomain.com, and click Deploy worker.
2. You'll see a confirmation with removal instructions. Over in Cloudflare, Workers Routes will now list an otterly-agent-… worker on the route yourdomain.com/.

That's it; AI-bot visits will start appearing in Agent Analytics as they happen. You can find more information about the connector in this article.

💡 Removing the connection later is easy: the confirmation in Step 7 includes removal instructions, and you can delete the otterly-agent-… worker from Workers Routes in Cloudflare at any time.