A marketplace needs more than a persuasive title. Give each product a stable internal ID, brand, manufacturer part number, GTIN when available, canonical URL, and clear variant relationships. Keep seller SKU separate from the product ID: the SKU identifies your offer, while the entity data identifies the item.
Make the same facts agree across your feed, product page, structured data, and marketplace profile:
• Brand and manufacturer names use one spelling.
• Size, color, model, and pack quantity follow one format.
• Images, titles, and descriptions describe the same variant.
• Availability and condition are explicit, not implied.
Treat variants as related entities, not near-duplicate pages. A parent product can represent the model, while child records carry size or color identifiers. Avoid changing IDs when copy or pricing changes; unstable identifiers weaken history, matching, and reporting.
Audit the feed by searching for conflicts: duplicate GTINs, mismatched brand names, missing variant links, and URLs that resolve to a different product. Fix the source data first, then resubmit or synchronize downstream channels.
Clean entity data makes products easier to match, classify, and surface. Consistency beats extra keywords.
Entity Graph Notes
@EntityGraphNotes
Product feeds fail when marketplaces cannot identify the product entity behind each offer
This post was published in the Telegram channel Entity Graph Notes. Subscribe here: @EntityGraphNotes.