PricingHow It WorksDocsBlog
Log In
Webflow guide · Hosted site builder

Marech for Webflow Sites

One embed monitors AI-scraper traffic across every page — and if you front Webflow with Cloudflare, you can block scrapers at the edge too.

PlatformHosted site builderSetup~2 minutesBlockingSupported

How Marech protects a Webflow site

Webflow's site-wide custom code makes monitoring a one-paste job — the snippet lands in the <head>of every page automatically. On Webflow's own hosting that's as far as it goes, but if you point your domain through Cloudflare you can add a Worker that blocks scrapers before they reach Webflow.

Mode 1

Monitoring — the snippet

One line of JavaScript in your <head>. It reports scraper traffic to your dashboard and overlays JS-running bots. Works on Webflow in ~2 minutes.

Mode 2

Blocking — the edge check

A server-side check (a Cloudflare Worker at the edge) returns a 403 to scrapers before your content is served — the only thing that stops non-JS scrapers.

Before you begin

You'll need a couple of things ready. The monitoring step needs only the first two.

  • A Marech account — start a free trial (no credit card).
  • Access to edit your Webflow site's theme, settings, or code.
1

Install the monitoring snippet

One line of JavaScript that reports scraper traffic to your dashboard. Works on every Webflow plan and takes about ~2 minutes.

Webflow → Site Settings → Custom Code → Head Code
1
Copy your Marech snippet
After signing up, go to your Marech dashboard and click "Get Snippet Code". Copy the script tag.
2
Open your Webflow project
Log in to Webflow and open the Designer for your site.
3
Go to Site Settings → Custom Code
Click the gear icon in the top-left, then choose the Custom Code tab.
4
Paste into the Head Code section
In the 'Head Code' field, paste your Marech snippet. This applies it to every page automatically.
5
Save and Publish
Click Save Changes, then Publish your site. Custom code only goes live on publish, so don't skip this step.
Verify monitoring is live
Custom code runs on the published site, not the Designer preview — open your live URL in a browser and watch the visit land in your dashboard. If nothing appears, confirm you clicked Publish after saving.
Monitoring vs. blocking — the honest version
The snippet above reports traffic and overlays JS-running bots — but non-JS scrapers (curl, python-requests, GPTBot…) download your HTML directly and never run it, so it can't block those. On Webflow's own hosting the snippet can only monitor. To actually block non-JS scrapers, front your Webflow site with Cloudflare and run the BlockMe Worker at the edge — it checks each request before it reaches Webflow. Full details in the integration guide.
2

Turn on real blocking (optional)

Stops non-JS scrapers before your content is served, using a Cloudflare Worker at the edge. Needs a Marech API key and a block policy.

1
Route your domain through Cloudflare
Add your custom domain to Cloudflare and set the Webflow DNS records to Proxied (orange cloud) so requests pass through Cloudflare's edge first.
2
Create an API key and a block policy
In the Marech dashboard, create an API key (shown once — copy it) and add a block policy (e.g. bot types scraper and ai_tool).
3
Deploy the BlockMe Cloudflare Worker
Follow the Cloudflare integration guide to deploy the Worker with your API key and API URL, routed to your domain. Scrapers get a 403 before reaching Webflow; it fails open on any outage.

Verify it's blocking. With the Worker live, a fake GPTBot request returns a 403 while a normal browser loads your published Webflow site.

verify blocking
curl -A "GPTBot/1.0" -I https://yoursite.com/

Troubleshooting & FAQ

Can I block without Cloudflare?
Not on Webflow hosting alone — Webflow serves the HTML directly, so there's no place to insert a check. Fronting the site with Cloudflare (free plan is fine) gives you an edge you control, which is where the Worker runs.
Does the snippet work on Webflow's free .webflow.io domain?
Monitoring works on any Webflow domain. Blocking needs a custom domain you can route through Cloudflare, which isn't possible on the free *.webflow.io subdomain.
Does the snippet slow down my site?
No. The script is tiny and loads asynchronously, so it never blocks your page from rendering. Server-side blocking adds a single fast check in front of your origin and fails open, so it can't slow down or take down your site.
Will it block real visitors or hurt SEO?
No. Marech targets automated scrapers, not people, and search engines you care about are allowed by default — you decide exactly what gets blocked with policies. See how detection works.

Next steps

How detection works
The signals Marech uses to tell scrapers from real visitors.
All platform guides
Compare setup and blocking support across every platform.
Write a block policy
Decide exactly which bots get stopped and where.
Plans & pricing
Free 7-day trial, then pick the plan that fits your traffic.

Ready to protect your Webflow site?

Free 7-day trial. No credit card required.