The agentic web is the new shopping surface — an audit for it

On April 21, 2026 Microsoft rolled out a package: AI Max for Search campaigns, Offer Highlights ad format, Universal Commerce Protocol in Microsoft Merchant Center, Copilot Checkout, and AI-visibility tracking in Clarity. The framing line: "optimizing for clicks to optimizing for selection." Your product no longer needs to rank — it needs to be chosen by an AI agent on behalf of the user.

Google is moving the same direction via Shopping Graph (35 billion listings, hourly refresh). Perplexity Shop already lets users buy inside a chat answer. OpenAI's ChatGPT Browse recommends products from the web.

The Agentic Commerce Readiness Audit scores your product page on the structural signals that determine whether an AI agent can find it, trust it, and transact with it.

What it audits

Five sections, weighted by impact:

1. Product schema completeness (~40 points)

Every agent-commerce surface — Microsoft UCP, Google Merchant feed rich results, Perplexity Shop, Copilot Checkout — requires schema.org/Product with:

• name, image, description, brand
• A product identifier: gtin, gtin13, mpn, sku, or productID
• offers block with price, priceCurrency, availability, itemCondition
• shippingDetails (required for Google rich results since March 2024)
• hasMerchantReturnPolicy (same)
• aggregateRating or review (agents prefer verified ratings)

Missing any of these knocks you out of the eligibility pool.

2. Organization trust signals (~11 points)

Agents don't transact with anonymous sellers. Organization schema with logo, sameAs (Wikidata, LinkedIn, X, Crunchbase), and contactPoint is the entity layer agents verify.

3. Agent discovery files (~12 points)

• /.well-known/mcp-server.json — Model Context Protocol manifest, for agent-callable tools
• /.well-known/agent-card.json — human-readable agent identity
• /.well-known/ai-plugin.json — OpenAI-style plugin manifest
• /llms.txt — your canonical content index for AI retrievers
• /ai.txt — crawler policy

4. Microsoft UCP readiness signals (~7 points)

• og:type=product meta tag
• product:price or og:price:amount microdata
• Twitter Card type

5. One-shot buyability (~7 points)

• Visible buy CTA ("Add to cart", "Buy now", "Checkout")
• Established payment integration (Stripe, Shopify, PayPal SDK detected)
• HTTPS (non-negotiable for agent commerce)

Scoring bands

• READY (70-100%): Agent-commerce eligible today. Submit feeds, request inclusion.
• PARTIAL (40-69%): Major gaps. Agents can find but not confidently transact.
• NOT READY (0-39%): Fundamental structural gaps. Prioritize Product schema + Org schema first.

Why "optimizing for selection" is not the same as SEO

Google ranks 10 organic results per query. An AI agent picks one product per query. The funnel compresses from "top 10" to "top 1." The criteria also shift:

• Rank factors weighted for click-likelihood don't matter (title CTR, snippet copy).
• Rank factors weighted for selection matter more: product-data completeness, brand trust signals, review density, return policy, shipping clarity.
• The visible page matters less. Agents rarely load the page UI — they read the structured data and the Merchant feed.

This audit targets the selection-criteria layer. Its recommendations are invisible to your human visitors and fully visible to the AI agent.

How to use it

1. Go to /tools/agentic-commerce-readiness/
2. Paste the URL of a product page (a specific product, not a category)
3. Click Run. The tool fetches the page + tests six discovery-file endpoints. ~5-10 seconds.
4. Read the 5-section scorecard. Green sections are ready; red sections block selection.
5. Click Copy fix prompt for a consolidated patch plan covering everything flagged.

Pair with the rest of the agentic stack

• GEO Content Extractability Scorer — paired release; evaluates non-commerce pages for AI-retrieval readiness.
• MCP Server Audit — if you expose agent-callable tools, verify the manifest.
• Rich Results Eligibility Audit — full schema-type validation.
• Schema Graph Visualizer — visualize how your Product schema connects to Organization + Offer + Review.
• LLM Answer Citation Tracker — check whether Perplexity / you.com / Bing AI are citing your product pages today.

What the tool can't check (yet)

• Actual feed diagnostics — Microsoft Merchant Center + Google Merchant Center have their own validators that check your XML/CSV feed. This audit checks the page layer; submit the feed for the other half.
• Payment-SDK transaction compatibility — Copilot Checkout requires specific Stripe / Shopify integrations. This audit detects the SDK's presence but not the integration flow.
• Real agent selection signal — whether Copilot actually picks you for "buy me a waterproof jacket" depends on the agent's ranking model, which isn't public. The audit maximizes your eligibility, not your final rank.

Related reading

• GEO Content Extractability Scorer — paired release
• Mega SEO Analyzer v2 — the orchestrator
• Every new AEO tool for 2026
• AI Content Disclosure

Fact-check notes and sources

• Microsoft AI Max + Copilot Checkout launch (April 2026): Search Engine Land — Microsoft launches AI Max + new ad tools for the agentic web era.
• Google Shopping Graph scale (35B listings, hourly refresh): Google blog — Generative AI in Search.
• Google rich result shipping + return policy requirement (March 2024): Google Search Central — Merchant listings structured data.
• Schema.org Product reference: schema.org/Product.
• Model Context Protocol: modelcontextprotocol.io.
• Universal Commerce Protocol: announced by Microsoft Merchant Center; public spec forthcoming as of 2026-04.

This post is informational, not SEO-consulting, commerce, or legal advice. Mentions of Microsoft, Google, Perplexity, OpenAI, ChatGPT, Anthropic, Claude, Stripe, Shopify, PayPal, and similar products are nominative fair use. No affiliation is implied.