Merchant Center Price Mismatch

Assuming the MPN and GTINs appears in your feed XML, that should be fine.

Google’s docs (see https://support.google.com/merchants/answer/9773429) suggest they read meta tags as well, so you may want to re-enable the ‘product:price’ meta tag (it is currently missing from your webpage).

Since WPSSO Core v14.6.0, using the WooCommerce variations URLs moves the variation price top-most, but for this feature to be active, the WPSSO GMF add-on must be active (the add-on triggers activation of this feature).

Although moving the variation offer top-most for a variation URL should address that Google merchant crawler bug, in the future WPSSO Core will probably implement https://schema.org/ProductGroup markup instead. Although new and still pending implementation in the Schema.org standard, the Google merchant crawler may read this markup better than using multiple offers (ie. they mention https://schema.org/inProductGroupWithID in their documentation at https://support.google.com/merchants/answer/6386198).

js.

Assuming the MPN and GTINs appears in your feed XML, that should be fine.

Confirmed in the feed here:

so you may want to re-enable the ‘product:price’ meta tag

I don’t recall ever having a reason to disable this, but it is now enabled. I’ll see if this leads to any change in merchant center in tomorrow morning’s update.

but for this feature to be active, the WPSSO GMF add-on must be active (the add-on triggers activation of this feature).

WPSSO GMF add-on is active, but I’m still using the GPF plug-in xml to feed merchant center since I still have more to configure with WPSSO and the GPF xml is currently working well for most products.

Although moving the variation offer top-most for a variation URL should address that Google merchant crawler bug, in the future WPSSO Core will probably implement?https://schema.org/ProductGroup?markup instead.?

This sounds promising, but is there any kind of timeline on it? We’re launching a new product soon that will have different-priced variations and I expect to have this same issue with it. Not being able to advertise that product makes this a high priority for us.

It all depends how much time I get to work on it, but I’d say another week, maybe two. The Google merchant crawler is quite buggy – always has been – so there’s no guarantee that changing the structure from product offers to the new https://schema.org/ProductGroup type with a https://schema.org/inProductGroupWithID value will fix Google merchant’s crawler bug, but I’m hopeful. ?? The https://schema.org/ProductGroup type was proposed specifically for variations, and Google’s merchant docs specifically mention supporting a https://schema.org/inProductGroupWithID value (if their crawler actually understands it is a different story). Keep in mind that Google search uses a different crawler, and any changes we do will have to clear the Google search validator first. No use changing the structure for Google merchant if Google search doesn’t like it. ??

FYI, if you’re a Premium customer, and you want to install the Development versions on your development / staging server(s), you can select the Development branch for WPSSO Core and its add-ons under the SSO > Update Manager settings page.

js.

FYI, if you’re a Premium customer, and you want to install the Development versions on your development / staging server(s), you can select the Development branch for WPSSO Core and its add-ons under the SSO > Update Manager settings page.

We are premium and do have a staging site set up, but since that’s not connected to merchant center I’m not sure how it would help us validate that the updates resolve the mismatch error.

Ultimately, I’d like to move towards moving our sitemaps and product feed to WPSSO so I can reduce the number of different developers’ plugins we have going, so thanks for helping with this!