Product schema: required fields and common mistakes

• ✓name
• ✓offers with price and priceCurrency, or an AggregateOffer

• +image
• +description
• +sku
• +brand
• +aggregateRating
• +review

These are hints, not blockers. Our validator marks them non-critical for exactly that reason: a missing optional field does not make the item invalid, and treating it as an error would make every report noisy and therefore ignorable.

• A price that does not match the price on the page. Google checks the visible content, and a mismatch removes the rich result and can earn a manual action.
• Marking a category page as a Product. A page listing many products is an ItemList, not a Product.
• An AggregateOffer with no lowPrice, which is the field the feature needs.
• A price in a currency string, like "$10", instead of 10 and priceCurrency: USD.

Structured data describes the page; it does not make the page true. Google also requires the visible content to match, and it decides eligibility on its own published requirements — which change without notice. A valid block that matches the page is the whole of what you control.

Test it on a real URL with the free schema validator — no account, and it reports eligible, ineligible, or not applicable without inventing a score.

• Article — Marks a page as a news or blog article. Covers BlogPosting and NewsArticle too.
• LocalBusiness — Marks a page as a physical business, with an address and opening hours.
• Organization — Marks a page as representing an organisation rather than a person.
• BreadcrumbList — Marks a page as a position in a hierarchy, for the breadcrumb in a result.
• Person — Marks a page as being about, or written by, a person.
• WebSite — Marks the site itself, usually on the homepage.
• FAQPage — Marked a question-and-answer page. Google stopped showing these as a rich result.
• HowTo — Marked a set of steps. Google stopped showing these as a rich result.