You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm just looking over how schema.org metadata is implemented. I'm wondering if It makes more sense to implement schema.org as blocks of JSON+LD instead of as inline microdata. I don't really have an opinion one way or another, I'm just wondering about the maintainability of the code, the readability, and if someone wanted to use the apa style as a template does the microdata implementation make sense?
My understanding is that JSON+LD is google's prefered method, while microdata is bing's prefered method. (though I haven't looked at this in a while. Also I don't know what impact inserting a bunch of blocks of JSON+LD has. That is should they be in someway combined into one block or is there absolutely no reason to combine them.
I'm just looking over how schema.org metadata is implemented. I'm wondering if It makes more sense to implement schema.org as blocks of JSON+LD instead of as inline microdata. I don't really have an opinion one way or another, I'm just wondering about the maintainability of the code, the readability, and if someone wanted to use the apa style as a template does the microdata implementation make sense?
My understanding is that JSON+LD is google's prefered method, while microdata is bing's prefered method. (though I haven't looked at this in a while. Also I don't know what impact inserting a bunch of blocks of JSON+LD has. That is should they be in someway combined into one block or is there absolutely no reason to combine them.
see: https://stackoverflow.com/a/30205733
and: https://webmasters.stackexchange.com/questions/122836/can-we-add-multiple-schema-org-json-ld-code-blocks-to-the-home-page-of-a-website
and: https://stackoverflow.com/questions/30723531/best-json-ld-practices-using-multiple-script-elements
What thoughts do you have about this?
The text was updated successfully, but these errors were encountered: