Websites promotion & analytics

Select your language

Ask a question +38 096 558 7514

Microdata schema.org of the site

You’ve probably noticed some unique search results where stars, reviews, lists, events, prices, or stock availability are displayed, making the site’s listing stand out more than others. This happens because the website is using schema markup for structured data, sending special signals to search engines.

Schema markup is a special structured data markup used on a website for search engines.
Structured data refers to standardized page data types that can be templated and marked up, enabling search engines to generate rich snippets in search results.
A snippet is the way your website appears in search results. It can be just a title and description, or it might include additional links, prices, ratings, and other details from the page if they are marked up correctly.
The recognized standard for structured data markup is schema.org.
Schema.org is the accepted schema markup standard by all search engines. If you need schema markup, you should follow the guidelines provided by schema.org.

Why is schema markup necessary for your website?

  1. It standardizes data for search engines.
  2. It allows search engines to display additional data in the search results via the snippet.
  3. It facilitates data exchange between Google services (for example, Google Merchant Center for Google Shopping extensively uses schema markup).
  4. It enriches search results, allowing users to get more information without needing to visit various websites.

Wouldn’t you agree that these types of results save users time by providing answers without the need to visit the site?

микроразметка сайта schema org

Schema markup provides more detailed search results, often called rich snippets.

In this article, we’ll cover the basics and fundamentals of schema markup, explaining its practical use, which is often overlooked on the official schema.org site.

Methods for implementing schema markup

On schema.org, you’ll notice that schema markup can be implemented in a few different ways:

JSON-LD

This is the most favored method among developers because the markup is placed within a script and separated from the visible content. The structured data is pulled from variables, which typically don’t change if the design of the page is updated. The markup is usually stored in a block that doesn’t require frequent editing.


<script type="application/ld+json">
{
  "@context": "http://schema.org/",
  "@type": "Organization",
  "name": "Your Company Name",
  "url": "https://holostenko.ua/",
}
</script>

Microdata

This method involves embedding schema markup directly within the HTML of the page. The downside is that you must carefully manage the markup when updating the site. This method is preferred by marketers because it’s easier to verify the logic of the markup.


  <p itemscope itemprop="organization" itemtype="http://schema.org/Organization">
  <a href="http://npr.org" itemprop="url">
    <span itemprop="name">Your Company Name</span></a> has a sponsor:
        <span itemprop="sponsor" itemscope itemtype="http://schema.org/Organization">
          <a itemprop="url" href="https://holostenko.ua/">
          <span itemprop="name">Your Company Name</span></a>
        </span>.
</p>
  

RDFa

This is similar to microdata but requires that the data be visible to users.


<p vocab="http://schema.org/" typeof="Organization">
  <a href="http://npr.org" property="url">
  <span property="name">Your Company Name</span></a> has a sponsor,
  <span property="sponsor" typeof="http://schema.org/Organization">
    <a property="url" href="https://holostenko.ua/">
    <span property="name">Your Company Name</span></a>
  </span>.
</p>

Schema markup methodology

No matter which implementation method you choose, the basic methodology remains the same. You define the type of data and the object’s properties and values.

Data types

Some of the most common schema data types include:

Object properties

After defining the data type, you declare the properties and contents of the object. For example, if you're working with products, properties like price, date, name, availability, and product images are all essential.

These properties are usually defined using itemprop.

Object values

We mark the content of the object: what content will be sent to the search robot and will go into the snippet. For example, we mark the title of the article “name” and the value “Micro-markup for the site”.

Attention!

If a specific type does not have the required amount of data, then micro-markup will not work. More on that later.

Example of schema markup


<div itemscope itemtype="http://schema.org/Organization">

<meta itemprop="name" content="Your Company Name">

<meta itemprop="description" content="Company description">

<meta itemprop="image" content="https://holostenko.ua/images/logo-blue.jpg">

<meta itemprop="telephone" content="+38 (000) 000 00 00">

<meta itemprop="url" content="https://holostenko.ua/">

</div>

Note! No matter the format or method you choose, always define the data type first, followed by the properties and values.

Validating schema markup and managing display

Each search engine provides a tool for checking schema markup. Google has a Structured Data Testing Tool, which was updated in 2020.

In 2021, schema.org also launched its own validator at https://validator.schema.org/

Some key features include:

  • URL validation;
  • Code editing;
  • Debugging;
  • Previewing.
проверка микроразметки

If a preview is available, then everything is set up correctly. There are isolated cases when there are errors and as a result, the micro-markup works. This is usually the case in markup with a large amount of data, where one error can be considered insignificant.

* Additionally, we share a portal for developers specifically on micro-markup, this portal is regulated by Search Console itself.

Schema markup in Google Search Console, indexing

Once schema markup is implemented on your site, Google’s search bots will start indexing this data. If problems are detected, you will be notified via email or in the Google Search Console’s coverage section.

ошибки в микроразметке

Schema markup via Tag Manager: is it worth it?

In theory, yes, but only for basic use cases. Complex schemas, like product lists, require database parsing to extract prices, which Tag Manager can’t handle effectively. For complex elements, avoid using Tag Manager for schema markup.

Schema markup plugins and automation

Most CMS platforms, such as WordPress, OpenCart, Magento, and Joomla, offer automated schema markup plugins. However, these plugins are often only relevant when first created. Rarely are they updated, and outdated markup can cause errors.

Therefore, we recommend manual implementations and constant monitoring by SEO specialists for errors in Search Console.

Additionally, you can find the Google micro-markup wizard, which supposedly allows you to make micro-markup using a visual editor. But there is one but - in the end, the service gives out code that must be implemented into the site, which in 99% of cases does not fit with the site programming.

FAQs:

✔ Why use schema markup?

To make your site stand out with richer, more visible search results.

✔ How to implement schema markup?

Ideally, this involves technical specs and developer implementation, followed by validation from SEO specialists.

✔ What results can you expect?

Enhanced snippets, higher click-through rates, and potential improvements in organic search rankings.

Our schema markup services

In our work, schema markup is part of our SEO promotion services, helping increase click-through rates, visibility, and site rankings. We provide clear technical specs and monitor for errors. For more details, contact our agency.

If you have any questions about our services, please write how to contact you and briefly describe your business.

* Your personal data is completely protected and will not be disclosed to third parties.

Please select the best way to contact you.

  • United States+1
  • United Kingdom+44
  • Afghanistan (‫افغانستان‬‎)+93
  • Albania (Shqipëri)+355
  • Algeria (‫الجزائر‬‎)+213
  • American Samoa+1
  • Andorra+376
  • Angola+244
  • Anguilla+1
  • Antigua and Barbuda+1
  • Argentina+54
  • Armenia (Հայաստան)+374
  • Aruba+297
  • Ascension Island+247
  • Australia+61
  • Austria (Österreich)+43
  • Azerbaijan (Azərbaycan)+994
  • Bahamas+1
  • Bahrain (‫البحرين‬‎)+973
  • Bangladesh (বাংলাদেশ)+880
  • Barbados+1
  • Belarus (Беларусь)+375
  • Belgium (België)+32
  • Belize+501
  • Benin (Bénin)+229
  • Bermuda+1
  • Bhutan (འབྲུག)+975
  • Bolivia+591
  • Bosnia and Herzegovina (Босна и Херцеговина)+387
  • Botswana+267
  • Brazil (Brasil)+55
  • British Indian Ocean Territory+246
  • British Virgin Islands+1
  • Brunei+673
  • Bulgaria (България)+359
  • Burkina Faso+226
  • Burundi (Uburundi)+257
  • Cambodia (កម្ពុជា)+855
  • Cameroon (Cameroun)+237
  • Canada+1
  • Cape Verde (Kabu Verdi)+238
  • Caribbean Netherlands+599
  • Cayman Islands+1
  • Central African Republic (République centrafricaine)+236
  • Chad (Tchad)+235
  • Chile+56
  • China (中国)+86
  • Christmas Island+61
  • Cocos (Keeling) Islands+61
  • Colombia+57
  • Comoros (‫جزر القمر‬‎)+269
  • Congo (DRC) (Jamhuri ya Kidemokrasia ya Kongo)+243
  • Congo (Republic) (Congo-Brazzaville)+242
  • Cook Islands+682
  • Costa Rica+506
  • Côte d’Ivoire+225
  • Croatia (Hrvatska)+385
  • Cuba+53
  • Curaçao+599
  • Cyprus (Κύπρος)+357
  • Czech Republic (Česká republika)+420
  • Denmark (Danmark)+45
  • Djibouti+253
  • Dominica+1
  • Dominican Republic (República Dominicana)+1
  • Ecuador+593
  • Egypt (‫مصر‬‎)+20
  • El Salvador+503
  • Equatorial Guinea (Guinea Ecuatorial)+240
  • Eritrea+291
  • Estonia (Eesti)+372
  • Eswatini+268
  • Ethiopia+251
  • Falkland Islands (Islas Malvinas)+500
  • Faroe Islands (Føroyar)+298
  • Fiji+679
  • Finland (Suomi)+358
  • France+33
  • French Guiana (Guyane française)+594
  • French Polynesia (Polynésie française)+689
  • Gabon+241
  • Gambia+220
  • Georgia (საქართველო)+995
  • Germany (Deutschland)+49
  • Ghana (Gaana)+233
  • Gibraltar+350
  • Greece (Ελλάδα)+30
  • Greenland (Kalaallit Nunaat)+299
  • Grenada+1
  • Guadeloupe+590
  • Guam+1
  • Guatemala+502
  • Guernsey+44
  • Guinea (Guinée)+224
  • Guinea-Bissau (Guiné Bissau)+245
  • Guyana+592
  • Haiti+509
  • Honduras+504
  • Hong Kong (香港)+852
  • Hungary (Magyarország)+36
  • Iceland (Ísland)+354
  • India (भारत)+91
  • Indonesia+62
  • Iran (‫ایران‬‎)+98
  • Iraq (‫العراق‬‎)+964
  • Ireland+353
  • Isle of Man+44
  • Israel (‫ישראל‬‎)+972
  • Italy (Italia)+39
  • Jamaica+1
  • Japan (日本)+81
  • Jersey+44
  • Jordan (‫الأردن‬‎)+962
  • Kazakhstan (Казахстан)+7
  • Kenya+254
  • Kiribati+686
  • Kosovo+383
  • Kuwait (‫الكويت‬‎)+965
  • Kyrgyzstan (Кыргызстан)+996
  • Laos (ລາວ)+856
  • Latvia (Latvija)+371
  • Lebanon (‫لبنان‬‎)+961
  • Lesotho+266
  • Liberia+231
  • Libya (‫ليبيا‬‎)+218
  • Liechtenstein+423
  • Lithuania (Lietuva)+370
  • Luxembourg+352
  • Macau (澳門)+853
  • North Macedonia (Македонија)+389
  • Madagascar (Madagasikara)+261
  • Malawi+265
  • Malaysia+60
  • Maldives+960
  • Mali+223
  • Malta+356
  • Marshall Islands+692
  • Martinique+596
  • Mauritania (‫موريتانيا‬‎)+222
  • Mauritius (Moris)+230
  • Mayotte+262
  • Mexico (México)+52
  • Micronesia+691
  • Moldova (Republica Moldova)+373
  • Monaco+377
  • Mongolia (Монгол)+976
  • Montenegro (Crna Gora)+382
  • Montserrat+1
  • Morocco (‫المغرب‬‎)+212
  • Mozambique (Moçambique)+258
  • Myanmar (Burma) (မြန်မာ)+95
  • Namibia (Namibië)+264
  • Nauru+674
  • Nepal (नेपाल)+977
  • Netherlands (Nederland)+31
  • New Caledonia (Nouvelle-Calédonie)+687
  • New Zealand+64
  • Nicaragua+505
  • Niger (Nijar)+227
  • Nigeria+234
  • Niue+683
  • Norfolk Island+672
  • North Korea (조선 민주주의 인민 공화국)+850
  • Northern Mariana Islands+1
  • Norway (Norge)+47
  • Oman (‫عُمان‬‎)+968
  • Pakistan (‫پاکستان‬‎)+92
  • Palau+680
  • Palestine (‫فلسطين‬‎)+970
  • Panama (Panamá)+507
  • Papua New Guinea+675
  • Paraguay+595
  • Peru (Perú)+51
  • Philippines+63
  • Poland (Polska)+48
  • Portugal+351
  • Puerto Rico+1
  • Qatar (‫قطر‬‎)+974
  • Réunion (La Réunion)+262
  • Romania (România)+40
  • Russia (Россия)+7
  • Rwanda+250
  • Saint Barthélemy+590
  • Saint Helena+290
  • Saint Kitts and Nevis+1
  • Saint Lucia+1
  • Saint Martin (Saint-Martin (partie française))+590
  • Saint Pierre and Miquelon (Saint-Pierre-et-Miquelon)+508
  • Saint Vincent and the Grenadines+1
  • Samoa+685
  • San Marino+378
  • São Tomé and Príncipe (São Tomé e Príncipe)+239
  • Saudi Arabia (‫المملكة العربية السعودية‬‎)+966
  • Senegal (Sénégal)+221
  • Serbia (Србија)+381
  • Seychelles+248
  • Sierra Leone+232
  • Singapore+65
  • Sint Maarten+1
  • Slovakia (Slovensko)+421
  • Slovenia (Slovenija)+386
  • Solomon Islands+677
  • Somalia (Soomaaliya)+252
  • South Africa+27
  • South Korea (대한민국)+82
  • South Sudan (‫جنوب السودان‬‎)+211
  • Spain (España)+34
  • Sri Lanka (ශ්‍රී ලංකාව)+94
  • Sudan (‫السودان‬‎)+249
  • Suriname+597
  • Svalbard and Jan Mayen+47
  • Sweden (Sverige)+46
  • Switzerland (Schweiz)+41
  • Syria (‫سوريا‬‎)+963
  • Taiwan (台灣)+886
  • Tajikistan+992
  • Tanzania+255
  • Thailand (ไทย)+66
  • Timor-Leste+670
  • Togo+228
  • Tokelau+690
  • Tonga+676
  • Trinidad and Tobago+1
  • Tunisia (‫تونس‬‎)+216
  • Turkey (Türkiye)+90
  • Turkmenistan+993
  • Turks and Caicos Islands+1
  • Tuvalu+688
  • U.S. Virgin Islands+1
  • Uganda+256
  • Ukraine (Україна)+380
  • United Arab Emirates (‫الإمارات العربية المتحدة‬‎)+971
  • United Kingdom+44
  • United States+1
  • Uruguay+598
  • Uzbekistan (Oʻzbekiston)+998
  • Vanuatu+678
  • Vatican City (Città del Vaticano)+39
  • Venezuela+58
  • Vietnam (Việt Nam)+84
  • Wallis and Futuna (Wallis-et-Futuna)+681
  • Western Sahara (‫الصحراء الغربية‬‎)+212
  • Yemen (‫اليمن‬‎)+967
  • Zambia+260
  • Zimbabwe+263
  • Åland Islands+358
Thanks! Your message has been sent.
Sending failed. Please fix the errors and try again.