Tuesday, April 16, 2024 10:28:53 PM
Product schema for Attribute Combinations suitable for Google Merchant/Shopping
Home / Forums / SEO Plugins / Rich Cards (JSON-LD) / Product schema for Attribute Combinations suitable for Google Merchant/Shopping
The JSON this plugin renders for products with attribute combinations uses AggregateOffer and lists all GTINS in the combinations and the high and low price.
As explained on https://technicalseo.com/insights/blog/product-schema-google-merchant-vs-google-search/ this is not suitable for Google Merchant Centre/Google Shopping where the product schema for every combination (variant) is needed.
Could this be included? If so I would not hesitate to purchase the multi-domain license. Thank you.
As explained on https://technicalseo.com/insights/blog/product-schema-google-merchant-vs-google-search/ this is not suitable for Google Merchant Centre/Google Shopping where the product schema for every combination (variant) is needed.
Could this be included? If so I would not hesitate to purchase the multi-domain license. Thank you.
It is done by simply nesting multiple "offers" inside a single "product", each offer being one attribute combination.
The following Google page discusses multiple offers on a page (see under "Getting started"): https://support.google.com/merchants/answer/7331077?hl=en-GB
Here is a website page (not NOP) that uses Microdata with multiple offers successfully with Google Shopping: https://bit.ly/3lZeL73. Each "offer" has the GTIN, price etc, and Google Shopping/Google Merchant Centre regularly crawls the page to automatically update price and availability for each size of the product that is available (https://support.google.com/merchants/answer/7050465?hl=en-GB).
The plug in would need to work with both products with attribute combinations and products without (on the same website).
I have today purchased your "Rich results" plugin (multiple domains) along with another plugin of yours, but am hopeful that you can upgrade it to cater for attribute combinations - that is vital for my website (the non-NOP one I mentioned above) which I am working on migrating to NOP, due to the products being advertised on Google Shopping. Thank you.
The following Google page discusses multiple offers on a page (see under "Getting started"): https://support.google.com/merchants/answer/7331077?hl=en-GB
Here is a website page (not NOP) that uses Microdata with multiple offers successfully with Google Shopping: https://bit.ly/3lZeL73. Each "offer" has the GTIN, price etc, and Google Shopping/Google Merchant Centre regularly crawls the page to automatically update price and availability for each size of the product that is available (https://support.google.com/merchants/answer/7050465?hl=en-GB).
The plug in would need to work with both products with attribute combinations and products without (on the same website).
I have today purchased your "Rich results" plugin (multiple domains) along with another plugin of yours, but am hopeful that you can upgrade it to cater for attribute combinations - that is vital for my website (the non-NOP one I mentioned above) which I am working on migrating to NOP, due to the products being advertised on Google Shopping. Thank you.
I read a lot of official Google and Facebook documentation.
Only Google can read HTML pages with several product variants. Facebook can't do it.
I found the only way.
Create the new item Product + Offer for each product variant.
Each product variant will have the same product description etc.
Google recommend to have the different URL for each product variant.
I'll see if I find the more each way.
Only Google can read HTML pages with several product variants. Facebook can't do it.
I found the only way.
Create the new item Product + Offer for each product variant.
Each product variant will have the same product description etc.
Google recommend to have the different URL for each product variant.
I'll see if I find the more each way.
Thank you for looking in to this. I understand the solution you mention, but unfortunately with over 1,000 products, most with multiple variants (sizes), some with as many as 10, that would make it very difficult for customers to use the website as they would sometimes see an entire page full of the same product.
I can understand it isn't a problem for retailers where there are no variants or only a few, but with apparel - clothes and shoes, it is not practical to do it that way. Do you have any customers selling apparel who use this plugin?
Is it possible to add an option to the plugin to activate a mode that will automatically render the relevant JSON for attribute combination products? Without this I am concerned that we won't be able to sell on Google Shopping as we are able to do on the current non-NOP website at present.
Thank you.
Kind regards,
Andre
I can understand it isn't a problem for retailers where there are no variants or only a few, but with apparel - clothes and shoes, it is not practical to do it that way. Do you have any customers selling apparel who use this plugin?
Is it possible to add an option to the plugin to activate a mode that will automatically render the relevant JSON for attribute combination products? Without this I am concerned that we won't be able to sell on Google Shopping as we are able to do on the current non-NOP website at present.
Thank you.
Kind regards,
Andre
I am curious. Does the structured data matter if you are using the foxnetsoft "Feed Manager" plugin to push product data to Google? Or do you need both? I thought the feed manager plugin was all you needed. I myself would like to link up the Google merchant account but have not had the time to complete the setup.
Yes, if you have lots of products that can go out of stock at any time, or that change price (e.g. sales/repricing), it is vital. Otherwise, if Google detects a mismatch, e.g. a product in your feed that goes out of stock during the day, or you put a sale on, the products can be disapproved by Google and it can take a while to get them back online when needed, and if it happens too frequently, your account can be suspended (we only just managed to avoid this).
This Google page explains it: https://support.google.com/merchants/answer/3246284
We have thousands of products, many with low stock, and due to disqualifications, we learned to ensure the structured data markup worked properly, as as we are moving to NOP, we are going to need it.
It might be feasible to do without it if your products don't go out of stock or change prices frequently (and you can force a refresh of the feed after every change), but that is not practical with a lot of products.
This Google page explains it: https://support.google.com/merchants/answer/3246284
We have thousands of products, many with low stock, and due to disqualifications, we learned to ensure the structured data markup worked properly, as as we are moving to NOP, we are going to need it.
It might be feasible to do without it if your products don't go out of stock or change prices frequently (and you can force a refresh of the feed after every change), but that is not practical with a lot of products.
Please see the "Variants grouped using 'inProductGroupWithID'" section on https://support.google.com/merchants/answer/6386198 - would this be the correct way to (optionally) render products that have Product Attributes that vary with size? (i.e. inProductGroupWithID is set to the Product table ID for each Product Attribute)