+1 Gains Respect and What You Should Know About Microdata for SEO

 

Back in March, Google officially started rolling out the +1 Button in its search results, allowing users to vote up the pages they found most useful. Two months later, on June 1, it launched a widget that lets website owners integrate the button into their pages, just like they do with Facebook’s ‘Like’ and Twitter’s ‘Tweet’ buttons. See more.

The +1 button and the Google+ project are both about making it easier to connect with the people you trust online. For the +1 button, that means bringing advice from trusted friends and contacts right into Google search, letting the users who love your web content recommend it at the moment of decision. But when you’re managing a website, it’s usually not real until you can measure it. So we’re happy to say we’ve got one more announcement to make — today we’re releasing reports that show you the value +1 buttons bring to your site. First, +1 metrics in Google Webmaster Tools can show you how the +1 button affects the traffic coming to your pages. See more here.
Microdata are HTML5 specifications enabling webmasters to embed semantic data inside the code of existing web pages. Schema.org, which employs microdata, is an organized markup with common vocabulary. This enables webmasters to efficiently place machine-readable data in their HTML5 code. Aaron Bradley did a fantastic write-up on schema.org and the implications for SEO and beyond. See more from Clickz and more from SEOSkeptic.com.
Affluent consumers are tapping into mobile and online tools to support purchase decisions more frequently than the general population, research indicates. This gives marketers more opportunities to reach them through newer digital channels. Mobile Video.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>