{"id":52100,"date":"2019-08-29T12:55:27","date_gmt":"2019-08-29T10:55:27","guid":{"rendered":"https:\/\/www.humanlevel.com\/sin-categorizar\/datos-estructurados-equivalentes-a-etiquetas-semanticas-de-html5.html"},"modified":"2023-10-11T09:27:18","modified_gmt":"2023-10-11T07:27:18","slug":"structured-data-equivalent-to-html5-semantic-tags","status":"publish","type":"post","link":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/structured-data-equivalent-to-html5-semantic-tags","title":{"rendered":"Structured data equivalent to HTML5 semantic tags"},"content":{"rendered":"

\"Structured
\nThe fact that there is structured data in schema.org<\/a><\/strong> that is equivalent<\/strong> or almost equivalent to HTML5 semantic tags<\/strong>, makes one suspect that this information<\/strong> may be important<\/strong> for Google’s spider (remember that schema.org is partly created by them).<\/p>\n

It is not known for certain if Google takes into account<\/strong> this type of structured data<\/a> and semantic tags in5<\/strong>in which case the effect can only be positive, since would allow the spider to know how the pages are organized and how they are <\/strong>answer several questions<\/strong> you need to resolve in order to correctly index the contents.<\/p>\n

Questions such as: “How do I separate the header and footer from the main content?”, “Is there content that is not part of the main content but only transversal to it?” or “Which groups of links serve to navigate between several pages and are not simply a list of links on a specific page?”.<\/p>\n

In short, it allows us to better identify the main content<\/strong> of the pages, which is the one that should be positioned and stand out<\/strong> above the rest of the content of each of our pages.<\/p>\n

Marking this information with HTML5 semantic tags and at the same time with their equivalent structured data may seem redundant<\/strong>, but as we do not know to what extent Google takes into account one and the other, we recommend implementing both<\/strong>.<\/p>\n\n

What are the structured data types equivalent to HTML5 semantic tags?<\/h2>\n

The tags <header><\/em> and <footer><\/em><\/strong>, are used to mark the header and footer of any root section or content section element in HTML5. When used, the most important <\/strong>ones are those that are placed as direct daughters of the root section element <body>, <\/em>without intermediate content section elements (<nav><\/em>, <article><\/em>, <section><\/em> y <aside><\/em>), since they indicate that it is the header and main footer that is repeated throughout all pages of our site<\/strong>.<\/p>\n

Interestingly, there are the structured data types https:\/\/schema.org\/WPHeader<\/strong><\/em> and http:\/\/schema.org\/WPFooter<\/strong><\/em> which equivalently represent the header and footer of the website<\/strong>. It would not be correct to use this type of structured data within tags. <header><\/em> y <footer> <\/em>that were, in turn, within a content section element since they were, in turn, within a content section element since they were, in turn, within a content section element since they were, in turn, within a content section element because this structured data type is equivalent only for the main <header> and <footer> of the page<\/strong>.<\/p>\n

Similarly, we can use the structured data https:\/\/schema.org\/SiteNavigationElement<\/strong><\/em> for all elements <nav><\/em>, but the only really important one is the one containing the main menu of the page<\/strong>, although we could also mark the footer links. For breadcrumbs it is better to use<\/strong> the typehttps:\/\/schema.org\/BreadcrumbList<\/strong> while paginators Google currently detects them without even specifying which is the next and previous page, so it is not necessary to apply it to this case either.
\nFor the <aside> <\/em><\/strong>tag, used for any type of content transversal to the main content<\/strong> (whether it is in a sidebar or not), we have the type https:\/\/schema.org\/WPSideBar<\/strong><\/em>. On the other hand, if the aside element contains only ads<\/strong>, the correct thing to do would be to use the type https:\/\/schema.org\/WPAdBlock <\/strong><\/em>instead.<\/p>\n

For <body> <\/em><\/strong>we have the data type http:\/\/schema.org\/WebPage<\/strong><\/em>. Marking the body of the document seems not very useful<\/strong>, but there are structured types derived from it with which we can specify what type of page it is<\/strong>. For example a FAQ(https:\/\/schema.org\/FAQPage)<\/em>, a contact page (https:\/\/schema.org\/ContactPage)<\/em> or an “About” (https:\/\/schema.org\/AboutPage)<\/em>, etc.<\/p>\n

But most importantly, the https:\/\/schema.org\/WebPage<\/em><\/strong> type has several properties that mimic the meaning of the <main> tag<\/strong>, useful for marking the main content of the page<\/strong>.<\/p>\n

The structured data properties equivalent to the tag <main><\/em>, are:<\/p>\n