In my last post, I explored the idea of creating a schema layer on top of AI-generated HTML.
The more I think about it, the more I believe the schema is the interesting part.
Not because it helps WooCommerce or Jetpack Forms integrate with AI-generated pages, although it does.
What’s interesting is everything that becomes possible after WordPress understands what a page actually contains.
From HTML to meaning
Today, an AI-generated page might look like this:
<h1>Build Better Websites</h1>
<p>Create pages with AI</p>
<a href=”#”>Get Started</a>
A person immediately recognises this as a hero section.
WordPress doesn’t.
But if the plugin creates a schema like this:
{
“hero”: {
“headline”: “Build Better Websites”,
“description”: “Create pages with AI”,
“cta”: “Get Started”
}
}
suddenly WordPress understands what it’s looking at.
The page is no longer just HTML.
It has meaning.
AI editing gets much safer
Today, asking AI to improve a page often means giving it a chunk of HTML and hoping it doesn’t break anything.
With a schema, an AI agent can work at a much higher level.
Instead of:
Rewrite this HTML
it becomes:
Improve the hero headline
or
Generate three alternative CTAs
The agent edits content, not layout.
The design stays intact.
Site-wide content changes become possible
Once content is structured, you can start asking interesting questions.
For example:
Change every CTA on my website from “Get Started” to “Book a Demo”
Or:
Find every page that doesn’t have a testimonial section
Or:
Show me all pages missing a lead generation form
The plugin knows what those things are because it understands the schema.
Translation becomes easier
Translation plugins currently spend a lot of effort working out what content should be translated.
With a schema, they already know.
{
“headline”: “…”,
“description”: “…”,
“cta”: “…”
}
Translate the content.
Leave the design alone.
Simple.
Better search inside WordPress
Imagine searching for:
Show me all pricing sections
Or:
Find every testimonial on the site
Or:
List every product page
The plugin isn’t searching HTML.
It’s searching meaning.
That’s a very different capability.
Themes become less important
One thing that fascinates me is the separation of content and design.
Today they’re often tangled together.
With a schema layer you end up with three distinct parts:
Content
↓
Schema
↓
Design
The content exists independently.
The schema describes what it is.
The design controls how it looks.
That opens the door to redesigning pages without losing structure.
Agents start to make sense
This is the area I find most interesting.
Imagine an AI agent asking:
Show me all hero sections.
Or:
Find pages with weak calls to action.
Or:
Generate alternative versions of every testimonial.
Those are difficult problems when everything is trapped inside HTML.
They’re much easier when the content is structured.
The agent doesn’t need to scrape markup.
It simply works with the schema.
Maybe the schema is the product
When I started building my Visual HTML Editor, I thought the challenge was making AI-generated HTML editable.
Now I’m starting to wonder if that was only the first step.
Perhaps the bigger opportunity is helping WordPress understand AI-generated HTML.
AI creates the design.
The plugin creates the schema.
WordPress and plugins provide the functionality.
The schema becomes the bridge between them.
And once that bridge exists, a lot of interesting things start to open up.
Leave a Reply