10

I have both Micro Data and JSON-LD on my e-commerce product pages, describing the same thing (products in my case). For reasons beyond the scope of this question, I cannot remove either of the two formats. I am wondering:

  1. Is this a problem for Google? The structured data testing tool does display two items (products) instead of one.

  2. If one property, let's say the name of the product, is slightly different between the two formats, would any of the two formats, for example, JSON-LD take priority?

Milen Kovachev
  • 5,111
  • 6
  • 41
  • 58
  • 1
    Does this answer your question? [Google does not correctly merge microdata and json+ld in the same page using same URI id](https://stackoverflow.com/questions/33756091/google-does-not-correctly-merge-microdata-and-jsonld-in-the-same-page-using-sam) – David Riccitelli Jan 17 '20 at 07:11

1 Answers1

13

The problem is that a consumer would think that different things are described (or more accurately: the consumer wouldn’t know if the things are the same or not).

There is a way to prevent this¹: give each thing a URI, and in case the things are the same, the same URI.

This can be done with @id in JSON-LD, and with itemid in Microdata.

So a simple case could be:

<!-- markup on the product page, 
     so the fragment "#this" results in an absolute URI like 
     "http://example.com/products/foo#this" -->

<!-- JSON-LD -->
<script type="application/ld+json">
{
  "@context": "http://schema.org",
  "@type": "Product",
  "@id": "#this",
  "name": "Foo"
}
</script>

<!-- Microdata -->    
<article itemscope itemtype="http://schema.org/Product" itemid="#this">
  <h1 itemprop="name">Foo</h1>
</article>

In case a property like name has different values, the obvious way a consumer could handle this is to give the thing multiple names. For a feature where the consumer needs exactly one name (e.g., in a rich result), it’s not defined which of the name values will be used. If the consumer is a search engine, it will likely use its already existing proprietary algorithms to handle such cases.

¹ Of course it’s not clear if/how all the various consumers support it. But it’s the correct way to do this, and it’s the only explicit way to do this. Implicit ways include hoping that a consumer understands that identical values for typically (but not necessarily) unique properties (e.g., url, email, productID, etc.) mean that the things are the same. But such an implicit way can of course be used together with the explicit one.

Community
  • 1
  • 1
unor
  • 92,415
  • 26
  • 211
  • 360
  • 1
    "There is a way to prevent this¹: give each thing a URI, and in case the things are the same, the same URI." won't work for Google, see https://stackoverflow.com/a/59771262/565110 – David Riccitelli Jan 16 '20 at 13:59
  • @DavidRiccitelli Please, could you provide any proof or reference on your claim about incompatibility for Google? – Katapofatico Jan 07 '21 at 10:55
  • See this https://stackoverflow.com/questions/33756091/google-does-not-correctly-merge-microdata-and-jsonld-in-the-same-page-using-sam/59747826#59747826 – David Riccitelli Jan 08 '21 at 11:07
  • Also try to copy and paste JSON-LD and microdata using the same @id/item is in SDTT: they don’t merge. Cheers – David Riccitelli Jan 08 '21 at 11:08