JSON-LD or Microdata - Which schema format is better for ranking
JSON-LD or Microdata - which schema format is better for SEO and ranking on Google search? Learn the pros and cons of both approaches to represent the structured data on webpages.
JSON-LD and Microdata are two popular methods for Schema implementation to get better visibility on search engines. Modern search engines can show rich snippets on the search results that give additional information about your website. In order to decide what to show in the rich snippets, they depend on the structured data on the pages to a large extend.
The terms "Schema" and "Structured Data" are used interchangeably in this article. While "Schema" is a generic term that represents the industry standard to represent data objects on the web, the later is a term mostly used by web developers to represent the data that appears on search results in the form of rich results. Schema definitions are used to build structured data. Both represent more or less the same in the context of this article. Read more about Schema at www.schema.org and introduction to structured data.Common types of Schema
Some of the common Schema types used in various websites include:
There are several other Schema types that can be added to the websites. Depending on the nature of your website, you can choose the right Schema types. As a leading digital marketing company, we have been helping websites follow the best industry practices.
All SEO experts would agree that Structured Data can help in significantly improving the organic ranking and traffic generation for the websites, provided they have implemented it right.Structured Data Formats
Search engines like Google recognise structured data in the following formats:
In JSON-LD format, the data objects are embedded in the website in the form of a script, typically placed in <script> tag. In this approach, the data is separated from the main body of the page and thus is easier to read and understand by looking at the source of the page. it is cleanly separated from the HTML.
In Microdata format, the structured data is represented in the page by adding additional HTML attributes to the content already on the page.
RDFa is similar to Microdata but it uses an HTML 5 extension to add attributes to the text to represent structured data. RDFa can be placed in the <head> or <body> of the page.
Each of the formats has its own merits and demerits.
Now, let's come to the point - which to choose?JSON-LD or Microdata - Which is more effective?
Developers are often confused about which structured data format to choose from. Technically, they are just different implementations that achieve the same purpose in different ways. However, there are a few reasons why one could be better than the other in different scenarios.Reasons to choose JSON-LD over Microdata
1. Google prefers JSON-LD over Microdata
Google has made it clear in a few places that it prefers JSON-LD format over Microdata and RDFa. There is no explanation given in the official documentation on why it prefers one over the other but as of now, we have to go by what has been told to us.
If you want to go by the above official statements, then go for JSON-LD format. If you like to go for the easiest implementation, then you can ignore this and choose a format depending on other parameters mentioned below.
NOTE: Even though some official sources have said JSON-LD is it's the preferred method, all my research and experiments so far shows there is no difference when it comes to search engine ranking. This page itself is a case study. We have used Microdata to implement FAQPage schema and it appears as a rich snippet on SERP. You can read more about it towards the end of this article.2. Google can read dynamically injected JSON-LD
Does your website dynamically load content using Javascript or other scripting technologies? In such cases, JSON-LD will be the right approach. Google can read dynamically loaded scripts and recognise the schema in it. However, if you do the same with Microdata, Google may not recognise the schema in the dynamically pulled HTML content.3. Use Tag Manager to organise JSON-LD scripts
Here is another reason to choose JSON format. You can use Tag Manager or similar platforms to organise your JSON script. The Tag Manager is widely used by webmasters to manage scripts on their websites. You can add, modify or remove scripts on any web pages through the Tag Manager dashboard and don't need to modify the pages or even log in to the admin pages to make these changes. If you are planning to use JSON for structured data, you can add or modify them anytime on the Tag Manager without messing up the page content. With Tag Manager, you can handle this with minimal technical or programming knowledge. Also, your SEO team can work independently from the developers.Reasons to choose Microdata over JSON-LD
Here are some reasons to choose Microdata over JSON-LD.1. No need to repeat the data objects
As I said earlier, when using JSON format, you need to repeat the structured data in 2 places - one in the form of JSON-LD and another in the form of HTML for your readers. You can't choose to use it only as JSON and hide it from your readers. Google requires that all (most) structured data used in the website should be visible to the visitors. So, when you use the JSON format, you are required to show the same data in the form of HTML as well, leading to extra content on your website.
This won't be a problem for small pieces of JSON script. However, if you want to represent large objects like Article, FAQPage, QAPage etc, almost the entire content of the page needs to be represented in the schema and repeating the same in the form of JSON and HTML will almost double the size of your page and may affect your site's loading speed.2. Manage in one place
If you use JSON-LD, you have the same data in 2 places and when you make a change, you need to remember to change in 2 places. If you forget to change in one of these, you will end up inconsistent data and may even end up in violation of Google rules regarding structured data implementation.
My personal choice is Microdata for the 2 reasons mentioned above. I have been using this format in many websites and so far, it works perfectly fine. A Case Study - Microdata works as good as JSON-LD
This article is our case study to show that Microdata works as good as JSON-LD format. Search for "JSON-ld or Microdata which schema format is better" and you will see this article appearing on the first page of Google along with the FAQ used below in this page.
See the screenshot below:
So, this case study shows that Microdata format will work as good as JSON format when it comes to ranking on Google and showing rich snippets in the search results.How to verify your schema implementation and make sure it is working correctly
Once you implement the schema on your pages, using either one of the formats, you need to make sure it is done correctly. Considering the complexity of the implementation, there are good chances of error.
You can follow the steps below to test and verify your implementation:
Frequently Asked Questions
Conclusion
So, let me conclude this. Even though some search engines prefer JSON-LD format, I would say it is just because that is an easier format for its algorithm to read and process. In case of Microdata format, the engine needs to put some extra efforts to parse them, making it a bit tougher for it.
Irrespective of the efforts required for processing, when it comes to ranking and showcasing as rich snippets, the format used makes no difference. All supported structured data formats work equally well.References
Here are some additional references for more reading:
Do you have reasons to disagree with me? Share your comments below and I will be happy to review your points.
Most of the websites I have seen on the internet are using the JSON format for structured data. Is it because WordPress has built-in support for this format? Or, is it because Google prefers that approach? I am planning to incorporate schema for my website and like to get some clarifications before I proceed with the development.
Please give your suggestions.