schema.org/WebApplicationRich result eligible

WebApplication schema

A subtype of SoftwareApplication that runs in a browser.

Where to use it

Browser-based tools.

A complete example

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

web-application.json

{
  "@context": "https://schema.org",
  "@type": "WebApplication",
  "name": "Acme Reference",
  "applicationCategory": "DeveloperApplication",
  "browserRequirements": "Requires JavaScript",
  "offers": {
    "@type": "Offer",
    "price": "249.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.seoforsolos.com/pricing"
  },
  "permissions": "No special permissions required",
  "featureList": [
    "Generates JSON-LD",
    "Validates required properties"
  ]
}

Properties

WebApplication properties
Property	Status
`name`	Required
`applicationCategory`	Required
`browserRequirements`	Recommended
`offers`	Recommended
`permissions`	Recommended
`featureList`	Recommended

The three mistakes this type attracts

01Using SoftwareApplication when WebApplication is more specific.
02Omitting browserRequirements on a tool with real constraints.
03Duplicating both types in one graph for the same thing.

Related types

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

Questions

What is the WebApplication schema type for?

A subtype of SoftwareApplication that runs in a browser. Use it on: browser-based tools.

Which WebApplication properties are required?

WebApplication requires 2 properties: name, applicationCategory. It also recommends 4: browserRequirements, offers, permissions, featureList.

Does WebApplication produce a rich result?

WebApplication is eligible for a Google rich result when its required properties are present and valid. A validation error therefore has a visible cost in the search result itself.

What is the most common WebApplication mistake?

The most common WebApplication mistake is: Using SoftwareApplication when WebApplication is more specific.