Schema Markup: A to Z Guide to Structured Data for SEO

Schema markup is what powers the rich snippets and a number of SERP features that we’re seeing more and more of in today’s major search engines. It’s equally beneficial for the big players and small businesses alike. In this guide we share the nine Schema markup types with the most SEO value and show you how to add them to your site.

The best part? This guide is useful both for beginners and for those who already have some programming skills.

What is Schema markup and why is it important?

Schema markup, also known as Schema, is a semantic vocabulary of standardized tags that are added to a page’s HTML. These tags help a search engine understand the content and context of your web page and represent it better in search results. Basically, Schema is just the language used to represent data. The actual data is called structured data.

If what you just read left you confused, here’s an example. Take a look at this simple structured data that we used in our latest article.

<script type="application/ld+json">
{
  "@context" : "http://schema.org",
  "@type" : "Article",
  "headline" : "How to Make an SEO-Friendly Website Redesign",
  "author" : {
    "@type" : "Person",
    "name" : "Zlata Verzhbitskaia"
  },
  "datePublished" : "2022-11-08",
  "image" : "https://cdn1.link-assistant.com/upload/news/posts/169/1667572689.png"
}
</script>

How does structured data work?

This piece of code describes the main entities found on the page in a format that is easily digestible by Google and other search engines. So, once this page is crawled, Google can tell what the article’s name is, who the author is, and when it was published.

Besides improving how we communicate information to major search engines, adding structured data to a webpage brings a number of benefits that can directly impact your organic traffic and appearance in search. First, you can get a rich snippet with complete information about your product, for example.

You can also occupy an coveted position zero for certain types of search queries, thus gaining additional traffic from various search engines.

And the main benefit of structured data is that it helps you build entities and relationships between them. This is especially important in light of the upcoming Google MUM update. The list could go on, and I’ll touch on other benefits for each schema type later in this guide.

How to implement structured data on your site?

When it comes to implementing structured data, you have two options:

• Markup generators (good for beginners)
• Manual markup

Markup generators

Schema markup generators allow you to implement structured data without any coding expertise.

In most cases, SEOs and website owners (and we are no exception) use
Google’s Structured Data Markup Helper. It offers 12 schemas, which is more than enough for beginners.

How do structured data generators work?

The process is really simple: you just need to choose the type of structured data and mark all the necessary elements on your web page.

Once you are done specifying the elements, the tool will generate a piece of code that you can add to your page.

There are also other structured data generators that offer more Schema types:

• Hall Analysis Schema Markup Generator
• Merkle Schema Markup Generator
• Schema Builder Extension for Chrome

Manual markup

In case you can’t find the schema type you need in structured data generators, you can add it manually. The code looks scary at first, but it’s actually quite simple, and you’ll only need to change a few values. So you can try manually marking up structured data even if you don’t have coding skills.

Here are the two ways you can implement manual markup: with JSON-LD or Microdata.

JSON-LD

JSON-LD is a more popular method for manually adding structured data to a web page. Moreover, this method is recommended by Google. It is also easier to understand and distribute than microdata or other outdated formats like RDF or microformats.

You’ve already seen a piece of simple JSON-LD code at the beginning of this guide. In case you skipped it, here it is again:
<script type="application/ld+json">
{
"@context" : "http://schema.org",
"@type" : "Article",
"headline" : "How to Make an SEO-Friendly Website Redesign",
"author" : {
"@type" : "Person",
"name" : "Zlata Verzhbitskaia"
},
"datePublished" : "2022-11-08",
"image" : "https://cdn1.link-assistant.com/upload/news/posts/169/1667572689.png"
}
</script>

The above script is added to the
section of the page and communicates the following information to a search engine:

• @context.
  Specifies the vocabulary (schema.org).
• @type.
  Specifies the type of schema used.
• name.
  Tell a search engine what the name of the article is.
• author. Tell search engines who wrote the article.
• datePublished. Specify the date the article was published.
• Image. Link to the article’s cover image.

If you look closer, you will see that this JSON-LD code has a very simple structure. First comes the Schema type, and then followed by defined properties ( headline, author, datePublished ) and their values ( Article, Zlata Verzhbitskaia ).

This code snippet can be populated with more properties if needed. For example, if the article was updated, I can add the dateModified property right after the datePublished property. I can also combine multiple Schema types within a single piece of code. In the previous example, we combined structured data for Article and Person .

If I decide to use the same schema type for another article, I will simply take this code example and replace the values with the relevant ones.

If I need to use another schema, I will update the @type property with the required schema type and add new properties specific to this markup.

Important note:

The information embedded in the JSON-LD code must be present on your web page and visible to users. To avoid penalties from search engines, never add content parts that cannot be found on a page itself.

Microdata

Microdata are less popular than JSON-LD and are used in rare cases when you target a search engine, for example, Yandex, which simply does not support JSON-LD.

Unlike JSON-LD, with microdata, you cannot add a single piece of code to the of your page. Instead, you will need to mark up each element within your HTML code separately.

Here’s how it looks:

<div itemscope itemtype="http://schema.org/Article">
<h1 itemprop="headline">How to Make an SEO-Friendly Website Redesign</h1>
<span itemprop="datePublished">November 8, 2022</span>
</div>

In this snippet, we have three new values ( itemscope, itemtype, and itemprop ) in addition to those we saw in the JSON-LD code earlier in this guide.

Here’s what these values represent:

• itemscope. Creates an element and indicates that the rest of the element describes it.
• item type. Specifies the vocabulary and schema type ( Article ).
• itemprop. Specifies the property ( headline , datePublished ).

How to organize your markup workflow?

As we get closer to the practical part of this guide, it’s worth establishing the optimal workflow. Regardless of the schema type or implementation method you choose, the typical workflow will remain the same and look something like this:

Step 1. Choose the schema type and find the pages on your site where it can be applied.

Step 2. Create your markup. Generate the code with the help of tools or write it manually.

Step 3. Validate your markup. Before adding the code to your site’s pages, always validate it using Google Rich Results Test or Schema Markup Validator. This will help ensure that all search engines read your structured data correctly.

Step 4. Deploy the markup on your site. Passed the validation step? Now you can safely add the markup to your site.

Common structured data errors to avoid

Human error is always possible, but when it comes to structured data, things need to be double-checked at all times.

If your structured data markup contains errors, the least you can expect is that it simply won’t work as intended. In some cases, adding Schema markup that doesn’t fit the context may result in a penalty from Google.

To avoid this, here is a short list of things not to do on structured data:

Do not skip validating structured data

A single missed symbol in the javascript code can render the entire piece of markup obsolete. This is why it is a MUST to validate the code before adding it to your site. For these purposes, use Google Rich Results Test or Schema Markup Validator . The latter has extended functionality and will not only show you the structure of your markup but will also highlight any errors if found.

Do not add structured data to non-existent content

JSON-LD code can be added to any page on your website. But what you tell Google in the markup should also correspond to the content of the page.

If Google detects such misuse of markup, it will first issue a warning in Search Console, and if the problem persists, manual action will be taken.

Do not add page-specific structured data site-wide

One example of such markup misuse is when the review markup for an item is scaled to the entire category. This can also lead to a penalty from Google.

Do not violate Google’s guidelines

Be sure to check and carefully follow Google’s general guidelines for structured data . This will help you avoid any issues in the future.

How to monitor structured data improvements? 

To check the structured data improvements on your website over time, log in to Google Search Console , navigate to Enhancements , and check the health status of the various types of structured data markup applied to your pages.

In case errors are detected, you will be provided with the exact locations of the errors and some guidance on how to fix them.

Source Link Assistant

Pubblicato in Digital Marketing, SEO