What is Structured Data? And Why Should You Implement It?

Structured data is a standardized way to provide information about a web page. It helps search engines like Google to better understand what your content is about.

But what’s in it for you, and how do you implement it?

Let’s get into it!

ranking factor. It doesn’t directly help you to rank higher in Google. However, there are many benefits. We’ll focus on the four most important ones:

Get rich results
Get into Google’s Knowledge Graph
Support semantic search
Support your E‑A-T

1. Get rich results

Rich results are visually-enhanced search results with information pulled from relevant structured data. The most common type of rich results are rich snippets, like these:

These can often boost clickthrough rates and increase organic traffic to your pages.

2. Get into Google’s Knowledge Graph

Google’s Knowledge Graph is a knowledge-base of entities and the relationships between them. You, your brand, and your products can all become entities that are established and influenced by structured data.

The most direct implication of getting into the Knowledge Graph is having a Knowledge Panel that provides more brand visibility and authority:

3. Support semantic search

Semantic search focuses on the meaning behind search queries instead of traditional keyword matching. It’s how Google manages to return perfect results when you search for something as vague as this:

Because structured data helps Google to better understand what your pages are about, it may help them show up for more relevant search queries.

4. Support your E‑A-T

E‑A-T stands for expertise, authoritativeness, and trust. These three things are “what Google looks for in a web page.” Using structured data feeds Google information about your website, its content, and its authors, and makes it easier to assess your E‑A-T.

Schema markup provides such a universally recognized format for structuring data on the Web.

If I want to tell search engines that my first name is Michal, I need to look up how to annotate it. Looking up “name” in the schema.org vocabulary brings me to the givenName property:

You need to use this in its exact form in your code. Using variations like FirstName, firstName, or given_name won’t work. Standardization is the key to structured data, and the schema.org vocabulary provides it.

Take, for example, an airline flight: schema.org has a lexicon to notate the type of aircraft, the departure gate, and even a description of the meal service:

That’s it for the theory. Let’s take a look at how all of this works on your website.

Organization markup using JSON-LD:

<script type="application/ld+json">
{
  "@context": "https://schema.org/",
  "@type": "Organization",
  "name": "Ahrefs",
  "url": "https://ahrefs.com/",
  "description": "Ahrefs is a software company that develops online SEO tools and free educational materials for marketing professionals.",
  "email": "support@ahrefs.com"
}
</script>

This script can be placed anywhere in the <head> or <body> section of your HTML.

Microdata

Unlike JSON-LD, where structured data is in one big digestible block, Microdata is sprinkled throughout the page to markup content on-the-fly.
Here’s the same Organization markup as above, but in Microdata format:

<p itemscope itemprop="organization" itemtype="https://schema.org/Organization">
<a href="https://ahrefs.com/" itemprop="url">
<span itemprop="name">Ahrefs</span></a>
<span itemprop="description">Ahrefs is a software company that develops online SEO tools and free educational materials for marketing professionals.</span>
Contact us at: <span itemprop="email">support@ahrefs.com</span>
</p>

As you can see, you mark up everything as it appears on the page. That’s fine for simple markup like this, but it can get very messy and near-impossible to manage for complex applications. Some SEO plugins use Microdata to generate your schema markup and do the work for you, though.

RDFa

RDFa works like Microdata. You markup HTML elements on the page, rather than providing markup in one big block like JSON-LD. It’s probably the least-used schema syntax, but you will still occasionally encounter it because it’s what Facebook’s Open Graph meta tags are based on.

Here’s how that same Organization markup looks using RFDa:

<p vocab="https://schema.org/" typeof="Organization">
<a href="https://ahrefs.com/" property="url">
<span property="name">Ahrefs</span></a> <span property="description">Ahrefs is a software company that develops online SEO tools and free educational materials for marketing professionals.</span>
Contact us at: <span property="email">support@ahrefs.com</span>
</p>

So, nothing much different from Microdata. But how do you know that all of this is a valid markup?

Testing your structured data

No sane person would deploy code without testing it first. Go to Structured Data Testing Tool, input your code snippet or URL, and see if the markup is valid.

This is what I get when I test the Microdata snippet:

Unfortunately, Google will soon deprecate this tool, and only the Rich Results Test tool will remain. As you can tell from the name, it focuses on your eligibility for rich results, but let’s hope that Google will eventually combine both tools’ functionalities. Classy Schema is a great alternative tool as well.

Before you start marking up your content

Structured data isn’t rocket science, but it takes time to get into it, figure out what to prioritize, and learn how to deploy it at scale. Many CMS’ and plugins often take care of the most basic markup out of the box, but I want to make one thing clear:

For most people, there are way more important SEO tasks than deploying schema on your website. We expand on the prioritization and implementation in our dedicated schema markup post, where you’ll learn everything you need to know about this.