WebDecoy tells you which automated traffic reaches your site, and whether it is really who it claims to be. Crawlers that never run JavaScript are invisible to analytics. WebDecoy sees them at the request level, verifies the ones that publish their IP ranges or sign their requests, and flags the ones forging a well known user agent.
Connect a project and WebDecoy sets up a Vercel log drain, so your site reports crawler traffic with no code change and no redeploy. Drains need a Pro or Enterprise team. On Hobby, add one line of @webdecoy/next middleware instead.
Monitoring only. It never blocks or challenges a request.
WebDecoy sets up a log drain for that project. Vercel then sends WebDecoy the requests your site answered: user agent, path, status, client IP and TLS fingerprint. No code change, no redeploy.
It also sets three environment variables (WEBDECOY_SITE_KEY, WEBDECOY_SCANNER_ID, WEBDECOY_SENSOR_KEY), which the @webdecoy/next middleware reads if you run it. The sensor key is written as a Vercel sensitive variable, on production and preview only.
Drains need a Pro or Enterprise team. On Hobby, WebDecoy tells you so and points you at the middleware.
Crawlers, tools, and requests with no user agent. Human visitors are never reported. If your team hides client IPs in Drains, WebDecoy says coverage is limited rather than showing a quiet site.
Disconnect a project and WebDecoy deletes its drain and exactly the three variables it created. Disconnect the integration and it removes everything.
