Agentic Landmark · The Brief
Briefs tagged google in The Landmark Brief.
Google's holiday guidance tells retailers to optimize for people, not bots. Its other recommendations are all written for machines: richer product feeds, real-time price and inventory, agentic checkout. The contradiction resolves once you separate the surface layer from the infrastructure layer.
Think with Google told brands that foundational SEO remains the formula for AI search visibility. In the same article, DoorDash describes integrating 500,000 SKUs with merchant-level availability so Gemini knows what is actually in stock. The example refutes the headline.
Most agent-ready advice collapses two different problems into one. Being cited and being usable run on different infrastructure, fail in different ways, and must be fixed in a fixed order. A map of the four-standard stack, from robots.txt to WebMCP, and why the sequence is the argument.
Adyen Agentic removes the protocol-fragmentation bet: integrate once, and it translates your catalog across every agentic platform. The thesis is right, build for the layer, not the platform. But the layer solves integration, not data quality. A bad catalog gets distributed everywhere at once.
Every agentic commerce protocol was built to reassure merchants: the brand stays the merchant of record. Real protection, and incomplete. The merchant of record is not the merchant of decision, and under agents the two unbundle. The decision is made on the platform before your checkout ever fires.
DuckDuckGo just hit its highest search traffic ever, US iPhone installs up 95% since Google I/O. It is not an anti-AI story. These consumers want the option Google removed: to stay in the selection loop, to browse and decide for themselves. That is the Curator posture, and it is still the majority.
Designers now have a name for serving a human and an agent at once. But the emerging work is almost all about monitoring what an agent does. The harder problem comes first: the grant screen, where a consumer configures what an agent may do at all. AP2 shipped that infrastructure; the UX has not.
Google says you do not need llms.txt for Search, and it just added a Lighthouse check for it. Both are true, because they answer to different audiences. It is not a search signal; it is an agent signal, the site's way of telling a browser agent where to start. Google is now measuring both.
Forrester is right that agentic commerce calls for strategy over urgency, not panic. But "prepare now" implies the viable moment is ahead. For the brands on Google's Universal Cart launch list, it already arrived. The infrastructure timeline and the urgency timeline are the same timeline.
Every platform now offers retailers the agent intelligence it built for itself, on its own infrastructure. You keep the brand label; they keep the nervous system. The retailers who own the next decade will read that offer clearly and choose which layer to rent and which to own.
