Schema markup is code you add to a page that tells search engines and AI systems what the page is about in a shared vocabulary (schema.org): this is a company, this is a software product with this price, this is an article by this author. It is usually written as JSON-LD inside a script tag, it does not change how the page looks, and it can make a page eligible for rich results such as review stars and breadcrumbs. You can write it without touching JSON by hand using the free schema markup generator.
Schema markup is not a ranking boost. Google has said so repeatedly, and the list of rich results it rewards has shrunk several times since 2023. What it does is remove guesswork: it states facts about your page in a form machines read without error. For a startup with a new domain and few signals, that clarity is cheap and worth having.
This guide covers what structured data is, what it earns in 2026, the schema types that matter for a SaaS site, two complete JSON-LD examples, how to add the markup in common stacks, and how to test it with the schema markup checker.
What schema markup is
HTML tells a browser how to display text. Schema markup tells a machine what the text means. The words "Acme Invoices, free, 4.8 stars" are just text to a crawler. Wrapped in markup, they become a SoftwareApplication named Acme Invoices, with an Offer whose price is 0 and an AggregateRating of 4.8.
Structured data, schema.org and JSON-LD: three names, one idea
- Structured data is the general idea: information in a fixed format with labeled fields.
- Schema.org is the vocabulary: a shared dictionary of types (Organization, Product, Article) and properties (name, price, author), founded by Google, Microsoft, Yahoo and Yandex.
- JSON-LD is one way to write it: a block of JSON in a
<script type="application/ld+json">tag.
People say "schema markup", "schema" and "structured data" interchangeably. They all mean the same thing in practice: schema.org types, usually written in JSON-LD.
The three formats
| Format | How it is written | Maintenance | Use it? |
|---|---|---|---|
| JSON-LD | A separate script block of JSON | Easy: lives apart from your layout | Yes. Google recommends it |
| Microdata | Attributes such as itemprop on visible HTML tags | Fragile: breaks when templates change | Only if a platform forces it |
| RDFa | Attributes such as property on visible HTML tags | Fragile, and rarely used for SEO | Rarely |
What structured data does in 2026, and what it does not
Be clear about the payoff before you spend time on it. Schema markup does three things.
- Makes a page eligible for rich results. Breadcrumb trails instead of a raw URL, review stars on a software or product result, product prices and availability, video thumbnails, event dates. Eligible is the key word: Google decides per search whether to show one.
- States entities and their relationships. Your company name, logo, official profiles and founder, linked together, help search engines connect your brand to the right knowledge panel and avoid confusing you with a company that has a similar name.
- Gives AI systems clean facts. Assistants and answer engines that read pages can extract a price, a date or an author from markup without parsing your layout. None of them promises to use it, but there is no downside to being unambiguous. Our guide on getting cited by ChatGPT and Perplexity covers the rest of that work.
What it does not do: improve rankings directly. Google's own documentation on structured data says it helps Google understand a page and can enable rich results, not that it lifts positions. A page with perfect markup and a weak answer still ranks like a weak answer.
The rich results Google has retired
Google has been simplifying its results page, and several schema types no longer earn anything visible in Google Search:
- HowTo: rich results removed in 2023.
- FAQPage: limited to well-known government and health sites in August 2023, then shown for no site from May 7, 2026. Our FAQ schema guide covers what that markup still does.
- June 2025 batch: Google announced it would phase out Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement and Vehicle Listing (Book Actions was on the list too, then reinstated in November 2025). Google said the change would not affect ranking.
- Late 2025: a further set of lesser-used features, including Dataset markup and practice problems, was announced for phasing out.
Retired features do not make the markup invalid. It stays valid schema.org, other systems can still read it, and there is no penalty for leaving it in place. Google's search gallery lists the features it currently supports; check it before you build markup for a rich result.
The schema types that matter for most sites
Schema.org defines hundreds of types. A startup needs a handful. The "key fields" column lists what our checker looks for, which follows the fields Google's rich results most often need.
| Schema type | Where it goes | Key fields | What it can earn in Google |
|---|---|---|---|
| Organization | Home page (or about page) | name, url, plus logo and sameAs | Logo and details in knowledge panels |
| WebSite | Home page | name, url | Your site name in results |
| SoftwareApplication | Product or pricing page of an app | name, offers, and aggregateRating or review | Software app result with rating and price |
| Product | A page selling one physical or digital product | name, and offers, review or aggregateRating | Price, availability and review stars |
| Article, BlogPosting | Blog posts, guides, news | headline, datePublished, author | Better headline, image and date handling |
| BreadcrumbList | Any page below the home page | itemListElement | Breadcrumb trail instead of a raw URL |
| VideoObject | Pages with a main video | name, thumbnailUrl, uploadDate | Video thumbnail and key moments |
| FAQPage | A page with a visible FAQ | mainEntity | Nothing visible since May 2026 |
A page can carry several types. A blog post can have BlogPosting and BreadcrumbList; a home page can have Organization and WebSite. Put each in its own script tag, or combine them in one @graph, as shown below.
Schema markup for SaaS: a page-by-page plan
Here is where each type belongs on a typical SaaS site. Start at the top and stop when the pages you have are covered.
- Home page: Organization (name, URL, logo, description, sameAs links to your X, LinkedIn, GitHub and Crunchbase profiles) and WebSite.
- Product or pricing page: SoftwareApplication with
applicationCategory,operatingSystem("Web" for a browser app) and anoffersblock. Use a price of 0 for a free plan. AddaggregateRatingonly from real reviews shown on that page. - Blog posts and guides: BlogPosting or Article with headline, image, datePublished, dateModified and an author that points to a real author page.
- Every page below the home page: BreadcrumbList matching the visible breadcrumb.
- Docs and help pages: Article (or TechArticle) and BreadcrumbList. Mark up a visible FAQ with FAQPage if you like; it is cheap, just not rewarded in Google any more.
Two SaaS-specific traps. First, Google shows the software app rich result only when the markup includes a rating or a review from real users; without one, the markup is valid but plain. Second, never invent a rating to get the stars. Ratings in markup must match reviews visitors can read, and misleading markup can cost you rich results for the whole site through a manual action.
JSON-LD examples you can copy
Organization for your home page
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://acme.com/#organization",
"name": "Acme",
"url": "https://acme.com",
"logo": "https://acme.com/logo.png",
"description": "Invoicing software for freelancers and small agencies.",
"sameAs": [
"https://x.com/acme",
"https://www.linkedin.com/company/acme",
"https://github.com/acme"
]
}
</script>
The @id is a stable identifier for your company, written as a URL with a fragment. It lets other blocks on other pages refer to the same organization instead of repeating it.
SoftwareApplication with a free plan
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "SoftwareApplication",
"name": "Acme Invoices",
"url": "https://acme.com",
"applicationCategory": "BusinessApplication",
"operatingSystem": "Web",
"offers": {
"@type": "Offer",
"price": "0",
"priceCurrency": "USD"
},
"publisher": { "@id": "https://acme.com/#organization" }
}
</script>
Note the publisher pointing at the Organization's @id. That one line connects the app to the company. If you have real reviews on the page, add an aggregateRating with ratingValue and ratingCount.
Several types in one block with @graph
If you prefer one script per page, wrap the objects in a @graph array: {"@context": "https://schema.org", "@graph": [ {...Organization...}, {...WebSite...} ]}. Search engines read both styles the same way. Pick one style per site and keep it consistent.
How to add schema markup, step by step
- Decide the type from the page, not from the rich result you want. A pricing page is SoftwareApplication; a guide is Article. Use the table above.
- Open the schema markup generator and pick Organization, Software app, Product, Article or Breadcrumbs. It runs in your browser, so nothing you type is sent anywhere.
- Fill in the fields from what is visible on the page. The generator lists the fields Google requires or recommends for that type and which ones are still missing.
- Copy the script and paste it into the page it describes, in the head or the body.
- Publish, then test the live URL as described in the next section.
Where to paste it in common stacks
- Plain HTML or a static site: just before
</head>. - Site builders: the page-level custom code field. Use the site-wide field only for Organization and WebSite, which belong on the home page anyway.
- WordPress: most SEO plugins write Organization, WebSite, Article and BreadcrumbList for you. Check what they output before adding your own, or you will have duplicates.
- Next.js or React: build the object from the same data that renders the page and output it with a script tag of type
application/ld+json, usingJSON.stringify. One source of truth keeps the markup and the page identical.
For an FAQ section, the FAQ schema generator builds the FAQPage block from your questions and answers.
How to test schema markup
Test the live page, not the snippet in your editor. Templates, plugins and caching layers change what actually ships.
- Our schema markup checker: paste a URL and it finds every JSON-LD block and microdata type on the page, lists each type with its fields, and flags invalid JSON and missing key fields. Use it to catch duplicates and broken JSON quickly.
- Google's Rich Results Test: the final word on whether a page is eligible for a rich result Google still supports.
- The Schema.org validator: checks the markup against the full vocabulary, including types Google does not use.
- Search Console: the enhancement reports show errors across every page of a type, weeks after you ship. Check them monthly.
Common schema markup mistakes
| Mistake | Why it is a problem | Fix |
|---|---|---|
| Marking up content visitors cannot see | Google's guidelines require markup to describe visible content | Only mark up what is on the page |
| Fake or self-written ratings | Misleading markup can lose rich results site wide | Ratings only from real, visible reviews |
| Organization markup on every page with different details | Conflicting facts about one entity | One Organization with an @id, referenced elsewhere |
| A plugin and a manual script both writing the same type | Duplicate, sometimes conflicting, blocks | Keep one; the checker lists duplicates |
| Trailing commas or curly quotes in JSON | One syntax error invalidates the whole block | Generate the JSON instead of hand-typing it |
| Prices in markup that differ from the page | The markup no longer describes the page | Build both from the same data |
Relative URLs in url, logo or image | Some readers cannot resolve them | Use full https URLs |
Is schema markup worth it for a small site?
Yes, in proportion. Organization on the home page, the right type on your product page, Article and BreadcrumbList on your content: that is an afternoon of work for a small site, and then it maintains itself if it is generated from your data. Going further, such as marking up every paragraph with obscure types, adds noise, not value.
Spend the rest of the effort on what markup cannot do: pages that answer the search better than anything else ranking. The on-page SEO checklist covers that work, and the same discipline of describing your page precisely applies to your Open Graph tags, which control how links to your pages look when shared.
FAQ
What is schema markup in SEO?
Schema markup is structured data, written in the schema.org vocabulary and usually in JSON-LD, that describes what a page contains: a company, a product, an article, a list of breadcrumbs. Search engines use it to understand the page and to decide whether it is eligible for rich results.
Does schema markup improve rankings?
Not directly. Google treats structured data as a way to understand a page and enable rich results, not as a ranking factor. A rich result can raise your click rate, and clear entity data helps search engines identify your brand, but rankings still come from relevance, quality and links.
What is the best schema markup generator?
Any generator that produces valid JSON-LD for the type you need and lists missing fields will do. The free schema markup generator on Aback Launch covers Organization, SoftwareApplication, Product, Article and BreadcrumbList, runs in your browser and shows which recommended fields you have not filled in yet.
Is JSON-LD better than microdata?
For almost every site, yes. JSON-LD sits in its own script block, so redesigns do not break it, and it is the format Google recommends. Microdata is woven into your visible HTML, which makes it harder to maintain. Search engines read both.
Which schema types should a SaaS website use?
Organization and WebSite on the home page, SoftwareApplication on the product or pricing page, BlogPosting or Article on posts and guides, and BreadcrumbList on every page below the home page. Add FAQPage to pages with a visible FAQ if you want, knowing Google no longer shows FAQ rich results.
How do I check if my schema markup is working?
Test the live URL. A schema markup checker shows every block it finds and flags invalid JSON; Google's Rich Results Test confirms eligibility for supported rich results; Search Console's enhancement reports show errors across your whole site over time.
Generate it once, check it, move on
Schema markup is a precise label on content you already have. Pick the type that matches each page, build it with the free schema markup generator, check the live page with the schema markup checker, and put the time you save into the page itself.
Ask AI about this page
Open your assistant with a prompt to summarize this page, already filled in.
Written by
Devvrat Hans
Founder
By subscribing, you agree to get our newsletter by email. Unsubscribe any time in one click. See our Privacy policy and Terms.
Related Articles
App Store Optimization (ASO): Keywords, Title, Subtitle and Screenshots for iOS and Google Play
A practical app store optimization guide: how App Store and Google Play search read your listing, keyword research, the app title and subtitle, the 100 character keyword field, Google Play ASO, screenshots, ratings and testing.
Broken Link Checker Guide: How to Find and Fix Broken Links, 404 Errors and Broken Backlinks
How a broken link checker works, which status codes count as broken, whether 404 errors hurt SEO, the fastest ways to find broken links on your site, and how to fix each kind, including broken backlinks.
Core Web Vitals: LCP, INP and CLS Explained, How to Test Them and How to Improve Them (2026)
What Core Web Vitals are in 2026, the good and poor thresholds for LCP, INP and CLS, field data vs lab data, how to run a Core Web Vitals test, and the fixes that move each metric on a startup site.