Adding Schema Markup to GoHighLevel Pages

GoHighLevel schema markup now has a dedicated panel on every page of the website and funnel builder, under "SEO & AI search optimization" in the editor menu. That's a shift from pasting JSON-LD into a custom code block and hoping it survives.

The tool covers more than 140 schema types, from Organization and LocalBusiness to Article, Event, and FAQPage.

Two editing modes sit side by side. Form View walks non-technical users through guided fields for a chosen type.

JSON View lets anyone paste or hand-write JSON-LD directly, useful for a migration or schema a developer built elsewhere.

Either way, a "Validate & Save" step checks the fields against Schema.org and Google's rich-result requirements before anything publishes.

Agencies handling a client build through our GHL setup and configuration work will recognize the pattern from the rest of the page editor.

The schema you add stays scoped to that single page or funnel step; it doesn't carry over automatically.

Pages built with GoHighLevel's AI assistant don't get schema generated for free either, so you add it once the content is finished.

What Changed in GoHighLevel Schema Markup, May 2026

On May 6, 2026, GoHighLevel expanded the manual schema builder from 12 parent-level types to 19, adding seven new categories:

• Offer
• Review
• Aggregate Rating
• Recipe
• ImageObject
• Service
• Course

That list matters most to e-commerce, food, education, and service businesses, the categories Google rewards with richer snippets when the data is there.

The expansion only applies to the manual Form and JSON views, since GoHighLevel's AI-assisted schema flow already generates any valid Schema.org type on its own.

Schema That Stops Paying Off

Adding schema markup doesn't guarantee a rich result, and Google has been pulling features out from under site owners who assumed otherwise.

FAQPage is the clearest recent example.

Google stopped showing FAQ rich results in Search on May 7, 2026, then started removing the FAQ filter, the Search Console report, and Rich Results Test support the following month, according to Search Engine Journal.

FAQPage is still a valid Schema.org type, so leaving old markup in place won't cause problems; it just won't earn the visual treatment it used to.

Google's own structured data guidelines are worth checking before you lean on habit.

Every property your schema claims has to match what's actually visible on the page, and reviews or ratings need to come from real users rather than invented ones.

That's worth reviewing against whatever you've already shipped through GoHighLevel's broader SEO setup and landing page SEO controls, since schema is one piece of a page's search footprint.

If you're building new pages, the website builder's defaults are a reasonable starting point, but the schema panel is where you confirm Google can actually read what the page is about.

Cover photo by Bibek ghosh on Pexels