Imagine asking your WordPress site:
Which services don’t have testimonials?
Which products mention pricing but don’t explain delivery?
Summarise everything we offer for beginners.
Show me every product launch we’ve announced in the past two years.
Generate a newsletter from this month’s company announcements.
Today, WordPress can’t answer those questions.
It can store content.
It can display content.
It can help you create content.
But it doesn’t really understand the content.
And that’s true whether you’re running a five-page brochure site, a WooCommerce store, a university website, or a large publisher.
The Gap Between Content and Understanding
Consider these two headlines:
WordPress.com launches a new AI website builder
Apple acquires Acme AI
To WordPress, they’re largely the same thing.
A title.
Some paragraphs.
A featured image.
A few categories and tags.
To a human, they’re completely different.
One is a product launch.
One is an acquisition.
The meaning is obvious to us, but largely invisible to the platform.
Blocks Added Structure, Not Understanding
One of Gutenberg’s biggest achievements was adding structure.
WordPress understands headings, buttons, galleries and columns.
But structure and meaning are not the same thing.
For example:
Heading
Paragraph
Button
describes structure.
Product Launch
Executive Quote
Customer Testimonial
Special Offer
describes meaning.
That’s a different layer entirely.
AI Makes a Semantic Layer Possible
Historically, creating this kind of understanding required manual effort.
Editors added tags.
Publishers built taxonomies.
Developers created custom fields.
AI introduces another option.
Given a piece of content, AI can often identify:
- Product launches
- Acquisitions
- Reviews
- Events
- Tutorials
- Services
- Offers
- Testimonials
and create a semantic representation automatically.
Not perfect.
Not authoritative.
But useful.
Content Starts Becoming Knowledge
This is where things get interesting.
A publisher could ask:
Show me every acquisition story from the last 12 months.
Generate a timeline of AI product launches.
Create a newsletter from this month’s company announcements.
A WooCommerce store could ask:
Which products don’t mention delivery times?
Which products don’t have reviews?
Create a comparison table for all products under £20.
A consultant could ask:
Which services don’t have case studies?
Which testimonials mention training?
Summarise my experience working with agencies.
A yoga studio could ask:
Which classes don’t have testimonials?
Which offers are no longer featured anywhere on the site?
Summarise everything we offer for beginners.
The content hasn’t changed.
WordPress simply understands more about it.
Core Provides the Infrastructure
If WordPress ever explored this, I don’t think Core should define what every piece of content means.
Instead, Core could provide:
- A semantic schema registry
- Storage
- Revision history
- A standard API
- Hooks for AI and other extraction systems
Plugins would then teach WordPress about specific domains.
WooCommerce could register:
- Products
- Reviews
- Offers
An events plugin could register:
- Events
- Venues
- Speakers
An education plugin could register:
- Courses
- Lessons
- Learning outcomes
A news plugin could register:
- Product launches
- Acquisitions
- Interviews
Core provides the framework.
Plugins provide the expertise.
A Product Launch Is More Than a Page
Consider this headline:
WordPress.com launches a new AI website builder
Most systems see a page.
A semantic layer might see:
{
“content_type”: “product_launch”,
“organization”: “WordPress.com”,
“product”: “AI website builder”
}
Now WordPress understands what the content is actually about.
That understanding can power search, recommendations, AI assistants, analytics, content audits, publishing workflows, newsletters, and future experiences we haven’t even imagined yet.
From Content Management to Meaning Management
Posts were about content.
Custom post types were about structure.
Blocks were about composition.
A semantic layer would be about understanding.
Not how content is rendered.
Not how content is stored.
But what the content actually means.
For most of WordPress’s history, we’ve focused on helping people create and publish content.
The missing layer might be helping WordPress understand it.
Leave a Reply