And, from a "why use JSON-LD rather than [fill in name of syntax here]" see yoast.com/yoast-seo-11-0/
1
2
3/2 Additionally, it's much easier to *generate* JSON-LD because it isn't tied to the HTML structure.
So the tooling is much better in terms of tools that can dynamically or statically generate the JSON-LD for you, based on your inputs.
Doing that with microformats is not easy
1
1
if you're generating HTML from templates anyway, generating microformats means adding a few classes (and a parsing testcase to your build). Not maintaining another sidefile in an entirely different structure with different syntax.
2
1
I know that you're a huge microformats fan Kevin, but among other things: 1) they're not remotely expressive enough for contemporary structured data requirements; 2) they're HTML-bound, meaning you can't provide data like this developers.google.com/action…
3
1
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
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.
Jan 22, 2020 · 4:54 PM UTC
1