Elementor content is not a POM MCP authoring format
POM AI’s authoring resources and validators support POM classic builder shortcode content. They do not expose an Elementor schema, document tree, validator, or safe Elementor write tool.
Elementor pages commonly depend on structured editor data outside the visible post_content. Updating only rendered HTML or treating that data as generic post meta can desynchronize the editor and frontend. POM AI also blocks sensitive or private meta-key patterns rather than providing unrestricted access to editor internals.
What MCP can still do
The client may use ordinary WordPress read tools to identify the page, title, status, excerpt, or public content returned by WordPress. It can prepare replacement copy or media as a draft for a human editor. It must not claim that it has preserved Elementor sections, widgets, responsive controls, or global styles.
Safe handoff
For an Elementor layout change:
- identify the exact page and desired outcome;
- prepare approved text and Media Library attachments;
- make the structural edit in Elementor;
- publish through the normal editor workflow;
- optionally reconnect and read supported WordPress fields for confirmation.
Do not convert an Elementor page to POM shortcode markup unless the user explicitly requests a planned migration and a separate supported migration process exists.
Related guides: POM builder resource, edit an existing page, and unsupported operations.