Feed quality
The difference between a valid feed and a profitable feed
A valid feed is readable and contains the required fields. A profitable feed goes further: it helps shopping channels understand, match and present products well.
Validation checks the basics
Technical validation is about structure, required fields, accepted values and whether the feed can be processed. These checks are necessary, but they do not tell the full commercial story.
A validator can confirm that a feed contains an id, title, link, image link, price and availability. It can also flag values that are empty, duplicated, too long or hard to map. That is the foundation. Without it, the channel may reject products or import them incorrectly.
But validation is mostly a minimum standard. It tells you whether the feed can be read and whether obvious requirements are met. It does not automatically tell you whether the product data is strong enough to help matching, classification or performance.
Feed quality affects how products are understood
Product titles, identifiers, categories, images and descriptions all help channels understand what a product is. Weak product data can make matching and diagnostics harder even when the feed is accepted.
For example, a title like “Sneaker black” may be valid, but it gives the channel and the shopper very little context. A title that includes brand, product type, model and relevant attributes is usually more useful. The same idea applies to GTINs, product type, Google product category and image quality.
This is why Product Feed Check treats feed review as more than a pass or fail result. The goal is to show where the feed is readable, where required fields are present, and where the data may still be too thin or inconsistent to be commercially useful.
How to think about both levels
Start with technical issues because they block everything else. If the feed cannot be parsed, if required fields are missing, or if product IDs are unstable, those problems should be fixed first.
After that, review quality signals on your important products. Look at titles, identifiers, categories, images, descriptions, prices and availability. Ask whether a person who does not know your catalog could understand the product from the feed alone.
A good feed review combines both views: can the channel process the feed, and does the feed describe the products well enough to support useful shopping results?
Why this matters
Merchants often stop once a feed is accepted, but accepted products can still have poor visibility or weak matching when product data is thin or inconsistent. Separating validity from quality helps you decide whether you are fixing import problems or improving the product data itself.
Common mistakes
- Treating Merchant Center approval as the final goal.
- Using generic titles that do not identify the product clearly.
- Leaving identifiers, categories or image quality unchecked.
- Only fixing hard errors and ignoring broader data quality.
Practical recommendations
- Start with required fields and parsing issues.
- Review identifiers, titles, images and categories on a sample of important products.
- Compare feed values against the actual product page.
- Use validation as the first step in a broader feed quality review.
Related field guides
Related articles
Check your feed
Upload or analyze your XML or CSV product feed and get a quick overview of missing fields, mapping issues and shopping channel readiness problems.