An XML feed is a file in XML format in which an online shop publishes data about its products: name, price, availability, image, link and other attributes. Ad platforms such as Google Merchant Center and Meta, and price comparison sites such as Heureka, download it regularly and use it to display your offers. The quality of the feed decides whether products appear at all, whether they are matched correctly and how much you pay for them.
In short:
- An XML feed (product feed) is a machine-readable list of products at a fixed URL that a comparison site or ad platform fetches on its own.
- Every channel has its own specification: Google Merchant Center uses RSS 2.0 with attributes prefixed g:, Heureka uses SHOP and SHOPITEM elements.
- The mandatory core is similar everywhere: ID, title, product URL, image, price including VAT and availability.
- Feeds are produced by the shop platform, a plugin, a feed manager or a custom generator. They cannot be maintained by hand.
- The most common mistakes: price and availability that do not match the website, missing GTIN/EAN or brand, the wrong category and titles that are internal codes.
What is an XML feed
XML (Extensible Markup Language) is a text format that stores data in named tags. A product XML feed is a file at your shop's address, for example your-shop.com/feed/google.xml. Each product forms its own block, with the product's attributes inside it. Unlike a web page, it is meant for software that builds offers from it, not for people.
You will also see it called a product feed, data feed or XML export. Do not confuse it with an XML sitemap: a sitemap tells search engines which pages to crawl, while a product feed passes on data about your goods.
What an online shop needs an XML feed for
- Shopping ads and free listings: Google Merchant Center turns the feed into Shopping ads and free product listings.
- Social catalogue ads: Meta builds catalogue ads on Facebook and Instagram from a product catalogue that can be filled from a feed.
- Price comparison sites: in Central Europe, for example, Heureka (Czechia and Slovakia) and Zboží.cz (Czechia) take offers from the feed and match them to product pages where shoppers compare prices.
- Marketplaces and partners: some retailers and marketplaces can take over offers from an XML feed.
A shop therefore usually has several feeds, one per channel in that channel's format. The data should come from a single source so that prices and stock levels never drift apart.
What an XML feed looks like: a Google Merchant Center example
A simplified example of one product in the RSS 2.0 format used by Google Merchant Center. The values are illustrative.
<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:g="http://base.google.com/ns/1.0">
<channel>
<title>Your Shop product feed</title>
<link>https://www.your-shop.com</link>
<description>Products of Your Shop</description>
<item>
<g:id>COFFEE-ETHIOPIA-1KG</g:id>
<g:title>Ethiopia Yirgacheffe Whole Bean Coffee 1 kg</g:title>
<g:description>Speciality whole bean coffee, light roast.</g:description>
<g:link>https://www.your-shop.com/coffee-ethiopia-1-kg</g:link>
<g:image_link>https://www.your-shop.com/img/coffee-ethiopia.jpg</g:image_link>
<g:availability>in_stock</g:availability>
<g:price>26.90 EUR</g:price>
<g:condition>new</g:condition>
<g:brand>Your Roastery</g:brand>
</item>
</channel>
</rss>Google requires the g: namespace on every Merchant Center attribute; attributes without the prefix are ignored. Price comparison sites such as Heureka use a different structure, with a SHOP root element containing one SHOPITEM per product. Special characters such as & must be written as an entity (&), otherwise the file is invalid.
Mandatory feed elements by channel
| Google Merchant Center | Meta (catalogue) | Heureka | |
|---|---|---|---|
| Format | RSS 2.0, attributes prefixed g: | CSV, TSV, RSS XML, Atom XML or Google Sheets | XML, SHOP and SHOPITEM |
| Required data | id, title, description, link, image_link, availability, price; brand for new products; gtin where the product has one | id, title, description, availability, condition, price, link, image_link, brand | ITEM_ID, PRODUCTNAME, URL, IMGURL, PRICE_VAT, CATEGORYTEXT, DELIVERY_DATE, DELIVERY |
| Bids in the feed | no, bids are set in Google Ads | no, budget is set in the campaign | HEUREKA_CPC |
| Watch out for | the file must contain all products; a product left out is removed from the account | a single XML line may not exceed 5,242,880 characters | ITEM_ID max. 36 characters, category from Heureka's category tree |
Specifications change, so open the channel's current documentation before any major change (links are in the Resources below the article). Merchant Center setup and the Shopping ads themselves are covered in our guide to Google Shopping ads and Merchant Center.
Titles, descriptions, variants and GTIN: what drives matching
- Title: brand, product type and the key attribute people search for. Internal codes do not sell.
- Description: plain text without HTML, describing real product features.
- GTIN/EAN and brand: identifiers help Google and comparison sites match your offer to the right product. Heureka calls the field EAN (13 digits), Google calls it GTIN.
- Variants: colours and sizes of one product are linked by a group ID (item_group_id at Google, ITEMGROUP_ID at Heureka); each variant should have its own URL.
- Images: clean product photos without promotional text; Heureka accepts up to 10 additional images besides the main one.
- Availability: keep it in sync with the shop, otherwise products get rejected or you pay for clicks on items that are sold out.
How to create an XML feed: three routes
| Route | How it works | For whom |
|---|---|---|
| Export from the shop platform | the platform or a plugin generates feeds for the main channels | most small and medium-sized shops |
| Feed manager | one source feed is converted by rules into each channel's format and edited in bulk (titles, categories, excluded products) | shops on several channels that need to adjust their data |
| Custom generator | a script or module reads data straight from the shop, warehouse or ERP | custom-built shops and large catalogues |
Ready-made platforms usually offer feeds natively or through a plugin; see our comparison of Shoptet, Upgates and WooCommerce. Custom solutions typically pull data through the API of the stock or accounting system.
How to prepare an XML feed step by step
- 1Choose your channels and open their current specifications.
- 2Complete the data in your shop: GTIN/EAN, brand, categories, variant attributes and good images. A feed is only as good as the data in your admin.
- 3Generate the feed at a fixed public URL, ideally in UTF-8.
- 4Check the file: valid XML, mandatory elements for every product, prices and availability matching the website, no empty attributes.
- 5Add the feed URL to each channel: in Google Merchant Center as a data source with a scheduled fetch (files under 4 GB), in Meta Commerce Manager as a catalogue data feed.
- 6Set the update frequency to match how often prices and stock change. A feed fetched once a day will not catch an afternoon sell-out.
- 7Monitor diagnostics in each channel and fix rejected or unmatched products.
The most common XML feed mistakes
- Price or availability in the feed differs from the website because the feed is not generated often enough.
- Invalid XML: unescaped characters, broken encoding or unclosed tags.
- Missing GTIN/EAN or brand, so the offer is not matched to the right product.
- Titles that are internal codes ("K-001 1kg") instead of words people search for.
- HTML tags in a description that should be plain text.
- Variants without their own URL or without a shared group ID.
- A different product ID in the feed than in conversion tracking, so clicks cannot be tied to orders.
An illustrative example, not one of our clients: a fictional coffee shop has a platform feed for one comparison site only. It has two more feeds generated from the same data for Google and Meta, adds GTINs and puts coffee type and weight into the titles. Only then does it launch Google Ads campaigns, because without a clean feed it would pay for clicks on unmatched or sold-out products.
When to hand your XML feed to a specialist
If your platform exports feeds for every channel you use and the data in your admin is complete, you can set up the feed yourself. A specialist pays off when channels reject products, offers are not matched, you need feeds for several countries, or the shop runs on a custom build without exports. We connect feeds to the shop, warehouse and ERP as part of e-commerce development and build PPC campaigns in Google Ads and on Meta on top of clean data. With 9+ years of experience and 50+ projects, we have found that most problems with product ad performance start in the feed. Tell us about your shop via the contact form.
Frequently asked questions
What is an XML feed?
How do I create an XML product feed for Google?
What is the difference between an XML feed and an XML sitemap?
How often should an XML feed be updated?
Is one XML feed enough for all channels?
Sources

Written by
Peter GáboríkProject Manager – AI, Automation & SEO
Project manager and founder of Weboptim. Builds growth strategies around SEO, automation and AI; in online marketing since 2017.
Related service
Tips that save time – once a month
One e-mail a month: a new guide, the automation of the month and one number from practice. No spam.



