Why existing schema causes issues
Google does not allow dual schema. Any schema that is already on your page will automatically take priority over our schema, and Google will ignore ours. This could also negatively impact your search ranking because it is bad for SEO when you have conflicting schema.
Options for using our schema
For our injected schema to work, you would need to implement one of these solutions.
Remove your existing schema. Doing this would allow for our injected schema to be the only schema on the page and will allow Google to read it correctly.
Convert your existing schema to JSON-LD. Doing this allows Google to basically see both schemas as the same one and will read both of them in.
Modifying your existing schema
The other option to get stars to show in search is to add the review markup to your existing schema and turn off our schema injection. Your developer would likely need to use our API to pull the review information and then use that to create the markup. This takes quite a bit of coding knowledge, but if your developer is comfortable with making schema changes our API can be found here: https://api.shopperapproved.com/ui/#/products
Schema examples
Microdata Schema- This is a schema type that we want to have removed and replaced with JSON-LD schema
Microdata will be separated into paragraphs and has a lot of “<>” signs, like this picture.
JSON-LD - This is the type of schema that our system uses. You can tell it is JSON-LD because it is contained within a script tag with a type of "application/ld+json"
Platform limitations
Some ecommerce platforms do not allow you to edit the existing schema manually. This means that you may not be able to add stars to your markup unless you were to use a platform plugin/extension. Examples of major platforms that do not allow this include, but not limited to, Volusion and Yahoo.