JSON-LD Product Schema syntax issues (Data Types & Case Sensitivity

Hello SASWP Support Team,

I am using your plugin to generate Product Schema for my store and I really appreciate your work. However, during a detailed JSON-LD audit, I noticed a few syntax issues regarding data types and case sensitivity that might affect Google validation and indexing.

Could you please look into the following 4 points and consider fixing them in the next update?

1. Invalid Case for priceSpecification @type Currently, the plugin generates the type with a lowercase letter: "@type": "priceSpecification" Expected behavior: Schema.org types are case-sensitive. It should be PascalCase: "@type": "UnitPriceSpecification" (or PriceSpecification)

2. valueAddedTaxIncluded should be Boolean, not String Currently, it outputs: "valueAddedTaxIncluded": "false" Expected behavior: According to Schema.org, this property expects a Boolean value: "valueAddedTaxIncluded": false

3. offerCount should be Integer, not String Currently, inside AggregateOffer, the count is a string: "offerCount": "10" Expected behavior: This property expects a Number (Integer): "offerCount": 10

4. Missing priceCurrency inside priceSpecification (Recommendation) While the currency is defined in the parent Offer, the nested priceSpecification object currently lacks it. Recommendation: For strict Schema.org compliance and data integrity, it is best practice to include "priceCurrency": "PLN" (or the relevant store currency) inside the priceSpecification object as well.

These changes would greatly improve the technical quality of the Schema output and prevent warnings in Google Merchant Center and Rich Results Test.

Thank you for your time and help!