Skip to content

SoftwareApplication schema for SaaS and apps: a working guide

How to add SoftwareApplication structured data for a SaaS product or app: Google's required properties, offers, ratings, WebApplication and what it does not do.

By Crawlito · 6 min read

In short

  • Google's software app rich result requires name, offers.price and either aggregateRating or review; applicationCategory and operatingSystem are recommended.
  • For a free app Google says to set offers.price to 0, and for a paid app it recommends adding offers.priceCurrency.
  • Google supports the MobileApplication and WebApplication subtypes, and says it will not show a rich result for a page typed only as VideoGame.
  • Google's review guidelines say not to aggregate reviews or ratings from other websites, so ratings copied from a review platform do not belong in your markup.
  • The markup can make a page eligible for a rich result; Google says AI Overviews and AI Mode need no special markup, and no AI assistant documents using SoftwareApplication.
On this page

SoftwareApplication is the schema.org type for describing an app: its name, what kind of app it is, which platforms it runs on, what it costs and how users rate it. Google uses it for a software app rich result, and to be eligible a page needs at least name, offers.price and either aggregateRating or review. For a SaaS product you would normally use the WebApplication subtype.

The markup is useful when it describes the page accurately. It does not decide whether Google shows a rich result, and no AI assistant documents using it to pick sources. The rest of this guide covers the properties, a working example, the rules on ratings that trip up most SaaS sites, and how to test.

What Google requires for software app markup

Google's software app structured data documentation splits the properties into required and recommended:

PropertyStatusNotes
nameRequiredThe app's name
offers.priceRequiredSet to 0 if the app is available without payment
aggregateRating or reviewRequired, one of the twoMust follow Google's review snippet guidelines
applicationCategoryRecommendedMust be one of Google's supported app types
operatingSystemRecommendedFor example Windows, macOS, Android or a browser requirement
offers.priceCurrencyRecommended for paid appsSo Google does not have to infer the currency

The supported applicationCategory values include BusinessApplication, DeveloperApplication, FinanceApplication, EducationalApplication, DesignApplication, SecurityApplication, UtilitiesApplication and others. Most B2B SaaS products fit BusinessApplication or DeveloperApplication. Use the exact value from Google's list; free text such as "Marketing software" is not one of them.

The required rating is the condition many sites cannot meet honestly, and it is covered in its own section below.

SoftwareApplication, WebApplication or MobileApplication?

Google says the MobileApplication and WebApplication subtypes are supported. Schema.org's WebApplication adds one property to SoftwareApplication, browserRequirements, a plain-text note such as "Requires a modern browser with JavaScript".

Your productType to use
SaaS used in the browserWebApplication
iOS or Android appMobileApplication
Desktop download, CLI toolSoftwareApplication
GameVideoGame co-typed with another type

Google says it does not show a rich result for a software app that has only the VideoGame type, so a game needs a second type such as MobileApplication. If your product has a web app and mobile apps, mark up the one the page is about rather than combining them in one object.

A complete example for a SaaS product

This example is for a page about one product with a free plan and real, on-page user reviews. Replace every value with your own.

html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebApplication",
  "name": "Example Scheduler",
  "url": "https://www.example.com/scheduler",
  "description": "Online appointment scheduling for small clinics.",
  "applicationCategory": "BusinessApplication",
  "operatingSystem": "Any",
  "browserRequirements": "Requires a modern browser with JavaScript enabled",
  "softwareVersion": "4.2",
  "screenshot": "https://www.example.com/images/scheduler-calendar.png",
  "featureList": "Online booking, SMS reminders, Calendar sync",
  "offers": {
    "@type": "Offer",
    "price": "0",
    "priceCurrency": "USD"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.6",
    "ratingCount": "128"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Software Ltd",
    "url": "https://www.example.com/"
  }
}
</script>

Notes on the optional properties:

  • softwareVersion, screenshot and featureList are schema.org properties of SoftwareApplication. Google's page does not list them as used for the rich result, so treat them as extra description, not ranking inputs.
  • publisher links the app to your organisation. If you already have Organization markup on the site, use the same name and URL.
  • Google's documentation shows offers as a single Offer. If you sell several paid plans, the price you mark up must match a price that is visible on the page. Our post on SaaS pricing pages covers how to make plan prices readable in the first place.

The rating requirement and the review-site trap

Google requires aggregateRating or review for this rich result, and its review snippet guidelines apply. Three rules matter most for software companies:

  1. Do not aggregate ratings from other sites. Google says plainly not to aggregate reviews or ratings from other websites. Copying your G2, Capterra or app store average into aggregateRating breaks this rule, even if the number is accurate.
  2. Ratings must be visible on the page. Google says the review content you mark up must be readily available to users on the marked-up page.
  3. Mark up the specific product. The rating belongs to the app object, not to your whole company.

Google's separate rule against self-serving reviews names LocalBusiness and Organization. It does not mention SoftwareApplication, so it does not explicitly forbid a software company from marking up reviews of its own app collected on its own site. That is not a licence to invent or cherry-pick them: the reviews must be real, shown on the page and gathered from your users.

If you have no on-page reviews, you do not meet the requirement for the rich result. You can still publish SoftwareApplication markup without a rating to describe the product, but the page will not be eligible for the software app rich result. Do not add a rating to get around that. Review and aggregate rating schema goes deeper on the rules.

What SoftwareApplication markup does and does not do

What it does:

  • Makes a page eligible for Google's software app rich result, if every requirement is met.
  • Gives any parser that reads JSON-LD an unambiguous statement of the product's name, category, platform and price.

What it does not do:

  • It does not guarantee a rich result. Google decides whether to show one. Pages that break the guidelines can also receive a manual action, in which case Google ignores their structured data.
  • It is not required for Google's AI features. Google's AI features page says you do not need new machine-readable files, AI text files or markup to appear in AI Overviews or AI Mode.
  • No AI assistant documents using it. OpenAI, Anthropic and Perplexity do not mention SoftwareApplication in their crawler documentation. Some tools may parse JSON-LD, but there is no published evidence that this type influences what they cite.

The practical value is consistency. If the visible page says "Free plan, then $29 per month" and the markup says the same thing, every system reading the page gets the same answer. Structured data for AI search explains why markup that contradicts the page does more harm than none.

How to test SoftwareApplication markup

  1. Check it is in the raw HTML. Many SaaS marketing sites inject JSON-LD with a tag manager or client-side script. Fetch the page without JavaScript and confirm it is there:

    bash
    curl -s https://www.example.com/scheduler | grep -c 'application/ld+json'
  2. Run Google's Rich Results Test. It reports whether the page is eligible for the software app result and lists missing required properties.

  3. Run the Schema Markup Validator. It checks the markup against schema.org generally, including properties Google ignores.

  4. Compare with the visible page. Price, currency, rating value and rating count must match what a visitor sees.

  5. Monitor Search Console. If the site has eligible pages, Search Console may show an enhancement report for the type, with errors and warnings over time.

If the tests report parse errors, fixing JSON-LD errors covers the common causes, such as trailing commas and unescaped quotes.

Common mistakes

MistakeWhy it is a problemFix
Rating copied from a review siteGoogle says not to aggregate ratings from other websitesShow and mark up only reviews collected on the page
applicationCategory: "SaaS"Not a supported valueUse BusinessApplication or another listed value
No offersoffers.price is requiredAdd an Offer with price and priceCurrency
Price in markup differs from the pageContradicts the visible contentGenerate both from the same source
Markup injected only by JavaScriptCrawlers that do not run scripts never see itRender JSON-LD in the server HTML
One object for web, iOS and AndroidMixes products with different platforms and pricesOne object per app, on the page about that app

Frequently asked questions

Is SoftwareApplication schema required to rank a SaaS page?

No. It makes a page eligible for a software app rich result. Google ranks pages on many signals, and its AI features need no special markup.

Can I use my G2 or Capterra rating in aggregateRating?

No. Google's review snippet guidelines say not to aggregate reviews or ratings from other websites. Mark up only ratings collected and shown on your own page.

Should a SaaS product use WebApplication or SoftwareApplication?

Use WebApplication for software that runs in the browser. Google supports it as a subtype, and it is still a SoftwareApplication, so the same required properties apply.

What price should a free product use?

Google says to set offers.price to 0 if the app is available without payment. If there is a free plan and paid plans, the markup should still match a price that is visible on the page.

Check your product pages

The free check fetches a page's raw HTML and reports whether structured data is present, parses and matches the visible content. For a SaaS site with many feature and pricing pages, an audit reviews them together.

Filed under Structure and schema. Topics: structured-data, json-ld, google