SoftwareApplication Schema
SoftwareApplication is the schema.org type purpose-built for SaaS products. Most indie SaaS sites don't use it, which means they look like generic web pages to AI systems. SaaSalyst validates a SoftwareApplication (or fallback Product) JSON-LD block with the required fields.
What SaaSalyst Checks
SaaSalyst parses every JSON-LD block (walking @graph) and looks for @type: SoftwareApplication or @type: Product. The check passes when name, applicationCategory, and either offers or aggregateRating are present. It warns when name + applicationCategory exist but offers and aggregateRating are both missing. It fails when no SoftwareApplication or Product exists, or when required fields are absent.
Why This Matters
SoftwareApplication is structured data that tells AI systems and search engines: "this is a software product, here's its category, here's what it costs, here's what users rate it." Generic Organization schema doesn't carry that information; FAQPage and Article carry different content.
Google's docs at developers.google.com/search/docs/appearance/structured-data/software-app describe the field set; AI systems use the same vocabulary. The expected field is applicationCategory (e.g., BusinessApplication, DeveloperApplication) — without it, AI systems know it's software but don't know what kind.
We expect roughly 85% of $0–5K MRR SaaS sites to fail this check on first scan. That's intentional product positioning: SaaSalyst is a SaaS-aware scanner, and most generic SEO tools don't validate this. Adding SoftwareApplication schema is one of the highest-leverage AI discoverability fixes for indie SaaS.
How to Fix It
- Add a <script type="application/ld+json"> block with @type: SoftwareApplication, name, applicationCategory (e.g., "BusinessApplication"), and either offers (price + currency) or aggregateRating (ratingValue + reviewCount).
- Use Product as a fallback if your offering doesn't fit SoftwareApplication's mold (rare for SaaS). SaaSalyst accepts both.
- Place it on the homepage and on product/pricing pages. Google specifically calls out homepage and /pricing as the right surfaces.
- applicationCategory values should match Google's recommended list — "BusinessApplication", "DeveloperApplication", "DesignApplication", etc.
Frequently Asked Questions
Why is this SaaS-specific?
Because SoftwareApplication has fields (applicationCategory, offers, aggregateRating, operatingSystem) that don't make sense for content sites or e-commerce. SaaSalyst validates these specifically to catch the case where a SaaS product is missing the structured data type that fits it.
Why warn instead of fail when offers/aggregateRating are missing?
Because some SaaS products don't have public pricing (enterprise sales) or aren't on review platforms yet (early stage). The schema is structurally valid without those fields. SaaSalyst warns to surface the opportunity without penalizing pre-revenue stages.
What if I have Product schema instead of SoftwareApplication?
SaaSalyst accepts Product as a fallback. Both are valid for software, though SoftwareApplication is more semantically precise. Switch to SoftwareApplication if your product fits — it carries more information that AI systems can use.
Check Your SaaS Now | Free
SaaSalyst scans your website in 30 seconds and checks for SoftwareApplication Schema along with 101+ other business readiness signals.
Scan Your App