2026-07-23
Trusted AI agent or bot? Agent identity for WooCommerce
How WooCommerce merchants can distinguish useful agents from bots, what Visa Trusted Agent Protocol changes, and which security boundaries still matter.
Primary data and engineering notes on agent-readable commerce for WooCommerce.
How WooCommerce merchants can distinguish useful agents from bots, what Visa Trusted Agent Protocol changes, and which security boundaries still matter.
WebMCP lets a web page register tools for browser agents, inside the tab. Server-side MCP serves headless agents over HTTP. What Chrome's proposal actually is, how it differs from the MCP server on your WordPress site, and why the two compose.
Measure discoverability and verifiable catalog signals before making AI visibility claims.
A static orientation file and a live commerce catalog solve different problems.
Turn AEO and GEO vocabulary into verifiable WooCommerce catalog foundations.
Keep WooCommerce authoritative while giving compatible agents a live, discoverable catalog surface.
What AI shopping agents need beyond catalog data: exact variants, current stock, destination-aware shipping, delivery evidence and authoritative checkout.
A field-by-field checklist for making WooCommerce product data easier for ChatGPT and shopping agents to ingest, compare and verify without guessing.
A practical explanation of why WooCommerce stores need an agent-readable catalog layer before they need fully autonomous checkout.
Consumers are beginning to use AI agents for shopping, but full purchase delegation is still limited. The first trust layer is not payment: it is accurate, current, machine-readable product data.
A federated catalog can help agents find candidates, but it must preserve provenance, verify with the merchant, survive partial failure and enforce revocable consent.
Shopify’s central catalog is a real distribution advantage. WooCommerce needs local Bridge nodes and explicit federation to create comparable agent-facing reach without centralizing merchant stores.