Schema.org microdata markups for Blogger blogs! Passes +Snippet and Rich Snippets Testing Tool!

In my last post, I have shown you some examples of Schema.org microdata markups that bloggers can apply on their Blogger-powered blogs to give Google +Snippet the right kind of information about our blogs and blog posts before they are shared with other people in Google+.


I don’t know about you but I’m very particular about how tools such as +Snippet grab information about our blogs and blog posts. I want to see everything looks good for other people because first appearance matters the most for most people. It would be bad if your blog’s first appearance fails you over and over again in Google+!


Alright, before I show you a few more examples of Schema.org microdata markups that you can apply on your Blogger-powered blog, let’s take a closer look at Google +Snippet.


Things you should know before you markup your blog with Schema.org microdata


I think you all know by now that Google strongly recommend bloggers and webmasters to ‘use’ +Snippet with Schema.org microdata markups. Now, I want you to focus on what Google had said:


If the page is annotated with schema.org microdata, the +Snippet will use the name, image, and description properties found on any schema.org type.

I don’t have any problems with Schema.org’s name and image properties. It’s the use of Schema.org’s description property that perplexes me the most. I have gone through Schema.org’s documentations and is able to conclude that the description property is more or less similar with HTML meta description tag property. In another word, the property should be unique!


Now, you tell me. How in the world are we going to make descriptions of our blog posts unique?


Blogger certainly didn’t give us any tools to make unique descriptions of our blog posts. There is a trick (as shown in my last post) that you can use to do that but I don’t like the idea of making each meta tag description manually, one by one.


What I’m trying to tell you right now is that we could not exactly give Schema.org microdata description property the correct value. The examples that I’m going to show you tomorrow would only grab snippets of our blog posts and tag them as descriptions for +Snippet.


You should also know that you cannot put Schema.org microdata markups in Blogger widget and section tags. Examples as shown down below:


<b:section class='main' id='main' showaddelement='no'>
<b:widget id='Blog1' locked='true' title='Blog Posts' type='Blog'>

For some unknown reasons, Blogger completely purge markups from such tags after you have saved your Blogger template. So please don’t waste your time trying.


As for today, let’s see some more examples of Schema.org microdata markups that you can apply on your Blogger blog to give Google +Snippet that much needed assistance in ‘understanding’ your blog better.


Schema.org microdata markups that can help Google +Snippet grab the actual description of your blog


First and foremost, you have to tell not only +Snippet but also search engines that your blog’s home page URL points to a blog. Right after <body>, markup the first HTML tag with [itemscope='' itemtype='http://schema.org/Blog']. You also have to wrap your chosen HTML tag with some Blogger conditional tags. An example is shown down below:


<b:if cond='data:blog.url == data:blog.homepageUrl'>
<div id='tab' itemscope='' itemtype='http://schema.org/Blog'>
</div>
<b:else/>
<div id='tab'>
</div>
</b:if>

Now you may go and look for <data:description/> in your Blogger template. Once found, wrap it with an HTML span tag marked up with [itemprop='description']. You also have to wrap everything with some Blogger conditional tags, similar with the ones shown earlier. An example is shown down below:


<b:if cond='data:blog.url == data:blog.homepageUrl'>
<span itemprop='description'><data:description/></span>
<b:else/>
<span><data:description/></span>
</b:if>

Don’t forget to save your Blogger template when everything is done. The above examples will produce something similar with the following screenshot whenever people share your blog in Google+.




What’s next?


Certainly not today! Tomorrow I will show you how to markup your blog posts with Schema.org microdata so that you can achieve the following results (as shown in the following screenshot) whenever somebody shares any one of your blog posts in Google+.




Stay tuned!

Subscribe via RSS or Email:

Related Posts


9 comments:

Beben Koben said...

i'll have doing this
<body itemscope='' itemtype='http://schema.org/Blog'>
the rest all do not get it :D

homebiss said...

Beben,

OMG! Tell you what. Just give me your full Blogger template and let me tell you later when and where to put those Schema.org microdata markups. You can send it via email. You can find the link from my Google+ profile.

Melvin Corney said...

Hello HomeBiss,
I have little kwonledge of this can i also send my template to you and can you tell me where and how to place the tags so that google+ and searches grab the right content thanks in advanced
-TheEmoLab

homebiss said...

Melvin Corney,

Sure, no problem! You can send me your full Blogger template to me via Google+. Please send it via email, not message. :)

Melvin Corney said...

hey i sent it a day ago i was wondering did you get it

homebiss said...

Melvin Corney,

Yes, I got it. Will work on it later in the day.

homebiss said...

Melvin,

I have given you some Schema.org markup suggestions. Please read my latest post.

Herman Max said...

please help me, i have sent my blogger template to you. .

Yuviter Pradeska said...

thanks i like

Post a Comment

  • Commenters are encouraged to leave comments via OpenID but if you have problems in leaving one via OpenID, please refer to this excellent guide.
  • Comments that add tremendous value to the blog post will not only get approved but also will be personally tweeted (learn how!) by the blogger behind this blog, giving commenters the opportunity to get even more traffic and gain even more exposure to their sites or blogs.
  • Comments that have links in the bodies of comments will never be approved.
  • Preferably comments should be made in English but comments in other languages are also acceptable.