Know who crawls your Vercel projects.
Connect a Vercel project and WebDecoy provisions a log drain for crawler visibility without a code change. Choose a separate Firewall or SDK policy when you are ready to act.
Set up WebDecoy on Vercel
Choose your installation path
Vercel log drains require Pro or Enterprise. On Hobby, use the WebDecoy Next.js SDK and deploy the application change instead.
Install and select projects
Open the WebDecoy Vercel integration, choose the team and projects, then return to WebDecoy. Choose which WebDecoy site corresponds to each project and select Connect.
Confirm traffic is arriving
WebDecoy provisions the drain without a redeploy. Review coverage after requests reach the project. Vercel’s IP Address Visibility setting and any drain sampling affect attribution and completeness.
Configure protection separately
For provider actions, configure the Vercel Firewall integration with the appropriate token, project, action, and detection filters. Review recorded results. Connecting the monitoring drain alone does not block or challenge visitors.
Visibility after Vercel answers a request
The log drain can report crawler requests served from the cache or without a function invocation. WebDecoy filters for automated traffic and drops query strings before storing the reported paths.
A drain observes completed requests; it cannot intercept the request being reported. Vercel bills drain delivery according to your plan and usage.
Choose a separate enforcement path
The Vercel Firewall integration supports configured IP blocking, challenges, or logging in response to detections. Its credentials and provider capabilities are separate from the marketplace monitoring connection.
For application-level detection and policy, use @webdecoy/next. SDK setup requires an application change and redeployment. Do not assume the marketplace install injects middleware or installs the Netlify clearance validator.
Understand incomplete coverage
If Vercel removes client IPs from the drain, WebDecoy cannot attribute those requests to actors and reports limited coverage. Sampling also limits the traffic it sees.
Review connection health and recorded activity before treating an empty dashboard as evidence of no bots. Disconnecting the monitoring integration removes its drain; review and reverse Firewall actions separately before deleting their credentials.
Questions about Vercel
Does the Vercel marketplace install require a redeploy?
The log-drain install does not. Adding the Next.js SDK is a separate application change and does require a deploy.
Can I use WebDecoy on Vercel Hobby?
Use the Next.js SDK on Hobby. The log-drain monitoring connection requires Vercel Pro or Enterprise.
Does the log drain block bots?
No. It reports requests after Vercel answers them. Configure Firewall actions or an application policy separately.
Choose your platform
Start with the setup that matches where your site runs. Monitoring, request verification, and provider firewall actions are separate choices.
| Platform and setup guide | Detection | Protection |
|---|---|---|
| Netlify | Extension injects a crawler sensor at build time. | Opt-in clearance checks on protected paths; Monitor first, then Enforce. |
| Cloudflare | Managed Worker observes requests before your origin. | Worker clearance validation and separately configured WAF response actions. |
| Vercel | Log drain on Pro or Enterprise; Next.js SDK alternative. | Configure Firewall actions or SDK policy separately from the monitoring install. |
| AWS CloudFront | Browser script or SDK for detection. | Lambda@Edge clearance validator; optional AWS WAF integration. |
| WordPress | Plugin adds browser detection and decoy surfaces. | WordPress rules and form protection; an edge validator extends coverage before PHP. |
| Shopify | App embed and Web Pixel cover storefront and checkout activity. | Order tagging and risk assessments support merchant decisions; no edge validator installed by the app. |