HIGHCategory-specific fields need review+13
For uncategorized, CRS detected size but not as standardized fields, and could not find color, weight, dimensions.
How to fix it
Review existing product data for size and standardize those exact source-derived values. Also check whether color, weight, dimensions exists elsewhere in the product record before adding any new 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.
sizecolorweightdimensions
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 relies on vague wording+9
CRS found vague wording (innovative) that is harder to match to specific shopper queries.
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