--- url: "https://auraplusplus.com/studio/which-schema-markup-does-a-saas-website-need" markdown: "https://auraplusplus.com/studio/which-schema-markup-does-a-saas-website-need.md" category: "studio" type: "studio" published: "2026-11-05" --- # Which Schema Markup Does a SaaS Website Actually Need? > Which schema markup a SaaS site needs in 2026: Organization, WebSite, SoftwareApplication, BlogPosting and breadcrumbs, with copy-paste JSON-LD and tests. ## Article Most SaaS websites need four or five schema types, not forty. Put Organization and WebSite markup on the homepage. Add SoftwareApplication to your main product or pricing page, but only with facts that are visibly on that page. Put BlogPosting (or Article) on each blog post, with real dates. Add BreadcrumbList on deeper pages if you show breadcrumbs. That covers what Google can actually use for a typical software company in 2026, and everything you add has to match what a visitor can see on the page. This guide is for founders who keep hearing "add schema" and want to know which bits matter, what to paste, and what to skip. It's not written for SEO specialists, so there's no deep vocabulary here, just the pages most startup sites have and the markup each one needs. The Google documentation quoted below was read on 5 November 2026. **Last checked: Nov 5, 2026** ## What does structured data actually do? Structured data is a small block of machine-readable facts about a page: this is a company, this is its logo, this is an app and what it costs, this article was published on this date. Search engines read it to understand the page with less guessing. The honest version of the benefit is narrower than most "add schema for SEO" posts suggest. Google's [structured data general guidelines](https://developers.google.com/search/docs/appearance/structured-data/sd-policies?utm_source=auraplusplus&utm_medium=seo_blog&utm_campaign=blog_content&ref=auraplusplus&source=auraplusplus) say plainly that "Google does not guarantee that your structured data will show up in search results, even if your page is marked up correctly." Markup makes a page eligible for richer search features. It doesn't push the page up the rankings. The same page notes that a structured data manual action removes a page's eligibility for rich results and "doesn't affect how the page ranks in Google web search." So think of schema as labelling, not as a growth lever. Good labels help Google show your logo, your site name, your article dates and your breadcrumbs correctly. Bad or fake labels get ignored at best. That's worth an hour of work, not a month. ## Which rich results can a SaaS site still get in 2026? A lot of older advice is out of date, because Google has cut several rich result types. Two that SaaS sites used to chase are gone: - FAQ rich results. In August 2023 Google limited them to "well-known, authoritative government and health websites." Then, according to the [Search Central documentation changelog](https://developers.google.com/search/updates?utm_source=auraplusplus&utm_medium=seo_blog&utm_campaign=blog_content&ref=auraplusplus&source=auraplusplus), the feature would "no longer appear in Google Search starting May 7, 2026," and the FAQ documentation was later removed entirely. - How-to rich results. Google's [2023 HowTo and FAQ announcement](https://developers.google.com/search/blog/2023/08/howto-faq-changes?utm_source=auraplusplus&utm_medium=seo_blog&utm_campaign=blog_content&ref=auraplusplus&source=auraplusplus) was updated in September 2023 to say How-to results were no longer shown on desktop either, "which means this result type is now deprecated." Here's what's left that a normal software company can realistically use: Schema type What it can affect Realistic for a small SaaS? Organization Which logo Google shows, knowledge panel details Yes, homepage only WebSite The site name shown in results Yes, homepage only SoftwareApplication App details and rating in results Partly: the rich result needs a real rating or review Article / BlogPosting Title, image and date in article features Yes, on every post BreadcrumbList The path shown above your result Yes, but Google shows it on desktop only FAQPage, HowTo Nothing in Google any more No, skip them The breadcrumb point comes from Google's own changelog: in January 2025 it added a note that breadcrumbs "only appear on desktop search results, not mobile." Still worth doing, just don't expect it to change much. ## Which schema goes on which page? This is the table I'd use for a typical startup site with a homepage, a pricing page, a blog and some docs or feature pages: Page Schema type Key properties What to skip Homepage Organization + WebSite name, url, logo, sameAs (your real profiles) Ratings, addresses you don't show, a search box you don't have Product or pricing page SoftwareApplication (or WebApplication) name, offers with price, applicationCategory, operatingSystem aggregateRating unless real reviews are shown on that page Blog posts BlogPosting headline, image, datePublished, dateModified, author Fake "updated today" dates, keyword lists Docs, feature and deep pages BreadcrumbList itemListElement with name and item for each level Breadcrumbs that aren't visible on the page Help center or FAQ page Nothing special Clear headings and answers in plain HTML FAQPage markup aimed at Google rich results Login, app and account pages None Usually noindex anyway All schema If a page type isn't in that table, the default answer is "no schema needed." You can always add more later. Removing wrong markup across a whole site is the annoying part. ## Should you use JSON-LD or microdata? Use JSON-LD. Google's [introduction to structured data](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data?utm_source=auraplusplus&utm_medium=seo_blog&utm_campaign=blog_content&ref=auraplusplus&source=auraplusplus) says all three supported formats are "equally fine for Google," but also that "in general, Google recommends using JSON-LD for structured data if your site's setup allows it," because it's the easiest to implement and maintain. The practical reason is that JSON-LD sits in its own script tag, separate from your visible HTML. Your designer can change a pricing card without breaking the markup, and you can see every fact in one place. Microdata is woven into the HTML attributes, which is fine for a static page and painful on a site that changes weekly. ![A blank kraft paper tag hanging on a string against a brick wall](https://images.pexels.com/photos/8148580/pexels-photo-8148580.jpeg?auto=compress&cs=tinysrgb&w=1200&h=800&fit=crop) ## What should the homepage markup look like? One Organization block and one WebSite block, on the homepage only. Here's a made-up example for an invented meeting-notes app called Ferrowink. Swap in your own details: ``` [ { "@context": "https://schema.org", "@type": "Organization", "@id": "https://www.example.com/#organization", "name": "Ferrowink", "url": "https://www.example.com/", "logo": "https://www.example.com/logo-512.png", "sameAs": [ "https://www.linkedin.com/company/example", "https://github.com/example" ] }, { "@context": "https://schema.org", "@type": "WebSite", "name": "Ferrowink", "url": "https://www.example.com/", "publisher": { "@id": "https://www.example.com/#organization" } } ] ``` A few notes. Google's Organization documentation says there are no required properties, so add the ones that are true and skip the rest. The logo must be at least 112x112 pixels and crawlable. Only list sameAs profiles you actually control and keep active. I've already written a longer guide on getting Google to show your brand properly, including site name markup and sameAs, so I won't repeat it here. If your startup doesn't appear for its own name, read [how to rank for your own startup name on Google](https://auraplusplus.com/studio/how-to-rank-for-your-own-startup-name-on-google) first. Schema is one small part of that fix. ## How do you mark up your product or pricing page? Google documents a [SoftwareApplication type](https://developers.google.com/search/docs/appearance/structured-data/software-app?utm_source=auraplusplus&utm_medium=seo_blog&utm_campaign=blog_content&ref=auraplusplus&source=auraplusplus) for apps, and says it also supports the WebApplication subtype, which is the honest fit for most browser-based SaaS. The required properties are a name, an offer with a price (use 0 if the app is free), and a rating or review. That last requirement matters. Without a real rating or review, you won't get the app rich result. You can still add the markup for clarity, but don't invent a rating to fill the gap. Here's the made-up Ferrowink example without one: ``` { "@context": "https://schema.org", "@type": "WebApplication", "name": "Ferrowink", "url": "https://www.example.com/", "applicationCategory": "BusinessApplication", "operatingSystem": "Web browser", "offers": { "@type": "Offer", "price": "12.00", "priceCurrency": "USD" }, "publisher": { "@id": "https://www.example.com/#organization" } } ``` If you do show real reviews on the page, collected from real users, you can add an aggregateRating with the actual average and count. Two rules from Google's [review snippet guidelines](https://developers.google.com/search/docs/appearance/structured-data/review-snippet?utm_source=auraplusplus&utm_medium=seo_blog&utm_campaign=blog_content&ref=auraplusplus&source=auraplusplus) are worth knowing before you do. Don't "include fake or undisclosed incentivized reviews," which includes reviews given in exchange for money, discounts or free products without a clear disclosure. And Google says that if an organization "controls the reviews about itself," its pages using Organization markup are ineligible for star reviews. Stars about your own company, on your own site, are a dead end. The price has to match the price on the page. If you change your pricing, the markup must change the same day. A hard-coded price in a template is the most common way schema quietly goes wrong. ## What should a blog post carry? BlogPosting is a subtype of Article, and Google's [Article documentation](https://developers.google.com/search/docs/appearance/structured-data/article?utm_source=auraplusplus&utm_medium=seo_blog&utm_campaign=blog_content&ref=auraplusplus&source=auraplusplus) says there are no required properties. The useful ones are headline, image, datePublished, dateModified and author. Here's an example: ``` { "@context": "https://schema.org", "@type": "BlogPosting", "headline": "How We Cut Our Meeting Notes in Half", "image": ["https://www.example.com/blog/notes-cover-1600x900.jpg"], "datePublished": "2026-11-05T09:00:00+05:30", "dateModified": "2026-11-05T09:00:00+05:30", "author": { "@type": "Person", "name": "Jane Founder", "url": "https://www.example.com/about" }, "publisher": { "@id": "https://www.example.com/#organization" } } ``` Google asks for dates in ISO 8601 format and recommends including a timezone, otherwise it falls back to Googlebot's timezone. Now the bug I see constantly: placeholder dates. A developer builds the blog template, types a sample date like 2024-01-01 into the JSON-LD so the validator stops complaining, and that date ships on every post forever. Or the field gets a JavaScript object instead of a string and prints something useless. Every post on the site then claims the same publish date, which is wrong and makes your markup look careless. Open three of your posts, view source, search for datePublished, and check the dates are different and true. It takes two minutes. The other date trap is the reverse: bumping dateModified on every deploy so posts look fresh. Only change it when the content really changed. ## Do you need BreadcrumbList? Only if you show breadcrumbs on the page. If your docs show "Docs > Integrations > Slack," mark up that same trail: ``` { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Docs", "item": "https://www.example.com/docs" }, { "@type": "ListItem", "position": 2, "name": "Integrations", "item": "https://www.example.com/docs/integrations" }, { "@type": "ListItem", "position": 3, "name": "Slack" } ] } ``` If your site has no visible breadcrumbs, don't add the markup just for Google. Remember the general rule: don't mark up content that isn't visible to readers. ## How do you add schema in Next.js, WordPress or Webflow? **Next.js.** The [Next.js JSON-LD guide](https://nextjs.org/docs/app/guides/json-ld?utm_source=auraplusplus&utm_medium=seo_blog&utm_campaign=blog_content&ref=auraplusplus&source=auraplusplus) recommends rendering structured data "as a