8 min read
The Best Product Feeds for AI Shopping in 2026 — GMC, Bing, Stripe ACP, OpenAI, MCP
Google Merchant Center fed search. AI shoppers read different feeds. Here are the 7 product feeds that matter in 2026 — which agents consume each, refresh cadence, setup difficulty, and a decision tree for what to prioritise.
xpay✦
30 May 2026Google Merchant Center is no longer the only feed that matters. In 2026 there are seven feeds AI shoppers read, with different mechanics, audiences and refresh costs. The right strategy is not "fill them all" — it's match feeds to where your buyers are searching. Below: the full ranking, who consumes each, and a decision tree for which to prioritise. For brands that need a single agent-readable layer over all of them, the MCP feed is the unifying shape.
Why feeds multiplied in 2026
Until 2024, "product feed" meant one thing: a Google Merchant Center file. That changed when shopping moved into AI answers. ChatGPT Shopping needs a different shape than Google AI Overviews. Perplexity reads structured PDPs directly, not a feed. Stripe's Agentic Commerce Protocol expects a feed shaped for agent checkout, not for search. Meta's catalog feeds ads, not LLMs. And the MCP (Model Context Protocol) feed is becoming the vendor-neutral shape agents prefer to consume.
Seven feeds, four audiences, two refresh cadences. The merchants winning citations are the ones treating feeds as a portfolio, not a checkbox.
The seven feeds that matter
| Feed | Who consumes it | Cadence | Setup | Verdict |
|---|---|---|---|---|
| 1. Google Merchant Center | Google Search, Shopping, AI Overviews | Daily–hourly | Medium | Required for any brand that wants traffic from Google |
| 2. Bing Merchant Center | Bing, ChatGPT (when invited), Copilot Shopping | Daily | Medium | Increasingly the under-rated lever — ChatGPT routes here for some queries |
| 3. Meta catalog | Instagram + Facebook ads, Reels Shopping | Daily | Medium | Conversion-side, not LLM-side. Keep clean if you spend on Meta |
| 4. Stripe ACP catalog | Agents that checkout via Stripe Agentic Commerce | Real-time | Hard | Required if you sell into Operator-class agents that transact directly |
| 5. OpenAI catalog (ChatGPT Shopping) | ChatGPT Shopping mode | Daily | Hard — invite-driven | The cleanest path into ChatGPT Shopping. Partners surface it for you |
| 6. MCP feed | Claude, GPT-4o tool-use agents, Operator, agent SDKs | Real-time | Medium | The unifying agent-readable shape. Future-proofs you for the next wave |
| 7. Schema.org JSON-LD (per-PDP) | Every LLM crawler (Perplexity, Claude, generic agents) | Real-time | Easy | Not a "feed" technically — but the substitute for one when an agent skips structured feeds. Non-negotiable |
Who needs what — by D2C segment
Single-channel Shopify D2C, less than $1M GMV: GMC + on-page JSON-LD. Skip everything else until volume justifies it.
Multi-channel D2C, $1M–$10M GMV: GMC + Bing Merchant + Meta + on-page JSON-LD. Add MCP feed as the agent-readiness lever — it costs little to maintain and unlocks Claude / direct-agent traffic.
D2C above $10M GMV: All seven. Stripe ACP becomes relevant once a meaningful share of orders come from agentic checkout. OpenAI catalog usually arrives via a Shopify or Stripe partnership, not direct setup.
Subscription / configurator-heavy brands: Schema.org per-PDP becomes more important than any feed — your products are variant-rich and agents need to extract that off the page anyway.
Per-feed setup — the snippets that matter
Google Merchant Center
Two paths: Direct feed (Shopify app, BigCommerce app, manual upload) or Schema.org auto-import (Google pulls from your on-page JSON-LD). The auto-import is cleaner and stays in sync — but only works if your Product + Offer schema is correct. Stale prices are the #1 GMC error. Aim for hourly price syncing if you discount actively.
Bing Merchant Center
Often forgotten because Bing search share is small. The reason it matters now: ChatGPT Shopping routes some queries through Bing when OpenAI doesn't have an inbuilt answer. A Bing Merchant feed costs almost nothing to maintain (Microsoft accepts the same Google feed format) and unlocks an unmeasured slice of ChatGPT traffic.
Stripe Agentic Commerce Protocol catalog
Stripe's ACP is the most ambitious checkout-side feed: it lets an agent transact with your store without a browser. The feed is JSON, Stripe-hosted (or merchant-hosted under SFTP), and includes inventory, pricing, taxes and shipping. Don't set this up until you have an agent checkout flow tested end-to-end — a catalog without a working transact path generates support, not sales.
OpenAI catalog (ChatGPT Shopping)
Invite-driven. Most merchants get in via a partner — Shopify, Stripe, or a feed vendor that already has a relationship. The feed shape is close to GMC's, with stricter image and returns-policy requirements. If your GMC feed is clean and your schema is open, you are 80% ready.
MCP feed
The Model Context Protocol feed is the vendor-neutral agent-readable shape. Anthropic originated it for Claude; OpenAI, Stripe and the open-source agent ecosystem now consume it. The MCP feed is the single layer that travels well — a brand that exposes MCP shows up in Claude, in Operator, in any agent SDK that adopts the spec.
This is also where xpay sits — we emit a single MCP-shaped feed over your storefront, and route the same data into GMC / Bing / Stripe ACP / OpenAI catalog formats automatically.
Schema.org JSON-LD (per-PDP)
Not technically a feed — but for the LLMs that crawl directly (Perplexity, Claude, generic agents) it's the only signal that matters. See the exact Product + Offer + Review schema patterns that win citations →
Cadence matters more than completeness
The #1 mistake D2C brands make on feeds is treating them as a one-and-done setup. Stale prices, out-of-stock items still listed, sale dates expired — these don't just hurt search; they actively get you downranked. Daily refreshes are table stakes; hourly for any feed touching live inventory.
The MCP feed plus a real-time inventory webhook is the simplest 2026 pattern: one feed, real-time, all surfaces.
Decision tree — what to prioritise
Make sure your on-page Product + Offer + AggregateRating + Review JSON-LD is complete and validates. This unlocks Perplexity, Claude, generic agents, AND feeds Google's auto-import. See the patterns →
If your Google traffic dropped because of AI Overviews: The fix is not "more feed". The fix is open schema + reviews density + brand entity consistency. See the GEO playbook.
If you want to show up in ChatGPT Shopping: Bing Merchant + clean PDP schema + Shopify/Stripe partner relationship. Run the ChatGPT diagnostic first to see where you stand.
If you want to be in agent-checkout flows: MCP feed + UCP/ACP endpoint. Schema alone is not enough — agents need a transact path, not just a discover path.
How xpay fits
xpay emits a single MCP-shaped feed from your storefront and projects it into the surfaces that need different shapes — GMC, Bing, Stripe ACP. We also surface the agent checkout endpoint (UCP) so the brands ranked highly on the Agent-Readiness Leaderboard can actually close transactions with agents, not just be named in answers.
If you want to see what your store currently looks like to an agent across these feeds, run the live diagnostic.
Related reading
- How AI shoppers find D2C brands — the canonical mental model + signal hierarchy
- Agent-Readable Product Pages — JSON-LD patterns that win citations
- Why ChatGPT doesn’t recommend your store — diagnostic
- The D2C brands AI shoppers actually find — leaderboard
- The 2026 Merchant’s Playbook for Agentic Commerce
- Agentic Storefront for Shopify — setup guide
Last updated 2026-05-30.