The goal is consistency: the same real product facts should show up in your store, feed, and markup. Google says using both a Merchant Center feed and page structured data can maximize eligibility for its shopping experiences; eligibility is not a promise that a result will appear. See the Google overview .
THE CATALOG
Start with one reliable product feed.
If you sell through Google, Merchant Center is one place to provide catalog data for Google’s shopping surfaces. Its exact requirements depend on the destination, market, and product type, so treat the current product data specification as the field reference—not as a universal feed format for every platform.
Start with an export or sheet for a small group of products. Make one row per sellable item or variant, give it a stable ID, and decide which system owns each value. Then check these essentials:
A stable product ID
Give each item a durable ID and keep it the same when you update the feed. A store SKU can work as your feed ID; it is not a substitute for a manufacturer GTIN.
A specific title and description
Name the item plainly and include useful distinctions such as material, size, or color. Match the feed text to what shoppers see on the product page.
A working product URL and image
Point to the item’s own landing page and a clear image of that item. Check that the URL resolves and that the selected image matches the product and variant.
Current price and availability
Use a numeric price and the target currency code in the feed. Keep the price and stock status consistent with the product page, checkout, and structured data.
Real identifiers and relevant attributes
Include a manufacturer-assigned GTIN when one exists. Add accurate brand or MPN data where applicable, and send useful attributes such as color, size, or material when they distinguish a product.
THE PRODUCT PAGE
Mirror those facts in Product markup.
Structured data is a machine-readable description of the page. For a page where a shopper can buy from you, Google documents the merchant-listing form of Product data. Add the product facts and an Offer for the current purchase terms. The snippet below is sample data, not a real product; replace the sample facts and reserved .invalid URLs before publishing. Its InStock value is only an example; use the live status.
{
"@context": "https://schema.org",
"@type": "Product",
"name": "SAMPLE: natural linen tote",
"image": "https://example.invalid/sample-product-image.jpg",
"description": "SAMPLE ONLY: replace with product facts",
"sku": "SAMPLE-SKU-001",
"brand": {
"@type": "Brand",
"name": "SAMPLE BRAND"
},
"offers": {
"@type": "Offer",
"url": "https://example.invalid/sample-product-page",
"price": 29.00,
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
}
}Keep price, three-letter currency code, and availability current and aligned with the visible page and checkout. For Google merchant listings, its docs recommend placing Product markup in the initial HTML; they also warn that JavaScript-generated markup can make Shopping crawls less frequent and reliable for fast-changing details. Read the current merchant listing requirements before choosing optional properties. The wider vocabulary is defined by Schema.org Product and Offer , while Google’s feature has its own eligibility rules.
SIZE, COLOR, MATERIAL
Make each variant unambiguous.
If a product comes in several colors or sizes, give each variant its own accurate identifier and distinguishable attributes. Use a matching image, price, stock status, and variant name. For a store with variant-selecting URLs, check that each URL opens with the correct choice selected and the details visible.
Google supports ProductGroup and variant markup for this relationship. Its implementation details differ for single-page and multi-page variant setups, so follow the product variant guide for your page structure. For a feed, use the destination’s group and variant fields rather than assuming the labels match Schema.org property names.
A LIGHTWEIGHT QA LOOP
Test the details before scaling up.
- 01
Pick one in-stock product and compare its store page, checkout, feed row, and Product markup side by side.
- 02
Check the name, image, product URL, identifier, price, currency, and availability. Confirm a variant points to its own correct details.
- 03
Run a product URL through Google’s Rich Results Test, then review any feed or Merchant Center diagnostics for the destination you selected.
- 04
When inventory or prices change, update the source system and check that every published copy follows. Re-test after theme, feed, or structured-data changes.
Google Rich Results Test Merchant Center product data specification
THE LIMITS
Clarity helps systems read facts; it cannot choose outcomes.
Google describes Product structured data and Merchant Center feeds as ways to provide product information and become eligible for its shopping experiences. It also says rich-result display is decided by each experience. Accurate data is a sound foundation for interpretation, but this guide does not promise higher rankings, impressions, traffic, sales, or a place in an AI-generated recommendation.
AI assistants do not all publish the same product-data requirements or use the same sources. Clear visible product facts and accessible, valid markup may help an automated system understand a page when it reads it; no shared schema can force an assistant to crawl, include, or recommend a product. Treat feed and markup work as data quality, then measure actual outcomes separately.
PRIMARY REFERENCES
Go to the source for current requirements.
The feed and eligibility statements above summarize official documentation reviewed for this guide. Requirements can vary by market, product category, destination, and change over time; check the linked source before making a catalog-wide update.
- 01Introduction to Product structured data
Google Search Central · Explains product snippets, merchant listings, feed and markup options, and eligibility limits.
- 02Merchant listing structured data
Google Search Central · Requirements and guidance for product pages where shoppers can buy from the merchant.
- 03Product data specification
Google Merchant Center Help · Feed attributes, formats, matching guidance, and market or product-specific requirements.
- 04About unique product identifiers
Google Merchant Center Help · When to use GTIN, MPN, and brand data—and when not to invent an identifier.
- 05Product variant structured data
Google Search Central · How Google represents a product group and its distinct variants.
- 06Product and Offer types
Schema.org · The shared vocabulary for product facts and offers; Google feature eligibility has additional rules.
This guide explains data hygiene, not a ranking tactic. The ShopSkein guide does not claim that feed submission or structured data causes more traffic or sales.
A PRACTICAL NEXT STEP
Want a second set of eyes on your product data?
Small ecommerce brands can ask ShopSkein to review their product data and share practical recommendations for next steps. A review does not promise higher rankings, AI recommendations, or sales.