What is Schema.org?

Schema.org is a shared vocabulary for structured data, supported by Google, Bing, Yahoo and Yandex. Schema.org defines standardized types and properties such as Product, Article or FAQPage, which a web page uses to mark up the meaning of its content so search engines and AI systems can read it. Schema.org is usually implemented through the JSON-LD format, a compact block of data in the source code of the page.

Schema.org explained: the shared vocabulary for structured data with the types Product, Article, FAQPage and the JSON-LD format

Schema.org is the language a website uses to tell search engines what a piece of content means. Without that markup, Google sees only text and cannot tell whether 129 EUR is a price, a phone number or a house number. With the right schema type, plain text turns into an unambiguous statement that Google and AI systems can process directly.

Term at a glance

Property	Detail
Kind	Vocabulary and open standard for structured data
Founded	2011 by Google, Bing, Yahoo and Yandex
Pronunciation	skee-muh dot org
Scope	More than 800 types and around 1,400 properties (extended continuously)
Preferred format	JSON-LD (recommended by Google)
Related terms	Structured data, JSON-LD, rich snippets, entity

How do Schema.org, structured data and JSON-LD fit together?

Schema.org, structured data and JSON-LD are three layers of the same job: the concept, the vocabulary and the format. The terms are often mixed up, but they mean different things.

Structured data is the concept: the idea of storing page content in a machine-readable, standardized scheme.
Schema.org is the vocabulary: the concrete set of types and properties the major search engines have agreed on.
JSON-LD is the format: the notation in which the Schema.org vocabulary is written down and placed inside the page.

A JSON-LD block that uses the Schema.org vocabulary looks like this for a product:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Cordless Drill X200",
  "brand": { "@type": "Brand", "name": "taismo Tools" },
  "offers": {
    "@type": "Offer",
    "price": "129.00",
    "priceCurrency": "EUR",
    "availability": "https://schema.org/InStock"
  }
}
</script>

The @context points to Schema.org and loads the vocabulary. @type selects the type Product, and the properties name, brand and offers fill it with values. Besides JSON-LD there are the older formats Microdata and RDFa, which weave the markup straight into the HTML. Google recommends JSON-LD today, because it sits separately from the visible content in the <head> or <body> and is easier to maintain.

Fig. 1: Structured data, Schema.org and JSON-LD as concept, vocabulary and format.

Which schema types matter for SEO?

Schema.org holds more than 800 types, but only a dozen or so produce visible results in Google. These types matter most for SEO:

Organization / LocalBusiness: company data, logo, address and opening hours. The basis for the knowledge graph entry and for local results.
Product / Offer: price, availability and reviews. Triggers price and star displays in shopping and search results.
Article / BlogPosting: headline, author and date. Marks up editorial content and supports authorship.
FAQPage: Question and answer pairs. Google stopped showing them as a rich result on May 7, 2026, but the markup still helps AI systems and topic assignment.
BreadcrumbList: the navigation path display that replaces the URL path in the result listing.
Review / AggregateRating: star ratings for products, recipes or companies.
Event, Recipe, HowTo, JobPosting, VideoObject: specialized types for events, recipes, instructions, job ads and videos, each with a rich snippet of its own.

Every type sits at a fixed place in the Schema.org hierarchy. BlogPosting is a subtype of Article, and Article in turn is a subtype of CreativeWork. A type inherits all properties of its parent class, which is why the more specific type is almost always the better choice.

How do you implement Schema.org?

Schema.org is added in 4 steps. The sequence is the same for every type and takes a few minutes for a single page.

Pick the type: determine the Schema.org type that fits the page content, for example Product for a product page or FAQPage for a block of questions.
Write the JSON-LD: fill the required and recommended properties with real values from the page. Google documents per type which fields are required.
Embed it: put the JSON-LD block into the source code as <script type="application/ld+json">, in WordPress usually through an SEO plugin such as Yoast or through a code snippet of your own.
Test it: check the markup with the Google Rich Results Test and the Schema.org validator, and monitor errors in Google Search Console.

Fig. 2: Implementing Schema.org in four steps, from the type to the Rich Results Test.

What does Schema.org deliver? Rich snippets and AI visibility

Schema.org delivers two concrete benefits: more visible search results and better citability in AI systems. Both follow from machines understanding the page content without ambiguity.

Rich snippets: Google enriches the search listing with extra information such as star ratings, prices, breadcrumb paths or recipe images. These rich snippets make the listing bigger and lift the click rate without changing the position itself.
AI visibility (GEO): AI systems such as ChatGPT, Perplexity and Google AI Overviews rely on facts that are clearly marked up. Schema.org anchors a page as a clearly named entity with defined properties and raises the chance of being quoted, which is the goal of generative engine optimization.

One thing to keep straight: Schema.org is not a direct ranking factor. The markup does not improve the position, it improves the presentation and the machine readability. That markup work is a core building block of professional SEO services and the foundation for solid visibility in Google and in AI answers.

Frequent questions about Schema.org

Is Schema.org a ranking factor?
No, Schema.org does not improve rankings directly. The markup produces rich snippets and a clearer machine interpretation, which indirectly strengthens the click rate and AI visibility.

What is the difference between Schema.org and JSON-LD?
Schema.org is the vocabulary of types and properties, JSON-LD is the format that vocabulary is written in. You use Schema.org terms inside a JSON-LD block.

Does every website need Schema.org?
Every website benefits from basic markup such as Organization and BreadcrumbList. Additional types such as Product, Event or Recipe pay off as soon as the page holds matching content that Google offers rich snippets for.