Your next visitor is probably an agent
Autonomous AI agents are starting to compare prices, fill out contact forms, and book meetings on small-business websites. Here's how we're handling it.
What's actually happening
A growing share of traffic to small business sites isn't a person any more. It's a research agent doing comparison shopping, a meeting-booker acting on someone's behalf, or an LLM-powered "concierge" filling out forms to surface answers to its user. The volume is still small. The trajectory isn't.
This is mostly good. Your customers are starting to delegate the boring parts of finding you to software, and that software is getting better at reading websites the way humans do. But it changes a few of the assumptions our forms and analytics were built on.
Three small shifts
- Form payloads get cleaner. Agents fill the fields you asked for, in the format you asked for, every time. Validation rejections drop. So do typos.
- Source attribution gets weirder. A lead's referrer might be a chat session, not a search engine. Anything leaning on UTM tags will under-count.
- Some submissions are exploratory, not committed. An agent comparing five plumbers might submit to all five before its user picks one. The submission is real; the intent isn't yet.
How ctrlsignal handles it
We're not building an "agent firewall." Agents are just visitors with a different shape. What we are doing:
- Lead capture treats every submission as a real lead, but tags the likely source ("agent-like" vs "human-like") on a best-effort basis, so you can filter or route differently if you want to.
- Per-(app, IP) rate limiting on form ingest stays in place. Bad-actor agents look like bad-actor humans at the network layer; the existing controls catch both.
- The editor is gaining a "preview as agent" mode that strips images and JS and shows the page the way a text-mode crawler will. If your hero is a background image with no alt text, an agent can't read it.
-
Sites get an opt-in
llms.txtat the root — a short, handwritten summary of what the business does, who it's for, and the canonical answers to common questions. It's the simplest way to make your site agent-legible without bloating the page itself.
What we're not doing
No CAPTCHAs by default. They punish humans more than they stop agents, and the agents that matter (the ones acting for your future customers) aren't trying to be sneaky. They identify themselves, retry politely, and quit when told to.
No separate "AI version" of the page either. The same HTML should answer "what do you do, where are you, how do I book you" for a person reading it and for a model reading it. If it doesn't, that's a problem with the page, not a reason for a parallel one.
Where this goes
The boring outcome is the right one: small business sites that work for people and for the software acting on people's behalf. No popup blockers for bots, no crawler arms race. Just a site that answers questions clearly, captures signals reliably, and tells the owner what happened in plain English.
Ready to try it? Start building with ctrlsignal →