If all you care about is SEO then do whatever Google says to do this year and you're fine. Today that's JSON-LD, tomorrow it's ???? I need to update this chart for 2020 but as we see, history keeps repeating itself. aaronparecki.com/2016/12/17/…
2
2
2
Unless I'm missing something, this chart is lacking 2017, 2018, 2019, as well as 2020. Google is strongly recommended JSON-LD usage today, and has been since 2016-ish. And there are a number of rich snippets that _only_ work as JSON-LD. developers.google.com/search…
1
Yes, read the linked post, it's from 2016
1
This implies schema.org is invented by Google; it isn't. "Since April 2015, the W3C Schema.org Community Group is the main forum for schema collaboration, and provides the public-schemaorg@w3.org mailing list for discussions." schema.org/docs/about.html
1
Literally on schema.org... "Founded by Google, Microsoft, Yahoo and Yandex..." and look at the names on their about page too. Even if it's not created exclusively by them (which I never said), that looks an awful lot like an oligopoly to me anyway.
1
Correct, but spun off as a neutral standard, as has happened for many of the technologies that we're using today. Regardless, Google is consuming only JSON-LD going forward for some types of structured data, so it'll end up being a choice you have to make at some point.
2
Would you like to make a Long Now bet on whether Google will parse your preferred syntax in 10 years, versus HTML?
1
I would. Book it! In 2030, we'll assess the state of microformats vs. JSON-LD. $100 sounds fair!
1
OK. I'll have a look - Your site is at the beginning of microformats support: indiewebify.me/validate-rel-…
2
Ironically, I have no microformat code on the site. It's pulling that from the JSON-LD "sameAs" URLs, I presume.
2
Microformats != Microdata microformats.io tbh I also can't stand the itemprop= itemscope= stuff, it's so messy. That's why I like the Microformats approach instead.

Jan 22, 2020 · 5:17 PM UTC