Schema.org is structured markup that you can add to your HTML documents to help search engines understand your content, and it makes your snippets stand out in the search engine result pages (SERPs).
Other forms of structured data in digital marketing are Open Graph and Twitter Cards.
Throughout this article, we’ll be using the term “Schema” to indicate a type of content that you can mark up using Schema.org.
Search engines are pretty good at understanding your content’s topics, but often you can help them understand your content better by far if you define the content’s type using Schema.org. This makes it more likely for them to display enhanced snippets for your pages. Enhanced snippets stand out from the regular snippets, resulting in more clicks.
A familiar example of an enhanced snippet is one that includes review data. Take for example these two snippets in Google:
Which snippet do you think gets the most clicks (not taking into account the position of the snippet)?
Exactly - the first one. It stands out from regular snippets, and when there’s solid review data, it builds trust.
Practitioners often ask, "What's the point of exhaustive structured data on my pages? Should I use just what is necessary?" There are two reasons to go wild with your markup.
The first is future-proofing: search giants introduce new rich features that utilize extended portions of the Schema.org library all the time. If you're prepared, you'll benefit immediately.
The second is philosophical: Tim Berners Lee wrote, "Properly designed, the Semantic Web can assist the evolution of human knowledge as a whole." Structuring your site makes your website applicable for internet ontologies, aiding greatly the organization and dissemination of information online. Much like making your pages WCAG-compliant, good structured data includes your site in an experiment that benefits the free exchange of ideas.
Marking up reviews is one example of using structured data, but there are many more.
Here are the most popular Schema types:
Articleis a more generic Schema type.
NewsArticleis often used by publishers for news articles and
BlogPostingby organizations with websites that contain blog posts.
AuthorSchema type for an article.
Article schema type is the parent type of
When to use which one?
Article: this is the generic type, which we don't recommend using. The more specifically you mark up your content the better, so choose between
Google supports enhanced snippets for articles, specifically
NewsArticle, so we'll be zooming in on that Schema type in this section.
Please note that even if you don’t mark up your news articles with the
NewsArticle Schema type, search engines may still show an enhanced snippet if you're included in their news results. In Google's case, there's a vetting process you have to go through in order to be included in those results. Just marking up your articles with the
NewsArticle Schema type does not mean you'll automatically get into the news results. If you are included, we always recommend implementing the
NewsArticle Schema type. Search engines are able to identify your news article to a certain extent, but it's better to be safe than sorry, and implement that
NewsArticle mark up!
If you're included in the news results, your news articles could look something like this:
Google distinguishes between required and recommended properties when it comes to Schema. Even though some properties aren't required by Google, they are highly recommended in order to paint a complete picture of your content type. Google further distinguishes between AMP and non-AMP news articles. They require more properties for news articles that are marked up using AMP.
Below we'll describe the required and recommended properties for non-AMP news articles.
The properties below are required for
|headline||Text||The article's headline - a maximum of 110 characters.|
||One or more images, at least 696 px wide.|
The properties below are highly recommended for
||The date when the article was published.|
||The definition of the author.|
||The definition of the publisher.|
||The date when the article was last modified.|
|description||Text||A description of the article.|
||Indicates a page (or other CreativeWork) for which this "thing" is the main entity being described.|
If you want to read more about
NewsArticle, check out:
Organization Schema type describes an organization, including its logo, website address, social media profiles, and contact information. It’s used for organizations that people don’t physically visit. For organizations that people do visit, we have the
LocalBusiness type instead.
A knowledge graph card, the block on the right hand side of a search engine result page, is basically the enhanced snippet of an organization. And these aren't easily earned, as they’re mostly reserved for well-known brands such as Apple and Mercedes-Benz and for online businesses such as Mashable.
Here's what it looks like:
Below we describe the required and recommended properties for
The Schema type named
Organization has only one required property. While this is technically correct, it's useless information, and it won't get you anywhere if you want your Schema implementation to move the needle for you - so implement the recommended properties too.
|url||URL||Your homepage URL.|
We highly recommend implementing as many as possible of the recommended properties below to describe your organization.
||The URL for your company's logo. Additional requirements:
|sameAs||URL||Used to define one ore more of an organization’s social media profiles. Supported platforms:
||One or more contactPoint records.|
If you want to read more about
Organization, check out:
Person Schema type is used to describe a person. It's often used in relation to defining an author of an article using
Author, but can also be used to describe a person's role within an organization.
Organization, the enhanced snippet for
Person is the knowledge graph card. Here's what it looks like when we search for "Steve Jobs":
Person has few required properties. And again, if you only go for the required properties, your
Person implementation is going to be useless. Therefore, we highly recommend implementing the recommended properties as well. Remember, when it comes to structured data: more is more.
The Schema type
Person only has one required property. While this is technically correct, it's useless information, and it won't get you anywhere if you want your Schema implementation to move the needle for you.
|name||Text||The name of the person.|
We highly recommend implementing as many as possible of the recommended properties below to describe the person.
|url||URL||URL for the person's website.|
|sameAs||URL||Used to define one ore more social media profiles. Supported platforms:
||The person's date of birth.|
||The person's place of birth.|
||The organization that the person's affiliated with.|
If you want to read more about what you can do with the Person Schema type, check out these resources:
Schema should be included directly in a page’s source code. It can be implemented using any of three formats:
The recommended format for implementing Schema is via JSON-LD. JSON-LD is a way to encode Linked Data using JSON (which is a file format standard with similarities to XML). It’s less error prone than Microdata and RDFa. In this article, we’ll focus on implementing structured data using JSON-LD.
What does a data implementation look like then? Let’s look at the BlogPosting Schema type. This is what the JSON-LD code looks like:
So what does that say?
This is a relatively simple example, but there are much more advanced examples for putting Schema to use.
Implementing Schema JSON-LD mark up can be done through:
When implementing structured data, keep in mind Google’s guidelines to become eligible for enhanced snippets and to prevent a potential Google penalty.
After adding Schema to your pages, make sure it’s present by looking up the pages in question in ContentKing. We directly recommend using ContentKing for this, as it’s a task you need to perform at scale, rather than page-by-page using Google's Structured Data Tester (see below). Don't have a ContentKing account yet? Create a free trial account here!
Then test whether your structured data implementation is correct, by using Google’s Structured Data Tester and choosing random pages. Note that Google’s Structured Data Tester tool only supports checking URL by URL, so it can be quite time consuming.
Additionally, if you’ve got access to Google Search Console you’ll get feedback from Google on the structured data implementation in two sections:
Search Appearance >
Structured Data. Please note that this feedback is delayed, but it can be great for catching errors.
Schema.org is an initiative that was launched in 2011 by Google, Bing, and Yahoo. A few months after its launch, Yandex joined the initiative as well.
Out of all the search engines, Google has by far the best support for Schema.org. Throughout this article we focus on implementing Schema for Google, but what about the others?
In March 2018, Bing confirmed that it was supporting Schema.org. They support the following Schema types via Microformats, RDFa, and JSON-LD (similar to Google):
More information can be found in their help section about marking up your site.
While Yahoo's webmaster resources don't say anything about support for Schema.org, they do support it. Yahoo Search, which is powered by Bing, seems to support the same Schema types as Bing does.
Yandex supports the following Schema types, via Microformats only:
More information can be found in the Yandex Webmaster Support section on Schema.org.
In 2017, Baidu mentioned that they'd be aiming at supporting Schema.org, but for the moment they don't support it yet.
If you're dependent on multiple search engines, you may run into compatibility issues. Yandex for example requires some properties that aren't required for Google. So keep in mind that search engines may want to see different, or more complete data. It doesn't hurt to include more data; the search engines will just grab what they can use.
Yes and no.
While structured data is not a direct ranking factor, it does indirectly impact your rankings. Structured data helps you get more clicks on your snippets, leading to a higher CTR. We - and many SEOs along with us - believe that CTR does impact rankings, because it sends a quality signal to search engines.
These tools will come in handy when you're working with Schema:
Yes, you still need Schema. You've been very fortunate, because it doesn’t happen that often that Google figures out your content types on their own. To increase your chances of their showing enhanced snippets for your content types, it’s still highly recommended that you implement Schema. This enables them to process your content better and more quickly, as describing your content types using Schema is far less error-prone. Keep in mind that your competition isn't sitting around, so you want to make sure you're doing everything in your power to stay ahead of them.
No, that’s not possible. In the end it’s up to Google’s discretion to enhance your snippets.
Please note that it can easily take up to a few weeks before Google picks up on your structured data, and even then it may not be valid, so they may just disregard it.
While it would make sense for your homepage to be shown with the review data, Google doesn’t do this for any websites. Google will only show review data for pages other than the homepage.