Search is no longer only about retrieval. It is increasingly about action.
TechRadar's June 26 “Know your agent” piece frames the next layer clearly: if AI agents can access data, call tools, and act on behalf of users, then identity verification becomes part of the infrastructure. That logic also applies to brand discovery.
Source Note
The primary commentary source here is TechRadar's “Know your agent” piece. I pair it with Cloudflare's trust and bot-classification framing and Google's AI Mode behavior data to translate the trust issue into a website and discovery question.
Why the trust layer matters now
Google's May 19 AI Mode data shows more planning, more multimodal behavior, and longer questions. That means the user journey is getting closer to “help me decide” and “help me do this,” not just “show me links.”
Cloudflare's July 1 update adds another layer: some automated traffic is now better described as Agent behavior, not just search or training. That is an important distinction because a real-time agent acting for a person deserves different treatment from a training crawler.
Analysis: once discovery gets close enough to action, trust stops being a nice-to-have brand signal and becomes part of the interaction model.
What service websites need
A service site that expects AI-mediated discovery should get clearer about four things:
- Identity. Who is behind the offer and where can that identity be corroborated?
- Permission. Which pages or tools should real-time agents be able to touch?
- Proof. What claim-supporting pages help an agent decide the brand is trustworthy?
- Escalation. Where must the machine stop and a human take over?
That is the same logic I would use in agent architecture. Discovery surfaces, forms, booking flows, and account areas now sit on the same trust spectrum.
CTA: If AI is increasingly part of how buyers compare and act, then “Know Your Agent” is not only a security idea. It is also a discovery and website-design requirement.
A short agent-readiness check
Identity, permission, proof, and escalation are easy to agree with and easy to leave abstract. Here is how I turn them into something a small service site can actually check.
For identity, open your site as a stranger and ask whether you can confirm who is behind it without leaving the domain, then whether an outside source would confirm the same thing. For permission, list the pages an agent could reach and mark which should ever be acted on versus only read: a pricing page is fine to read, a booking form is an action, an account area should probably be off limits to anything unattended. For proof, check that every big claim on a service page has a nearby link to a case, a system, or a result, not just more description. For escalation, find the point in each flow where money or commitment is involved and make sure a human is clearly in the loop there.
Most small sites pass identity and fail the other three, usually because nobody has drawn the line between reading and acting. Drawing that line once, on paper, is most of the work. It turns "are we ready for agents?" from a vague worry into four concrete yes-or-no answers you can fix one at a time.