Here’s what I’m running into with the new Schema Markup feature.

Issue

When using the Schema Markup JSON editor to build a Product schema with an Offer, adding shippingDetails (Schema.org OfferShippingDetails) causes the editor to fail to save and shows a generic error:

“Technical issue in JSON script. Review the script and make the necessary changes before saving.”

The JSON-LD is valid per Schema.org, but the HighLevel editor rejects it. This blocks users from addressing Google’s Merchant Listings “missing shippingDetails” warning using the built-in Schema Markup tool.

Google Search Console flags shippingDetails as an optional-but-recommended field for Merchant listings (product offers). If the HighLevel schema editor can’t save it, we’re forced into a workaround (adding separate JSON-LD in header custom code), which defeats the purpose of the schema feature.

Steps to reproduce

Open any Website / Funnel page in the editor.

Go to SEO & AI search optimization → Schema Markup.

Add a Product schema (and optionally Organization/FAQ, doesn’t matter).

Switch to JSON view and include a basic Offer under offers (price, currency, availability, url, seller).

Click Validate & Save -> saves successfully.

Now add this valid Schema.org snippet inside the Offer object:

"shippingDetails": [

{

"@type": "OfferShippingDetails",

"shippingRate": {

"@type": "MonetaryAmount",

"value": 0,

"currency": "USD"

},

"shippingDestination": {

"@type": "DefinedRegion",

"addressCountry": "US"

}

}

]

Click Validate & Save again.

Result: Fails with “Technical issue in JSON script…” and provides no field-level feedback.

Expected

It should accept and save valid JSON-LD for shippingDetails under Offer.

Actual

Refuses to save the schema as soon as shippingDetails is included.

• Current workaround (not ideal)

Keep schema in HighLevel without shippingDetails, then inject a separate JSON-LD <script> into the page header (custom code) using the same Offer @id to supply shipping. Google reads it, but this should be supported inside Schema Markup directly.