+34 600 576 996
ua
Submit Request
8 May | 2021

Everything You Need To Know About Micro-Markup Schema.ORG

Olga Kyvliuk| 110| 0

Everything You Need To Know About Micro-Markup Schema.ORG

In this article, I want to tell you everything about micro-markup schema.org. We could start talking directly in the introduction about its importance in SEO promotion of the site, or we can just insert a meme with Agutin. I chose the second variant ?

WHAT IS MICRO-MARKUP?

To put it briefly and clearly, micro-markup is a single scheme for semantic HTML markup, which has been recognized by such search engines as:

  • Google;
  • Yandex;
  • Bing;
  • Yahoo!

It consists entirely of <span>, <div> tags, and the content in them.

With the help of micro-markup, you can single out individual fragments of the relevant content, what, in its turn, ensures the correct recognition of the information by search engines. In addition, it makes such a snippet more attractive in the eyes of the user.

WHAT IS SCHEMA.ORG?

Schema.org is one of the most popular dictionaries in the world, which, like other dictionaries, consists of properties and sets of classes.

Schema is used to form an extended snippet and increase the relevance of the content.

As an example, this markup describes the page with the movie “The Lord of the Rings: The Fellowship of the Ring”:

In this snippet, breadcrumbs are displayed at the top, and information about the director, the translation of the film, its quality, which lists it is included in, as well as links to the next part of the film and the actors is displayed at the bottom. Is it convenient? Definitely yes.

PRACTICE

In order to mark up the data yourself, you need to visit the official website schema.org, go to the “Schemas” section, select the necessary entity, decide what properties we will specify and start, in fact, gather the code.

ENTITY TYPES

At the moment, the number of entities that Google supports exceeds 50. The most popular ones are:

It is impossible to pass by without mentioning three new types of entities:

  • HowTo — it is the best for use for pages with step-by-step instructions.
  • FAQ– it is good for pages with a question and an answer on a specific topic.
  • Q&A — it is used for pages where the questions are answered by the users themselves.

MICRO-MARKUP FAQ

For adequate display of this entity, the page shall meet the certain criteria:

  1. The content on the page should contain a list of questions and, accordingly, answers to them.
  2. The content that is marked up with this micro-markup shall be available for users on the home page.
  3. The content must be informative, without any advertising.
  4. And, of course, the content should not contain any hatred, materials with sexual content, propaganda of violence, etc. (anything that Google does not accept)

The FAQ markup works well with such markups as Product and LocalBusiness.

HOWTO MICRO-MARKUP

And again, we shall start with the requirements:

  1. Each stage of actions must include all the content of a similar stage from the page (one stage from the page cannot be divided into several stages).
  2. No advertising.

The text of the stage itself is not clickable, however, by embedding of the links in the structured data, an anchor can be attached to each step, which will lead to the page with this subsection.

Example of micro-markup in the search results:

(By the way, the tips in the image are perfectly suitable for the question “How to get to fall in love a search engine with”)

Q&A MICRO-MARKUP

The difference between this entity and the FAQ micro-markup is that it is intended for a single question and multiple answers to it by users, while in the FAQ, the questions and the answers are already written in the content itself.

This is one of the main requirements for this markup, but you should not forget about the standard requirements (absence of advertising content and absence of prohibited themes).

Thus, this micro-markup shows itself the best on the pages of forums and technical support.

Do not forget that when using the above mentioned entities, each user can find the answer to his or her question without visiting your site.

SYNTAX

For markup Schema.org the following syntaxes can be used:

  • JSON-LD;
  • microformats;
  • microdata;

Microformats are a limited and outdated syntax, thus, we will not consider it, as well as RDFa, which is rarely used anywhere (usually in Yandex).

MICRODATA

This syntax is used quite often, its implementation on the page is a time-consuming process due to the fact that it must be written manually.

This syntax consists of content, properties, and attributes, each of which has its own tags:

  • itemscope – describes each block, allows you to describe information at the entity level;
  • itemtype – required to specify the entity type;
  • itemprop – it is used to specify additional properties.

Example of markup:

JSON-LD

It should be at once noted that this markup is preferred for the Google search engine.

Here’s what it looks like in its basic form:

After inserting the micro-markup code into the framework, which consists of the same values, properties, and entities, we will get the following code:

WHAT IS THE EASIEST WAY TO MAKE JSON-LD MARKUP?

Of course, you can do the markup manually, but you will quickly give up this idea after learning that there are generators for JSON-LD.

Here are several of the most popular ones:

  • com – a paid tool with a trial period of 14 days, it supports all entities Schema.org;
  • com – a free service that supports 6 entities (Local Business, Website, Person, Organization, Product, Event);
  • com — it is also a free service that supports 13 entities (in addition to creation of markup, this platform has a number of useful tools, I advise you to have a look at it).

MARKUP VALIDATION

If you create markup using a generator or manually, you should always check its validity before loading the code. Validators from search engines can help you with this:

  • Extended data check from Google
  • The micro markup validator from Yandex

INSERT THE MICRO MARKUP ON THE PAGE

After we have checked the code for validation, and there are no problems with it, we insert it on the required page between the <head></head> tag.

IMPLEMENTING MICRO MARKUP WITHOUT USING CODE

If you don’t want to spend a lot of time selecting, writing, and implementing micro-markup, you can use a tool from Google called Data Marker.

Using this option you will need to:

  1. Click on the link at the top, select or confirm your resource in Google Search Console.
  2. Indicate the URL of a similar page on the site, for example, the product page in the online store.
  3. Select the type of information and click on the “Start selection” button.
  4. After that, the page you selected will load. On the right, you will see the list of properties available for the entity you selected.
  5. Highlight the desired line and select the desired property in the appeared window. Thus, mark up all the necessary elements and click the button “Done”.
  6. After that, you will be asked to select a group of similar pages that the system has created or create your own. After that, click on the “Create a group of pages” button.
  7. As a result, you will be asked to check the correctness of the markup. Click “Publish”, and if you have any errors, correct them.

INSTEAD OF CONCLUSIONS

Micro-markup Schema.org is a cool and necessary tool that is not so difficult to implement, in particular, using special tools and services. Thus, be sure to insert it on your site if you still don’t have it.

I want to thank you for reading my article to the end, and I hope that it was useful for you.

08 May 2021| Olga Kyvliuk| 110| 0

ARE YOU READY TO IMPROVE YOUR PROJECT WITH #UAATEAM?

We will be happy to discuss your project, along with your main goals and objectives. You can schedule a meeting with one of our managers.

Open->
to new

Start working with #UAATEAM

  • United States+1
  • 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
  • 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
  • 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
  • Macedonia (FYROM) (Македонија)+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
  • Swaziland+268
  • 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
Select a Service:
Please fill in all required form fields