Which schema markup does a SaaS website need?

Most SaaS sites need four kinds of schema: Organization on the homepage, WebSite, BreadcrumbList on deeper pages and Article on blog posts. Add SoftwareApplication only where you show real pricing and ratings. FAQ markup is optional now that Google has dropped FAQ rich results. Schema helps search engines understand you; it doesn't win AI citations on its own.

Why schema questions get so heated

Somewhere in your Slack there's a thread that started with "should we add schema for AI?" and ended 40 messages later with a developer, a growth marketer and a plugin salesperson all disagreeing.

Here's the calm version. Schema markup is a label on a moving box. The label says "kitchen, plates, fragile," so the movers know what's inside without opening it. Labels help. But a well-labeled box full of junk is still a box of junk, and nobody unpacks a house by reading labels alone. (The movers still open the box.)

Google and AI engines are the movers. They read your page either way. Schema just tells them, in a format machines don't have to guess at, what's in it.

What does schema actually do in 2026?

Two separate things, and mixing them up causes most of the bad advice.

It helps search engines understand who you are. Google says Organization markup helps it "better understand your organization's administrative details" and "disambiguate your organization in search results" (Google Search Central). For a SaaS company whose name is also a common word, that disambiguation matters more than any rich result.

It can make you eligible for rich results in Google. That list keeps shrinking. Google stopped showing FAQ rich results in Search on May 7, 2026 (Google Search Central), following HowTo results, which went away in 2023.

What about AI search? Microsoft's Fabrice Canel said on stage in March 2025 that Bing uses schema markup to help its LLMs understand content (Search Engine Land). That's real, and it's about understanding. Nobody we trust has shown that schema alone moves AI citations. Clear, answer-first copy and third-party mentions do that heavy lifting, as we explain in the pillar guide on getting your SaaS recommended by ChatGPT.

So: label the boxes, but don't expect the labels to sell the house.

The SaaS schema stack: what matters and what's theater

This is the stack we'd put on a typical B2B SaaS site. It runs from essential to optional.

The three essentials take an afternoon. The rest depends on what's actually on your pages.

Organization: the label that matters most

If you do one thing, do this one. Google says Organization markup has no required properties, so include the ones that apply (Google Search Central). For SaaS, the useful ones are:

• name: your exact company name, the same one everywhere.
• url and logo: your homepage and a crawlable logo file.
• sameAs: links to your LinkedIn, G2, Capterra, Crunchbase, GitHub and other profiles that describe you.
• description: your one-line positioning sentence, word for word the same as on your site.

That sameAs list is the quiet hero. It ties your scattered profiles into one identity, which is the same consistency problem we cover in why ChatGPT recommends your competitor. Same box, same label, every room.

SoftwareApplication: when it's worth it

This is the one SaaS teams most want, and the one most often done wrong.

Google's SoftwareApplication rich result requires name, offers.price and either aggregateRating or review (Google Search Central). That rating requirement is where the trouble starts. If your product page has no visible ratings, there's nothing honest to mark up, and inventing a 4.9 in your code is the moving-box equivalent of writing "fine china" on a box of rocks. Google's structured data rules expect markup to describe what's actually on the page.

Use it when:

• Your pricing page shows a real starting price (or "free," marked as price 0).
• You display real ratings on the page, sourced and up to date.

Skip it when your pricing is "contact sales" and you don't show ratings. You can still describe the product with applicationCategory and operatingSystem for understanding, just don't expect stars.

Is FAQ schema still worth adding?

It's lost its main payoff in Google, but it's not useless.

FAQ dropdowns no longer appear in Google Search, and Google's documentation now says so plainly (Google Search Central). Keeping existing FAQ markup won't hurt you, and other engines may still read it.

Our take: don't build FAQ sections for the schema. Build them because buyers and AI engines both love direct question-and-answer passages. If the FAQ is already on the page, marking it up is a five-minute job. If it isn't, write the FAQ first. The words do more than the label.

How to add schema without breaking anything

1. Pick one format. Use JSON-LD in the page's head. It's Google's recommended format and easiest to maintain.
2. Generate it from real data. Pull the price, name and ratings from the same source your page uses, so a price change updates both.
3. Test it. Run key pages through Google's Rich Results Test and the Schema Markup Validator after every template change.
4. Watch Search Console. The enhancements reports flag errors on templates before they spread across hundreds of pages.
5. Recheck quarterly. Google changes which rich results it supports. A quick review keeps you from maintaining markup for features that no longer exist.

If you'd like a second set of eyes on your site's structure, book a call with us. And if your next move is content rather than code, start with comparison pages that AI engines quote.