How-To Guide

How to Create Agent-Readable Product Feeds

Step-by-step 2026 guide to publishing product feeds AI agents can read: Schema.org Product, agent-specific feed formats, MCP integration, and validation.

By Ramanath, CTO & Co-Founder at Presenc AI · Last updated: May 15, 2026

Why Agent-Readable Product Feeds Matter in 2026

Agentic commerce surfaces — ChatGPT Shopping, Perplexity Shopping, OpenAI Operator, Apple Intelligence purchase flows, and emerging x402-based agent marketplaces — read product data through structured feeds and APIs, not by parsing your retail website. Brands without an agent-readable product feed are reachable to human shoppers but invisible to agentic buyers. This guide walks through publishing one.

Step 1: Audit Your Current Data Sources

  • Google Merchant Center feed (if you sell on Google Shopping).
  • Schema.org Product JSON-LD on PDPs.
  • Product API (REST/GraphQL) if you have one.
  • Catalogue export (CSV or JSON) used internally.

Most brands have 2-3 of these but no unified agent-readable feed. The goal is one canonical feed that agentic surfaces can consume reliably.

Step 2: Pick the Canonical Format

FormatBest forNotes
Schema.org Product (JSON-LD on PDP)Any brandRequired baseline. Agents extract this directly.
Google Merchant Center feedGoogle Shopping + GeminiRequired if you want Gemini Shopping presence.
OpenAI Shopping feed formatChatGPT ShoppingDocumented in OpenAI partner programme.
MCP server with product toolsForward-looking agent surfacesHighest leverage for 2026-2027.
OpenAPI-described REST endpointCustom agent integrationsOften used alongside Schema.org.

Step 3: Implement Schema.org Product on Every PDP

This is the universal baseline. Every product detail page should carry a complete Product JSON-LD block:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Acme Wireless Headphones X5",
  "image": "https://acme.example/products/x5.jpg",
  "description": "Active-noise-cancelling wireless headphones, 40-hour battery, adaptive EQ.",
  "brand": { "@type": "Brand", "name": "Acme" },
  "sku": "ACX5-BLK",
  "gtin": "0123456789012",
  "offers": {
    "@type": "Offer",
    "url": "https://acme.example/products/x5",
    "priceCurrency": "USD",
    "price": "299.00",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.6",
    "reviewCount": "1284"
  }
}
</script>

See the Schema.org JSON-LD examples gallery for additional fields (energyConsumption, colour, material, hasMerchantReturnPolicy).

Step 4: Publish a Catalogue Feed

Generate and host a daily-refreshed JSON or CSV catalogue at a stable URL like https://acme.example/catalogue.json. The minimum schema:

{
  "generated_at": "2026-05-15T08:00:00Z",
  "currency": "USD",
  "products": [
    {
      "sku": "ACX5-BLK",
      "gtin": "0123456789012",
      "name": "Acme Wireless Headphones X5",
      "brand": "Acme",
      "category": "headphones / wireless / over-ear",
      "url": "https://acme.example/products/x5",
      "image_url": "https://acme.example/products/x5.jpg",
      "description": "Active-noise-cancelling wireless headphones.",
      "price": 299.00,
      "availability": "in_stock",
      "rating": 4.6,
      "review_count": 1284
    }
  ]
}

Step 5: Expose Through MCP

Add an MCP server with at least search_catalogue, get_product, get_pricing, and check_availability tools. See the MCP server starter template and the how-to-build guide.

Step 6: Validate Across Surfaces

  1. Run every PDP through Google's Rich Results test.
  2. Submit your Google Merchant Center feed and resolve all warnings.
  3. Test a sample of products in ChatGPT Shopping by name and confirm description, price, and availability are correct.
  4. Test in Perplexity Shopping and Gemini Shopping similarly.
  5. Connect your MCP server to Claude Desktop and run a test query.

Step 7: Keep It Fresh

Stale product data is worse than no data. At minimum:

  • Regenerate the catalogue feed daily.
  • Set MCP server cache TTL to 1 hour or less for pricing and availability.
  • Push immediate updates for price changes, stockouts, and new launches via your Google Merchant Center API.
  • Monitor for drift between your storefront and the feed.

Common Mistakes

  1. Schema.org Product only on some PDPs. Inconsistent schema is treated as low-trust by AI assistants.
  2. Missing price or availability fields. Required for agentic-commerce surfaces.
  3. No GTIN or SKU. Disambiguation across multiple retailers requires these.
  4. Stale stock status. Selling out-of-stock items via agentic flows damages brand trust fast.
  5. No agent-readable returns policy. ChatGPT Shopping and Perplexity Shopping increasingly include returns terms in their answer; if yours isn't published, you default to industry norms.
  6. MCP server with no product tools. Brand catalogue is the highest-value MCP tool category in 2026.

Frequently Asked Questions

Yes. Schema.org Product on every PDP is the universal baseline read by ChatGPT, Perplexity, Claude, and Gemini. A catalogue feed is for bulk consumption (Google Merchant Center, OpenAI Shopping partner ingest, your own MCP server). They complement each other.
Not strictly required, but increasingly differentiating. Brands with MCP servers can be queried by ChatGPT, Claude, Cursor, OpenClaw, and other MCP clients for live pricing and availability — data their crawled web pages cannot reliably provide. As agentic commerce surfaces grow, MCP becomes more important.
Catalogue feeds should regenerate daily at minimum. Pricing and availability should propagate within minutes (via Google Merchant Center API push and MCP server cache TTL ≤ 1 hour). Stale data on agentic surfaces leads to bad purchase experiences and brand-trust loss.
You still benefit from a brand-owned Schema.org Product + catalogue feed on your own site. Agents increasingly cross-reference brand-owned data with marketplace listings, and brands without their own data are described as the marketplaces describe them — often less accurately or favourably than the brand would.

Track Your AI Visibility

See how your brand appears across ChatGPT, Claude, Perplexity, and other AI platforms. Start monitoring today.