Draft a marketplace schema QA: product/offer markup, seller reviews, and feed validation.
- User
Draft a marketplace schema QA: product/offer markup, seller reviews, and feed validation.
Assistant
The user wants a "Marketplace Schema QA" document. The focus is on three specific areas:
- Product/Offer Markup (Schema.org structured data).
- Seller Reviews (AggregatedRating, Review).
- Feed Validation (Data feed quality and syntax).
The goal is to provide a structured "QA" (Quality Assurance) checklist or guide to ensure these elements are implemented correctly for a marketplace environment (like Google Shopping, Amazon, or a proprietary marketplace).
Target Audience: Developers, SEO specialists, QA testers, or Product Managers working on a marketplace platform.
Structure of the Response:
- Introduction: Briefly define the scope (Google Search/Shopping Center mostly, as that's the standard for "schema").
- Section 1: Product & Offer Markup: This is the core. Needs to cover required fields, nesting, and common errors.
- Section 2: Seller Reviews: Distinguishes between product reviews and seller reviews (crucial for marketplaces).
- Section 3: Feed Validation: How to check if the data is actually readable and correct programmatically.
- Checklist/Summary: A quick "copy-paste" actionable list.
Drafting Content - Section 1: Product/Offer Markup
- Context: Marketplaces have multiple sellers for one product or distinct products per seller.
- Key Schema types:
Product,Offer(orAggregateOfferif multiple sellers). - Critical Fields:
name,image,description,offers. - Inside Offer:
price,priceCurrency,availability,seller,url. - Common QA issues:
- Currency mismatch.
- Price mismatch (markup vs. visible text).
- Missing
sellerproperty (very important for marketplaces). - Images too small or generic placeholders.
Drafting Content - Section 2: Seller Reviews
- Context: In a marketplace, trust is in the merchant, not just the item.
- Key Schema types:
OrganizationorStore(often embedded in the Offer) +AggregateRating. - Implementation: Sometimes this is done on the seller profile page, sometimes on the product page.
- Critical Fields:
itemReviewed(must point to the Seller/Org),ratingValue,reviewCount. - Common QA issues:
- Confusing Product Reviews with Seller Reviews (e.g., rating the shipping speed vs. the product quality).
- Self-serving reviews (schema rules).
- Missing specific
itemReviewedtype.
Drafting Content - Section 3: Feed Validation
- Context: If this is for Google Merchant Center or similar, the schema isn't enough; the XML/CSV feed matters.
- Tools: Google Rich Results Test, Schema Validator, Merchant Center diagnostics.
- Key Checks:
- Global Trade Item Number (GTIN) vs. Brand/MPN.
- Identifier exists.
- Availability status matching stock.
- Image link crawling errors.
Refining the Output Format: I should present this as a structured QA Checklist/Playbook. I'll use categories like "Visual Inspection," "Code Validation," and "Business Logic."
Self-Correction during thought process: The prompt asks for "Marketplace Schema QA." This implies a platform where multiple sellers exist. Crucial nuance: Does a specific product page represent a single offer or an aggregate of offers?
- Scenario A: Amazon style (one product page, multiple buy boxes). -> Use
AggregateOffer+ distinctOfferobjects. - Scenario B: Etsy style (one listing = one seller). -> Simple
Offer. - Decision: I will cover both or focus on the
sellerproperty being the differentiator.
Let's structure the final response into three distinct modules corresponding to the user's request.
Module 1: Product/Offer Markup (The "What")
- Check:
@type: Product - Check:
offers->@type: Offer - Check:
seller-> This is the marketplace specific bit. - Check:
priceValidUntil - Check:
skuvsgtin.
Module 2: Seller Reviews (The "Who")
- Distinguish between
Productreviews andOrganizationreviews. - Check:
itemReviewedisOrganizationorLocalBusiness, NOTProduct. - Check:
authorof the review.
Module 3: Feed Validation (The "How")
- This usually refers to Google Merchant Center (GMC) if talking about "feeds" alongside schema.
- Alignment between Schema and Feed (Price/ID matching).
Final Polish: Make it actionable. Use "Pass/Fail" criteria. Mention specific tools (Rich Results Test, Schema.org validator).
Let's write it out. This is a comprehensive QA Checklist and Implementation Guide for Marketplace Structured Data. It focuses on the specific complexities of marketplaces where multiple sellers offer products, and where both product and seller reputation impact visibility.
Phase 1: Product & Offer Markup (The "What")
In a marketplace, the most common mistake is conflating the Product (the item itself, e.g., iPhone 15) with the Offer (the specific listing from Seller A).
1. Schema Architecture (JSON-LD)
- Use
Productas the wrapper: Define the product details once. - Nest
Offerobjects: If multiple sellers sell the same product on one page (an aggregated page), nest multipleOfferobjects inside theProductschema. If it is a specific Seller Product Page (SPP), nest a singleOffer.
2. QA Checklist: Required & Recommended Properties
Property Context Validation Logic (Pass/Fail) @idGlobal Does the Product have a unique canonical ID (usually the SKU or GTIN)? Crucial for Google to recognize this item across different sellers. gtin/mpn/brandProduct Are Global Trade Item Numbers present? If generic, is brandclearly defined? Google penalizes marketplaces that allow sellers to omit these for branded goods.imageProduct Are the images high-res (>50px) and do they match the product variant (not a generic placeholder)? priceOffer Is the price a number (e.g., 19.99)? FAIL if it includes currency symbols ($) or text.priceCurrencyOffer Is the ISO 4217 code present (e.g., USD,EUR)?availabilityOffer Does it match the frontend? If the button says "Pre-order", schema must be PreOrder, notInStock.itemConditionOffer Is it set to Used,Refurbished, orNew? Crucial for second-hand marketplaces.sellerOffer (Marketplace Critical) Is the sellerproperty populated with anOrganizationorPersontype? FAIL if the seller is "Website Name".3. Edge Case QA: Price Validity
- Check: If the price is discounted, is
priceValidUntilincluded? - Check: Does the schema price match the visible price on the screen exactly? (Google Merchant Center will disapprove mismatches).
Phase 2: Seller Reviews (The "Who")
Marketplaces rely on trust. You must separate Product Reviews (how good the item is) from Seller Reviews (shipping speed, service).
1. Schema Architecture
- Do not mix Seller Reviews into the
Productschema. - Connect Seller Reviews to the
Organization(the Seller) defined in the Offer. - Best Practice: Create a dedicated "Seller Profile" page or fragment where the
Organizationschema lives, and attachAggregateRatingthere.
2. QA Checklist: Seller Reputation
Property Context Validation Logic (Pass/Fail) itemReviewedReview Is the type OrganizationorLocalBusiness? FAIL if it points toProduct.authorReview Is the reviewer name present? (Anonymous reviews like "User123" are often devalued). reviewRatingReview Is the ratingValuewithin thebestRatingandworstRatingscale?Content Policies Manual Are the reviews "Self-Serving"? You cannot mark up reviews written by the marketplace itself about the seller.
Phase 3: Feed Validation (The "How")
If you are feeding this data into Google Merchant Center (GMC) or Facebook Catalog, schema markup is only half the battle.
1. Automated Testing Tools
- Rich Results Test: Paste a URL. Does it render "Product" and "Review" snippets without errors?
- Note: Warnings are acceptable; Errors are blockers.
- Schema.org Validator: Check for syntax validity (missing commas, nesting errors).
- Google Search Console: Check the "Enhancements" tab. Look for "Manual Actions" or "Parsing Errors."
2. Data Alignment QA (The "Cross-Check")
This is the most common failure point for marketplaces using feeds + on-page markup.
Check Logic Price Sync Does the pricein the XML/CSV feed equal thepricein the JSON-LDOffer? Mismatches cause disapproval.ID Sync Does the skuorgtinin the markup match theidin the Merchant Center feed?URL Canonicalization Does the urlproperty in the schema point to the canonical URL submitted in the feed? Avoid tracking parameters in the canonical URL.
Sample JSON-LD Template (Marketplace Context)
Here is a valid structure for a Product being sold by a specific Seller, where the Product has its own reviews, and the Seller has their own rating.
<script type="application/ld+json"> { "@context": "https://schema.org/", "@type": "Product", "name": "Mechanical Keyboard Model X", "image": "https://example.com/keyboard.jpg", "description": "A high quality mechanical keyboard.", "sku": "MK-001", "brand": { "@type": "Brand", "name": "KeyMaster" }, "offers": { "@type": "Offer", "url": "https://marketplace.com/product/keyboard?seller=techgear", "priceCurrency": "USD", "price": "129.00", "priceValidUntil": "2024-12-31", "availability": "https://schema.org/InStock", "itemCondition": "https://schema.org/NewCondition", "seller": { "@type": "Organization", "name": "TechGear Solutions", "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.8", "reviewCount": "212", "itemReviewed": "TechGear Solutions" // Note: Strictly, Seller Ratings are separate, // but nesting here associates the seller quality with the offer. } } }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.5", "reviewCount": "89" } } </script>