Agent Lane: AI Bot & Spam Protection For Forms Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Agent Lane sits behind the form plugins you already use. Every submission is scored on your server from request signals plus a small signed token that the browser fills in while a person uses the form. Submissions that look like a person are delivered as usual. Submissions that look like a bot, a script or an AI agent are held in a separate queue in wp-admin, where you can read them, release them or delete them.
Why another anti-spam plugin
Spam written with AI tools reads like a real message. It fills every field correctly, it carries none of the usual junk, and it passes honeypots and reCAPTCHA v3 scores. Site owners have been reporting exactly this on the WordPress.org and Shopify forums: 85 threads in 90 days by our count in September 2026, and at least one anti-spam vendor confirming in its own support forum that AI bots now bypass its checks.
Agent Lane does not judge the text alone. It looks at how the request arrived. Did a browser render the page first? Did a pointer or a finger move before typing? How long between render and submit? Does the request carry the headers a real browser sends? Does the user agent belong to a known crawler or agent? Each answer adds to a score, and the score decides the lane.
What you get
- Two queues in wp-admin: People (delivered) and Automation (held). Nothing is deleted on the way in.
- No CAPTCHA, no puzzle, no checkbox. Visitors never see Agent Lane.
- A hidden “agent purpose” field. Honest AI agents can state who they act for. Those land in the Automation queue with the label “declared agent”, and you decide.
- Support for Web Bot Auth, the request signature that agents such as ChatGPT agent send. Reading the operator name is always on. Verifying the signature against the operator’s published keys is optional and off by default.
- Plain reasons on every held item, such as “No mouse or touch movement before typing” or “No behavior signals were received from the page script”.
- Release in one click. The submission is marked as human and a copy with all fields is emailed to you.
- Mark as bot. The sender’s fingerprint goes on a blocklist stored on your site.
- A bundled directory of known agents and crawlers: OpenAI, Anthropic, Google, Perplexity, Meta, Microsoft, Apple, Amazon, ByteDance, Common Crawl, Browserbase, Anchor, Manus, and headless browser markers. Set allow, queue or block per agent.
- A dashboard widget with the last 7 days: people, automation, and a breakdown by class (bots, suspected, declared and verified agents).
How it works
- When a page with a supported form renders, a small script (under 8 KB, no dependencies) adds hidden fields: a signed token with the render time, a honeypot with a random name chosen for your site, and the agent purpose field. The token is tied to the visitor’s network range and browser family, so a token carried to another network or browser counts against the submission (this can be turned off for cached sites). It counts pointer moves, touches, key presses, focus order and timing. It never records what was typed.
- On submit, the form plugin hands the request to Agent Lane before anything is sent or saved. The plugin reads the request headers, the token, the counters and the user agent, and adds the weights into a score from 0 to 100.
- Below the queue threshold (default 55) the submission is a person and the form plugin continues as normal. At or above it, the submission is held in the Automation queue and the form plugin is told to treat it as spam. At or above the block threshold (default 90) the form shows a short message and the submission is kept for 7 days only.
- Declared agents (purpose field filled, or a valid agent signature) are held by default with their own label. You can change that to allow or block, for all agents or per operator.
Which forms
- Contact Form 7
- WPForms (tested with WPForms Lite)
- WordPress comments
- Gravity Forms (experimental)
- Elementor Pro Forms (experimental)
Contact Form 7, WPForms Lite and comments are tested on WordPress 7.1. The Gravity Forms and Elementor Pro integrations are written against the documented hooks of those plugins and have not been run against them on a live site yet. If you use one of them, watch the Automation tab during the first days and report anything odd in the support forum.
Other form plugins are not touched. Agent Lane loads nothing on pages without a supported form.
What it does not do
- It does not show a CAPTCHA or any other challenge.
- It does not send submissions, IP addresses or anything else to a third party. Scoring runs inside your site.
- It does not delete anything on its own, apart from the retention schedule you set.
- It does not stop search crawlers from reading your site. It only looks at form submissions.
- It does not protect the login page, the REST API or WooCommerce checkout.
- It is not a content filter. A person who writes a rude message is still a person.
Privacy
Agent Lane is built to keep data on your site.
- No external calls by default. Scoring, the directory of known agents and the list of datacenter IP ranges are bundled with the plugin. No submission, address or header ever leaves your server.
- One optional external call. When “Verify signed agents” is on, the plugin fetches the public signing keys of an agent operator from that operator’s own website (the
/.well-known/http-message-signatures-directoryaddress under the domain named in the request). It is a plain GET for a public key file, cached for 24 hours. The request carries nothing about your site or your visitors. The setting is off by default, and the disclosure text is shown next to it. - What is stored. For every held or blocked submission: the submitted fields, a truncated IP address, the browser user agent, the score, the reasons and the time. For every delivered submission (the People tab): the time, the form, the score, the reasons, the truncated IP address and the user agent, but no field contents, for the last 200 submissions.
- IP truncation. Addresses are stored with the last octet zeroed (IPv4) or cut to /64 (IPv6). “Store full IP address” is off by default.
- Retention. Automation queue items are deleted after the retention period (default 30 days). Blocked submissions are kept 7 days. People entries are trimmed to the last 200.
- Browser script. The script counts pointer moves, touches, key presses, focus changes and timing, and records screen size, device pixel ratio, the number of plugins and languages, and whether the browser reports automation control. It does not record field contents or which keys were pressed. It sets no cookies. The page token is tied to the first half of the visitor’s IP address and the browser family through a one-way hash; neither value is stored for that purpose.
- Blocklist. “Mark as bot” stores a one-way hash of user agent, stored IP and message text. The original values are not kept for that purpose.
- Email. Releasing a submission emails its fields to the notification address from settings and to no one else.
- Privacy policy. The plugin adds a suggested paragraph to Settings > Privacy > Policy Guide that you can paste into your policy.
- Uninstall. Deactivation keeps the data. Deleting the plugin removes the queue table and all plugin options.
- No telemetry, no usage statistics, no remote configuration, no update checks other than WordPress.org.
- Data sources. The bundled agent directory and datacenter IP ranges are compiled from the operators’ public documentation and IP feeds; no third-party library is bundled.
Screenshots
Automation queue. Held submissions with class, score and the reasons behind the score. Release anything that belongs to a person; nothing is removed until the retention period ends.
People tab. Submissions delivered as usual, kept as a light copy so you can see what came through.
Settings. Scoring thresholds, hidden form fields, privacy and retention. No CAPTCHAs, no third-party services, no data leaves the server.
Per-agent policy. Allow, Queue or Block for every known AI agent and crawler, with a sensible default per agent.
Dashboard widget. People versus Automation for the last 7 days, counts per class, and how many submissions are held right now.
