PricingHow It WorksDocsBlog
Log In
Framer guide · Hosted site builder

Marech for Framer Sites

Drop one snippet into Framer's custom code and watch the AI scrapers hitting your site appear in your dashboard — no developer needed.

PlatformHosted site builderSetup~2 minutesBlockingMonitor only

How Marech protects a Framer site

Framer's custom-code panel injects the monitoring snippet into the <head> of every published page, so setup is a single paste. Framer hosts and serves your site on its own managed infrastructure — great for monitoring, but because it owns the request path and manages SSL, scrapers can be observed rather than blocked.

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 Framer in ~2 minutes.

Mode 2

Blocking — the edge check

Requires a checkpoint in front of your server. Framerowns the whole request path, so this mode isn't available here — monitoring only.

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 Framer 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 Framer plan and takes about ~2 minutes.

Framer → Site Settings → General → Custom Code → Start of <head> tag
1
Copy your Marech snippet
After signing up, open your Marech dashboard and click "Get Snippet Code". Copy the one-line script tag.
2
Open your Framer project settings
In the Framer editor, open Site Settings (the gear/settings icon for the whole site, not a single page).
3
Go to General → Custom Code
Find the Custom Code section. You'll see fields for 'Start of <head> tag' and 'End of <body> tag'.
4
Paste into 'Start of <head> tag'
Paste your Marech snippet into the 'Start of <head> tag' field so it loads on every page.
5
Publish your site
Click Publish. Custom code only goes live on the published site, so monitoring starts once you publish.
Verify monitoring is live
Custom code runs on your published Framer site, not the editor preview. Open the live URL in a browser and confirm your visit appears in the dashboard feed.
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. Framer hosts your site and manages its own domain routing and SSL, so there's no place to insert an edge proxy or worker that runs before your page is served. On Framer, Marech monitors traffic and overlays JS-running bots, but non-JS scrapers can't be blocked. See how the two modes differ in the docs.

Blocking on Framer

Framer hosts your site and manages its own domain routing and SSL, so there's no place to insert an edge proxy or worker that runs before your page is served. On Framer, Marech monitors traffic and overlays JS-running bots, but non-JS scrapers can't be blocked.

Monitoring only — and why
Framerowns the entire request path — server, domain, and TLS — so there's no way to insert an edge proxy or worker that runs beforeyour page is served. Marech still monitors traffic and overlays JS-running bots here, but non-JS scrapers can't be blocked. If real blocking matters, host your site somewhere you control the edge (a custom domain via Cloudflare, or a self-hosted setup) — see the platform guides.

Troubleshooting & FAQ

Can I block scrapers by putting Cloudflare in front of Framer?
It's not officially supported. Framer manages your domain's SSL and expects its own DNS setup, so proxying through Cloudflare (which is where an edge Worker would run) tends to conflict with Framer's certificate handling. For reliable blocking, use a platform where you fully control the edge.
Is there anything I can do besides monitor?
You can add AI-crawler directives to your robots.txt, which well-behaved crawlers like GPTBot and ClaudeBot honor. It won't stop a scraper that ignores robots.txt, but combined with monitoring it gives you visibility plus a polite opt-out signal.
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 Framer site?

Free 7-day trial. No credit card required.