An XML product feed is a structured catalog file that organizes product data, name, price, image, availability, using nested XML tags, the specific format still required by Google Shopping and most comparison shopping engines despite being older and more verbose than newer alternatives.
A simple answer to what is an XML product feed worth remembering: it’s the older, still-mandatory format for one specific but important channel, not a relic that’s disappeared everywhere.
Why an Older Format Still Dominates One Specific Channel
An XML product feed persists for a straightforward reason: Google Shopping and several major comparison engines built their systems around this format years ago and never fully moved away from it, even as newer, more compact formats emerged elsewhere. This means an ecommerce store serious about Shopping ads doesn’t get to choose a more modern format instead, XML remains the required structure for that specific channel regardless of what a store might prefer to use internally.
XML Product Feed Structure
An XML product feed structure nests data inside tags, each product wrapped in its own entry, with individual fields nested further inside that:
- A root element wrapping the entire feed, typically
<rss>or<feed>depending on the specific schema required. - An item or entry tag for each individual product, repeated once per item in the catalog.
- Nested field tags inside each item,
<title>,<price>,<availability>,<image_link>, each holding one specific piece of product data.
This nested structure is precisely what makes XML more verbose than newer formats, every piece of data needs its own opening and closing tag, which produces a considerably larger file than the same data expressed more compactly.
XML Product Feed vs JSON Feed
XML product feed vs JSON feed, covered in detail elsewhere in this glossary, comes down to structure and use case:
- XML remains the required format for Google Shopping and most comparison engines, regardless of how the rest of a store’s tech stack is built.
- JSON, more compact and faster to parse, has become the preferred format for real-time integrations, including the dynamic content used inside email, covered under dynamic product feed elsewhere in this glossary.
Most ecommerce platforms generate both simultaneously from the same underlying catalog, XML for advertising channels that require it, JSON for faster, real-time uses like email personalization, rather than forcing one format to serve every destination.
Keeping an XML Product Feed for Google Shopping Accurate
An XML product feed Google Shopping submission that goes stale, showing an old price or a sold-out item as available, doesn’t just create a poor shopper experience, it can trigger policy issues directly, since accuracy requirements are enforced more strictly on paid shopping placements than on most other channels. Keeping this feed synced automatically from the actual store catalog, rather than updated manually on any kind of delay, avoids both the customer experience problem and the platform compliance risk at once.
Related terms:
Adflipr connects directly to a store’s Shopify or WooCommerce catalog, keeping the JSON-based feed that powers email content synced automatically alongside whatever feed formats a store maintains for other channels.
