Description: We are starting (last week) to receive warnings from Google about the Rich Snippets code generated by Miva as being deprecated.

Right now it is a warning like this:

Search; some might be reclassified as errors in the future. The following warnings were found on your site:
data-vocabulary.org schema deprecated
We recommend that you fix these issues when possible to enable the best experience and coverage in Google Search.


I think I read that data-vocabulary.org code will be fully unsupported in March 2020 and then these warnings will turn into errors.

There is in the PROD page a section of generic boilerplate looking hunk of code that seems to be the area of concern for Rich Snippets.

Not an expert with SMT but the code looks generic/boilerplate and nothing specific to my Levels ReadyTheme or these stores.

The Google suggestion is to convert the code to use schema.org and I am not sure how to do that (not even a Mini Mivite or smart enough yet). I've experimented and gotten close but still end up with at least one warning from the Google Structured Data Testing Tool.

I imagine this will be a complaint on every product detail page in both our stores and also Miva should understand that this could be a problem for every Levels ReadyTheme and maybe other ReadyThemes.

I looked in the Miva App Store at the other ReadyTheme examples (View Live Demo) where Collosus does not seem to use Rich Snippets, StoryTeller seems to be using Schema.org and all the others are still showing the old data-vocabulary.org.

Does this mean that almost every Miva ReadyTheme store on the planet is going to have this problem and need to be updated?

Come March I don't need Google sending me 50,000+ error messages for every product page.

I opened a Support ticket where they acknowledged the problem and was told that our 6 month old Levels stores are now legacy and there will be no fixes/updates and we should hire a developer (5th problem report with that offered "solution").

I don't feel we should have to hire a developer for this since it is not just going to be our store with this problem - every Levels ReadyTheme store of our vintage (and maybe other Themes) will have this problem.

What about all the other ReadyTheme stores and if the code is generic/boilerplate does Miva intend on fix/update the code since I think whatever will work for one ReadyTheme might work for all (or close).

Does anyone have a fix for Levels ReadyTheme they will share?

Will Miva post a fix (the actual hunk of code) for non legacy ReadyThemes that I can test in our Levels stores - at least I can give it a shot.

The code looks generic and boilerplate - is there a replacement for that piece of code available from some other Miva implementation that will pass the Google Structured Data Testing Tool?

I will be happy to be the guinea pig for validating the fix.