AI page building in WordPress: where does the AI actually write?

Every AI page tool can turn a prompt into a layout. That part is solved, and honestly it stopped being impressive about a year ago. The question nobody asks in the demo is the boring one that decides everything later: when the AI finishes writing, where did the output actually go?

Not contractually. Architecturally. Nobody's terms of service is out to trap you. The storage format does it without anyone having to be a villain.

I prefer that framing because it survives an argument. Accuse a vendor of wanting to hold your page hostage and you'll get a rebuttal, probably a fair one. Elementor's own page pushes back on the lock-in idea directly, calling its output "not a locked export" (elementor.com, checked 2026-08-10). Fine. Take them at their word.

The architecture underneath doesn't change either way: Elementor content is rendered by Elementor. Divi's layout generation happens inside the Visual Builder (help.elegantthemes.com, checked 2026-08-10). That's not an accusation, it's a dependency. Dependencies are fine. Accidental ones are less fine.

So ask any AI page tool one question: if I switch this off tomorrow, what's left in the database? Ask it on day one. It's a much cheaper question to answer then than after you've built forty pages on top of the answer.

Yes, and this is the part the whole category tends to skip. It's also the reason this plugin exists.

Generating a page is the easy half. Day 40 is the hard half. The AI isn't in the room, nobody remembers the prompt, and someone in marketing needs to change one headline before a 3pm meeting. If your answer is "ask the agent again" or "open the HTML," congratulations: your marketing page is now a developer ticket.

Every section carries a content_fields_schema, which declares a type, label and description per field. That schema builds Content Mode, where an editor gets labelled inputs (text, WYSIWYG, image picker, icon picker, colour, select) and never has to look at markup. Developers still get Advanced Mode with raw HTML, CSS, JS and per-section dependencies. One section, two audiences, nobody filing a ticket.

The plugin also nags the AI about this, which I enjoy more than I expected. Since v0.21.1 it returns a low editability warning when a section gets saved as mostly hardcoded text with barely any editable fields, pushing the agent to pull that copy into real fields instead of welding it into the HTML. Left to its own devices an agent will happily hand you a gorgeous, completely unmaintainable wall of markup. This is the thing that stops it.

Like this. What follows is a real section from the documentation hub on this site, pulled straight out with get_page. I didn't tidy it up for the post.

template_html — plain HTML with {{placeholder}} markers:

<section class="aid-phead">
  <div class="aid-phead__orb"></div>
  <div class="aid-phead__inner">
    <span class="aid-phead__badge">{{badge}}</span>
    <h1 class="aid-phead__title">{{title}}</h1>
    <p class="aid-phead__desc">{{description}}</p>
  </div>
</section>

content_fields — the values, kept separate from the markup:

{
  "badge": "Documentation",
  "title": "Documentation",
  "description": "Everything you need to install NoLeemits AI Design, connect an AI assistant to it, and hand the result to someone who has never seen the plugin before."
}

content_fields_schema — what makes it editable by a non-developer:

{
  "badge":       { "label": "Eyebrow",          "type": "text" },
  "title":       { "label": "Page title (H1)",  "type": "text", "required": true },
  "description": { "label": "Intro",            "type": "textarea" }
}

scoped_css — styling that belongs to this section and nothing else:

section.aid-phead {
  background: #1a1a2e;
  padding: 4.5rem 5% 4rem;
  position: relative;
  overflow: hidden;
  font-family: 'Inter', sans-serif;
  text-align: center;
}
h1.aid-phead__title {
  font-family: 'Space Grotesk', sans-serif;
  font-size: clamp(1.85rem, 3.6vw, 2.7rem);
  font-weight: 800;
  color: #fff;
}

There's no fifth thing. No serializer, no block grammar, no builder runtime quietly resolving that into something else on the way to the browser. {{title}} gets swapped for the value of title, and the result ships. That's the trick. There isn't a bigger one hiding behind it.

Site-wide consistency comes from design tokens, CSS custom properties the agent reads before it writes a single line. The live values on this site:

{
  "colors":  { "primary": "#667eea", "secondary": "#764ba2", "accent": "#f093fb",
               "background": "#ffffff", "foreground": "#1a1a2e" },
  "fonts":   { "heading": "'Space Grotesk', sans-serif", "body": "'Inter', sans-serif" },
  "spacing": { "section-y": "80px", "section-x": "5%", "gap": "2rem" },
  "shape":   { "radius": "12px", "shadow": "0 4px 24px rgba(0,0,0,0.06)" }
}

Change --ppd-primary once and every section that referenced it follows along. This is the thing standing between you and eleven subtly different shades of blue scattered across your site, each one confidently described as "the brand colour."

The best version of this argument isn't the code sample though, it's the site you're reading it on. noleemits.com/ai-design/ was built this way, by an AI agent, through this plugin. View source and see for yourself. It's just HTML.

• It's not a drag-and-drop canvas. If nudging boxes around with a mouse is your idea of a good afternoon, you want a page builder, and you should go get one. This is for people who'd rather describe a change than hunt for it.
• Uninstalling stops the rendering. Covered above. Run Convert to Page first, and remember that Convert to Page and Restore both only go one direction.
• Client support is narrower than "any AI." Three tested clients. That's the claim, and it's staying that size until I've tested more.
• It's not an SEO plugin. It emits clean semantic HTML and deliberately stays out of Yoast, RankMath and SEOPress's way. The built-in LocalBusiness JSON-LD is opt-in and tells you when it spots a conflict.
• It's paid, with no free tier. Annual, with a 14-day trial and no credit card required. Kicking the tyres beats reading about the tyres.

Do I need an AI account to use this plugin? Nope. Content Mode and Advanced Mode work perfectly well with no AI connected to anything. The MCP server is entirely optional. Switch it on only if you want an assistant writing pages for you.

Will my content survive if I uninstall the plugin? The data survives, since sections live in post meta as a JSON-serializable array. It stops rendering, though. Run Convert to Page first and the section gets baked into a regular WordPress page with its CSS intact. That conversion only goes one way, so do it deliberately.

Does it work with my theme? Yes. You get two render modes: full, where the plugin owns the whole <body> and supplies header and footer from global sections, and content, where your theme keeps its header and footer and the plugin only fills the content area. Set it per post type or override it per post. Block themes work fine, archive templates included.

Does it work alongside Elementor, Divi or Bricks? Yes, by getting out of the way. Spot a builder on a post and the plugin disables itself for that post automatically. You can also switch it off per post type. No turf war over who owns the page.

Which AI assistants is it actually tested with? Claude Desktop, Claude Code and the Anthropic SDK. It speaks MCP over Streamable HTTP, so other MCP clients should be fine. They're unverified though, and until somebody builds a real page through one, "should" is the only honest word for it.

Architecture described here was verified against the plugin source on 2026-08-10. Version-specific figures are deliberately kept out of this post and live on the release notes instead, which are generated from the plugin. Competitor claims cite each vendor's own current page, with the date checked. Where a claim couldn't be sourced from a vendor page, it isn't in this post.