Website

Bug: Schema Markup editor won’t save valid shippingDetails in Product Offer (blocks Merchant Listings schema)
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.
1
·
under review
Global SEO Templates and Dynamic Variables for All Pages, Funnels, and Sites
Overview -- GoHighLevel needs a Global SEO Template System that allows administrators to define platform-wide defaults for meta titles, meta descriptions, open graph tags, canonical URLs, and other SEO elements using dynamic variables. -- This would eliminate repetitive manual edits, reduce errors, and bring GHL in line with SEO capabilities found in WordPress, Webflow, Shopify, HubSpot CMS, and other modern platforms. Current Limitation -- All SEO fields must be updated manually one page at a time across websites, funnels, funnel steps, blog posts, and membership pages. -- This is inefficient and inconsistent, especially for agencies managing multiple client accounts. Proposed Solution: Add Global SEO Defaults with Dynamic Variables -- Add a new section under Site Settings labeled SEO Defaults where users can define global SEO templates. -- Allow variables such as {{page.title}}, {{ site.name }}, {{page.path}}, {{ brand.phone }}, {{ brand.location.city }}, {{brand.location.state}}, and {{brand.domain}}. -- These variables would automatically populate SEO metadata on every new page unless manually overridden. Examples of Global SEO Patterns -- Meta Title Template: {{page.title}} | {{ site.name }} -- Meta Description Template: Learn more about {{page.title}} from {{ site.name }}. -- Open Graph Title Template: {{page.title}} – {{ site.name }} -- Canonical URL Template: https://{{brand.domain}}/{{page.path}} Benefits -- Massive time savings by removing the need to edit SEO metadata on dozens or hundreds of pages manually. -- Eliminates human error by ensuring consistent metadata across all pages and funnels. -- Essential for agencies that want standardized SEO practices across multiple client accounts. -- Supports multi-location and programmatic SEO using dynamic variables. -- Improves overall search performance through consistent, correct, and structured metadata. Optional Enhancements -- Option to force global templates unless overridden on a specific page. -- Option to bulk-apply global SEO settings to all existing pages. -- Ability to define global no-index rules for pages like thank-you, checkout, and upsell steps. Conclusion -- A Global SEO Template System with dynamic variables would significantly strengthen GoHighLevel’s SEO capabilities, reduce operational workload, and provide consistent, professional SEO foundations for all sites and funnels on the platform.
1
·
under review
Load More
→