If you look in your [url="https://search.google.com/search-console/"][blue]Google Search Console[/blue][/url], notice the menu category labelled 'Shopping'. Under that see two sub-categories:

> Product snippets which we are all familiar with, and
> [maroon]Merchant listings[/maroon] which is NEW as from Tuesday, 13 September 2022. Read the [url="https://developers.google.com/search/blog/2022/09/merchant-listings"][blue]Google Blog Post here =>[/blue][/url]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Now when you run a Product webpage URL (with standard ECT microdata snippets) through the [url="https://search.google.com/test/rich-results"][blue]Google Rich Results Test Tool[/blue][/url], the 'Detected structured data' appears in two categories:

> Product snippets, 1 valid item detected, the usual [orange]non-critical issues[/orange], all good
> [red]Merchant listings, 1 invalid item detected[/red], groan

The [red]1 critical issue[/red] is: offers ... [red]Invalid enum value in field 'itemCondition'[/red]

[code][font=Courier New][size=3]<meta itemprop="itemCondition" itemscope itemtype="http://schema.org/OfferItemCondition" content="http://schema.org/NewCondition" />[/size=3][/font=Courier New][/code]
NOTE: That HTML code only appears when you enter this parameter in [purple]includes.php[/purple]: (Yes, it can be omitted.)

[code][font=Courier New]$setschemacondition=[green]TRUE[/green]; [orange]// Rich Snippet for Product item condition is set to "NewCondition".
// $schemaitemcondition="UsedCondition"; // OVERRIDE options are DamagedCondition, NewCondition, RefurbishedCondition, UsedCondition[/orange][/font=Courier New][/code]
==> So WHY would itemprop "itemCondition" pass as [green]Valid[/green] in Product snippets but [red]Invalid[/red] in Merchant listings

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

I went to the Google Search Community and grizzled: [url="https://support.google.com/webmasters/thread/179656054"][blue]https://support.google.com/webmasters/thread/179656054[/blue][/url]

The answer given suggests the structured data was found on hidden content. The solution suggested is "This markup can (and should) be presented in conjunction with text that is visible to the user."

So Vince, if we had another element named "[purple]availability[/purple]" to display on the Product webpage like ...

[code][font=Courier New][green]$detailpagelayout[/green]="productimage, productname, navigation, dateadded, sku, manufacturerlink, [purple]availability[/purple], reviewstarslarge, socialmedia, discounts, listprice, quantitypricing, options, price, addtocart, description, reviews, previousnext";[/font=Courier New][/code]
... that would / should fix it. And perhaps a way to select the Item Condition in Product Admin. Yes, what a pain, I agree.

I suppose a clean result in [maroon]Merchant listings[/maroon] snippets is important? Do you think it is necessary to include "Item Condition" at all? Other Ecommerce Templates users might comment?

Gary
[img]https://itzap.com.au/pics/logo/itzap-website-design-works-mini-logo.png[/img]

That is weird...

I just tested a few of my product pages and they all come back with valid:

Product snippets
Merchant listings
Review snippets

No critical issues of any kind

Patrick

I see that Patrick, but you are using ...

[code][font=Courier New][green]<!-- ECT Product Schema Markup Generator v1.0 - by DLSS -->
<!-- JSON-LD Structured Data -->[/green][/font=Courier New][/code]

Gary
[img]https://itzap.com.au/pics/logo/itzap-website-design-works-mini-logo.png[/img]

Hey Gary,

Yes... I forgot I was using that.

Hopefully Vince can fix the stock ECT version.

Hope all is well with you.

Patrick

I am fine thanks Patrick. One question for you.
Curious to know if you are able to select the ItemCondition: [green]NewCondition, UsedCondition, DamagedCondition, RefurbishedCondition[/green]
Or is every Product on your website advertised as NewCondition ?

Gary
[img]https://itzap.com.au/pics/logo/itzap-website-design-works-mini-logo.png[/img]

Everything is NewCondition as that is all we offer

Hey Gary,

If used in conjunction with the Google Merchant Center feed I offer, the condition is changeable in admin and is represented in the schema.

Mike

Mike Beebe
President,
DataLinks Software Solutions
www.dlss.ca
Rate Me Here

ASP and PHP mods - www.dlss.ca/products.asp
A Tremendous Home - www.ATremendousHome.com
Buy Cigars Online www.CigarSmokeShop.net

Hi Mike,

Interesting to know that your Google Merchant Center AddOn permits the itemCondition to be changed in the ECT Admin Panel, thank you.

However, testing product pages on Patrick's Badman Bullets website, I must comment that your JSON-LD entry [font=Courier New][purple]"itemCondition" : "http://schema.org/NewCondition"[/purple][/font=Courier New] appears only in the Source Code.
Nowhere on the webpage itself does it tell the customer "Item Condition: New".

So that leaves me bewildered as to why Google Merchant Listings interpret your JSON-LD snippet as [green]Valid[/green], but the standard ECT microdata snippet as [red]Invalid[/red].

I say that is Bulltish !

Gary
[img]https://itzap.com.au/pics/logo/itzap-website-design-works-mini-logo.png[/img]

From how it reads, it sounds like if you are using microdata with HTML tags, the data must be both tagged and visible to the user. Not marked up for Google only.

Just my interpretation.

Mike

Mike Beebe
President,
DataLinks Software Solutions
www.dlss.ca
Rate Me Here

ASP and PHP mods - www.dlss.ca/products.asp
A Tremendous Home - www.ATremendousHome.com
Buy Cigars Online www.CigarSmokeShop.net

[code][font=Courier New][size=3]
<div itemscope itemtype="https://schema.org/Product">
<div class="detailname"><h1 itemprop="name">OZPIG Smoker</h1></div>
<div itemprop="offers" itemscope itemtype="https://schema.org/Offer">
<meta itemprop="priceCurrency" content="AUD"> <span class="price" id="pricediv0" itemprop="price" content="279.95">$279.95</span>
<meta itemprop="availability" content="http://schema.org/InStock" />
[purple]<p itemprop="itemCondition" itemscope itemtype="https://schema.org/OfferItemCondition">
[navy]Condition:[/navy] <b itemscope itemtype="http://schema.org/NewCondition">[navy]New[/navy]</b></p>[/purple]
</div>
</div>
[/size=3][/font=Courier New][/code]
There is a Microdata snippet for "itemCondition" with text visible on the webpage to say "[navy]Condition: New[/navy]". Run that <code> through the Google Rich Results Test Tool and the result given is:
> Product snippets, [green]Valid[/green]
> Merchant listings, [red]Invalid enum value in field 'itemCondition'[/red]

Therefore, Microdata being "visible to user" makes no difference.

In Merchant listings, the Google Testing Tool says the enum value "NewCondition" is Invalid. But this page [url="https://schema.org/NewCondition"][blue]https://schema.org/NewCondition[/blue][/url] confirms that the Testing Tool is wrong. But Google will not fess up to it.

For now, I have removed this $parameter from the includes.php configuration file:
[code][font=Courier New][size=3]
[orange]// $setschemacondition=TRUE; // Rich Snippet for Product item condition is set to "NewCondition".[/orange]
[/size=3][/font=Courier New][/code]
Now no snippet for itemprop="itemCondition" appears in the code and we get a clean [green]Valid[/green] result in both Product snippets and Merchant listings.

Check again in 1 or 2 months and bet that Google will have fixed that false report.

Gary
[img]https://itzap.com.au/pics/logo/itzap-website-design-works-mini-logo.png[/img]

Scratch that, I finally found the SOLUTION ...
[code][font=Courier New][size=3]
<div itemscope itemtype="https://schema.org/Product">
<div class="detailname"><h1 itemprop="name">OZPIG Smoker</h1></div>
<link itemprop="image" href="https://example.com/photos/16x9/photo.jpg" />
<div itemprop="offers" itemscope itemtype="https://schema.org/Offer">
<meta itemprop="priceCurrency" content="AUD"> <span class="price" id="pricediv0" itemprop="price" content="279.95">$279.95</span>
<meta itemprop="availability" content="http://schema.org/InStock" />
[purple]<meta itemprop="itemCondition" content="https://schema.org/NewCondition" />[/purple]
</div>
</div>
[/size=3][/font=Courier New][/code]
Run that <code> through the Google Rich Results Test Tool and the result given is:
> Product snippets, [green]Valid[/green]
> Merchant listings, [green]Valid[/green]

Therefore Vince, if you could kindly change the Microdata snippet inserted for:

[code][font=Courier New][size=3]$setschemacondition=[green]TRUE[/green];[/size=3][/font=Courier New][/code]
From:
[code][font=Courier New]<meta itemprop="itemCondition" [red]itemscope itemtype="http://schema.org/OfferItemCondition"[/red] content="http://schema.org/NewCondition" />[/font=Courier New][/code]
[red]delete the red bit[/red] and just have:
[code][font=Courier New][size=3]<meta itemprop="itemCondition" content="http://schema.org/NewCondition" />[/size=3][/font=Courier New][/code]
That will fix this issue

Gary
[img]https://itzap.com.au/pics/logo/itzap-website-design-works-mini-logo.png[/img]

Good find

Mike Beebe
President,
DataLinks Software Solutions
www.dlss.ca
Rate Me Here

ASP and PHP mods - www.dlss.ca/products.asp
A Tremendous Home - www.ATremendousHome.com
Buy Cigars Online www.CigarSmokeShop.net

Well thanks very much once again, Gary . . . and that is now changed in the updater.

Vince

Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater

Hi, I seem to be getting the merchant listing error referred to in this post.. I just updated to 7.4.10 hoping this would fix it, but my pages are still producing this error. Is the fix included in this version or do I need to update to 7.5.3?

Richard.

Yes Richard, you need to update to the latest v7.5.3 advanced.

Gary
[img]https://itzap.com.au/pics/logo/itzap-website-design-works-mini-logo.png[/img]

Hi Richard
If you are not in a position to update to v7.5 now then please let me know and I'll get this fix into the v7.4 updater.

Vince

Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater

Thanks Gary ..I'll do that.

Richard.

Thanks Vince, but no need as I have now updated to 7.5. All seems to be working ok..

Richard.

Vince, might you be able to provide a patch for this that we can apply to our v7.4.11 store?

We considered updating to 7.5 but it looks like some of our content would break.

Thanks in advance for any help you can give.

- Paul D.

Hi Paul, all you need to do is ...

In vsadmin\inc folder, open incproddetail.php
Search for the one line containing: [purple][font=Courier New]itemprop="itemCondition"[/font=Courier New][/purple]
In that line delete the bit of code which says: [red][font=Courier New]itemscope itemtype="http://schema.org/OfferItemCondition"[/font=Courier New][/red]

So now that line will just say:

[font=Courier New]if(@$GLOBALS['setschemacondition']&&!$GLOBALS['noschemamarkup']) print '<meta itemprop="itemCondition" content="http://schema.org/'.(@$GLOBALS['schemaitemcondition']!=''?$GLOBALS['schemaitemcondition']:'NewCondition').'" />';[/font=Courier New]

Save incproddetail.php and upload to server.

Gary
[img]https://itzap.com.au/pics/logo/itzap-website-design-works-mini-logo.png[/img]

Thanks for this, Gary.

Fingers crossed that the Invalid enum value in field "itemCondition" (in "offers") Merchant listing errors go away now that we've edited and uploaded incproddetail.php and Google re-indexes those pages.

This is much appreciated