Offer schema

Where to use it

Nested inside Product, Service or SoftwareApplication.

A complete example

Valid as written, with every required property and the recommended ones that carry real information.

{
  "@context": "https://schema.org",
  "@type": "Offer",
  "price": "249.00",
  "priceCurrency": "USD",
  "availability": "https://schema.org/InStock",
  "url": "https://www.seoforsolos.com/example",
  "priceValidUntil": "2027-07-27",
  "priceSpecification": {
    "@type": "UnitPriceSpecification",
    "price": "249.00",
    "priceCurrency": "USD",
    "valueAddedTaxIncluded": true
  },
  "seller": {
    "@id": "https://www.seoforsolos.com/#organization"
  }
}

Properties

The three mistakes this type attracts

1. 01A price without a currency, which is not a price.
2. 02Omitting availability, leaving stock state unknown.
3. 03A price as a float with floating point error rather than a fixed decimal string.

Related types

• ContactPoint
• PostalAddress
• Thing
• Organization
• WebSite
• WebPage

Where this appears in the playbook

• Structured data: what each type is for and which ones earned their place.
• The schema graph: composing types into one graph with stable identifiers.
• One JSON-LD script per page, holding one @graph
• Stable @id anchors that cross-reference rather than duplicate
• Optional fields are omitted, never emitted as empty strings