Netlify Edge Functions Cloaking
Jamstack traffic filtering for modern funnel sites — and the missing intelligence layer.
Jamstack funnels need filtering too
A huge number of affiliate landing pages, comparison sites, and lead-gen funnels are Jamstack builds: Astro, Eleventy, Hugo, or plain HTML deployed on Netlify. Static sites are fast and cheap — but they're also wide open: every bot, scraper, and ad reviewer sees the same HTML as your best customer. Netlify Edge Functions are the natural place to fix that, running Deno-based code on every request before your static content is served.
The DIY pattern on Netlify
export default async (request, context) => {
const country = context.geo?.country?.code ?? '??';
const ua = request.headers.get('user-agent') ?? '';
if (country === 'XX' || BOT_UAS.test(ua))
return context.rewrite('/safe');
return context.next();
};
Geo rewrites and simple UA filters work out of the box. But like every DIY edge setup, the intelligence decays: ad review bots rotate ranges, spoof UAs, and increasingly emulate real browser behavior. A Netlify Function can route traffic — it can't reliably classify it, week after week.
Completing the stack with Cloaker.net
🧩 In-function classification
Call the Cloaker.net API from your Edge Function and rewrite based on its verdict — your routing stays in your codebase.
🛡️ Upstream protection
Or point ad URLs at a Cloaker.net-protected domain entirely — bots never even reach your Netlify site, saving bandwidth and keeping analytics clean.
Either way, you get what no hand-written Edge Function delivers alone: ad-platform-specific bot intelligence, AI behavioral detection, minute-level database updates, and per-visit logs. Jamstack speed + Cloaker.net intelligence = funnels that convert humans and baffle bots. Start at cloaker.net.
Static-site speed. Cloaker-grade security.
Protect your Jamstack funnel with Cloaker.net.
Try Cloaker.net →
