--- title: "Schema Markup for SaaS: JSON-LD That Actually Validates" description: "The five schema types every B2B SaaS site should ship — Organization, SoftwareApplication, FAQPage, BreadcrumbList, Article — and how to validate them so they actually earn rich results." url: "https://serpnaut.xyz/playbook/schema-markup-for-saas" verifiedAt: "2026-06-09" canonical: "https://serpnaut.xyz/playbook/schema-markup-for-saas" --- # Schema Markup for SaaS: JSON-LD That Actually Validates > TL;DR — Schema markup for SaaS is the JSON-LD that earns the FAQ accordion, the breadcrumb trail, and the brand knowledge panel in Google's SERP. Most SaaS sites either ship nothing or ship plugin-generated invalid markup that silently fails the Rich Results Test — the cheapest SERP real estate competitors don't bother claiming. In plain English: Schema markup for SaaS is structured data (JSON-LD) embedded in a page so Google parses it as an Organization, SoftwareApplication, FAQPage, BreadcrumbList, or Article. The five-schema baseline is the minimum a B2B SaaS site needs to be eligible for rich results. ## Key takeaways - Ship five JSON-LD types as a baseline: Organization, SoftwareApplication (or Product), FAQPage, BreadcrumbList, Article. - Always validate in Google's Rich Results Test before shipping — plugin dashboards lie. - Never ship FAQPage schema without a visible Q&A block on the page — Google penalises mismatched schema. - Person schema on the author/about page is the cleanest E-E-A-T signal a SaaS site can ship. - JSON-LD only — skip microdata and RDFa; they couple markup to visible HTML and break on template changes. ## Definition Schema markup for SaaS is structured data, shipped as JSON-LD, that tells search engines what a B2B software page literally is — an Organization, a SoftwareApplication, an FAQPage, an Article, a Person — so the page is eligible for rich results and the brand is disambiguated as an entity. ## Why it matters Most SaaS sites either ship no schema or ship invalid schema generated by a plugin. Both are wasted opportunities to claim SERP real estate competitors don't bother with. Rich results — FAQ accordions, breadcrumb trails, sitelinks, product knowledge panels — measurably lift click-through rate, and CTR is a ranking input. ## The five schemas every SaaS site needs Organization on the home page, with company name, logo, URL, and a sameAs array linking to every official social profile and company directory. This is what tells Google what kind of entity owns the site and powers the brand knowledge panel. SoftwareApplication (or Product) on the product or pricing page, with name, description, applicationCategory, operatingSystem, and an offers block listing the price. Earns the product-style rich result. FAQPage on every page with a real Q&A block — homepage, audit, pricing, key landing pages. Each entry is a Question and Answer pair. Earns the expandable FAQ accordion. BreadcrumbList on every page below the root. Tells Google the hierarchy and replaces the URL line in the SERP with a clean breadcrumb trail. Article on every blog post: headline, image, datePublished, dateModified, author block. The foundation of the publisher signal Google uses to surface posts in Top Stories and Discover. ## Person and author schema A Person block on the About page — with name, jobTitle, image, sameAs linking to LinkedIn / X / GitHub / personal sites, knowsAbout listing the areas of expertise, and worksFor referencing the Organization — turns an author byline into an entity Google can score for expertise. Link author bylines on every long-form page to that Person entity. Article schema citing a real Person, that Person referenced across the site, with external sameAs corroboration — is the cleanest E-E-A-T setup a SaaS site can ship. ## Service and Offer schema If you sell a productised service (an audit, a sprint, a retainer), wrap each in a Service or Offer block with name, description, provider, areaServed, and the price. This is how Google parses 'SERPNAUT runs a $0 SaaS SEO audit and a $4k Fix Sprint' as a structured offering rather than as marketing prose. Don't double-stack: a SoftwareApplication on the product page and a Service on a packages page is fine; the same Offer block in three places is not. ## Validation and avoiding spam penalties Run every page through the Rich Results Test before publishing. If it doesn't validate, it doesn't count. Plugins that emit invalid JSON-LD are everywhere; trust the validator, not the plugin's dashboard. Don't ship FAQPage schema that isn't backed by a visible FAQ block on the page. Don't ship Review schema with self-written reviews. Google penalises both, and the penalties can affect the whole domain. ## Implementation: JSON-LD only Use JSON-LD inside a