The protocols and tools behind an agentic website, explained for a business owner rather than a standards committee. These articles cover WebMCP, MCP, llms.txt, the ARD catalog and the Chrome and Cloudflare tooling, with a plain note on how much each is used today.
On October 6, 2026 Sierra and Meta announced Personal Agent Protocol, an open standard for how personal AI agents deal with businesses, with Genesys, Rocket, Shopify, Stripe and Walmart among the partners. The design puts two permission decisions in one OAuth session: what access a customer grants their agent, and what a business lets any agent do. What that settles, what the unpublished spec leaves open about who an agent represents, and why a first introduction is a different consent question.
Cloudflare expanded BotBase beyond known-good bots and made verified status conditional on behavior. What continuous behavior evaluation covers, and the two trust problems it leaves untouched.
Cloudflare launched a developer preview that injects a WebMCP bridge at the edge, so any site exposes callable agent tools from one dashboard switch. What it solves, and what it leaves open.
WebMCP is live in a Chrome origin trial and the spec keeps moving, yet an honest July 2026 read shows almost no mainstream agent calls the tools a site exposes. What that does and does not prove.
Vercel, Railway, GitBook, and site builders already list AI agents. Here is where to deploy a site agent in 2026, what each surface expects, and what a listing leaves out.
Web Bot Auth uses HTTP Message Signatures so an AI agent signs every request and your site can tell a real one from a spoof. It proves the agent is authentic. It does not prove the contact was wanted.
Alibaba open-sourced PageAgent, an in-page JavaScript agent that drives a website's own UI with natural language. What in-page agents change, and the identity layer they leave open.
Chrome 150 added an Agentic Browsing category to Lighthouse and shipped DevTools for Agents. Here is what the audit actually checks, why it is informational, and the gap it does not close.
ARD, announced by Google on June 17, 2026, is an open multi-vendor spec for how AI agents find and verify tools, other agents, and skills. What it standardizes, and the human-identity gap it leaves.
MCP, A2A, and WebMCP get drawn as a tidy three-layer agent stack. Here is what each layer actually does in plain words, and the front door, discovery and identity, the sketch leaves out.
An honest agent-readiness audit: the four scored Cloudflare buckets and its commerce checks, what third-party scorers measure well, and the identity row they leave out.
A practical 2026 guide to making a website agent-ready: the five honest layers, what the evidence supports, and the 60-minute version for site owners.
Evidence-led look at whether llms.txt drives AI citations, covering the SE Ranking 300k-domain study, Google's stated position, the Wix counterpoint, and what to ship.
How the agent payments stack composes: AP2 mandates spending, ACP carries the cart, x402 moves value over HTTP, MPP streams continuous flows. Walked layer by layer for builders.