CRITICALCategory-specific fields need review+20
For uncategorized, CRS detected size but not as standardized fields, and could not find material, color, weight, dimensions.
How to fix it
Review existing product data for size and standardize those exact source-derived values. Also check whether material, 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.
sizematerialcolorweightdimensions
CRITICALProduct schema missing+15
CRS could not find Product structured data for the page. This makes the product harder for crawlers to read as a product with offer, price, availability, and identifier fields.
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
HIGHDescription uses vague language and lacks specific product facts+10
CRS found vague wording (finest) and no 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
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