SoftwareApplication schema

Where to use it

Tool pages, app landing pages.

A complete example

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

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Acme Reference",
  "applicationCategory": "DeveloperApplication",
  "operatingSystem": "Web browser",
  "offers": {
    "@type": "Offer",
    "price": "249.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.seoforsolos.com/pricing"
  },
  "featureList": [
    "Generates JSON-LD",
    "Validates required properties"
  ],
  "softwareVersion": "1.0.0",
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": 4.8,
    "reviewCount": 42
  }
}

Generate a SoftwareApplication node with your own values in the schema generator, and lint what your page actually ships with the schema validator.

Properties

The three mistakes this type attracts

1. 01Omitting a free Offer on a free tool, leaving its cost unknown.
2. 02applicationCategory set to a value outside the documented list.
3. 03Using it for a marketing page that describes rather than provides the tool.

Related types

• SpeakableSpecification
• Product
• Offer
• AggregateOffer
• UnitPriceSpecification
• WebApplication

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
• Does schema markup work? What 42 types on one site actually did: which of these types measurably did anything in production.