✓ TestedWorks with CSV, Excel, Google Sheets → JSON-LD Schema
By dataclean.to team · 2026-02-05
B2B product catalogs contain item information including names, SKUs, descriptions, specifications, and pricing. Product schema enables rich shopping results with images, prices, and availability status. Structured product data improves e-commerce visibility and conversion in search results.
The Problem
Product databases store specifications as unstructured text and mix product variants without clear parent-child relationships. Brand names may be inconsistent and GTINs missing for many items. Without Product schema markup, search engines cannot display product rich snippets, comparison features, or availability filters, significantly reducing organic shopping traffic and product discovery. Schema.org Product
How to Fix It
1
Extract Product Identifiers
Parse product name, SKU, model number, and manufacturer part number. Extract GTIN (UPC, EAN, ISBN) codes when available. Map to sku, mpn, and gtin properties for product identification.
2
Structure Product Information
Extract product descriptions, features, and specifications. Parse brand name and manufacturer information. Map to description, brand (using Brand or Organization), and manufacturer properties.
3
Parse Pricing and Offers
Extract prices, currency codes, and availability status. Identify sale prices and valid date ranges. Map to offers property with Offer schema including price, priceCurrency, availability, and priceValidUntil.
4
Extract Reviews and Ratings
Parse customer reviews, ratings, and review counts. Calculate average ratings and distribution. Map to aggregateRating property with AggregateRating schema, and review property for individual Review objects.
5
Generate Product Schema JSON-LD
Output Product schema with required name field. Include sku, brand, offers, image, description, and aggregateRating for comprehensive product representation. Add category and additionalProperty for specifications.
Frequently Asked Questions
How should I represent product variants like size and color options?
Create separate Product schema instances for each variant with unique SKUs and GTINs. Link them to a parent product using isVariantOf property, or group using ProductGroup schema with variesBy property indicating variation dimensions.
What product identifiers are required for Product schema?
While name is the only strictly required field, include at least one global identifier (GTIN, ISBN, or MPN) plus brand for effective rich results. SKU is useful for internal tracking but not required by search engines.
Should product specifications go in description or separate properties?
Use description for marketing copy and key features. For detailed specifications, use additionalProperty with PropertyValue objects containing spec names and values. This enables structured filtering and comparison features.
Example: Input → Output
name
sku
price
brand
rating
Wireless Headphones Pro
WHP-001
$89.99
SoundTech
4.5
wireless headphones pro
WHP001
89.99
soundtech
4.5/5
Red rows show common data quality issues. dataclean.to normalizes and generates JSON-LD automatically.