Verbatim text from the 100-item checklist; this site does not re-judge it. The measured values on the right are from a single fetch and are not paired line by line.
Checklist criteria (verbatim) · 6
#18 商品页结构化数据
Product/Offer/Review/AggregateRating Schema 是否有效、Rich Result 报错
Fields come from this tool's M0 detector (a single fetch), with no day-over-day change or verdict; vantage server-KR. The checklist criteria on the left are verbatim and are not re-judged here.
A domain is scanned at most once every 10 minutes; this is the previous result (no new fetch).
Full report
Grouped by checklist item: criteria, general explanation, recommendations and official references are listed per item; the full set of measured values is listed separately at the end, not paired item by item. This site does not re-judge, and the explanations and recommendations do not give a compliance verdict on any single measurement.
Tool 商品数据质量 · Site mvmt.com · Vantage server-KR · Generated 2026-11-22T21:06:04.159Z · Reference version 2026-11-09 · 6 checklist items
Generated on this page from checklist references and this run's measurements; no history, change events or compliance verdicts.
Checklist items · 6
#18 商品页结构化数据 · P1
Criteria:Product/Offer/Review/AggregateRating Schema 是否有效、Rich Result 报错
Explanation
Product/Offer/AggregateRating JSON-LD is the main channel through which a shopping agent reads price, availability and reviews. Without it the agent guesses from rendered text and can misread the currency or treat a sale price as the list price. Typical failures: Product with no Offer, structured price disagreeing with the page, or fabricated review counts triggering Rich Result errors.
Recommendations
Emit a complete Product + Offer (price, priceCurrency, availability) on every product page.
Keep price and availability consistent across structured data, the visible page and the feed.
Validate every template with the Rich Results Test, not just one hand-written sample page.
Generate JSON-LD from product master data in the template rather than maintaining snippets by hand.
Criteria:Google Merchant Center / Meta Catalog 拒登原因、字段缺失、GTIN/价格不符
Explanation
Disapprovals in Merchant Center / Meta Catalog are usually data problems, not bidding problems: missing or wrong GTIN, incomplete item_group_id, or a feed price that disagrees with the landing page. When feed and site disagree, an agent distrusts both sources. Typical failures: currency or decimals differing from the page, out-of-stock items still in the feed, or missing variant attributes.
Recommendations
Clear disapprovals from the Merchant Center diagnostics page grouped by root cause, not one by one by hand.
Generate id, gtin, item_group_id, availability and price from the same master data as the site.
Force a feed refresh after every bulk price change and auto-compare feed prices with landing-page prices.
Validate currency, tax-inclusive display and decimal rules separately per country.
Inconsistent data across ERP/OMS, storefront, feed and ads is the most common hidden loss for a DTC store: overselling, wrong prices and mismatched size mappings turn directly into returns and chargebacks. When an agent cross-checks multiple public readings, conflicting data gets discarded wholesale. Typical failures: variant SKU not mapped to feed id, out-of-stock still marked InStock, or a detail-page price differing from checkout.
Recommendations
Make product master data the single source of truth for storefront, feed and ads.
Fix a stable SKU-to-id mapping for variants; never infer it from titles or ordering.
Sample-compare detail-page, checkout and feed prices after every sync.
Write availability back in real time and surface mismatches as a daily alert, not a month-end reconciliation.
Material, country of origin, dimensions/weight, battery and ingredient fields are needed for compliance and logistics and are also what a shopping agent uses to answer buyer questions. Low field coverage makes comparison impossible, so the agent cites a competitor instead. Typical failures: specs only in the title, mixed units, or battery info missing on powered goods.
Recommendations
Define required attributes per category and measure field coverage.
Put specs in JSON-LD additionalProperty instead of scattering them through free text.
Standardise and label units; for cross-border categories add origin, material, battery and ingredient data.
Sample-check fill rates regularly and prioritise low-coverage categories for backfill.
Sizing and unit-conversion errors are the leading cause of high return rates in apparel and footwear. If the chart and the text disagree on EU/US sizes, centimetres vs inches or kilograms vs pounds, an agent's advice is wrong too. Typical failures: the size chart is an image (unreadable to agents), two unit systems mixed on one page, or the chart not matching the product's actual label.
Recommendations
Use an HTML table rather than an image for the size chart and put key conversions in structured data.
Standardise and label units; generate both chart and copy from one conversion rule.
Manually sample-check conversions per category instead of trusting automatic conversion alone.
Give measurable sizing guidance on the product page and state how to measure.
Zero-decimal currencies such as JPY/KRW, tax-inclusive labelling and price consistency through payment are the most overlooked trust signals on a multi-currency store. A wrong decimal count makes an agent read 1000 as 10.00; unclear tax display shows a different amount at checkout. Typical failures: forcing two decimals everywhere, showing tax only at checkout, or sharing one price template across markets.
Recommendations
Configure decimals per currency (0 for JPY/KRW) instead of forcing two decimals site-wide.
Label prices tax-inclusive or exclusive and keep detail page, cart, checkout and feed amounts identical.
Render currency symbol, thousands separator and decimals per market.
Regression-test price display with multi-currency cases, especially rounding and stacked discounts.