Page buildersFree + Pro
GoBuildWP Elementor integration: requirements and coverage
The GoBuildWP Elementor integration reference groups calls by what they change: one page's _elementor_data document, the active kit inherited by other pages, a library or snippet post, or a file on disk. Free includes elementor-set-content for complete element-tree writing as well as individual edits. Pro adds compact higher-level composition, templates, popups, forms and shared design controls. Each group states its reach and recovery limits. Start with the Elementor MCP guide (/mcp-for-elementor) for setup and the workflow, then use the ability reference for the exact schema.
Give the pricing section our card class, and make sure visitors see it, not a cached copy.
wppilot/elementor-get-contentReadReturns the pricing page's skeleton with element ids, so the three card containers are addressed by id rather than by position.
wppilot/elementor-list-global-classesReadLists the kit's classes; the card class already exists.
wppilot/elementor-apply-global-classWriteAttaches the class to each card inside _elementor_data and records a before-image of the page.
wppilot/elementor-clear-document-cacheWriteOnly needed because the cards sit in a saved section template: each nested template caches its HTML separately from the page around it.
- Edition
- Free 18 + Pro 52
- Abilities
- 70
- Requires
- WordPress 6.9+, PHP 8.0+, Elementor 3.6.0+, Elementor (atomic elements only) 4.0.0+
Requirements and coverage
What this integration needs, and where the detail lives
- Edition
- Free (18) and Pro (52)
- WordPress and PHP
- 6.9+ and 8.0+
- Version floor
- Elementor 3.6.0+
- Version floor
- Elementor (atomic elements only) 4.0.0+
- Abilities
- 70, listed in the reference
Elementor MCP guide: setup and worked tasks Elementor ability reference (elementor-core) Elementor ability reference (elementor)
Data model
Four places an Elementor site keeps its design
A page's layout is JSON in a private custom field, _elementor_data, next to _elementor_page_settings for document options and _elementor_edit_mode, which marks the post as builder-owned. The JSON is a nested list of elements, each carrying an id, an elType and a settings object; classic widgets, containers and v4 atomic elements share that one array. After any write the free plugin deletes only that document's compiled CSS, its atomic style cache and Elementor Pro's _elementor_element_cache, then fires clean_post_cache, so the next request renders from the tree that was just changed.
Site-wide tokens are not on the page at all. Global classes, variables and the v3 system_colors, custom_colors and custom_typography lists are post meta on the active kit, which is itself a post. Theme Builder parts and popups are elementor_library posts with their display rules in _elementor_conditions, and Custom Code snippets are elementor_snippet posts holding _elementor_code, _elementor_location and _elementor_priority.
One Pro call leaves the database: an atomic widget is PHP written into mu-plugins. That split is the blast radius: a post_id means one document, the kit means every page bound to the token.
Worked example
Restyling one section and proving it reached the live page
Expected outcome to verify on the installed stack; this sequence has not been recorded as a runtime test.
The cards pick up the shared class and the page renders it on the next request. If the class had been missing, creating it would have been a kit write reaching every page, which is a different decision from styling one section.
Finish with an actual front-end check. Configured cache plugins may respond to post-cache hooks; verify each installed layer instead of assuming a particular purge.
elementor-get-contentReturns the pricing page's skeleton with element ids, so the three card containers are addressed by id rather than by position.
elementor-list-global-classesLists the kit's classes; the card class already exists.
elementor-apply-global-classAttaches the class to each card inside _elementor_data and records a before-image of the page.
elementor-clear-document-cacheOnly needed because the cards sit in a saved section template: each nested template caches its HTML separately from the page around it.
Limits
Where Elementor writes stop or cannot be undone
- The module registers against Elementor 3.6 or later; atomic elements, global classes and variables need Elementor 4.0.
- Theme Builder parts, popups, forms and Custom Code exist only when Elementor Pro is installed. The forms calls say so plainly on a site without it rather than writing a partial record.
- An atomic widget needs a writable mu-plugins directory. On a read-only filesystem the call fails before writing, and once written the file can only be removed by hand.
- Clearing the document cache is scoped to the ids you pass. There is no site-wide purge in this module; that belongs to your cache plugin.
Other plugins
Sharing a site with other Elementor tooling
- Elementor's own MCP edits atomic elements in the same _elementor_data field. From GoBuildWP Free 1.18.0, its writes are recorded on the Changes screen too: element, composition and page-settings edits can be rolled back, while a page it creates, a component or a default style is recorded as irreversible. Those writes skip GoBuildWP's confirmation unless the Other MCP servers setting is switched on, which needs WordPress 7.1.
- Post writes that fire clean_post_cache can notify page-cache plugins listening for that hook. Check the installed plugin's purge behavior and the affected URL afterwards; a WordPress cache-clean hook alone does not establish public freshness.
Questions
Elementor questions
Which Elementor abilities change every page at once?
Anything that writes the active kit: global classes, variables, v3 colours and typography, and compile-spec. They are stored on the kit post, so one edit reaches every element bound to the token. Rolling one back restores the kit post as it was.
The agent says the edit saved, but the page looks the same. Why?
Usually Elementor Pro's element cache on a template nested inside the page. A write drops the cache for the document it edited, but each nested template keeps its own. Pass the template ids to elementor-clear-document-cache and reload.
Can an agent start a page over without breaking its links?
Yes. elementor-delete-page-content empties the document but keeps the post, its title and URL. By default the post stops being an Elementor page; keep_builder_mode leaves an empty canvas to build into. It needs confirmation and can be rolled back.
Where these facts come from
GoBuildWP behaviour is taken from the plugin source and the ability reference; third-party details from the vendor documentation below, checked by the GoBuildWP team.
Elementor is a separate product; no partnership or endorsement is implied.