CRITICALCategory-specific fields missing+20
CRS could not find several fields commonly needed to evaluate uncategorized: material, size, color, weight, dimensions.
How to fix it
Review the product record and visible page for existing values covering material, size, color, weight, dimensions. CRS is asking for clearer catalog state, not new assertions or rewritten page copy.
Review prompt, not page copy: if this detail already exists in the product record, document category-specific fields using the exact source-derived value only.
materialsizecolorweightdimensions
HIGHBuyer-use context is unclear+10
CRS could not find clear buyer-use context for this uncategorized. Shoppers filtering by specific use case or compatibility will not match this page.
How to fix it
Review whether the product page states the primary use situation, compatibility with systems or requirements, quantity or size scope, and intended user type. Surface existing catalog values plainly if present.
Review prompt, not page copy: if this detail already exists in the product record, document buyer-use context using the exact source-derived value only. Relevant fields can include use case, compatibility scope, quantity or size range, intended user.
use_casecompatibilityquantity_or_sizetarget_user
MEDIUMDescription lacks binary-matchable specifications+9
CRS did not find binary-matchable measurable product facts, structured fields, package counts, sizes, identifiers, compatibility details, or category-specific specifications in the inspected title/description.
How to fix it
Review whether existing product details can be expressed as measurable product facts, structured fields, package counts, sizes, identifiers, compatibility details, or category-specific specifications.
Review prompt, not page copy: if this detail already exists in the product record, document source-derived measurable facts using the exact source-derived value only. Relevant fields can include weight, package count, size, SKU, GTIN, compatibility, included components, or category-specific facts.
description
MEDIUMStructured product data incomplete+5
CRS found Product structured data, but required or recommended fields are incomplete. Schema that is present but incomplete is better than absent schema, but still limits readability.
How to fix it
Review the page schema and make it mirror product information already shown to shoppers: name, brand, image, offer price, currency, availability, and SKU/GTIN/MPN when available.
Review prompt, not page copy: if this detail already exists in the product record, document schema fields from existing product data using the exact source-derived value only. Relevant fields can include name, brand, offers.price, priceCurrency, availability, and SKU or GTIN.
namebrandimageoffers.priceoffers.priceCurrencyoffers.availabilitysku/gtin/mpn
MEDIUMDescription structure is hard to parse+5
CRS found that the product description is difficult to scan into discrete product facts.
How to fix it
Review the description structure. Label existing product details by topic, such as Product Details, Specifications, Package Contents, Compatibility, Care, Ingredients, or Availability.
Review prompt, not page copy: if this detail already exists in the product record, document existing facts under clear labels using the exact source-derived value only. Relevant fields can include Product Details, Specifications, Package Contents, Compatibility, Care, Ingredients, or Availability.
description