schema.org - Should the blog index page be optimised for structured data as well as individual article pages? -

there many tutorials out there outline how apply structured data blog articles such one: http://edusagar.com/articles/view/72/how-to-add-microdata-to-markup-structured-data-in-your-blog

but 1 question i've had, , have never been able find answer blog index page, excerpts each blog article shown on 1 page?

how should these marked up, if @ all, using structured data?

is okay have several blogposting schemas on 1 page each blog article? because have currently.

but should applying structured data individual blog article pages, , not having on index page?

yes, that’s purpose of blog type , blogpost property.

on page listing 1 or multiple blog posts (semantically doesn’t matter if these full posts or teasers), each blog post can represented blogposting item gets referenced via blogpost property blog item.

with microdata this:

<section itemscope itemtype="http://schema.org/blog">   <article itemprop="blogpost" itemscope itemtype="http://schema.org/blogposting"></article>   <article itemprop="blogpost" itemscope itemtype="http://schema.org/blogposting"></article>   <article itemprop="blogpost" itemscope itemtype="http://schema.org/blogposting"></article> </section> 

if should can’t answered us. there no requirements involved unless have specific consumers , expectations/rules in mind (in case should consult documentation).

in general, best practice expressive possible. more structured data, better. if don’t want expressive in above example, omit blog item , list blogposting items on own:

<section>   <article itemscope itemtype="http://schema.org/blogposting"></article>   <article itemscope itemtype="http://schema.org/blogposting"></article>   <article itemscope itemtype="http://schema.org/blogposting"></article> </section> 

but blog posts don’t have relationship, , it’s not clear anymore part of same blog, , can’t give metadata blog (e.g., title).