2

One of my client is e-commerce marketplace. For their offer listing pages, I have provided a JSON structured data Product markup using aggregateRating as follows:

<script type="application/ld+json">
{
  "@context": "https://schema.org/",
  "@type": "Product",
  "name": "example name", 
  "description": "example description",
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.7", 
    "ratingCount": "20",
    "bestRating": "5",
    "worstRating": "1"
  }
}
</script>

So far everything is good. Everything works fine; and the structured data is displayed properly on Google SERP.

Issue

Although, there are 6 warning; as the markup is for Product. Here is the screenshot:

Warning are for the following six fields:

  • brand,
  • image,
  • offers,
  • review,
  • sku
  • unique identifier (either of isbn, mpn or gtin8)

There are 0 Pages with Errors, 40 Pages with Warnings and 0 Valid pages in Google Search Console. They recommend to fix these warnings so that it can be considered as a valid markup. Here is the screenshot:

I do not have SKU and unique identifier, so how can I fix these warnings? I did research on Google Documentations and Schema.org but there is no other way to fix these errors than to provide all these values.

I have a doubt that Google may penalize in future because of these warnings. Is there any way I can by-pass these errors or do tweak in code?

Update 1

Google keeps on sending notification about these warnings. Google suggests to fix them ASAP. Thing is, I do not have these values on the page. So is there any way to tell Google that these values do not exist on the page? For example can I add in structured data code something like

  • "brand": "Not Applicable";
  • "image": "Not Applicable";
  • "offers": "Not Applicable";
  • "review": "Not Applicable";
  • "sku": "Not Applicable";
  • "gtin8": "Not Applicable".

Update 2

I received below message on these warnings. This clearly stats that

Search Console has identified that your site is affected by 6 new Products related issues. This means that Products may be negatively affected in Google Search results. We encourage you to fix these issues.

1

As you can see those warnings are recommendation not mandatory. Google is suggesting you to add those information.

One of my client is e-commerce marketplace. For their offer listing pages, I have provided a JSON structured data Product markup using aggregateRating as follows:

As you said you're creating schema for offer, your JSON is not correct, you should go through - https://schema.org/Offer, you can also add offer type in your product.

  • Yes, I understand that it is a warning and not an error but we get emails from Google suggesting to fix these warnings ASAP, otherwise it can negatively affect our search rankings. That’s why I had a doubt. – Bhargav Joshi Apr 17 at 16:14
  • But I think there is no solution to it. I also asked this question in Google Community and received the same reply. – Bhargav Joshi Apr 17 at 16:16
4

I do not have SKU and unique identifier, so how can I fix these warnings?

Is there any way I can by-pass these errors or do tweak in code?

There is no way to fix this other than to provide the data.

I have a doubt that Google may penalize in future because of these warnings.

As long as it’s just a warning, you can still get the search result feature ("Please provide a value if available."). Depending on the missing data, the search result feature might miss some features.

If it’s an error, you can’t get the search result feature.

No matter how many warnings/errors the SDTT shows, your page won’t get penalized (unless you try to deceive). The only drawback is that the result for your page doesn’t get the search result feature.

  • Hi @unor All these six fields are not on the page, so I am unable to include in the Structured Data code. However, Google keeps on sending warning messaged and ask to fix this. So is there any other way to tell Google that we do not have these fields? for example can I mention "brand" : "Not Applicable", "SKU" : "Not Applicable" etc or anything I can write so Google can understand? – Bhargav Joshi Apr 11 at 3:19
  • @BhargavJoshi: I can only repeat my first sentence: there is no way around; you can either provide the data, or live with the warnings. What might be possible in some cases is to change a warning to a different warning/error (e.g., by providing a recommended property without giving it a recommended value, but still making sure not to lie) -- but you won’t gain any benefit with this, it’s only about what gets reported in Google’s interface. – unor Apr 11 at 22:08
  • Yeah, I see. Thing is we keep on receiving communication from Google. Today we also receive an email, asking us to fix issue, otherwise it might negatively affect in Google search results. I've updated that in my question. That's the reason I was thinking if there is some way to pass either a default value or something to mention that these values don't exist on page. But I guess there isn't any option to do that. – Bhargav Joshi Apr 12 at 3:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.