Has anyone had success using a variant-based feed with Google? I have the markup data properly update with the selected size/url, but Google only recognizes the schema of the parent product, regardless of what URL is submitted. To my understanding, Google does not process JavaScript for markup data, which means the server has to send over the correct information.

Hi Alex, On our Elbrus site we had to do some customizations to ensure compliance with all of Google's requirements. If Google is still only recognizing the parent schema even with the different URLs for the specific item then you need to test each URL using google's structured data testing tool https://search.google.com/structured-data/testing-tool And then compare the schema Google sees to what you would expect.

I have used this tool quite a bit. The problem that I have is that if I fetch a child URL with it, then it pulls the parent schema information. If I copy the html from the child page and try to check it with the tool, then it displays the correct information.

I wonder if when Google makes the request to SCA, SCA uses the SEO Generator engine which may be giving different schema.

That was my assumption. I looked into documentation and it seems like Google only cares about the server response. Since the SEO generator does not crawl child urls (to my knowledge), I'm not quite sure how to get around this issue.

which version of SCA are you using

We are currently running Vinson, but we will be upgrading soon to 2019.1.

I wouldn't bother going to 19.1 but go to 19.2 given the big changes. We are on Elbrus and will going to 19.2 early next year

I am the only developer here and have spent about 6 months working on 2019.1 (before 2019.2 was released). I'll take a look after this implementation for a potential upgrade. We have a lot of customizations.

Ahh, that makes sense. But definitely have a read of this blog by Steve https://developers.suitecommerce.com/announcement-suitecommerce-and-suitecommerce-advanced-20192

Thanks! I will definitely read that over. I was disappointed that es6 was not supported when I started on the 2019.1 upgrade. I'll probably look at upgrading after we have stabilized on the new version.

Can you send me an example URL of a child matrix item and I'll have a look

Child: http://www.plaquemaker.com/glass-desk-plates?custcol_matrix_name_plates=1 Parent: http://www.plaquemaker.com/glass-desk-plates

@Alex Cook, SEO Page Generator is used with Google and the structured data testing tool. Unfortunately, if you implement Schema.org using JSON, the page generator will remove it. you have to use the microdata markup.

@Keith Fetterman, we are using the microdata markup. I built upon the html that was provided by the base templates. The problem is that we need the child microdata sent to Google, which is defined by a url query. When I fetch the child item url from Google, I am getting the parent schema instead.

I recently had to deal with this for matrix items on the PDP. How did you create the submatrix item specific URLs to the PDP? The issue that I have found is that SC/SCA does not provide a way to generate the submatrix item specific URLs and it can’t find them to crawl.

I had wondered if that was a solutions a while back, but never actually tried it. All of our variations are defined by a url query, so the base url does not change. I will probably try to get one product changed over to show the schema of all children somehow.

I think it is ridiculous that Google does not support non-clothing variations. The Schema.org schema supports custom variations, but Google doesn’t recognize it. Here is the page from Google Merchant Center that talks about handling unsupported variations: https://support.google.com/merchants/answer/6231538 I implemented this by using multiple “Product” itemtypes on the PDP.