Install WebDecoy on Webflow
Webflow serves your site through Cloudflare, but through Webflow’s Cloudflare account, where you cannot add anything. Cloudflare’s Orange-to-Orange (O2O) setup puts your own Cloudflare zone in front of it. Your zone runs first, so the WebDecoy edge sensor can run there and see every request to the site: AI crawlers, search crawlers, scrapers and curl.
A script tag alone cannot do this. A browser detection script only runs in clients that execute JavaScript, and GPTBot, ClaudeBot, Googlebot’s crawl pass and most scrapers never do.
Before you begin
Section titled “Before you begin”- A Cloudflare account (Free works) with your domain added as a zone, so Cloudflare runs its DNS.
- The domain connected in Webflow.
- A WebDecoy account with this site added under the address visitors use, for example
https://www.example.com. Create a free account.
1. Point your hostname at Webflow through Cloudflare
Section titled “1. Point your hostname at Webflow through Cloudflare”In your Cloudflare zone, open DNS → Records and create a record for each hostname you want covered (usually the root and www):
- Type:
CNAME - Name: the hostname, for example
www - Target: see the table
- Proxy status: Proxied (orange cloud)
| Record | CNAME target |
|---|---|
| Your hostname | cdn.webflow.com |
Check the target Webflow shows when you add the custom domain under Site settings → Publishing, and use that if it differs. Cloudflare flattens a CNAME on the root domain automatically.
The orange cloud is required. On a DNS-only record your zone is skipped, and the sensor never runs.
2. Finish the domain setup in Webflow
Section titled “2. Finish the domain setup in Webflow”Add the custom domain in Webflow under Site settings → Publishing if it is not there yet, then publish to it. Once Webflow accepts the domain, requests go visitor → your Cloudflare zone → Webflow’s Cloudflare zone → Webflow.
3. Deploy the edge sensor
Section titled “3. Deploy the edge sensor”- In WebDecoy, select the site.
- Open Integrations → Cloudflare and choose Connect with Cloudflare, then approve the scopes on Cloudflare’s consent screen.
- Open Edge Sensor, choose the zone, and set the route to cover each hostname, for example
www.example.com/*andexample.com/*. - Select Deploy edge sensor.
No code is involved. The edge sensor guide covers the details, including Worker usage and the static-file paths it skips.
4. Fire a test request
Section titled “4. Fire a test request”curl -A "WebDecoy-Test/1.0" https://www.example.com/Swap in your own address. Within a minute a detection labelled Test appears, and Sensors shows the Edge Worker row as Reporting. Then let real traffic arrive: most public sites see search and AI crawlers within hours.
Add the browser script too (optional)
Section titled “Add the browser script too (optional)”The edge sensor sees every request. The browser detection script adds browser-integrity and behaviour signals from clients that do run JavaScript, such as headless browsers and browser agents. Paste the line from Detection Scripts into Webflow’s Site settings → Custom code → Head code (custom code needs a paid site plan).
Things to know
Section titled “Things to know”- The sensor does not block. It reports, and it lets the request through on any error of its own. Cloudflare notes that a Worker on the O2O hostname can interfere with traffic; the sensor only changes a response when you turn on enforcement for a path.
- Zone hold (Cloudflare Enterprise). If Webflow reports “The hostname is associated with a held zone”, release the hold temporarily (for a subdomain, turn off Also prevent Subdomains), then refresh the domain in Webflow.
- Certificates. If you have CAA records, they must allow Let’s Encrypt or Google Trust Services, or HTTPS can fail.
- One edge sensor per organization, today. Other sites in the same WebDecoy organization can report through the WordPress plugin, an SDK or the browser script.
- Support. For problems in your own Cloudflare zone, Cloudflare Support helps and consults Webflow where needed.
Next step
Section titled “Next step”Verify the install, then see what crawlers did in your site’s first report.