You describe the page, the AI builds it. Your SEO speaks the same language
On September 23 Elementor opened its editor to AI assistants. With the groundwork laid by WordPress 7, a web designer can describe a page and find it built as a draft, with their own design system. One question remains: who takes care of that page's SEO? The answer lives in the same conversation.
Published: September 25, 2026 · AI SEO News
Elementor MCP: the editor becomes a tool your assistant can use
After a one-week beta, Elementor MCP has been official since September 23, 2026. It connects an Elementor site to Claude Code, Claude Desktop, Codex, Cursor and other clients that speak MCP, the protocol AI assistants use to work with external tools. The difference from "AI that writes code" is real: the assistant doesn't produce HTML for you to paste, it works with the editor's native elements, the same ones you would use.
Pages and layouts
It builds full pages with content and styling in one pass, or reworks an existing layout instead of just stacking new blocks at the bottom.
Your design system
It applies the site's global classes and variables, responsive breakpoints included, so the result stays consistent with every other page.
Theme parts and components
Headers, footers, archives, popups and reusable components: the parts that usually mean a trip to the Theme Builder are now reachable from chat.
Dynamic content
It binds elements to post fields, taxonomies and custom fields, so a template page fills itself in.
Two of Elementor's choices deserve a mention. Everything the assistant generates is saved as a draft, never published. And the connection uses a WordPress application password, which Elementor creates for you along with a setup prompt to paste into your assistant.
Why now: WordPress 7 gave every plugin the same socket
Elementor MCP isn't a one-off, it's the result of work done in WordPress core. Version 6.9 introduced the Abilities API: a registry where every plugin declares what it can do, with which inputs and which permissions. WordPress 7.0, released on May 20, 2026, added the AI Client and a Connectors screen for OpenAI, Anthropic and Google. The official MCP Adapter plugin, which stays outside core, turns those abilities into tools an AI assistant knows how to call.
In practice this is a standard socket. Elementor registers its abilities, AISA registers its own, and WooCommerce, SEO plugins and form builders do the same: one assistant, connected with your user's permissions, sees everyone's tools and chains them in a single conversation. Neither plugin needs to know the other exists.
What changes for people who design websites
Before Build by hand, chase the SEO later
- Wireframes, then hours of dragging sections and widgets
- Placeholder copy that arrives late and breaks the layout
- SEO at the very end, often by someone else, sometimes never
- Pages live without a meta description, without an H1, with images missing alt text
Now Describe, review, refine
- A precise brief becomes a draft built with your design system
- Time moves to the review: hierarchy, rhythm, details
- SEO happens in the same conversation, before publishing
- You publish, after looking at the page in the editor
The web designer's value doesn't disappear, it moves. A well-built design system matters more, because it's the grammar the assistant will speak. Writing a good brief matters more, because it's the new wireframe. And a sharp eye in review matters more, because a generated draft is a great starting point and a poor finish line.
A page built by AI is born without SEO. That's where AISA comes in
Elementor MCP builds the page, it doesn't optimize it. A freshly generated draft usually has no SEO title, no meta description and no focus keyphrase, and sometimes no H1 because the headline ended up in a text widget. We've seen it on a real site running WordPress 7.1, Elementor 4.3 and AISA 2.0.1, where Elementor's tools and AISA's tools show up side by side in the same connector.
AISA SEO Pilot MCP (called SEO Commander inside the plugin) brings AISA's SEO tools into that same conversation. The workflow becomes:
Build with Elementor MCP
"Create the page for service X with a hero, three benefits, an FAQ and a contact block, using our classes." Result: a draft.
Audit with AISA
The on-page audit checks keyphrase, title, description, H1, subheadings, image alt text, the area you serve and the social image. It's in the free plugin.
Optimize
Title, description and keyphrase generated from the site's Brand Context and Writing DNA, written into the SEO plugin you already use: Yoast, Rank Math, AIOSEO, SEOPress or AISA on its own.
Fix
Failed checks are fixed in one call, including the keyphrase in the H1 inside Elementor's heading widget. AI Vision writes image alt text by actually looking at the pictures.
Verify and publish
A second audit, including the public page as visitors receive it. Then you look at the draft in the editor and publish it yourself.
Six reasons it isn't a bolt-on
It reads the real text
AISA reads the text inside Elementor's widgets, not the empty content WordPress sees underneath a builder page.
It writes where you work
No duplicate fields: the meta tags land in your SEO plugin, exactly where you've always found them.
Same permissions
The connection uses an application password: the assistant can only do what your user can do. API keys never leave the site.
Backup before any change
Before editing content AISA saves a revision and, with Elementor, a backup of the builder data.
Your brand's voice
Brand Context and Writing DNA make titles and descriptions sound like the rest of the site, in the page's own language.
In bulk too
For dozens of pages there's background optimization: you get a job ID and ask how it's going whenever you like.
A typical conversation
"Create a draft for the HR Consulting for SMEs page, using our classes and an FAQ section. Then run AISA's SEO audit, optimize the title and description, fix the failed checks including the H1, and write the image alt text. Finally, audit it again and tell me what's left."
One sentence, two plugins, not a single wp-admin tab opened. You read the summary, open the draft in Elementor, fix what your eye catches and the assistant doesn't, and publish.
What to know before you start
- Elementor MCP is two days old: expect it to change quickly, and try it on a test or staging site before production.
- AISA's reading tools are free; the ones that write or work in volume come with AISA Premium. Diagnosis is free, execution is Premium.
- Over MCP the assistant works page by page: it sees the page it's building very well, conflicts between pages less so, such as two pages targeting the same keyphrase. For the big picture there's still the SEO Doctor.
- Claude connects with the application password. ChatGPT requires OAuth, so you need a connector such as Easy MCP AI.
- Always look at a generated draft. The assistant has no taste, it has instructions: yours.
Build with Elementor, optimize with AISA, in the same sentence
The reading tools are in the free plugin: connect them to your assistant and ask for an audit of the next page you build. The step-by-step guide explains how to create the application password and what to tell Claude.
Try it freeGuide: Use AISA from Claude · Your site's SEO, at Claude's command · Five things to ask your AI
Sources: Elementor MCP announcement on the Elementor blog (September 23, 2026), WordPress Developer Blog on the MCP Adapter, WordPress 7.0 release notes. Third-party features and requirements may change: checked on September 25, 2026.