- Use cases
- Customer Success
- LOG IN
- Start free trial
In this article I will be looking at what exactly Schema.org structured data is, why it is essential for building E-A-T, and how we can leverage its huge range of types and attributes to communicate clear precise data to search engines.
Expertise, Authority and Trust, or E-A-T, is one of the main criteria that search engines use to decide which is the best site to show for a given search query. Using structured data will tell them very precisely who you are and what you do and this increases their trust in your site. Including additional data that shows expertise and authority will also increase trust and get your site ranked better.
There is a further level known as “YMYL”, or Your Money, Your Life, which includes all sites dealing specifically in finance and health. For this category Google is extra strict and you really need to be sure to include any information that demonstrates that you are qualified and competent to be talking about these subjects.
You may be wondering:
Structured data is information presented in a standardized format that can be understood by machines.
A huge exception to this is the information you put into the visible text content of your website pages. There are no rules governing how your data should be laid out. When search engines look at that content they analyze the chunks of text looking for things they can identify as particular types of data. But it’s always with a certain degree of uncertainty. For example, take a standard address such as :
Amazing Stuff Inc, 39 Main Street, 34000 Newtown, France
Humans from places that use this particular address format can instantly see that this is an address. But imagine you were someone from another part of the world that uses a different address format; would you understand what all the parts of the address were? This is what it is like for machines.
Artificial intelligence in search engines has developed to the point where it can recognize that this probably looks like an address, and extract the various elements, but it still is not 100% certain and needs corroboration from many other sources to feel confident about what it has guessed. Structured data, however, is built of pairs consisting of a standardized name, such as “streetAddress”, and the value assigned to it (in this case “39, Main Street”), and search engines scan the html code looking for this type of named data.
The problem, therefore, is that although the information in your web pages may look structured to the human eye, it isn’t structured at all for machines. They have to guess!
Schema.org is part of an initiative launched in 2011 by Google, Bing and Yahoo to provide a system of universal schemas to enable structured data to be marked up in websites. When the search engines see the line “@context”:”http://schema.org/” they start looking for named Schema.org data pairs they can recognize.
We can insert Schema structured data into the <head> section of our html like this :
Structured data in JSON-LD format
And this is how the search engines see it when they analyze the page :
Structured data in Google’s structured data testing tool
Isn’t that so much clearer? The search engine algorithms are now 100% sure about the identity and role of each bit of structured data. This makes their life much easier and will increase the level of trust they have in who you are and what you do, boost your E-A-T and improve your rankings.
I’ll start with the most basic Schema and then look at some additional optimisations.
Firstly, you’ll need to define your type of organization. Because the Schema.org system is a hierarchy of things (which you can see here) called types, you can start at the most general type and go deeper into the hierarchy until you find your type. The most general type is Thing, containing a number of broad subtypes, one of which is Organization. As you can see in Figure 3, Organization contains other types like Corporation, LocalBusiness, EducationalOrganization etc.
Part of the type hierarchy
You can see that LocalBusiness has a large number of subtypes, so you could continue digging deeper, but if you’re not a local business then you’re probably a Corporation, so you can look at that. Click here to see the page for Corporation.
Your Schema block would now look like this:
The Corporation type
This is great and doesn’t give us any errors in the Structured Data Testing Tool but it doesn’t tell us anything at all about the company, so we need to give it some attributes, or pieces of data that describe it.
On the Corporation page, you will see that it has a number of accepted attributes. It is important to spell the attribute names properly because once the search engine has seen the type it will look for the specific accepted attributes for that type. Attribute names start with a lowercase letter and type names start with an uppercase.
Some types have one or more required attributes: if you choose a LocalBusiness type (or a subtype of LocalBusiness) you may see errors displayed in the testing tool because it requires at least a name and an image url.
Errors for missing data
If this happens be sure to provide at least the required data as in figure 6 below, to avoid bad markup, and then you can add in extra data :
The errors are fixed
For the rest of this article I will take the example of sunfimmo.com, a company I have marked up in the past. It’s a French company but, remember, the attribute names are always in the standardized English form to be recognizable to the search engines.
The company is a real estate agency but they don’t have an actual physical agency you can visit, so they can’t be one of the LocalBusiness types. Instead of using RealEstateAgent their type has to be Corporation. The basic markup looks like this:
Basic Schema.org for a Corporation
We now have some good basic data about the company. Note that the legalname is not the same as the name used for trading – this is important because later we’ll be adding links to official company registration listings and the data needs to be the same if we want to build confidence in the exactness of the data. The same is true for the address and phone number; they need to be the same everywhere!
If a company has several contact points (in different towns, regions or countries) they can be marked up too. This company has two offices but they share the same telephone number so they are grouped together like this:
Basic Schema.org for a ContactPoint
Note that when a type (here it’s ContactPoint) is used as a value for an attribute it is marked up as a block in curly brackets; this is structured data! When an attribute has several values we can put them in square brackets, separated by commas.
You saw previously in the article that we can’t mark up the company as a RealEstateAgent because it’s not a local business but we CAN still show that it has the specific type of estate agent in a structured data format by using the Productontology system. I won’t go into detail now (the instructions are here) but it enables us to do this:
And we can also put a link to Wikipedia in a sameAs block:
Linking to official pages for increased credibility
We now have markup with basic details of the company and have provided a more specific type. But remember that we also want to increase trust and credibility and show that the company is a real thing. To do this we can link to official pages containing data that we cannot change ourselves, making them far more credible than, for example, social network accounts where basically anyone can claim to be anything they want!
Here in France, all companies have an official registration number (“SIRET”) and a code for the sector they’re working in (“CODE NAF”). So we can write a custom block that in effect says:
“This is an official identifier, here is what it is called, here is its value, here is a wikipedia page describing it and here is the official administration page with the listing”:
Using Schema.org identifier
To corroborate with further “official” information we can provide links to company information listings pages, along with any relevant active social accounts, in the sameAs block like this:
More sameAs links
Adding Schema data for a Person to increase expertise and authority
We’ve created our main block of Schema markup for Corporation and added a host of data to enhance its credibility and trustworthiness. A good way to increase authority and expertise (remember, this is all about E-A-T) is to include one or more people and what their credentials are. To do this we can include a Person block, like this:
Schema.org for a person
Here we’re saying that the founder is a Person called Jean-Bernard Huet, then we provide his LinkedIn account and state that he is an alumnus of two EducationalOrganization with a link to the pages of the specific diplomas obtained, one in economics & business and one in real estate law. To enhance his professional credibility we can include an identifier block, like for the company, but this time defining his real estate agent licence number and linking to official pages that describe what it is, along with the official Chamber of Commerce listing page:
Schema.org identifier for a person
So, now we have provided a massive amount of very precise data to Google in a format specifically designed to be easily understood by machines!
The one problem is that our block is now huge and contains entities within entities that are not all necessary in all the Schema blocks on all the pages. Take the example of the Schema markup block for the founders attribute where we want to include the Person and all the information about them, but we don’t want to have to include the whole Person block every time. This is where the @id comes into its own: once we have defined the Person block with an @id we can include that @id in the founders block …
Schema.org @id for entities
… and Google will link the entities via the @id as you can see in the Structured Data Tool Tool:
How google will see this block
To make the management of blocks more systematic you can put them as separate blocks into a container element like @graph and link them together using the @id, like this :
Using @graph for multiple blocks
So there we have it: structured blocks of clear precise data linked together via the @id attribute, telling Google and the other search engines exactly who you are, what you do and why you have the expertise and authority required for your pages to be well ranked in the search results. Anything you can do to help the search engines understand your site and reduce their workload will benefit your site.
This is a vast subject and we haven’t even looked at markup for products/services or blog articles, not to mention how we can mark up reviews and ratings in structured data to boost E-A-T, but these will be dealt with in future articles.
Have fun with your structured data and be sure to use the Structured Data Testing Tool!