Almost all publisher monetisation happens in one place: the browser, after a page has loaded and its JavaScript has run. CDN-layer monetisation, also called edge monetisation, moves it earlier, into the content delivery network, in the request-and-response exchange between a visitor and your origin server, before any page render. The reason to move it there is simple. A fast-growing share of your traffic is AI agents that never reach the browser stage and never run that JavaScript, so browser-based monetisation cannot touch them. The edge is the one layer every request passes through, which makes it the only place AI agent traffic can be seen, classified, and monetised at all.
Where the CDN edge sits
When a browser or bot requests a page, the request first reaches the content delivery network, the distributed layer that caches and serves content close to the user, before it reaches the publisher's origin server. The response travels back through the same edge. Everything that happens in this path, detecting who is requesting, classifying the request, and modifying the response, happens server-side, before any JavaScript in the page has a chance to run. That timing is the whole point. The edge sees and can act on every request, including requests from clients that will never execute the page's scripts.
Why browser-side monetisation fails for AI traffic
Traditional publisher monetisation lives in JavaScript. When a human loads a page, the browser executes the analytics tag, runs the programmatic ad auction, activates affiliate links, and checks the paywall. All of this happens after the HTML arrives, in the browser. AI agents break this model. A Live Search Agent dispatched by ChatGPT, Perplexity, Claude, or Gemini requests the page, reads the HTML as text, and leaves without executing any JavaScript. The analytics never fire, the ad auction never runs, and the publisher earns nothing. Because the agent never enters the layer where browser-side monetisation operates, that monetisation simply cannot reach it. The only layer that can is the edge, which the agent does pass through.
How CDN-layer monetisation works
Edge monetisation is implemented as a lightweight worker deployed on the CDN, on Cloudflare Workers, Akamai EdgeWorkers, Fastly Compute, CloudFront, or Nginx. The worker inspects each incoming request and identifies whether it is a human, a Live Search Agent, a training crawler, a search bot, or a scraper, attributing it to its owner. For human visitors it does nothing, so the human experience is unchanged. For an eligible AI agent retrieval, it can run a real-time auction and insert relevant content into the response before it is returned. blankspace works this way: when a Live Search Agent retrieves an eligible page, blankspace runs a sub-50ms auction at the edge and injects a relevant brand fact into the content as editorial context, then attributes the revenue the same day. There is no change to the CMS, the origin server, or the human-facing ad stack.
What CDN-layer monetisation makes possible
Operating at the edge unlocks three things browser-side tools cannot do. It makes AI agent traffic visible, because the raw request is seen and classified before any render. It makes that traffic monetisable, because the response can be enriched in the layer the agent actually reads. And it does both with zero performance impact on human readers and no client-side risk, since the logic runs at the network edge rather than in the page. For publishers, this turns the fastest-growing and previously invisible segment of their audience into a measured, monetised channel.
Edge monetisation and access control are different things
It is worth separating edge monetisation from edge access control. CDNs also offer ways to block or charge AI crawlers for access, such as default crawler blocking and pay-per-crawl marketplaces. Those are access decisions: allow, block, or charge at the door. Edge monetisation in the sense described here earns from the content the agent reads once it is allowed in. The two can run together. A publisher can block low-value scrapers, charge identified training crawlers for access, and monetise Live Search retrievals through content-layer advertising, all at the same edge.
Frequently asked questions
Why monetise at the CDN instead of in the browser?
Because a growing share of traffic, AI agents, never runs browser-side code. The CDN edge is the only layer that sees and can act on those requests, so it is the only place AI agent traffic can be measured and monetised.
Does CDN-layer monetisation slow down my site for human readers?
No. The logic runs at the network edge and short-circuits for human visitors, so the human experience is unchanged. There is no added client-side JavaScript and no client-side risk.
What do I need to deploy edge monetisation?
A single lightweight worker on your existing CDN, such as Cloudflare Workers, Akamai EdgeWorkers, Fastly Compute, CloudFront, or Nginx. It requires no changes to your CMS, origin server, or ad stack, and analytics can go live on the first request.
Is CDN-layer monetisation the same as pay-per-crawl?
No. Pay-per-crawl charges crawlers for access at the edge. CDN-layer monetisation as described here earns from the content an agent reads once it is allowed through. They address different traffic and can be used together.
Can it monetise human traffic too?
The edge sees all traffic, but the specific opportunity here is AI agent traffic, which browser-side tools cannot monetise. Human traffic continues to be monetised by your existing ad stack, which edge monetisation does not touch.