Building the biggest knowledge graph, in layman terms an information database, of all time. That is what Google is researching at this moment. New details were presented during the annual “Knowledge Discovery in Databases (KDD) conference” in New York two weeks ago. Behind the screens of corporations like Microsoft, Facebook, Amazon and IBM are similar systems being developed. It’s a race towards the first database which archives all human knowledge.
Today Google finally came with a clear statement about HTTPS: HTTPS as a ranking signal. So what will happen in the upcoming months is that lot’s of companies are going to buy some SSL certificates and migrate their website to a new domain. Sounbds easy, but in practice this is a complicate challenge which will be different for every websites.
Never forget: there will be a temporary traffic loss from organic traffic, even when everything is properly executed. Be prepared for that, add some extra AdWords budget for example to make sure sales are not decreasing to much. The biggest risk of not doing a migration properly is traffic loss over a longer period instead of just a temporary loss.
Today my fellow SEO, Sander Tamaëla pointed out on Twitter that the popular Chrome extension Webpage Screenshot (4 million downloads according to their website) is sending all kinds of data to their servers, like the visited pages, session IDs, social connections etcetera:
Webpage Screenshot extension voor Chrome: dat ding post allerlei info naar zijn servers, oa: sessie ID’s,bezochte pagina,social connections
This made me curious, since I was aware of the possibilities of tracking people’s behaviour by browsers add-ons like toolbars and extensions but I never heard anyone about a popular Chrome extensions. I’m not that paranoia and mostly aware of what I’m doing online, but I wanted to know how Google Chrome is dealing with plugin acception and how it communicates about these permissions given once you install an extension.
There is another rich snippet which gives you the possibility to add a picture to the SERPs: the recipe snippet! All the information can be found in Google’s documentation: Recipe rich snippet documentation. An example:
So you just add two of the required mark up data from this list of four characteristics:
prepTime, cookTime, totalTime, or ingredients
This means the following code is enough to implement, just use your blog title as the Name element, use your profile photo as the Photo element and reviews can be added everywhere:
<div itemscope itemtype="http://data-vocabulary.org/Recipe" >
<h1 itemprop="name">This is my blog title</h1>
<img itemprop="photo" src="author-photo.jpg" />
<span itemprop="review" itemscope itemtype="http://data-vocabulary.org/Review-aggregate">
<span itemprop="rating">4.0</span> stars based on
<span itemprop="count">35</span> reviews
Disclaimer: this tactic is not allowed by Google, so it could harm your other rich snippets if Google decides your spamming their SERPs with irrelevant rich snippet additions. In most cases they will removed all your snippets, it will not affect your rankings.