Product schema

Use Product when the primary entity represented by the visible page matches the Schema.org definition. Select a more specific subtype when accurate.

• name

• @id
• image
• description
• brand
• sku
• offers
• review
• aggregateRating

{
  "@context": "https://schema.org",
  "@type": "Product",
  "@id": "https://example.com/products/example/#product",
  "name": "Example Product",
  "description": "A visible description of the product.",
  "brand": {
    "@type": "Brand",
    "name": "Example Brand"
  }
}

• Choosing the type only because a rich result is desired.
• Adding properties not visible or supported by the site.
• Creating conflicting duplicate entities instead of using stable @id values.
• Failing to update markup when visible data changes.

Use Product only when the page visibly represents the corresponding entity or relationship. Begin with the page purpose and the entity graph, then select the most specific supported type. Do not let the available vocabulary dictate claims the page does not make.

• Commercial outcomes connected to the technical and content change.
• Record the page template, generator, source fields, responsible owner, and release reference.
• Avoid allowing price, stock, review, or product structured data to diverge from visible content.
• Test representative product, category, filter, cart, and checkout journeys and compare search and revenue signals.
• Schedule review when visible content, offers, ownership, locations, products, or consumer documentation changes.

Search visibility and user value improve when product answers the real questions people bring to the page. For business owners, marketers, seo practitioners, and developers, that means covering the decision context, observable signals, implementation boundaries, and proof that the result works in production—not repeating a keyword or publishing a longer version of the same incomplete explanation.

Use the page as part of a connected topic cluster. Link the broad concept to focused implementation guides, definitions, checklists, examples, and the Asuruas workflow that can identify affected URLs. The goal is to help a reader move from discovery to a confident next action while giving search systems clear entities, relationships, and page purpose.

• Inspect product and category discoverability.
• Inspect variant, offer, and availability consistency.
• Inspect checkout performance and error recovery.
• Inspect merchant, schema, and trust information.