SoftwareApplication schema markup
Describes a software product, its price, category and rating.
Does Google still show a rich result for this?
Supported, showing rating information, a description and a link — but note the catch. Google requires either an aggregateRating or a review, and the self-serving review rule means a company cannot supply that for its own software. In practice the rich result is reachable by app directories and review sites, and not by the vendor. A product typed only as VideoGame is excluded too; it needs a co-type such as MobileApplication.
When to use it
On a page for an app or a web application, including free tools. Add it to describe the software accurately even where the rating requirement puts the rich result out of reach — that is the position this site is in, and our own tool pages carry the markup without a rating for exactly that reason.
Required properties
nameoffers.priceeither aggregateRating or review
Recommended properties
applicationCategoryoperatingSystem
Example
{
"@context": "https://schema.org",
"@type": "WebApplication",
"name": "Free Meta Tag Checker",
"applicationCategory": "SEO Tool",
"browserRequirements": "Requires JavaScript",
"offers": { "@type": "Offer", "price": "0", "priceCurrency": "GBP" }
}Common mistakes
- Omitting offers.price for a free tool. Set it to 0 rather than leaving it out.
- Putting the platform into applicationCategory. That field takes a category such as "SEO Tool"; a browser application is expressed by the WebApplication type and browserRequirements.
- Inventing an aggregateRating to satisfy the rating requirement. The self-serving review rule applies here too, so a rating you wrote about your own software does not earn the rich result — it just puts a false claim in your markup. Ship without it.
Check what your own pages are missing
Our free checker reads the markup already on a page and names the types it is missing for its page type. No account needed.
Run the schema checker →Verified against Google’s structured data documentation and its changelog on 28/07/2026. Google changes what it supports without much notice — if you are reading this long afterwards, check the current documentation before acting on it. Background on why this markup matters beyond rich results is in the answer engine optimisation guide.