Schema Markup for SaaS: 8 Types With JSON-LD Examples

Last updated: November 2026.

Short answer: most SaaS sites need eight schema types: Organization and WebSite on the homepage, SoftwareApplication (with Offer and, if you have genuine on-page reviews, AggregateRating) on product and pricing pages, Article and BreadcrumbList on blog and docs pages, and FAQPage and HowTo where the content really is a FAQ or a set of steps. Use JSON-LD. Since 2023, Google shows FAQ rich results only for authoritative government and health sites and no longer shows HowTo rich results at all, so mark those up for machine understanding, not for stars and dropdowns in the SERP.

This guide covers each type with a short JSON-LD example, the rules that decide whether Google shows a rich result, and how to roll schema out across a SaaS site without breaking it. It sits alongside our guide to technical SEO for SaaS apps.

Schema types for SaaS at a glance

Schema typeWhere to use it on a SaaS siteRich result status (2027)
OrganizationHomepage (or About page)No visual rich result; feeds logo and company details in Google’s knowledge panel
WebSiteHomepageUsed for the site name shown in results; sitelinks search box retired in 2024
SoftwareApplicationProduct, pricing and app pagesEligible for software app rich results (rating, price) when rules are met
Review / AggregateRatingNested in SoftwareApplication on pages that show real reviewsEligible, but self-serving reviews of your own organisation are not shown
Article / BlogPostingBlog posts, guides, newsNo dedicated rich result for most sites; helps Google read title, dates and author
BreadcrumbListBlog, docs, glossary and nested pagesShown on desktop results; mobile results show the domain instead
FAQPageGenuine FAQ sections on product, pricing or support pagesLimited to well-known government and health sites since August 2023
HowToStep-by-step tutorials and docsRich result deprecated in 2023; not shown

Rich results are never guaranteed, even with valid markup. Google decides when to show them based on the query, the page and the site.

Why Schema Matters for SaaS Businesses

SaaS buyers compare several products side by side, often from the results page. Schema does not improve rankings directly, but it does three useful things:

  • Eligibility for rich results such as ratings and pricing on software pages, which can lift click-through rate.
  • Clear entity signals: which company you are, which product you sell, what it costs and which pages belong together. That helps Google, and AI search systems that read the same pages, describe you accurately.
  • Consistency at scale: templates that output the same facts (name, logo, pricing) across hundreds of pages reduce the chance of search engines showing outdated or conflicting information.

Schema works best as part of a broader SaaS SEO strategy, not as a standalone fix. If you are working with outside help, knowing how to choose the right SaaS SEO agency matters, because schema mistakes are easy to make at scale.

Understanding SaaS Schema Markup

Schema markup is structured data, using the Schema.org vocabulary, that tells search engines what each page means. For SaaS companies it differs from e-commerce: the product is digital and usually subscription-based, so the markup needs to describe software, recurring pricing, the company behind it and the educational content around it.

JSON-LD as the Preferred Format

JSON-LD is Google’s recommended format. It sits in a <script type="application/ld+json"> block, separate from your HTML, so it is easier to template, test and maintain than Microdata or RDFa. For SaaS sites with many feature, pricing and docs pages, that separation matters: you can generate it centrally from your CMS or product data.

Two rules apply to every type below: mark up only what is visible on the page, and keep the markup in sync with the page when pricing or ratings change. Better rich results can improve click-through, which then feeds your conversion rate optimization work.

1. Organization schema

Organization markup tells Google who you are: legal or brand name, logo, website and official profiles. Put it on the homepage (or the About page) once, not on every page. Use sameAs to link your LinkedIn, X, GitHub, Crunchbase and G2 profiles so the entity is unambiguous.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Acme Analytics",
  "url": "https://www.example.com/",
  "logo": "https://www.example.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/example",
    "https://github.com/example"
  ]
}
</script>

2. WebSite schema

WebSite markup on the homepage helps Google choose the site name it shows above your result. Include name and, if your brand has a common short form, alternateName. Google retired the sitelinks search box in late 2024, so you no longer need the potentialAction SearchAction block for that purpose.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Acme Analytics",
  "alternateName": "Acme",
  "url": "https://www.example.com/"
}
</script>

3. SoftwareApplication schema (Product schema for SaaS)

SoftwareApplication is the type Google uses for software app rich results, and it is the right choice for most SaaS product and pricing pages. To be eligible, Google requires a name, an offers price (use 0 for a free plan) and either an aggregateRating or a review. applicationCategory and operatingSystem are recommended.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Acme Analytics",
  "applicationCategory": "BusinessApplication",
  "operatingSystem": "Web",
  "offers": {
    "@type": "Offer",
    "price": "49.00",
    "priceCurrency": "USD"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.6",
    "ratingCount": "128"
  }
}
</script>

Handling Subscription Models in Schema

For several plans, use an AggregateOffer with lowPrice, highPrice and offerCount, or list each plan as its own Offer. Make sure the prices match what the pricing page shows, including currency and whether the price is monthly or annual. If you change pricing, change the markup in the same release.

<script type="application/ld+json">
"offers": {
  "@type": "AggregateOffer",
  "lowPrice": "0",
  "highPrice": "199",
  "priceCurrency": "USD",
  "offerCount": "3"
}
</script>

Align the markup with your pricing strategy: if a free plan or trial is central to your motion, a price of 0 for the entry plan is accurate and useful to buyers.

Product vs. WebApplication Schema

SoftwareApplication has two useful subtypes: WebApplication for browser-based products and MobileApplication for apps. Either works for the rich result. Generic Product markup is built mainly for physical goods and merchant listings, so for software, prefer SoftwareApplication or a subtype. Whichever you choose, use it consistently across the site.

Schema describes facts, not positioning. Put your product differentiation in the visible copy; use markup to make the facts behind it (category, platform, price, rating) machine-readable.

4. Review and AggregateRating schema

Ratings are the rich result most SaaS teams want, and the one most often lost through mistakes. Review and AggregateRating markup should be nested inside the SoftwareApplication it describes, not floated on its own.

Common Issues with Review Schema

  • Self-serving reviews. Since 2019 Google does not show review stars for an Organization or LocalBusiness that marks up reviews of itself on its own site. Put ratings on the SoftwareApplication, not the Organization.
  • Reviews not visible on the page. Every review or rating you mark up must be readable by visitors on that page.
  • Ratings copied from third-party sites. Don’t mark up your G2 or Capterra average as if it were your own. Embed their badges for visitors instead, and mark up only reviews you collected and display yourself.
  • Testimonials without attribution. Curated quotes on a landing page are not reviews. Don’t mark them up as Review.
  • Stale numbers. A ratingCount that never changes is a sign of hard-coded markup. Generate it from your review data.

Scaling Review Schema for SaaS

If you collect reviews in-product or through a review tool, output AggregateRating from that data automatically on the product page. Directory reviews still matter for buyers and branded search; our list of SaaS directories to list your product covers where to collect them, and user reviews in performance marketing covers how to use them in campaigns. Used correctly, reviews act as structured social proof.

5. Article schema

Use Article or BlogPosting on blog posts and long-form guides. It helps Google read the headline, images, publish and update dates, and the author. Link the author to a real profile page: clear authorship supports the signals described in our guide to E-E-A-T for B2B SaaS.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Reduce Churn in B2B SaaS",
  "image": "https://www.example.com/images/churn.png",
  "datePublished": "2026-03-02",
  "dateModified": "2026-11-10",
  "author": {
    "@type": "Person",
    "name": "Jane Doe",
    "url": "https://www.example.com/authors/jane-doe/"
  }
}
</script>

Only update dateModified when the content meaningfully changes. Bumping dates without changes is easy for search engines to spot.

6. BreadcrumbList schema

BreadcrumbList describes where a page sits in your site hierarchy: Home > Blog > SEO > this post. It is most useful on docs, glossary and blog sections with nested categories. Google shows breadcrumbs on desktop results; on mobile it now shows the domain only, but the markup still clarifies site structure.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {"@type": "ListItem", "position": 1, "name": "Blog", "item": "https://www.example.com/blog/"},
    {"@type": "ListItem", "position": 2, "name": "SEO", "item": "https://www.example.com/blog/seo/"},
    {"@type": "ListItem", "position": 3, "name": "Schema for SaaS"}
  ]
}
</script>

7. FAQ Schema for SaaS Websites

FAQPage markup describes a list of questions with one answer each. In August 2023 Google limited FAQ rich results to well-known, authoritative government and health websites, so a SaaS pricing page with FAQ markup will rarely, if ever, show expandable questions in Google results.

It is still worth adding where you have a genuine FAQ. The markup states the question-and-answer pairs explicitly, which helps other search engines and AI systems that parse structured data, and it costs little once templated.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Is there a free plan?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Yes. The Starter plan is free for up to 3 users."
    }
  }]
}
</script>

Where to Place FAQ Schema

Pricing pages, feature pages, comparison pages and support articles: the places buyers look for answers about pricing, integrations, security and contracts. A clear FAQ reduces friction the way an intuitive SaaS interface does.

Best Practices for FAQ Schema

  • Do mark up only questions and answers that are visible on the page.
  • Do keep answers short and factual: pricing, integrations, limits, security.
  • Don’t duplicate the same FAQ markup on many pages.
  • Don’t use FAQPage for user-submitted questions with multiple answers (that is QAPage) or for advertising copy.

8. HowTo Schema for SaaS Tutorials

HowTo markup describes a set of steps. Google deprecated HowTo rich results in 2023, first on mobile and then on desktop, so step-by-step markup no longer produces a visual result in Google Search.

For most SaaS teams, that means HowTo is low priority. The value of onboarding guides and knowledge-base articles now comes from the content itself: clear headings, numbered steps, screenshots and internal links. If you already have HowTo markup, it does no harm, but don’t invest new engineering time in it. A tutorial like a SaaS MVP readiness checklist ranks on content quality, and well-structured support content still supports customer success in SaaS GTM.

Testing and Validating SaaS Schema

A single syntax error can make Google ignore a block of markup. Validate before release and monitor after.

Tools to Use for Schema Validation

  • Google Rich Results Test: shows which Google rich results a page is eligible for and flags missing required properties.
  • Schema Markup Validator (validator.schema.org): checks general Schema.org validity, including types Google does not use for rich results.
  • Search Console enhancement reports: show errors and warnings across all pages of a type after Google crawls them.

Validation is as routine as tracking KPIs. Just as you rely on a SaaS metrics cheat sheet, check the Search Console reports monthly and after every template release.

Scaling Schema Implementation Across SaaS Sites

A SaaS site might have a homepage, dozens of feature and integration pages, a pricing page, hundreds of blog posts and a docs site, often on different stacks. Hand-written markup on each page drifts out of date quickly.

Automating Schema Markup

  • Template by page type. Homepage outputs Organization and WebSite; product and pricing templates output SoftwareApplication; blog templates output BlogPosting and BreadcrumbList.
  • One source of truth for facts. Pull pricing and ratings from the same data that renders the page, so a pricing change updates the markup automatically.
  • Connect entities with @id. Give the Organization an @id (for example the homepage URL plus #organization) and reference it as the publisher or provider elsewhere.
  • Watch for plugin duplication. SEO plugins, themes and page builders can each output their own markup. Check that each page has one coherent graph, not three conflicting ones.

Make schema part of marketing operations: add a markup check to the release checklist for new templates.

Business Impact of Schema for SaaS

Be realistic about what schema does. It does not raise rankings on its own, and the most visible rich results for SaaS (FAQ dropdowns and HowTo steps) are gone. What remains is meaningful: rating and price eligibility on software pages, a cleaner site name and knowledge panel, consistent facts across hundreds of pages, and content that machines, including AI search systems, can interpret without guessing.

Consistent, accurate structured data also reinforces your SaaS positioning: the category, product name and pricing search engines show match what your site says.

Take the Next Step with Schema

Start with Organization and WebSite on the homepage, SoftwareApplication on product and pricing pages, and Article plus BreadcrumbList on content. Add FAQPage where you have real FAQs, and leave HowTo as a low priority. If you want schema implemented as part of a technical SEO programme, see our SaaS SEO agency services or book a call with SaaS Consult.


FAQs on SaaS Schema

What schema type should SaaS companies start with first?

Start with Organization and WebSite on the homepage, then SoftwareApplication on your product and pricing pages. SoftwareApplication is the type that can earn rating and price rich results for software.

Should a SaaS product use Product or SoftwareApplication schema?

Use SoftwareApplication, or its WebApplication subtype for browser-based products. It is the type Google uses for software app rich results. Generic Product markup is designed mainly for physical goods and merchant listings.

Does FAQ schema still work in 2027?

Since August 2023 Google shows FAQ rich results only for well-known government and health websites, so most SaaS sites will not see them. FAQ markup still describes your Q&A clearly for other search engines and AI systems, so keep it on genuine FAQs.

Is HowTo schema still useful?

Not for Google rich results: Google deprecated HowTo rich results in 2023. Focus on clear numbered steps and screenshots in the content itself. Existing HowTo markup does no harm.

Can I use my G2 or Capterra rating in my schema?

No. Mark up only reviews and ratings that you collect and display on the page. Ratings copied from third-party review sites, and reviews of your own organisation, are not eligible for review stars.

Can a SaaS page have multiple schema types at once?

Yes. A pricing page can carry SoftwareApplication, BreadcrumbList and FAQPage together. Link them with @id references and make sure plugins are not outputting duplicate or conflicting blocks.

How do SaaS companies avoid schema penalties from Google?

Mark up only content visible on the page, keep prices and ratings accurate, and never mark up fake or copied reviews. Misleading structured data can lead to a manual action that removes rich result eligibility.

How long does it take to see results from schema?

Google needs to recrawl the page, which can take days to weeks. Check the Rich Results Test immediately, then watch Search Console enhancement reports and click-through rate over the following month.