How to implement SoftwareApplication schema on a SaaS site
Written by Olayinka Olayokun·Published ·Updated ·Verified
SoftwareApplication schema for SaaS is the JSON-LD markup applied to a SaaS product page that declares the page is about a software application, with required fields name, operatingSystem, applicationCategory, and optional offers, aggregateRating, and screenshot.
Summary and key takeaways
SoftwareApplication is the right schema type for a SaaS product page — not Product, not WebPage. The required fields are name, operatingSystem (use 'Web' for browser SaaS), and applicationCategory. Add offers for pricing visibility in SERPs, aggregateRating only if you have legitimate review data, screenshot for visual context. Skip features Google doesn't actually use.
- •Use SoftwareApplication, not Product or WebApplication, as the @type for a browser SaaS.
- •operatingSystem should be 'Web' for browser-based SaaS; list specific OSes only if there's a native app.
- •offers enables pricing data in SERP — only include if your pricing is stable and public.
- •aggregateRating requires real review data from a verifiable source; faking it triggers manual action.
- •Implement on the homepage and the dedicated product page; not on every page sitewide.
In plain English ·SoftwareApplication is the schema.org type that correctly describes a SaaS product. Required fields (name, operatingSystem, applicationCategory) plus optional offers and aggregateRating cover what Google actually uses; the rest of the type's schema is documentation Google ignores.
- 3
- Required SoftwareApplication fields: name, operatingSystem, applicationCategory schema.org SoftwareApplication
How this compares
| Schema type | Use when | Avoid when |
|---|---|---|
| SoftwareApplication | SaaS product page or homepage | Generic content / blog pages |
| Product | Physical goods or non-software products | Software SaaS (use SoftwareApplication) |
| WebApplication | Browser app, more specific than SoftwareApplication | When SoftwareApplication serves; WebApp is rarely needed |
| Offer (standalone) | Pricing page | Pages without pricing data |
Part of the Schema Markup for SaaS: JSON-LD That Actually Validates guide
SoftwareApplication schema for SaaS is the JSON-LD markup applied to a SaaS product page that declares the page is about a software application, with required fields name, operatingSystem, applicationCategory, and optional offers, aggregateRating, and screenshot.
Most SaaS sites either skip schema entirely (missing rich result eligibility and entity signal) or use the wrong type (Product instead of SoftwareApplication, generic WebPage instead of either). Both leave SERP CTR and AI Overview citation on the table. The fix is one well-formed JSON-LD block on two pages — a 15-minute implementation with measurable lift.
What this chapter covers: type-correct, field-minimal, page-scoped, validation-clean.
The minimum valid SoftwareApplication block
Three required fields: name (the product's display name), operatingSystem ('Web' for browser SaaS), and applicationCategory (use schema. org's vocabulary — 'BusinessApplication', 'DesignApplication', 'DeveloperApplication', etc. ).
Three required fields: name (the product's display name), operatingSystem ('Web' for browser SaaS), and applicationCategory (use schema.org's vocabulary — 'BusinessApplication', 'DesignApplication', 'DeveloperApplication', etc.).
Wrap in JSON-LD inside a single <script type="application/ld+json"> tag in the page <head>. Don't use microdata or RDFa — JSON-LD is Google's preferred format and the only one well-supported across other parsers (Bing, AI engines).
Optional fields worth including
offers: a single Offer object with price (use '0' for freemium) and priceCurrency. Unlocks price visibility in SERP rich results.
offers: a single Offer object with price (use '0' for freemium) and priceCurrency. Unlocks price visibility in SERP rich results.
screenshot: URL to a representative product screenshot (1200×800 minimum). Used in some rich result formats and AI Overviews.
aggregateRating: only if you have legitimate review data from a verifiable source. Don't fabricate.
publisher: an Organization node linking to your company. Required for proper entity graph connection.
softwareVersion, datePublished, fileSize, downloadUrl: rarely used by Google; skip unless documenting a downloadable variant.
Common implementation mistakes
Schema on every page sitewide: SoftwareApplication on a blog post is noise. Apply only on homepage and dedicated product page.
Schema on every page sitewide: SoftwareApplication on a blog post is noise. Apply only on homepage and dedicated product page.
Invalid offers (price as 'Free' instead of '0', missing priceCurrency): breaks rich result eligibility silently.
Schema in HTML that never reaches Google because the page is client-rendered: validate using URL Inspection → Rendered HTML, not just the source view in DevTools.
Multiple conflicting schemas on the same page (SoftwareApplication AND Product AND WebPage): Google picks one or none. Pick one and own it.
Validation workflow
Paste the page URL into Google's Rich Results Test. Fix every error before shipping. Warnings can usually be ignored if they apply to fields you intentionally omitted.
Paste the page URL into Google's Rich Results Test. Fix every error before shipping. Warnings can usually be ignored if they apply to fields you intentionally omitted.
Cross-validate with the Schema Markup Validator (validator.schema.org). Both should pass with zero errors. Re-test after every meaningful change to the page or the JSON-LD block.
The checklist for this chapter
- ✓Use @type SoftwareApplication (not Product or WebApplication)
- ✓Set operatingSystem to 'Web' for browser-based SaaS
- ✓Pick a real schema.org applicationCategory
- ✓Add offers with priceCurrency only if pricing is stable and public
- ✓Include aggregateRating only if legitimate review data is available
- ✓Validate with Rich Results Test and Schema Markup Validator before shipping
Where this chapter sits in the guide
clean server-rendered HTML — JSON-LD in a script tag that never reaches Google because the page is client-rendered is invisible. Read the related guide →
entity disambiguation — SoftwareApplication links the product node to the Organization node via the publisher field. Read the organization and sameas schema for saas entity disambiguation chapter →
Google's Rich Results Test and the Schema Markup Validator — both should pass with zero errors.
Product schema — Product is for goods; SoftwareApplication is the SaaS-specific subtype with software-relevant rich result eligibility.
Quick answers about softwareapplication schema for saas
- Why SoftwareApplication and not Product?
- Product is for physical goods or generic products; SoftwareApplication is the schema.org subtype specifically for software. Google parses both, but SoftwareApplication unlocks software-specific rich result eligibility (download counts, ratings, pricing) that Product doesn't.#
- Which pages should have SoftwareApplication schema?
- The homepage and the dedicated product/feature page. Not pricing pages (use Offer or PriceSpecification standalone there), not blog posts, not landing pages targeting specific use cases. Schema bloat on irrelevant pages is a negative signal.#
- Can I make up aggregateRating values?
- Absolutely not. Google's manual action team penalises fake ratings; legitimate ratings must come from a verifiable source like G2, Capterra, or a structured review feed on your own site. If you don't have legitimate aggregate review data, omit aggregateRating entirely.#
- How do I represent freemium pricing in offers?
- Use a single offers object with a low price representing the free or entry-level plan: offers.price = '0', offers.priceCurrency = 'USD'. Google then surfaces 'Free' in price-related SERP features. For paid-only plans, use the lowest tier as the price.#
Questions about softwareapplication schema for saas
- No — WebApplication is a subtype of SoftwareApplication. Pick the parent type unless you have a specific reason (rare) to use the more specific child. SoftwareApplication with operatingSystem='Web' is functionally equivalent to WebApplication for Google's purposes.
- SoftwareApplication is the schema.org type for software products including web apps. schema.org — SoftwareApplication
- Google supports structured data for software apps via SoftwareApplication. Google Search Central — software app
This chapter is one node in the founder-led playbook. To see which nodes your specific URLs are bleeding traffic from, get a founder-grade SEO audit of your URLs. Same six disciplines, applied to the pages you actually own.
Olayinka Olayokun
Founder, SERPNAUT and Invoicemonk
Written by Olayinka Olayokun. I run SERPNAUT, a founder-led SEO service for B2B SaaS, and Invoicemonk, the SaaS I grew from zero to 300+ organic visits and a paying customer in 28 days using the same playbook. Everything below is what worked on my own URLs and on the audits I've shipped since.
More chapters in this guide
SoftwareApplication is the foundational schema move for any SaaS site — the one block of structured data that earns its weight by signalling to both Google and emerging AI engines what your product actually is. Combined with Organization schema for entity disambiguation and BreadcrumbList for site structure, it forms the minimum schema kit every SaaS marketing site should ship with.
See the full guide at schema markup for saas: json-ld that actually validates. The commercial bridge above is the canonical path from this chapter to your URLs.