Category Archives: Microdata

Why Rich Snippets Will Become a Much More Challenging Feature in the Future

Many Web developers and SEO experts are interested in markup because they want to trigger Google Rich Snippets, i.e. the augmentation of search results by stars for ratings, price and inventory level information and more. This is a valid interest, and while we still lack quantitative evidence, it is pretty obvious that additional information (like the price of a product), in particular positive signals (five-star ratings or availability on stock) can increase the likelihood of a click.

Note that this will have multiple effects for search engine performance of a site:

First of all, it will lead to more traffic to your site, if people are more likely to click on on a result with Rich Snippet features than on others. This could either strengthen the appeal of the already prominent results on rank 1 – 3, or as well bring back into the game the otherwise unfortunate lower ranks in the results. For instance, if a result on rank 7 is the only one with Rich Snippet features, that one could become more attractive for search engine users than a result on that rank without any special appearance.

Second, Rich Snippets could reenforce the already good reputation of high-ranked sites. If Rich Snippets make visitors find faster what they need and direct them to the best match, all signals that measure user satisfaction with Google’s ranking will send positive feedback to the ranking ecosystem.

Third, Rich Snippets can send more qualified traffic to your site, because search engine users make a more informed decision on whether to visit your site.

So far, things are simple and positive. If you add markup properly and if your remaining SEO strategies are white-hat and fair, chances are high that you get Rich Snippets for a substantial subset of your pages.

But what will happen in the future? Well, be prepared that Rich Snippets will turn from something that you “control” to something that will be highly dynamic. Do not take it for granted that, in the future, Google will show Rich Snippets for all of your deep links to all visitors and queries alike, and that Google would activate all Rich Snippet features (e.g. price, inventory level, ratings, reviews, …) in the same manner.

Instead, I expect that the more structured data we find in Web sites, the more will Google selectively use Rich Snippets and future similar features to highlight small, significant details in search results. Same as with a text-marker, you do not highlight every single word even in the best of books, but only those words or paragraphs that matter the most. There is simply no gain for the user in showing fully-fledged Rich Snippets for ten of ten relevant search results.

So what will Google do? Here is my opinion:

First, they will scientifically monitor the ideal (from a user’s perspective) number of results with Rich Snippets (I guess it will be between three and four of ten items in the results).

Second, they will try to understand which pieces of information will benefit most from highlighting with Rich Snippets. For instance, if only two of ten sites indicate availability of an item, that will be more useful to show in a Rich Snippet as compared to a list of results with all or none showing positive inventory.

Third, I suspect that Google will use Rich Snippets to highlight diversity in the search results. Even as of today, it is a known topic in recommender systems research that the controlled inclusion of variety (e.g. a few less matching items) can improve user satisfaction. A typical example is a query where the search engine is uncertain about the exact meaning of the query (the “query intent”). So we can assume that Google includes a bit of less relevant, slightly off-topic results in a search even as of now, and Rich Snippets could be used to highlight this variety. Take, for example, in a list of products the only one with a price grossly higher than the others (e.g. the only professional camera in a list of amateur cameras). Google could turn on price information just for this one to point you to this more expensive item on rank 7.

I think we should understand that Rich Snippets and structured data markup are just one of many means for improving the human user experience in search, and I bet Google will use Rich Snippets and future visual features very cleverly for improving the interface between human minds and information on the Web.

This does not mean that or Rich Snippets are overrated. Quite to the contrary, they fundamentally transform how companies communicate with target audiences about their products and services. I just want you to be prepared that an effective online strategy for using structured markup does not end at asking a junior Web developer “to add a few elements in Microdata syntax.”. The whole infrastructure of digital marketing is changing.


Best wishes

Martin Hepp

Semantic SEO: What is the difference between and Microdata?

Often, developers being new to and the usage of semantic SEO techniques are confused about the relationship between and Microdata, Microformats, RDFa, GoodRelations, and other standards.

Here is a quick explanation that I have been given so often that I assume it may be useful for others:

When you expose structured data from within Web content by adding extra markup to HTML content, you have essentially two components:

1. A vocabulary (also known as data schema, ontology, data dictionary, depending on the background of the people you speak to): This provides global identifiers for types of things (“Product”, “Car”, “Restaurant” – often called “classes” or “types”) and for properties (e.g. “screen size”, “weight” – often called properties or attributes)

2. A syntax for publishing the data within Web pages in HTML. The syntax is the convention for the actual characters used to publish a piece of data. Relevant syntaxes in here are RDFa, Microdata, and recently JSON/JSON-LD.

Popular vocabularies on the Web are, GoodRelations, FOAF, SIOC, and a few others.

At Web scale, the absolutely dominant vocabulary for mainstream search engines is GoodRelations is a special case, since 99% of the GoodRelations vocabulary are now integrated in, so you do not have to choose between the two. In other words, is now a new namespace for using GoodRelations. Additional vocabularies may have relevance on the long tail and can typically be used in addition to with no negative effect. Once they will have gained sufficient popularity, search engines may care.

Now, you can use the same vocabulary in multiple syntaxes. For instance, you can publish in RDFa or Microdata or JSON/JSON-LD. The most appropriate syntax depends on the purpose and on the target applications of your data. In Web content, Microdata and RDFa should be equally well supported by search engines in theory. However, actual support varies.

As of now, I would recommend the following:

1. Microdata syntax for RDFa works, but not all structural variants of the same data will be understood by search engines and you need to be a real expert to find out which ones work and which ones don’t.

2. RDFa for GoodRelations in the original namespace, since for historic reasons, search engines know well how to process it.

3. JSON-LD for in eMails and other upcoming scenarios, see also

Microformats are a special case, since they combine syntax and vocabulary. For very simple data structures, this works well, and Microformats are widely understood by search engines. It is just my personal opinion, and I am sure advocates of Microformats will see things differently, but in the light of and generic syntaxes like Microdata, RDFa, and JSON-LD, Microformats will be limited to very basic usages, and likely fade out.

So in a nutshell, in Microdata is currently the most widely understood and recommended variant. in RDFa and in particular JSON-LD may become more important in the future, but you will have to monitor closely to which degree search engines can actually process data in those syntaxes.

JSON-LD: Finally, Google Honors Invisible Data for SEO

For quite a while, I have been arguing that RDFa as a syntax for structured data in Web content is problematic when it comes to exposing more granular data than just a few property names. While many advocates of RDFa stressed that reusing the exact same visible elements for structured data markup, as in this example

<div property="vcard:tel">+49-89-1234-0</div> 

was beneficial because it reduces redundancy, it also raises complexity for developers, since you violate the principle of “separation of concerns” – you have to align a given HTML tree structure with a given data structure, dictated by the vocabulary, like or GoodRelations.

As a consequence, I once developed and promoted the “RDFa in Snippets Style” approach, where the RDFa markup would reside in blocks of invisible <div> or <span> elements, like this:

<!-- Content for humans --> 
<!-- RDFa rich meta-data --> 
<div property="vcard:tel" content="+49-89-1234-0"/> 

This has been a big success – most of the GoodRelations extensions for shop software, running on at least 20,000 Web shops globally, use that approach and get their content honored by Google.

Now, one caveat has always been that Google indicated that invisible markup, i.e. RDFa elements that do not reuse visible content, would not be honored. The likely rationale for that guideline was that

  1. invisible markup invites spammers that try to manipulate the search engine,
  2. a link to human-readable content allows to combine the structured data and the textual content for information extraction heuristics, and
  3. the data quality is likely higher for visible content (since humans will complain otherwise).

Now, in silence, RDFa in “Snippet Style” (and similar patterns in Microdata) have for long been accepted by Google, as long as other quality indicators for the site were positive. But there was always a doubt, which was bad, since the development effort for weaving in advanced data markup in RDFa or Microdata syntax into HTML templates in a form that combined visible content elements with data markup was, in my experience, 5 – 10 times higher as compared to using RDFa in “Snippet Style”.

The bigs news is that this uncertainty is going away, since Google now openly moves to accepting data markup in JSON-LD syntax not tied to visual elements.

Of course, this is just a first signal, but I personally think that in the future, we will see JSON-LD in script elements for all advanced data markup, and RDFa and Microdata only for the very simple use-cases.

That is a good sign towards a broader use of data markup for e-commerce, for sure.