A product feed is a structured file or URL that lists products and their attributes, such as ID, title, price, availability, product link, and image link. Google Merchant Center and Meta catalogs fetch this data on a schedule and turn it into listings or catalog ads.
Key takeaways
- Use a stable product ID across every refresh and advertising channel.
- Keep price and availability tied to the store rather than an AI enrichment step.
- Create separate channel outputs when Google needs richer data and Meta needs a stronger first image.
Which fields belong in a product feed
The minimum useful row identifies the product, describes it, shows its current selling state, and gives the platform a landing page and image. In practice, that means fields such as id, title, description, link, image_link, price, availability, brand, and product category. Apparel, electronics, and other regulated categories may need additional attributes.
A field can be technically present and still be weak. A title such as 'Model 8048' does not explain the product. A category copied from the store menu may also be too broad for Google. Feed quality is therefore about accuracy and useful context, not simply the number of populated columns.
| Field | What the platform learns | Common problem |
|---|---|---|
| id | Which item this is across updates | ID changes after every export |
| title | Product type and important attributes | Internal code replaces a descriptive title |
| price / availability | Whether the offer can be shown now | Feed and landing page disagree |
| image_link | Which image represents the offer | Small, cropped, or generic image |
XML, CSV, and scheduled feed URLs
CSV is easy to inspect and edit, but a static export becomes stale unless someone uploads it again. XML and YML feeds are usually better for an active store because the platform can fetch the same URL on a schedule. The file format matters less than the update process behind it.
A reliable setup keeps the source URL stable. The store updates price, stock, and new products. A feed layer can then add channel-specific fields while preserving the original IDs and current commercial data.
- Confirm that the URL returns a complete feed without a login page.
- Check encoding, namespaces, and image URLs before scheduling imports.
- Record the last successful fetch and surface failed or unusually small updates.
How Google and Meta use the same catalog differently
Google uses product data to decide whether an item is eligible, which searches it may match, and what information appears in Shopping surfaces. Titles, identifiers, categories, and attributes carry much of that meaning.
Meta also needs accurate IDs, prices, links, and availability, but the first image has a larger creative job. A separate Meta output can use a controlled template with the price, promotion, delivery note, and brand elements while the Google output keeps a compliant product image and richer structured fields.
One source feed can support both channels, but the safest output is two reviewed versions rather than one compromise file.
A five-minute product feed quality check
Start with a small sample that includes a normal product, a sale item, an unavailable item, and a product with variants. Open each landing page and compare the title, price, availability, ID, and primary image with the feed row.
Then look for missing identifiers, generic titles, empty categories, and broken image links across the full file. A useful feed audit separates blocking errors from enrichment opportunities so the team fixes eligibility before rewriting copy.
Frequently asked questions
Does every ecommerce store already have a product feed?
Many ecommerce platforms can export one, but the default file may omit useful attributes or use store categories that do not match channel requirements. Check the actual XML or CSV output rather than assuming the connector produces a complete feed.
How often should a product feed update?
The right schedule depends on how often price, availability, and assortment change. A store with frequent stock changes may need several fetches per day. The important rule is that the feed and landing page should not disagree when a platform checks them.
Can Google and Meta use the same feed URL?
They can share one source, but separate output URLs are usually easier to control. Google may need enriched categories and attributes, while Meta may need a different image_link with a promotional template. Keep IDs, price, stock, and product links consistent.
Sources and methodology
This guide is checked against official platform documentation. Requirements can change by country, category, program, and date, so confirm the current documentation before changing a live feed.
Editorial disclosure. Uplify Feed is a product of Uplify Agency, so this guide is not an independent review of the service. We do not sell placements or use affiliate links. To report an error, email hello@uplify.agency; we will check the issue, correct the text, and update the date.
- Google product data specificationOfficial definitions and requirements for product data attributes.
- Meta Blueprint: Advantage+ catalog adsOfficial training material for ads that use a product catalog.