It is a disgusting mess; a far better way to do it is to use JSON-LD.
Intertwining the properties with HTML markup sounds like a nice idea, but in practice it ends up being really difficult to work with.
- nystudio107.com/blog/json-ld…
- nystudio107.com/blog/annotat…
2
4
It's not JavaScript, it's JSON-LD—literally it's just JSON Linked Data, there's nothing executable about it
It's significantly nicer to work with than the old intermingling of HTML & itemprop stuff. I've done both for many years, and by far prefer it separated out into JSON-LD
1
3
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/…
Jan 22, 2020 · 4:35 PM UTC
2
2
2
