Schema.org markup every SaaS website should have

Schema markup is one of those technical SEO tasks that gets either obsessively over-implemented or completely ignored. Neither is helpful. The right answer for most SaaS websites is a focused set of schema types that match the content the buyer is actually looking for, implemented properly with JSON-LD and validated regularly. Get that right and you make your site easier for Google to understand, easier for AI assistants to cite and more likely to win rich results in search.

We have implemented schema across SaaS marketing sites, MSP sites and IT service businesses, and the pattern that works is consistent. Here is what we recommend every SaaS website should have, why it matters and what to skip.

Why schema matters more in 2026 than it did in 2022

Two things changed. First, Google’s AI Overviews and the broader move towards LLM-driven search rely heavily on structured data to understand which sources to trust and cite. A page with proper schema is dramatically easier for these systems to parse than one without. Second, schema is no longer a “nice to have” for rich results, it is the default expectation for product, FAQ, review, breadcrumb and organisation markup.

We cover the AI search angle more broadly in structured data for AI search, and the relationship to citations in how LLMs cite sources. For SaaS specifically, the markup below is the foundation everything else builds on.

Use JSON-LD, not microdata

There are three ways to implement schema: JSON-LD (a script block in the head or body), microdata (attributes on HTML elements) and RDFa. Google strongly prefers JSON-LD and so do we. It is easier to maintain because the markup lives in one place rather than scattered through your templates. It is easier to debug because you can paste it into a validator. It is easier to update because the content team does not need to touch HTML attributes.

Every example below assumes JSON-LD.

The core types every SaaS site should implement

Organization

The Organization schema goes on every page (usually in the global header or footer template) and identifies the company. It is the foundation Google and LLMs use to associate everything else on the site with a known entity.

Include: name, URL, logo (with absolute URL), social profile URLs (sameAs), contact information and the founding date if it adds credibility. For SaaS companies with a parent organisation, the parentOrganization field can clarify the relationship.

WebSite with SearchAction

The WebSite schema, when paired with a potentialAction for site search, tells Google your site has internal search and can earn the sitelinks searchbox in some queries. It is small to add and worth having.

SoftwareApplication

This is the schema type that most SaaS sites get wrong or skip. Your product itself is a SoftwareApplication. Marking it up tells Google this is software, what category it sits in, what it costs and what users rate it.

Key properties: name, applicationCategory (e.g. BusinessApplication), operatingSystem, offers (with price or a PriceSpecification) and aggregateRating if you have legitimate review data from a recognised source like G2, Capterra or Trustpilot. We unpack why those review platforms matter so much for AI citation in G2 and Capterra in AI search.

A common mistake we see: SaaS sites putting aggregateRating based on testimonials they collected themselves. Google will spot this and may penalise the page. Only mark up review data that comes from a recognised, verifiable third party, and link to the source.

Product or Service

For SaaS sites that have multiple product tiers, package each tier as a Product (or Service) with its own pricing schema. This helps Google understand your pricing structure and can produce price-rich results.

BreadcrumbList

Breadcrumbs help users navigate and help Google understand site hierarchy. Implement them on every page below the homepage. The visual breadcrumb on the page and the BreadcrumbList schema should match.

FAQPage (used carefully)

FAQ schema can earn an FAQ rich result that takes up significant SERP real estate. Google has tightened the rules on this, so use it for genuine, page-relevant FAQs only, not stuffed keyword fishing. Each question must be a real question a user might ask, and each answer must be present on the page in visible text. The Q&A on the page must match the schema exactly.

Article and BlogPosting

For blog content, mark up posts as BlogPosting (a subtype of Article). Include headline, author (with a Person schema and ideally a link to their author page), datePublished, dateModified, image, publisher (which should reference your Organization) and mainEntityOfPage.

Person (for author pages)

If your blog has named authors with bios (which we recommend for SaaS, particularly for technical content), each author needs a Person schema. This supports E-E-A-T (Experience, Expertise, Authoritativeness, Trust) signals and is increasingly important for AI citation.

Event and Webinar

If you run webinars, conferences or product launches, mark these up as Event (or specifically Webinar for online events). This earns event-rich results in search and feeds calendar integrations. We cover the marketing angle of this in webinars on demand as SEO assets.

VideoObject

Demo videos, customer testimonials and product walkthroughs benefit from VideoObject schema. Include name, description, thumbnailUrl, uploadDate, duration and contentUrl or embedUrl. This earns video-rich results and feeds Google’s video indexing.

Review and AggregateRating (with caution)

Mark up reviews only when they are authentic, third-party-sourced or from genuine on-site reviews of a specific product. Do not mark up generic testimonials about your company. Google’s guidelines are explicit on this and the manual action risk is real.

What we skip on most SaaS sites

We are deliberately not recommending some types you will see in other guides.

• HowTo: Google removed HowTo rich results from most search experiences in 2023.
• JobPosting: only useful if you actively recruit through your site and want indexing in Google for Jobs. Most SaaS careers pages do not need it.
• LocalBusiness: SaaS companies are usually not LocalBusiness in the schema sense (that is for cafes, dentists, plumbers). Use Organization instead.
• Course: only relevant if you sell training courses.

Adding schema you do not need does not help. It just adds markup to maintain.

Implementation patterns that work

Build schema into your CMS templates rather than adding it page by page. For WordPress, use Yoast or Rank Math (both handle the basics well) and add custom JSON-LD via a child theme or plugin for the SaaS-specific types. For headless setups, generate JSON-LD as part of the page render in your front-end framework. Astro, Next.js and Nuxt all handle this cleanly. The same structural rigour pays back on technical content too, which we cover in designing developer docs.

Centralise the Organization, WebSite and Person schemas so they are defined once and pulled into every page. Page-specific schema (Product, Article, FAQ) goes in the page template.

Validation and monitoring

Implementing schema once and forgetting it is a slow path to broken markup. We do three things:

• Validate during development with Google’s Rich Results Test and Schema.org’s validator
• Monitor in Search Console under Enhancements, which flags errors and warnings on indexed pages
• Spot-check after every CMS or template change, because plugin updates and template tweaks routinely break schema in subtle ways

We also recommend periodically reviewing what shows up in the SERP for your branded queries. If a competitor has richer results than you, that is a sign their schema is doing more work.

Where it fits in the bigger picture

Schema is one piece of a wider technical SEO programme. It works best alongside a clean technical audit, strong internal linking and SEO-aware product page design. For SaaS sites in particular, we treat schema as part of the launch checklist, not a thing to bolt on later.

If you are scoping a SaaS website rebuild, replatform or technical SEO audit, we’d be glad to take a look. Our web design and SEO teams build schema into the foundations rather than treating it as a plugin you install at the end.