Skip to content

What Is Schema Markup? The Types a SaaS Site Needs in 2026

Schema markup is structured data in the schema.org vocabulary that tells search engines what a page describes. In “What Is Schema Markup? The Types a SaaS Site Needs in 2026”, Pavlo Zhydkykh explains JSON-LD with an example, the five types a SaaS website needs and what changed for FAQ rich results.

Pavlo Zhydkykh

Updated · 6 min read

Three squares in a column, each joined by a thin line to a round tag, the middle square solid blue, like labels that name what is on a page

Short answer

Schema markup is the block of code that tells search engines what a page is: a company, a product, an article. In 2026 the advice around schema changed. Google stopped showing FAQ rich results in May, and AI search raised new questions about what markup is still worth adding. This guide explains schema markup with an example and lists the types I add to every SaaS site I build on Framer or Astro + Sanity.

Key takeaways

  • Schema.org was launched on 2 June 2011 by Bing, Google and Yahoo!, and Yandex joined in November 2011.[1]
  • Google recommends JSON-LD in most cases and says JSON-LD, Microdata and RDFa are equally fine when the markup is valid.[2]
  • Google does not guarantee rich results even for correct markup, and markup must describe content readers can see.[3]
  • FAQ rich results stopped appearing in Google Search on 7 May 2026, and Google removed their documentation in June.[4]
  • Pavlo Zhydkykh adds Organization, WebSite, BreadcrumbList and Article markup to every Framer and Astro + Sanity build he delivers.

What is schema markup?

Schema markup is structured data that labels what a page describes, such as a company, a product or an article, using the shared schema.org vocabulary. Most sites add schema markup as a JSON-LD script block that search engines read alongside the visible page.

Wikipedia: Schema.org

“Schema is a label that must match the box. I add the five types a SaaS site needs and skip markup that only grabs space.”

Pavlo Zhydkykh · Web designer and developer since 2016

Last checked · 6 min read

What is schema markup?

Schema markup is structured data written in the schema.org vocabulary. Bing, Google and Yahoo! launched schema.org on 2 June 2011 and Yandex joined in November of that year, so one set of types works across the major search engines. Wikipedia counts over 823 schema types as of June 2026.

Google defines structured data as a standardized format for providing information about a page and classifying the page content. In plain words: the visible page says "Example AI, an AI note taker for sales teams", and the markup says the same thing in a form a machine cannot misread: this is an Organization, this is its name, this is its logo, these are its official profiles.

Schema markup can be written in three formats: JSON-LD, Microdata and RDFa. Google says all three are equally fine and recommends the one that is easiest to maintain, which in most cases is JSON-LD. I use JSON-LD on every site I build, because the code sits in one block and never mixes with the visible text.

A schema markup example in JSON-LD

This is a minimal Organization block for a SaaS home page. The whole thing sits in one script tag, in the head or the body of the page:

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

The sameAs links point to the company's official profiles on other sites. Google's Organization documentation says this markup helps Google tell your organization apart from others in search results, lists no required properties, and notes that some properties influence which logo shows in search results and in the knowledge panel.

What schema markup does in Google, and what it does not

Schema markup does two jobs in Google. First, the markup helps Google understand what a page is about. Second, the markup makes a page eligible for rich results: breadcrumbs under the title, star ratings, video thumbnails, a preferred site name.

Eligible is the key word. Google's structured data guidelines say that correct markup does not guarantee a rich result, because the algorithm decides what to show for each search. The same page also sets the hard rules:

  • Mark up only content that readers can see on the page.
  • No fake reviews and no markup unrelated to the focus of the page.
  • Keep time-sensitive information up to date.
  • A structured data manual action removes rich result eligibility, but does not change how the page ranks in web search.

So schema markup is not a ranking trick. Think of the markup as a label that has to match the contents of the box.

What changed in 2026: FAQ rich results are gone

The biggest change this year: on 8 May 2026 Google added a deprecation notice to its FAQ documentation, and the FAQ rich result stopped appearing in Google Search from 7 May 2026. In June Google removed the FAQ rich result documentation altogether. Both entries are in the Search Central documentation updates.

This follows a longer clean-up. In November 2025 Google added a deprecation notice to practice problem markup and clarified that Dataset markup is used only by Dataset Search, as part of what the changelog calls an effort to simplify the search results page.

Should you delete your FAQPage markup? I would not rush. The FAQPage type is still part of schema.org, and the questions and answers stay on the page for readers either way. What changes is the business case: if a FAQ block exists only to win extra space in Google, the extra space is gone. Spend that effort on the types below instead.

The schema types a SaaS site needs

Google's search gallery lists every structured data feature Google supports. Most of the list targets recipes, jobs, events and shops. For a SaaS marketing site, five types cover nearly all of it:

TypeWhere it goesWhat it does in Google
OrganizationHome pageLogo, company details and profiles for the knowledge panel
WebSiteHome pageYour preferred site name in search results
BreadcrumbListEvery inner pageThe page's position in the site hierarchy
ArticleBlog posts and guidesThe title and larger images in article results
SoftwareApplicationProduct or app pageApp details with a rating, if you have real reviews

SoftwareApplication has the strictest rules. Google requires a name, a price in offers.price (0 for a free app) and either an aggregate rating or a review. With no real reviews to mark up, skip the type rather than invent a rating. Testimonials need care too: Google's review snippet rules accept reviews about an Organization only on sites that collect reviews about other organizations, so quotes about your own company do not earn stars.

Beyond these five, add VideoObject to pages with a product demo video, and ProfilePage to team or author pages. Leave the rest of the gallery alone unless your product really is a course, a job board or a store.

Here the honest answer is short. Google's guide to optimizing for generative AI features says structured data is not required for generative AI search and that no special schema.org markup is needed. Google still advises keeping structured data as part of SEO, because the markup is what makes a page eligible for rich results.

Outside Google the picture is less clear, so I keep two rules. First, every fact in the markup also appears as plain text on the page, because that text is what any AI tool quotes. Second, the markup and the text are in the HTML the server sends. A crawl study by Vercel and MERJ found that none of the major AI crawlers render JavaScript, so markup injected by a script after load may never reach them.

For the rest of the AI search picture, read my guides to generative engine optimization, GEO vs SEO vs AEO and llms.txt.

How to add and test schema markup

  1. List your page templates: home, product, pricing, blog post, about, docs.
  2. Pick one type per template from the table above.
  3. Write the JSON-LD from the same data the page shows, so a price change on the page changes the markup too.
  4. Run each template through Google's Rich Results Test before launch.
  5. After launch, use the URL Inspection tool in Search Console to confirm Google found the markup.
  6. Check the Search Console rich result reports each month for errors after edits.

On a Framer site the markup goes into the custom code of each page or CMS template. On an Astro + Sanity site I generate it from the content model, which is how this site works: every page builds its JSON-LD from the same data as the visible page, so the two never drift apart.

Mistakes that cost you rich results

  • Marking up FAQ blocks purely for Google space, which no longer exists.
  • A SoftwareApplication rating with no real reviews behind it.
  • Your own testimonials marked up as Organization reviews.
  • Markup that says one price while the pricing page shows another.
  • Organization markup copied onto every page with a different logo or name.
  • JSON-LD added by a tag manager script that simple crawlers never run.

When to hand schema to a developer

A small site with a good CMS plugin can handle Organization and Article markup alone. Bring in a developer when the markup has to come from templates and a CMS, when you are moving platforms and the old markup must not get lost, or when the pricing page changes every quarter.

I include structured data in every build. A landing page starts at $1,200 (1 to 2 weeks), a multi-page site at $3,000 (2 to 4 weeks), and a migration at $2,200 (2 to 4 weeks), with SEO and GEO basics included in all three. Small fixes after launch are $30 an hour. See pricing, the technical SEO service, or start with the free AI visibility check.

If you need this built

A landing page from Pavlo starts at $1,200 (1 to 2 weeks), a multi-page site at $3,000 (2 to 4 weeks). The price is fixed before work starts.

See all prices

Frequently asked questions

What is schema markup in simple terms?

Schema markup is a short block of code, usually JSON-LD, that describes a page in the schema.org vocabulary: this is a company, this is its logo, this is an article and its author. Search engines read the markup to understand the page and to decide on rich results.

Does schema markup improve rankings?

Not directly. Google says correct markup makes a page eligible for rich results but does not guarantee them, and a structured data manual action removes rich results without changing rankings. The value is in clearer results and fewer misreadings of your page.

Which schema types does a SaaS website need?

Organization and WebSite on the home page, BreadcrumbList on inner pages, Article on blog posts, and SoftwareApplication on the product page only when you have real ratings or reviews to mark up.

Are FAQ rich results still shown in Google?

No. Google's changelog says the FAQ rich result stopped appearing in Google Search from 7 May 2026, and the FAQ documentation was removed in June 2026. The FAQPage type itself is still part of schema.org.

Do ChatGPT and other AI tools need schema markup?

Google says structured data is not required for its generative AI features and that no special markup is needed. For other AI tools, keep every fact in plain text on the page and in the server HTML, since a Vercel study found major AI crawlers do not run JavaScript.

How do I test schema markup?

Run the page through Google's Rich Results Test before launch, then use the URL Inspection tool in Search Console to confirm Google found the markup. The rich result reports in Search Console show errors after later edits.

Pavlo Zhydkykh

Written by

Independent designer and developer in Eastern Europe. He builds websites on Framer and on Astro with Sanity for AI, fintech and B2B startups, and writes these guides from client work.

First published · Updated

Start a project
Halftone mouse cursor Free tool Does ChatGPT recommend you?

Free report in 48 hours · 5 AI engines

Checklist

5 schema types a SaaS website needs

What Pavlo Zhydkykh adds to a SaaS marketing site, each type on the page template where Google expects it.

  1. 1. Organization

    On the home page: name, logo, URL and sameAs links to official profiles, which help Google tell the company apart from others.

  2. 2. WebSite

    On the home page: Google says WebSite markup is the most important signal for a preferred site name in search results.

  3. 3. BreadcrumbList

    On every inner page: the page's position in the site hierarchy, shown as a breadcrumb trail.

  4. 4. Article

    On blog posts and guides: the article title and images for article results.

  5. 5. SoftwareApplication

    On the product page, only with real reviews: Google requires a name, a price (0 when free) and a rating or a review.

Fit check

Is Schema markup work on a SaaS site
right for you?

A good fit if

  • The home page has no Organization or WebSite markup, so Google guesses the logo and site name.
  • Blog posts and guides have no Article markup and no breadcrumbs.
  • A platform move or redesign is planned: Pavlo Zhydkykh builds the markup into the new templates.
  • Prices or product facts change often and the markup has to follow the page automatically.

Not the right fit if

  • The plan is FAQ markup to win more space in Google: that rich result is gone since May 2026.
  • The goal is a star rating with no real reviews behind it: Google's rules forbid fake or self-serving reviews.
  • The pitch is special markup for AI answers: Google says its AI features need none.
  • Key pages are not indexed yet: fix crawling and content first, then add markup.

Compared

Schema markup in Google vs AI search

Google documents what markup does in Search; AI assistants document very little. Pavlo Zhydkykh builds every page for both columns.

Schema markup in Google vs AI search
CriterionGoogle SearchAI search
Is markup required?No, but needed for rich resultsNo; Google says its AI features need no special markup
What it readsJSON-LD, Microdata or RDFaMostly the page text in the server HTML
ScriptsGooglebot can render JavaScriptMajor AI crawlers do not run JavaScript, per Vercel
Visible payoffBreadcrumbs, logo, site name, ratingsNo documented display; the text gets quoted
Rule of thumbMark up only what readers seeKeep every marked up fact in plain text too

In their words

Schema markup, in the words
of Google and clients

Word for word, with the source linked: research, official documentation and the people Pavlo Zhydkykh has worked for.

“Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add.”

Google Search CentralOptimizing for generative AI featuresSource ↗

“Don't mark up content that is not visible to readers of the page.”

Google Search CentralStructured data general guidelinesSource ↗

“The results consistently show that none of the major AI crawlers currently render JavaScript.”

VercelThe rise of the AI crawlerSource ↗

“One of the best contractors I have worked with. Really thoughtful about communication. Went above and beyond in delivering the results that our team needs. Would 100% hire again for our projects.”

Client on UpworkFramer development · Framer Specialist contract on UpworkSource ↗

“Pavlo was a pleasure to work with on this project. The web and mobile designs he created were amazing. His communication was prompt which made for a smooth project. I highly recommend his services.”

Shawntae SpencerClient, QuickQuick Pay · Web and mobile design on UpworkSource ↗

“The collaboration went smoothly and the work was delivered as agreed. Communication was timely, and the final result aligned with the initial expectations. Overall, a very positive and rewarding experience!”

Client on UpworkE-commerce website · Home page redesign on UpworkSource ↗
Pavlo Zhydkykh

About the author

Pavlo Zhydkykh

Pavlo Zhydkykh is a web designer and developer in Eastern Europe who has built websites for AI, fintech and B2B startups since 2016, designing and building each project himself on Framer or Astro + Sanity. Clients include MStudio Asia, Silicon Data, Inturai, Accolade Pro, NimbleStax and Sancts.

  • Top Rated on Upwork
  • 100% Job Success
  • 10 years since 2016
  • 50+ sites shipped
  • 90+ PageSpeed at launch
Kulparkivska St. 200, Lviv 79021, Ukraine +380 93 610 62 68 pavlozhydkykh@gmail.com

Page reviewed by Pavlo Zhydkykh · Updated

AI visibility check

  1. 1Website
  2. 2Business
  3. 3Contact
  4. 4Check

Does ChatGPT recommend your website?

Pavlo Zhydkykh asks ChatGPT, Perplexity, Gemini, Claude and Grok 20 questions your buyers ask, and shows where you show up.

Free · report in 48 hours