The agent is one file on a coded site, a plugin on WordPress. Where that file goes depends on where the site runs — and what it can serve depends on whether it sees the response. Each guide says both, plainly, and what works on a host that runs no code of yours.
The five places the agent runs, with the exact file.
A plugin, three steps, no developer.
Static or server-rendered builds that deploy through an adapter — the agent goes where the adapter runs.
on Vercel, Netlify, Cloudflare Workers
frameworkon Vercel, Netlify, Cloudflare Workers, Node and Express
frameworkon Vercel, Netlify, Cloudflare Workers, Node and Express
frameworkon Vercel, Netlify, Cloudflare Workers, Node and Express
frameworkon Vercel, Netlify, Cloudflare Workers
frameworkon Vercel, Netlify, Cloudflare Workers
frameworkon Vercel, Netlify, Cloudflare Workers
No server code of yours runs here. What works from outside, and the route for the agent.
checks and tools from outside; a Worker in front for the agent
hostedchecks and tools from outside; a Worker in front for the agent
hostedchecks and tools from outside; a Worker in front for the agent
hostedchecks and tools from outside; a Worker in front for the agent
hostedchecks and tools from outside; a Worker in front for the agent
hostedchecks and tools from outside; a Worker in front for the agent
Free, from outside, in minutes — with the exact finding behind every line.