Schema Plus for SEO & JSON‑LD

Thank you for taking the time to share detailed feedback across the stores, Goatkits Store, and NipponKits.
Since the concerns you've raised are identical, we're addressing them together here in a single response. We've reviewed each point carefully and would like to provide some clarification based on our current technical implementation.

1. Judge.me integration and missing aggregateRating

We’ve double-checked this using Google’s Rich Results Test(https://search.google.com/test/rich-results/result?id=-ygnlHRtwQ96YhisRKUD5g), and it shows that SchemaPlus was successfully generating the expected aggregateRating and review data for products. We understand the importance of this feature and have confirmed it was functioning as intended.

2. Escaped characters in URLs (//, \u0026)

The use of \u0026 in JSON-LD is a safe and standard way to represent &. Google’s structured data guidelines fully support this, and it does not negatively affect indexing. These encodings are commonly used to prevent conflicts when JSON is embedded in HTML and are interpreted correctly by search engines.

3. Missing seller information

The same Rich Results Test confirmed that seller and brand information are included under the product offers. This data should be fully visible and valid in the structured markup.

4. Logo URLs returning 404

This issue may be due to the Organization logo uploaded via SchemaPlus being removed from the Shopify store’s assets. Once a store removes the uploaded logo or uninstalls the app, we lose access to those assets and cannot verify them.

5. Only one image generated

Our current schema includes multiple product image URLs, and we’ve confirmed that all available product images are included in the structured data.

6. HTTP in @context

According to schema.org documentation, using http://schema.org or https://schema.org in the @context field is treated the same. Both are valid and accepted. https://schema.org/docs/faq.html#19

7. Broken breadcrumbs despite “enabled” status

During your time with SchemaPlus, we observed functional breadcrumbs on search results, which matched the expected output. It’s unclear what specifically was perceived as broken, but we’d be happy to discuss further if you choose to reinstall.

8. Support message referencing Rich Results Test

You’re right that there’s a difference between validation and live display in SERPs. However, Google's own documentation(https://support.google.com/webmasters/answer/7445569) clarifies that passing the Rich Results Test does not guarantee that rich snippets will appear in search results. We meant to share that structured data was correctly implemented, but acknowledge that our communication could have been more nuanced.

9. “Blaming Google”

We aim to be transparent. Our intention was not to shift blame but to inform that Google ultimately determines what appears in search, and structured data implementation alone does not guarantee display.

10. Mentioning third-party apps

We do not place blame on other apps. However, we sometimes alert users that apps with aggressive speed optimization features may inadvertently delay or block schema scripts. This is shared in the interest of troubleshooting and transparency.

11. Translated handles

Currently, SchemaPlus supports translated pages, but translated handles created by certain translation apps can prevent schema from loading. This is a known limitation, and we are actively working toward a more robust solution.

We understand that our support did not meet your expectations and that the app caused concern for your business. Your feedback is important and will be shared internally to help us improve both our product and support experience.

Wishing you success with your stores moving forward.

SchemaPlus Team