SoftwareApplication Schema for SaaS: JSON-LD Examples, Google's Rules and What It Does for AI Search

#What SoftwareApplication schema is

SoftwareApplication is a schema.org type for describing a piece of software: its name, what category it's in, what it runs on, what it costs and how it's rated. You add it to a page as JSON-LD, a block of structured data in a script tag that search engines and other machines read without parsing your design.

It has more specific subtypes. Google supports two of them for software: WebApplication (anything that runs in a browser, which is most SaaS) and MobileApplication. Use the most specific one that fits.

For a SaaS site, SoftwareApplication is one of three blocks that belong on the homepage:

Every rule below comes from Google Search Central documentation checked on October 2, 2026.

#Google's rules for the software app rich result

Google's software app documentation lists what it needs:

The catch for a new SaaS is the third row. Without a rating or review, the page isn't eligible for the rich result with stars. That doesn't make the markup useless (it still describes your product in a machine-readable way), but don't expect stars until you have real reviews to show.

Google also notes that it doesn't guarantee any feature that uses structured data will appear, even when the markup is valid.

#Copy-paste JSON-LD for a SaaS homepage

Put all three in one script tag in the head of your homepage, using @graph so they can reference each other. Replace every value; don't ship the placeholders.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://yourproduct.com/#org",
      "name": "YourProduct",
      "url": "https://yourproduct.com/",
      "logo": "https://yourproduct.com/logo-512.png",
      "sameAs": [
        "https://x.com/yourproduct",
        "https://www.linkedin.com/company/yourproduct",
        "https://github.com/yourproduct"
      ]
    },
    {
      "@type": "WebSite",
      "@id": "https://yourproduct.com/#website",
      "name": "YourProduct",
      "url": "https://yourproduct.com/",
      "publisher": { "@id": "https://yourproduct.com/#org" }
    },
    {
      "@type": "WebApplication",
      "@id": "https://yourproduct.com/#app",
      "name": "YourProduct",
      "url": "https://yourproduct.com/",
      "description": "Invoicing for freelancers: create, send and chase invoices from one screen.",
      "applicationCategory": "BusinessApplication",
      "operatingSystem": "Web",
      "publisher": { "@id": "https://yourproduct.com/#org" },
      "offers": {
        "@type": "Offer",
        "price": "0",
        "priceCurrency": "USD",
        "description": "Free plan for up to 10 clients"
      }
    }
  ]
}
</script>

If you have real, visible ratings, add this inside the WebApplication object, with numbers that match what the page shows:

"aggregateRating": {
  "@type": "AggregateRating",
  "ratingValue": "4.7",
  "ratingCount": "38"
}

If you have paid plans, you can list the cheapest price in offers, or use an AggregateOffer with lowPrice and highPrice. Keep it in sync with your pricing page; a stale price in markup is a page that says two different things.

Useful optional properties from schema.org: featureList (the main features, as text), screenshot (an image URL), softwareVersion, and applicationSubCategory.

#Organization and WebSite: the two blocks to add first

If you only add one thing this week, add these two. They're simple, they have no rating requirement, and they tell Google who you are.

Organization. Google's Organization documentation says there are no required properties and recommends adding as many relevant ones as you can. The useful ones for a startup:

• url, which Google says helps it uniquely identify your organization.
• logo, at least 112 by 112 pixels, at a URL that's crawlable and indexable.
• sameAs, links to your profiles elsewhere (X, LinkedIn, GitHub, Crunchbase). You can list several.

WebSite. Google's site names documentation says WebSite structured data on your homepage is the most important signal for the site name shown in results, ahead of og:site_name, the title element and headings. It needs name and url (your canonical homepage), and alternateName if your product is also known by another name or an abbreviation. If Google shows your domain instead of your product name, this is the fix.

#Which applicationCategory to use

Google's documentation says applicationCategory must be one of its supported app types. Pick the one closest to what a buyer would call your product:

The full list also includes DesktopEnhancementApplication, DriverApplication, EntertainmentApplication, GameApplication, HomeApplication, LifestyleApplication, ReferenceApplication, ShoppingApplication, SocialNetworkingApplication and TravelApplication. One more rule: Google doesn't show a rich result for software typed only as VideoGame, so a game should be co-typed with another type.

#Schema for other pages on a SaaS site

The homepage carries the three main blocks. Elsewhere, add markup only where it describes what's really on the page:

• Pricing page: the same WebApplication entity (reference it by its @id) with offers for each plan. Keep prices identical to the visible table.
• Blog posts and guides: Article or BlogPosting with a headline, author, datePublished and dateModified. This helps Google show the right dates.
• Docs and nested pages: BreadcrumbList, which matches your breadcrumb trail.
• About page: the Organization entity again, with founders and founding date if you show them.

Don't copy the homepage's full SoftwareApplication block onto every page. One clear entity, referenced where needed, is easier for any system to read than twenty slightly different copies.

#The rules that get markup ignored or penalized

Google's general structured data guidelines are short and strict:

• Don't mark up content that isn't visible to readers. If the page doesn't show a 4.8 rating, the markup can't claim one.
• Structured data must be a true representation of the page. The price, the category and the name should match what visitors see.
• No fake or misleading content, including fake reviews. In July 2026 Google added that you shouldn't include fake or undisclosed incentivized reviews on the page or in the markup.

Self-serving reviews. Since 2019, Google has treated reviews of an entity placed on that entity's own site as self-serving, and pages using Organization or LocalBusiness markup are ineligible for star review snippets on that basis. SoftwareApplication is still eligible for review snippets, but only for real reviews from real users that the page shows. Ratings you collected yourself and don't display, or numbers copied from a review site without showing them, don't qualify.

#FAQ and HowTo schema in 2026

Many guides still tell you to add FAQPage markup for rich results. That advice is out of date:

• In August 2023 Google limited FAQ rich results to well-known, authoritative government and health sites, and deprecated HowTo rich results (announcement).
• In May 2026 Google deprecated the FAQ rich result entirely: its Search updates log says the feature no longer appears in Google Search starting May 7, 2026, and the documentation was removed in June.

FAQPage markup on a page with real questions and answers isn't harmful, and other systems may read it. But it won't earn a rich result in Google, so don't add it for that reason, and never add FAQ markup for questions that aren't on the page.

#Does schema help with AI search?

Less than most "schema for AI" articles claim, and Google is explicit about it. Its AI features documentation says there are no additional requirements to appear in AI Overviews or AI Mode, and that there's no special schema.org structured data you need to add. Its newer AI optimization guide says structured data isn't required for generative AI search, but that it's a good idea to keep using it as part of your overall SEO because it helps with rich result eligibility.

So here's the honest case for schema on a SaaS site:

• It states facts unambiguously: your product's name, category, platform, price and maker. Any system that reads it doesn't have to guess from your hero copy.
• sameAs connects your site to your profiles elsewhere, which helps systems tell your product apart from others with similar names.
• It feeds Google features that do exist: site names, logos and the software app rich result once you have ratings.

What it won't do is get you cited by ChatGPT, Perplexity or AI Overviews on its own. That comes from being crawlable, being clearly described, and being mentioned on the sources AI answers draw from. See how to get recommended by ChatGPT and how to check AI crawler access.

#How to add it and test it

1. Add the JSON-LD to the head of your homepage. In Next.js, render a script tag with type="application/ld+json" from your layout or page; in WordPress, most SEO plugins have a setting for organization and site details; on Webflow or Framer, use the custom code area for the page head.
2. Test with Google's Rich Results Test. It shows which rich result types the page is eligible for and any errors or warnings.
3. Validate the schema itself with the Schema Markup Validator. It checks against all of schema.org, not only what Google uses.
4. Check after indexing. Search Console shows reports for the structured data types Google finds on your site, with errors per page.

If the Rich Results Test says your SoftwareApplication item is missing a rating or review, that's expected for a new product. It means the page isn't eligible for stars yet; the Organization and WebSite blocks are unaffected.

#Check and generate it with Verdy

A free Verdy audit checks whether your pages have JSON-LD at all and flags pages with none, alongside your titles, previews, sitemap, robots.txt and AI crawler access. The launch console's website check includes the same JSON-LD check in your Launch Score. The paid fix pack generates Organization and WebSite JSON-LD from your own pages, and adds a SoftwareApplication block only when your page shows pricing, with a note to add your real prices and an applicationCategory. It deliberately doesn't invent ratings.

#Common mistakes

• Ratings that aren't on the page, or copied from a review site without showing them. Against Google's guidelines.
• Shipping the placeholders. "YourProduct" and "https://example.com" in production markup are more common than you'd think.
• Two Organization blocks from a theme and a plugin, with different names or logos. Merge them into one.
• A price in markup that differs from the pricing page. Update both when you change plans.
• Adding FAQ markup for rich results in 2026. The feature is gone from Google Search.
• Treating schema as an AI shortcut. Google says there isn't one.

#FAQ

#What is SoftwareApplication schema?

It's a schema.org type for describing software in structured data: its name, category, operating system, price and ratings. Google uses it for the software app rich result and supports the WebApplication and MobileApplication subtypes.

#What fields does Google require for SoftwareApplication?

Google requires name, offers.price and either aggregateRating or review. It recommends applicationCategory and operatingSystem, and offers.priceCurrency when the price is above zero. If the app is free, set offers.price to 0.

#Should a SaaS use SoftwareApplication or WebApplication?

WebApplication, if the product runs in the browser. It's a more specific subtype of SoftwareApplication, and Google supports it for the software app rich result. Use MobileApplication for a native app.

#Can I add star ratings to my SaaS schema without reviews?

No. Google's guidelines say you must not mark up content that isn't visible on the page, and fake or self-collected ratings that aren't shown violate them. Without real, visible ratings or reviews, you won't get stars, but the rest of the markup still describes your product.

#Is FAQ schema still worth adding in 2026?

Not for Google rich results. Google stopped showing FAQ rich results on May 7, 2026, after limiting them to government and health sites in 2023. Markup for real on-page questions isn't harmful, but it won't produce a rich result.

#Does schema markup help with AI search?

Google says there's no special schema needed to appear in AI Overviews or AI Mode. Schema still helps by stating your product's facts clearly and linking your profiles, and it supports regular rich results. Getting cited by AI answers depends more on crawl access and on being mentioned on the sources those answers use.

#What applicationCategory should a SaaS use?

Most B2B SaaS fits BusinessApplication. Use FinanceApplication for money tools, DeveloperApplication for developer tools, DesignApplication for design tools and SecurityApplication for security products. Google only accepts values from its supported list, so don't invent a category.

#How do I test my structured data?

Use Google's Rich Results Test to see which rich results a page is eligible for and any errors, and the Schema Markup Validator to check the markup against schema.org. After Google indexes the page, Search Console reports structured data issues across your site.

#Final recommendation

Add Organization and WebSite JSON-LD to your homepage today, then a WebApplication block with your real category, platform and price. Leave ratings out until you have real reviews showing on the page, skip FAQ markup for rich results, and test everything in the Rich Results Test. Then check the rest of your site's basics with a free Verdy audit, and read how to get recommended by ChatGPT for what actually moves AI visibility.