Why Product Feeds Matter for Agent Marketing
When an AI agent constructs a candidate set for a purchase or comparison query, the candidate set comes from one of four sources: (1) the model's training corpus, (2) live search retrieval, (3) a structured product feed the brand has submitted to the platform, or (4) an MCP server the brand has published. Product feeds are the cheapest, most predictable, and most under-invested of the four. This page consolidates the agent-readable feed standards in May 2026.
Product Feed Surface Comparison
| Surface | Format | Consumer Of | Status |
|---|---|---|---|
| Google Merchant Center | XML / Google product feed spec | Google Search, Shopping, Gemini Shopping | Production, ~20-year history |
| Schema.org Product (JSON-LD) | Embedded on product pages | All major LLM crawlers + search engines | Production, open standard |
| ChatGPT Shopping feed | OpenAI-defined JSON | ChatGPT product recommendations | Production (launched late 2024) |
| Perplexity product cards | Schema.org Product + Perplexity-specific extensions | Perplexity Shopping | Production |
| Microsoft Merchant Center | XML compatible with Google feed | Bing, Bing Copilot Shopping | Production |
| MCP "shopping" servers | MCP tool-call interface (Anthropic standard) | Claude Agent, custom agent stacks | Emerging |
| Agent Pay product manifest | AP2-compatible product declaration | AP2-integrated agents (Google Gemini Shopping, others) | Production |
Critical Schema.org Product Properties for Agent Extraction
| Property | Importance | Notes |
|---|---|---|
| name | Required | Exact product name as displayed |
| brand | Critical | Brand name; supports cross-product brand recall |
| offers (Offer) | Critical | priceCurrency, price, availability (InStock/OutOfStock), priceValidUntil |
| sku / mpn / gtin | High | Universal product identifiers; help dedupe across feeds |
| description | High | 3-5 sentence concise description; fact-dense |
| aggregateRating | High | ratingValue, reviewCount; drives agent confidence |
| image (multiple) | Medium | Multiple URLs at multiple resolutions |
| review (multiple Review) | Medium | Individual reviews with author + reviewRating |
| category | High | Google product taxonomy preferred; aids agent routing |
| weight, height, depth, width | Medium | QuantitativeValue; matters for shipping-related queries |
| shippingDetails | Medium | OfferShippingDetails with delivery time + cost |
| hasMerchantReturnPolicy | Medium | Return-policy details; agent purchase decisions weight this |
Six Things the Feed Landscape Tells You
- Schema.org Product on owned pages is the single most leveraged investment. One implementation produces extraction signal across every major LLM crawler, every search engine, and every agent stack. Brands with strong Schema.org coverage are extractable everywhere; brands without it are dependent on each platform's individual feed submission, which is fragmented and labor-intensive.
- Google Merchant Center remains the highest-volume feed surface. ~20-year ecosystem maturity, billions of products in catalog, and now feeds directly into Gemini Shopping. For commerce brands, Merchant Center completeness is table stakes.
- ChatGPT Shopping feed is the recent high-leverage entrant. Launched late 2024, the OpenAI-defined JSON feed is the only path to ChatGPT product recommendations. Submission is direct and underbuilt, which means competitive moats are still available to early movers.
- Bing Copilot inherits Merchant Center automatically. Brands submitting to Google Merchant Center can submit the same feed (with minor tweaks) to Microsoft Merchant Center for Bing Copilot Shopping. Low-incremental-cost coverage extension.
- MCP shopping servers are the emerging agent-side path. A branded MCP server that exposes product inventory, pricing, and availability gives agentic AI (Claude Agent, custom stacks) direct programmatic access. Currently very underbuilt; high-leverage for any brand with substantial inventory.
- Agent Pay product manifests are required for AP2 agent commerce. AP2-mediated agent purchases require AP2-compatible product declarations. Brands selling through AP2-integrated agents must publish these manifests to be eligible for agent-mediated purchase.
What This Means for Brand AI Visibility
Product feed completeness is now a structural input to commerce-related AI visibility. Brands selling through any AI-mediated shopping surface need: (1) comprehensive Schema.org Product on owned pages, (2) Google Merchant Center submission, (3) ChatGPT Shopping feed submission, (4) Microsoft Merchant Center (incremental from Google feed), (5) optionally an MCP shopping server and AP2 product manifest for agentic surfaces. The combined investment is moderate but the visibility lift compounds across surfaces. Brands that skip feed work cede agent-mediated commerce candidate-set inclusion to competitors who invested.
Methodology
Feed format details collected May 15, 2026 from vendor documentation (Google Merchant Center, Schema.org Product spec, OpenAI ChatGPT Shopping documentation, Microsoft Merchant Center). MCP and AP2 specifications from the Linux Foundation Agentic AI Foundation (AAIF) publications. Refreshed quarterly as feed surfaces continue to launch and evolve.
How Presenc AI Helps
Presenc AI tracks brand presence inside AI-mediated shopping surfaces (ChatGPT product recommendations, Perplexity Shopping, Gemini Shopping, Bing Copilot Shopping). When a brand's product fails to appear in a relevant agent candidate set, our instrumentation traces back to which feed source produced the gap.