SoftwareApplication markup for a small SaaS: what it needs
Short answer: SoftwareApplication markup describes your app to Google: its name, price and a rating or review, plus recommended details such as the app category and operating system. Google requires a name, an offer with a price (0 if free) and either an aggregate rating or a review. That last requirement is the catch for many young SaaS products: if you don't have genuine, visible ratings yet, you can't meet the eligibility rules honestly, and it's better to wait than to invent them.
Founders building a small software product often hear that "schema" will make their listing stand out. For software, the relevant type is SoftwareApplication, with subtypes for web and mobile apps. This explainer covers what Google actually asks for, how the fields map to a typical SaaS, and where the markup fits alongside your other pages.
What the markup is for
Google's documentation describes software app structured data as a way to better display your app's details in Google Search results, and notes that actual appearance may differ. The Rich Results Test can preview most features. In practice, the details that can surface are things like the rating and price.
The required fields
According to Google's documentation, three things are required:
1. name: the app's name.
2. offers.price: an Offer with the app's price. If the app is free, set the price to 0. For paid apps, Google recommends also including priceCurrency (otherwise Google tries to work out the currency). For a SaaS with several plans, the documentation's model of a single offer fits awkwardly; a common approach is to mark up the entry price of the plan shown on the page, matching what visitors see.
3. A rating or review: you must include either aggregateRating (the average score) or review (a single review), following Google's review snippet guidelines and their required and recommended properties.
Without all three, the markup isn't eligible for the software app rich result.
The recommended fields
applicationCategory: the type of app, which must be one of Google's supported values. The list includes BusinessApplication, FinanceApplication, DeveloperApplication, DesignApplication, EducationalApplication, CommunicationApplication and others. Most B2B SaaS products fit BusinessApplication or a more specific category.operatingSystem: the operating systems the app needs. For a browser-based SaaS, this is typically described as running in a web browser, with any platforms for companion apps.
Choosing the type
Google supports SoftwareApplication and its subtypes, including WebApplication for browser-based software and MobileApplication for mobile apps. A SaaS with a web app and companion mobile apps can describe the main product as a WebApplication on its product page.
The documentation also notes a gaming-specific rule: Google doesn't show a rich result for apps typed only as VideoGame, and recommends co-typing it with another type. That rarely affects business software, but shows how strictly types are read.
The rating problem for young products
Here's where many SaaS founders get stuck. The rating or review requirement means you need real feedback that's represented accurately.
Things that are tempting but wrong:
- an
aggregateRatingwith numbers that aren't shown anywhere on the page; - a rating made up from a handful of hand-picked testimonials;
- copying a score from a review platform without showing it or linking to it.
Google's review snippet documentation lists Software App among the types that support reviews, and it requires following its review guidelines. As a principle across all structured data, the information should reflect what visitors can see on the page.
What to do instead:
- Collect genuine ratings first. Build a simple, honest way for customers to rate the product in-app or after onboarding, and display the results on your site.
- Show the rating visibly on the page where the markup lives, with the number of ratings.
- Keep it current. Update the markup when the average or count changes; automating it from your database avoids drift.
If you don't have enough ratings yet, leave SoftwareApplication markup until you do, and put your effort into clear product pages and Organization markup.
Where the markup goes
- Product or home page: if your homepage is essentially the product page, the markup can live there. Otherwise, put it on the main product or pricing page that describes the app.
- One app, one main block. Don't repeat full SoftwareApplication markup on every blog post.
- Separate products, separate pages. If you offer more than one app, give each its own page and markup.
A simple example structure
For a hypothetical booking SaaS:
@type: WebApplicationname: the product nameapplicationCategory: BusinessApplicationoperatingSystem: a web browser descriptionoffers: Offer withpriceandpriceCurrencymatching the entry plan shown on the pageaggregateRating:ratingValueandratingCountfrom your own displayed ratings
Validate it with the Rich Results Test and fix errors before publishing.
How it fits with the rest of your site
SoftwareApplication markup is one piece. Organization markup (your company, logo and profiles) belongs on the homepage or about page. Clear pricing, feature and integration pages do more for both visitors and search than markup alone. And documentation or help pages, which many SaaS sites already have, often attract more search traffic than the product page itself.
FAQ
Can I use ratings from a third-party review site?
Only in ways that follow Google's review guidelines and reflect what's shown on your page. Displaying the rating and linking to the source is the minimum; check the guidelines before relying on it.
My SaaS has a free plan. Is the price 0?
If the app is available without payment, Google says to set the price to 0. If you only have paid plans with a trial, use the price of the entry plan shown on the page.
Do I need the operatingSystem field for a web app?
It's recommended, not required. Describing it as browser-based is accurate for most SaaS products.
Will this markup improve my rankings?
Structured data helps Google understand and display your page; it isn't a ranking shortcut. Google doesn't guarantee rich results will appear.
If you're unsure whether your SaaS is ready for software markup, share your product page and we'll check what you can mark up honestly today.