GoHighLevel Schema Markup Has a Dashboard Now — And It Will Tell You Which Pages You Forgot

Disclosure: I earn a commission if you sign up for GoHighLevel through links on this page. How that works is in the editorial policy.

Schema markup is the SEO chore everyone does once — on launch day, on the homepage, maybe the contact page — and then never looks at again. Twelve pages later, half your funnel has none, and the other half describes an offer you changed in March.

GoHighLevel schema markup finally has a place where you can see that mess all at once. HighLevel added an SEO & AEO tab to every website and funnel, and it does something the page builder never did: it tells you which pages you forgot.

A quick note on how this post was made: everything below comes from HighLevel’s changelog entry, its help docs and Google’s own structured-data documentation (all checked Oct 2026). It’s a docs-based walkthrough, not a hands-on test. Where the docs don’t say something, I’ll tell you rather than guess.

So what did HighLevel actually ship?

The short answer: GoHighLevel now has an SEO & AEO tab on every website and funnel (Sites → Websites/Funnels → select one → SEO & AEO). It shows a schema coverage rating and each page’s schema status, and lets you generate schema with AI in bulk or edit it by hand. Nothing goes live until you click “Save and publish.”

Schema — the structured data, usually JSON-LD, that tells search engines “this page is a local business, this is an FAQ, this is an event” — used to live inside each page’s settings in the builder. Fixing it meant opening pages one at a time. The changelog puts it plainly: until now, “keeping schema current meant going through the builder one page at a time, so most sites fell out of date.”

HighLevel also listed it in the Release Radar for the week of October 12, 2026 (checked Oct 2026) as “Centralized schema management” — “Manage schema markup across entire websites and funnels from a centralized SEO & AEO dashboard.”

And the “AEO” part? Answer engine optimisation — getting your pages understood, and ideally cited, by AI answer tools as well as classic search. HighLevel’s pitch is that accurate schema “helps AI answer engines understand and cite your business.” Note the verb. Helps. Not makes.

What does the coverage card actually grade?

Open the tab and the first thing you see is the Schema coverage card. Per the changelog, it rates the whole site as Needs work, Getting there, Good or Excellent, with counts for pages that are Up to date, Might be outdated and No schema.

Below it, every page gets a row with its schema types, its status and a last-updated date. There are five statuses:

• Up to date — schema exists and nothing has flagged it.
• Might be outdated — the page was edited and republished two or more times since its schema was created.
• No schema — exactly what it says.
• Unpublished — the page isn’t live.
• Unsaved — you’ve generated or edited schema but haven’t clicked “Save and publish” yet.

You can search by page name or path and filter by status, which is the part you’ll actually use. Filter for No schema, and you get a to-do list. Filter for Might be outdated, and you get the pages where your markup and your copy have probably drifted apart.

If you’ve ever rebuilt a sales page three times in a quarter, you already know which filter is going to hurt.

Why the “Generate schema” button deserves a second look

Here’s where it gets interesting. From the same tab, you can select one page or many and click “Generate schema” to have AI write the markup. HighLevel says progress shows live and results are available for review before anything goes live. You can also add schema by hand with Add schema, or click an existing schema tag to open the editor.

Then the safety net: generated or edited schema stays Unsaved until you click “Save and publish.” You can discard it instead.

But — and this is the line in the changelog I’d tape to the monitor — running Generate schema on a page that already has schema replaces it entirely. Not merges. Replaces.

Picture it. You spent an afternoon last spring hand-writing LocalBusiness schema for a client’s homepage — opening hours, service area, the lot. Today you filter for Might be outdated, select everything, hit Generate, and the homepage gets a fresh AI version that knows nothing about your afternoon. It sits there as Unsaved, looking helpful. One click on “Save and publish” and the hand-tuned version is gone.

So the rule I’d follow, as reasoning rather than a tested result:

1. Run bulk generation on No schema pages first. There’s nothing to overwrite.
2. For Might be outdated pages, open the existing schema and copy it somewhere before you regenerate.
3. Read every generated result against the visible page before you publish. Google’s structured data guidelines (checked Oct 2026) are blunt: “Your structured data must be a true representation of the page content,” and “Don’t mark up content that is not visible to readers of the page.” AI-generated markup that invents a review or an opening hour is your problem, not the AI’s.

Toggle, dashboard or builder — which one should you use?

You’d think this replaces the old ways of doing schema. It doesn’t. There are now three, and they overlap.

The changelog says schema editing in the page builder “still works exactly as before,” and the builder and the SEO & AEO tab stay in sync. And there’s a separate Auto-generate schema toggle, documented in HighLevel’s auto-generate schema help article (checked Oct 2026). You’ll find it in each website, funnel or webinar’s Settings tab, under SEO & AEO. When it’s on, HighLevel uses AI to add schema to pages that have none at the moment they’re published. Pages that already have schema are left unchanged.

Two details from that article worth knowing. Assets created before the release default to off, assets created after default to on. And it only runs on publish — existing pages stay as they are unless you republish them.

You want to…	Use	Why
See which pages across a site have no schema or stale schema	SEO & AEO tab	It’s the only place with a site-wide view and status filters
Fill gaps on many pages at once	SEO & AEO tab → Generate schema on No schema pages	Nothing to overwrite, and you review before publishing
Make sure new pages never ship without schema	Auto-generate schema toggle (Settings → SEO & AEO)	Runs on publish, skips pages that already have schema
Keep hand-written schema on a key page	Page builder, or Add schema / click a tag to edit	Avoids the full replace that Generate schema does
Refresh a page flagged Might be outdated	Edit the existing schema, or save a copy before regenerating	Regenerating replaces everything

Will any of this move your rankings?

Stay with me here, because this is where the launch-week posts will overreach.

HighLevel’s own claim is careful: accurate, current schema makes pages eligible for Google rich results. Google is even more careful. Its structured data policies (checked Oct 2026) say “Google does not guarantee that your structured data will show up in search results.” Eligible is the ceiling, not the floor.

So don’t sell this to a client as “we’ll get you stars in Google” or “ChatGPT will start recommending you.” Sell it as what it is — hygiene. Pages that describe themselves accurately, kept current, in one place you can actually audit. That’s worth doing on its own, the same way a landing page that converts is worth building properly whether or not anyone links to it.

Before you trust any generated markup, paste the live URL into Google’s Rich Results Test. It’s free, it takes a minute, and it’s the closest thing to a second opinion you’ll get.

If you’re still deciding whether GoHighLevel should host your sites and funnels at all, the honest GoHighLevel review and the comparison hub cover the bigger trade-offs. And the sales funnels pillar is where this fits in the wider build.

What to do this week

Four steps, in this order:

1. Open the SEO & AEO tab on one site — your own or a demo, not a client’s.
2. Filter for No schema and note how many pages turn up.
3. Generate schema for those pages, read every result against the page, and only then click “Save and publish.”
4. Check the Auto-generate schema toggle on any older asset, since those default to off.

If the client is paying for the sites, it’s worth knowing which plan covers how many sub-accounts before you roll this out across all of them. The plan picker answers that in about a minute.

FAQ

Where is the schema dashboard in GoHighLevel?

Per HighLevel’s changelog, go to Sites, then Websites or Funnels, select one, and open the SEO & AEO tab. Every website and funnel has the tab, and any schema you already added shows up there automatically.

Will Generate schema overwrite schema I already wrote by hand?

Yes, if you run it on that page. HighLevel’s changelog says generating schema on a page that already has schema replaces it entirely. The result stays Unsaved until you click Save and publish, so you can review it or discard it first.

What does Might be outdated mean in the SEO & AEO tab?

It means the page has been edited and republished two or more times since its schema was created, so the markup may no longer match what’s on the page. It’s a prompt to review, not proof that anything is wrong.

How is the SEO & AEO tab different from the Auto-generate schema toggle?

The Auto-generate schema toggle, in each asset’s Settings tab under SEO & AEO, adds AI schema to pages that have none when they’re published, and leaves pages with existing schema alone. The SEO & AEO tab is the dashboard where you see every page’s status and generate, edit or review schema in bulk.

Does adding schema in GoHighLevel guarantee rich results?

No. HighLevel’s changelog says accurate schema makes pages eligible for Google rich results, and Google’s structured data guidelines say Google does not guarantee that structured data will show up in search results. Treat schema as hygiene, not a ranking promise.

Can I still edit schema inside the page builder?

Yes. HighLevel says schema editing in the page builder still works exactly as before, and the builder and the SEO & AEO tab stay in sync, so an edit in one place shows in the other.

The pages you forgot

Remember that launch-day schema — the homepage, the contact page, and then nothing? That’s the gap this tab was built to show you. You don’t need to win any rankings argument to make it worth ten minutes. Open the tab, filter for No schema, and look at the number.

Then fix the pages you forgot, and leave the pages you hand-tuned alone.