Update (2016) . Meanwhile, Schema.org introduced a property indicating that the element is the main / main for the page: mainEntity
( see details ). Therefore, the answer below is somewhat outdated.
If they are also blog posts, you can use BlogPosting
.
Microdata is not just for the main content of the page. However, the Schema.org dictionary currently lacks the property to mark an element as the main element of the page content (the mainContentOfPage
property mainContentOfPage
allowed only for WebPage
).
Using articleBody
for the main BlogPosting
, capable consumers should be able to infer that other BlogPosting
elements on the page (which, of course, does not have the articleBody
property), are associated only with related posts.
So it might look like this:
<div itemscope itemtype="http://schema.org/Blog"> <article itemprop="blogPost" itemscope itemtype="http://schema.org/BlogPosting"> <div itemprop="articleBody">…</div> </article> <aside> <ul> <li> <article itemprop="blogPost" itemscope itemtype="http://schema.org/BlogPosting"> <a href="/post-4" itemprop="url"><span itemprop="name">Post 4</span></a> </article> </li> <li> <article itemprop="blogPost" itemscope itemtype="http://schema.org/BlogPosting"> <a href="/post-5" itemprop="url"><span itemprop="name">Post 5</span></a> </article> </li> </ul> </aside> </div>
source share