← All guides · Published November 14, 2026 · Reviewed November 14, 2026 · By the Ingenious AI team · 7 min read
Cloudflare Worker, WordPress Plugin or JS Snippet: Which Should You Deploy?
The short answer: deploy the layer that matches your stack and your seriousness. The Cloudflare Worker (free) enforces at the edge before requests reach your origin, and its Pro form carries the full policy — path matrix, sender gate, canary, rate caps. The WordPress plugin (Pro) enforces on your server and keeps the block log in your own database. The plain-JS snippet (Pro) enforces nothing — it deters and notifies in the visitor's browser, and any agent that disables JavaScript bypasses it completely. Same policy, three honest strengths.
Build my block kit — free · Test a policy in the simulator first
What is the three AgentBlock artifacts?
the deployable forms of one policy: a Cloudflare Worker template (edge enforcement, the free artifact), a generated WordPress plugin (server enforcement with an in-house block log), and a plain-JS snippet (a browser-side deterrent and notice layer that the kit itself labels as non-enforcing).
One policy, three physics
The artifacts differ because the internet has layers and enforcement is only real where it happens. The Worker runs on Cloudflare's edge, upstream of your origin: a refused request never touches your server, your bandwidth or your application, which is why the Worker is the right answer for load-sensitive objections like aggressive training crawlers. The plugin runs inside your WordPress request lifecycle: refusal happens on your server, after arrival but before content, and produces the in-house log. The snippet runs in the visitor's own browser — which, for a crawler, means it runs only if the crawler chooses to run it. Most do not.
AgentBlock generates all three from the same policy record, so the decision between them is purely about layer, never about maintaining separate rule sets. Owners routinely run two: Worker at the edge for force, plugin in-house for receipts.
The Worker in detail
The free Worker carries the core name-based site rule — the default posture most small sites need. The Pro Worker is where the full policy comes alive: the path matrix evaluating fences per request, the sender gate checking claimed names against vendor IP ranges and logging SPOOF-SUSPECT, the canary path tripwire, and rate caps soft-blocking over-budget agents with RATE-CAP verdicts. If your policy uses those features, the Worker is not an option among three; it is the artifact that implements them.
Its constraints are platform-shaped: you need Cloudflare in front of the site, and the operational skills are dashboard-and-route skills rather than server skills. For the fleet's typical small business, the free tier of the Worker is the highest-value artifact in the whole system — a real edge refusal for the price of pasting a template.
The plugin in detail
The plugin's virtues are jurisdiction and evidence. Enforcement happens inside infrastructure the owner controls, under the site's own roof, with the block log written to the site's own database and exported as CSV — a posture agencies and regulated clients find easy to approve. It requires WordPress 5.8+ and PHP 7.4+, activates like any plugin, and nags about staleness through its cron check, which the Worker cannot do for itself.
Its costs are the mirror of its virtues: refused requests still reach your server (bandwidth and load objections argue for the edge), and it exists only for WordPress. WooCommerce sites that live in WordPress admin daily usually find it the most operable tier; headless and static sites cannot use it at all.
The snippet, honestly
The kit's own header says it, and this guide repeats it without softening: the plain-JS snippet is a deterrent and notice layer only. It can present your policy to a cooperative agent, log a client-side signal, and raise the effort for casual copying. It cannot stop a crawler, because crawlers are under no obligation to execute your JavaScript, and the serious ones do not. AgentBlock sells it as a Pro download for the sites whose stack offers nothing else — some hosted website builders permit no edge and no plugins — while labelling its limits in the artifact itself.
Judge any vendor by this test: a tool that describes a browser snippet as 'blocking' is telling you how it will describe everything else. The snippet has real uses; enforcement is not among them, and a policy that matters should never rest on it alone.
Choosing, in one paragraph each
On Cloudflare already, or able to be: deploy the Worker — free for the core rule, Pro when your policy grows fences, caps and sender checks. On WordPress with client or compliance evidence needs: deploy the plugin, alone or beneath a Worker. On a locked-down hosted builder with no edge and no plugins: deploy the snippet as notice, price its limits honestly in your policy document, and treat migration to an enforceable stack as the real fix on your roadmap.
Whichever you choose, verify it: the kit verifier does not care which artifact it checks, and an unverified deployment of the strongest layer is still a hope, not a control.
Five actions to take today
- Match the layer to the stack. Cloudflare in front: Worker. WordPress in-house: plugin. Locked builder: snippet, with its limits written down.
- Use the Pro Worker for full policies. Path matrix, sender gate, canary and rate caps live in the policy-carrying Worker tier.
- Pair Worker and plugin for client work. Edge force plus an in-house, CSV-exportable log is the combination auditors approve fastest.
- Never rest a real decision on the snippet alone. It deters and notifies; the kit's own header says enforcement belongs at edge or server.
- Verify whichever you deploy. Kit ID and hash against the policy — an unverified strong layer is a hope, not a control.
Worked example: one policy, two layers, one honest exception
Northbeam Studio, a fictional design agency, standardised its client fleet on one pattern: the AgentBlock Worker at the edge for every client on Cloudflare (11 of 14 sites), the generated plugin beneath it on the 8 WordPress sites for in-house logs, and — for the 3 clients on locked website builders — the JS snippet plus a written limitation in each policy document naming enforcement as the migration goal.
The pattern's value showed in a single quarter's numbers: across the fleet, 212,000 refusal events logged at the edge, CSV evidence produced for 8 clients from their own databases without a single special request, and zero clients labouring under the belief that a snippet was a wall.
When one builder-hosted client migrated to WordPress, its policy did not change at all — only its artifact did, from snippet to plugin, generated from the same record in one sitting. That is what 'one policy, three layers' buys when it is time to move.
Frequently asked questions
Is the free Worker really enforceable?
Yes. The free Cloudflare Worker template is generated from your policy and refuses blocked agents at the edge — a real enforcement artifact, not a sample. The Pro Worker adds the advanced policy machinery: path matrix, sender gate, canary path and rate caps.
Can I deploy more than one artifact?
Yes — commonly the Worker and the plugin together, generated from the same policy so they cannot disagree. The verifier can check each artifact against the policy record; running two layers from two different rule sets, by contrast, is a drift incident waiting for its date.
Why is the JS snippet a paid download if it cannot enforce?
Because for sites on locked builders it is the only deployable layer, and its deterrent and notice functions are real for cooperative agents and casual copying. Its price buys the generated artifact and its honest labelling — the kit states its limits in its own header rather than overselling them.
Which artifact should a WooCommerce store choose?
Usually the plugin, for the in-house block log and CSV evidence inside the stack the store already runs — often with the free Worker in front of it for edge refusals and load relief. Both come from the same policy, so the pair costs one decision, not two.
What if my site is on none of these stacks?
The policy still generates its robots layer, which any stack can serve, and the AgentGate export carries the policy to other enforcement points on Team. But be honest in your documents about which layer is enforcing: a robots-only posture is a declaration, and the guides here treat it as such.
Related guides
- How to Block AI Scrapers and Bots from Your Website
- Which AI Crawlers Should You Allow?
- How Do You Block AI Bots on WordPress, Cloudflare, or Plain JS?
- Pre-deploy breakage simulator — test a policy before it ships
- Impact preview — your server log against a draft policy
- What Is the Complete AI Training Opt-Out Checklist for a Small Business?
- How Often Should You Review Your AI Crawler Policy?
- Does Blocking AI Crawlers Hurt Your SEO?
- What Is an AI Crawler?
- How Do You Block GPTBot Without Losing ChatGPT Citations?
- Block evidence — parse a log, build an evidence pack
- The dated agent database — 25 entries, graded