GoBuildWP

Page building use case

Edit Elementor pages with Claude, in the editor's own data, not pasted HTML.

Pasting a page into Claude gets you HTML that Elementor does not store. GoBuildWP Free gives Claude the element tree itself: it reads a compact skeleton, finds the exact widgets you describe, edits their settings through Elementor's controls, and every write is checked against the live widget schema before it is saved.

GoBuildWP Free + Pro, Works in Claude Desktop, Runs under Production Safe, Pricing

Illustrative ability sequence for GoBuildWP Free 1.18.6 and Pro 1.12.4. IDs, results and recovery outcomes are examples, not a recorded client or WordPress test. Select Read Only explicitly for the initial reads; Production Safe is the default. Connection management requires manage_options on a single site or superadmin on multisite.

The problem

Small Elementor edits are where the hours go

The same button label on eleven pages, a heading that should be an H2, a pricing column duplicated for a new plan. Each one is a minute in the editor, and together they are an afternoon of clicking through panels.

Through this configured connection, Claude can address supported widgets by ID, change one setting and leave the rest alone. A wrong value does not half-save: validation rejects the call and hands Claude the widget's real controls so it can correct itself.

What Claude Desktop can do here

  • Read any Elementor document as a compact skeleton, then open one widget's full settings on demand
  • Find every element matching a widget type, a setting value or visible text
  • Edit, add, move, duplicate, reorder and delete elements, with fresh ids on every copy
  • Change page settings, and check whether the site is ready for Elementor v4 atomic editing
  • Open the draft's preview in its own browser, when the client has a browser tool that is already signed in to the site

What it cannot do

  • Create Theme Builder templates, popups, global classes or display conditions with Free's Elementor abilities. Those are among Pro's 52; the one Free exception is the site header, which build-site-header saves when Elementor Pro is installed
  • Save a setting that is not a real control on that widget. Validation refuses the whole write
  • Judge spacing, animation or the mobile layout from the tree alone. Someone has to look
  • Edit pages made with another builder. Elementor abilities only work on Elementor documents

Why pasted output breaks

Why raw REST output breaks Elementor layouts

Elementor does not keep a page's layout in the post content. Its developer documentation says the page data and layout are stored as JSON in WordPress post metadata, a private custom field in the wp_postmeta table. The key is _elementor_data, and GoBuildWP's own code only treats a page as an Elementor page when a second key, _elementor_edit_mode, is set to builder.

That JSON is a recursive tree. Each element carries an id, an elType such as container, section, column or widget, its settings and a nested elements array; widgets add a widgetType. HTML that Claude sends through the REST API's content field lands in post_content, outside that tree, so there is no element for the widget panel to select and nothing Elementor renders from.

Writing the meta directly is not enough either. Elementor keeps a compiled stylesheet per page, and Elementor Pro caches rendered element HTML in post meta and checks that cache before its render filters run, so a write that leaves either in place can succeed and still not show. GoBuildWP's Elementor writes clear that one page's CSS and element cache after saving, and the generic update-post ability refuses builder keys such as _elementor_data and points to the Elementor abilities instead.

Sources: Elementor developers: data structure (seen 29 September 2026); Elementor developers: page content (seen 29 September 2026); GoBuildWP Free source: Elementor page writes.

The prompt

The prompt to paste into Claude Desktop

Five precise edits in one message. Claude reads the skeleton and the targeted elements first; request size depends on the page and client.

  • The compact skeleton keeps Claude's context for the edit instead of for motion-effect settings.
  • [CONFIRM] tells Claude to leave the value for you rather than make one up.
  • Asking for the changed ids gives you something exact to check in the editor and in the ledger.
Paste into Claude DesktopEdit the URLs and brackets
On the Pricing page (draft), make these edits in Elementor:
1. Read the page as a compact skeleton first. Do not dump every setting.
2. Find every button whose text is "Get started" and change it to "Book a demo". Keep the links.
3. The heading "Plans for every team" should be an H2, not an H1.
4. Duplicate the Pro plan column and change its title to "Agency", price [CONFIRM].
5. Do not change styles, spacing or any other widget.
6. Give me a preview link and list the element ids you changed.

Under the prompt

The abilities Claude Desktop will call

Registered GoBuildWP abilities, each with its own schema and permission check. The live ability list on your site is the final word; the tool map lists every group.

  • elementor-check-setup

    Elementor and Pro versions, v4 atomic availability, kit values, configuration issues

    ReadFree
  • elementor-get-content

    Compact skeleton by default; one element's full settings on request

    ReadFree
  • elementor-find-elements

    Element ids matching a widget type, a setting value or text

    ReadFree
  • elementor-get-widget-params

    Only the settings a build actually uses, not all 186 controls of a heading

    ReadFree
  • elementor-edit-element

    Merges new settings; unknown controls abort the write with the schema inline

    WriteFree
  • elementor-duplicate-element

    Copies a subtree with fresh ids so styles do not collide

    WriteFree
  • elementor-delete-element

    Removes an element and its children

    Needs confirmationFree
  • get-page-view-link

    The preview URL and widths to check; flags when a draft needs a signed-in browser

    ReadFree
  • elementor-apply-global-class

    Attaches a v4 global class so the page follows your design system

    WritePro

Safety and recovery

Edits you can trace to an element id

Safety profile
Production Safe. Element edits are ordinary content writes; Read Only is for looking around first.
Change ledger
Element edits are recorded against the document with the ability, the element and the acting credential. capture-page can attach a screenshot to the entry, so a change has a picture beside it.
Rollback
Since Free 1.15.0 the ledger keeps a copy of the page before each element edit, so an edit can be rolled back from its entry with or without Pro; with Pro active, Pro's own Elementor capture is used. Before 1.15.0, Free alone recorded these edits without a way back. After a rollback, open the page in Elementor once to confirm the tree looks the way you expect.
Change ledgerExample entries
  • #1402Button text on 3 elements, PricingRollback available for this supported edit
  • #1403Heading tag H1 to H2, PricingRollback available for this supported edit
  • #1404Duplicate column 9b41c0, PricingScreenshot attached

Things the tree does not tell you

  • Elementor Pro caches rendered elements. When a change does not show, Free's elementor-clear-document-cache clears that cache for the page so it is rebuilt on the next view.
  • Classic v3 widgets and v4 atomic elements take different settings. elementor-audit-atomic-readiness shows which kind a page uses.
  • If someone has the page open in the Elementor editor, their next save can overwrite an agent's change. Edit pages nobody is editing.
  • Passing schema validation checks supported controls and values. Reopen the native editor and inspect desktop/mobile output; validation alone does not prove complete structural or visual correctness.

How profiles, confirmations and rollback fit together: safety profiles and the change ledger.

Setup

Connect Claude Desktop

Claude Desktop works with a live site or one running on your own machine, which makes it a good fit for trying edits on a local copy first.

Free

GoBuildWP Free includes 18 Elementor abilities: read documents, check schemas, find, edit, add, move, duplicate and delete elements, and page settings.

Pro

Pro adds 52 more: elementor-build-page, which composes a page from one nested description (Free already writes a whole page tree with elementor-set-content), Theme Builder templates and conditions, popups, forms, global classes, variables and custom code.

Need every page rather than one widget? The site-wide brief writes header and footer templates, page layouts, a menu and a contact form: build a business website with AI on WordPress.

  1. Install GoBuildWP Free

    No Pro licence is needed for these edits. Turn the abilities on and set the site domain on the settings screen.

  2. Add a custom connector

    In Claude Desktop: Settings, then Connectors, then Add custom connector. The .mcpb bundle from the Connect screen is the no-typing alternative.

  3. Sign in with OAuth

    Approve the connection in WordPress as an administrator-level user (manage_options, or a super admin on multisite); GoBuildWP refuses lower roles. Limit the connection with its scope and profile ceiling instead.

  4. Check what Claude sees

    Ask Claude to run elementor-check-setup and list your Elementor pages. Nothing changes.

  5. Edit a draft copy first

    Review the copy in Elementor and a browser. Before any live edit, re-read the original's IDs, settings and shared dependencies and approve a fresh diff. Do not replay draft or staging calls unchanged.

FAQ

Questions about how to edit Elementor pages with Claude

Is Elementor editing really free?

Yes. GoBuildWP Free includes 18 Elementor abilities for reading documents, checking schemas, editing elements and writing a full page tree. Pro adds 52 for building a page from one nested description, Theme Builder templates, popups, forms and global styles.

Does it work alongside Elementor's own MCP?

They are separate servers with separate tools, and a client can connect to both, but we have not tested every combination, so try it on staging first. Elementor's official MCP focuses on v4 atomic pages; GoBuildWP edits classic widgets and atomic elements, and its readiness audit tells you which kind each page is built from. Do not let both edit the same page in one session, because either can overwrite a change the other just saved.

Can Claude see the page it edited?

If your Claude client has a browser tool, get-page-view-link gives it the preview URL; for a draft, that browser has to be signed in to the site already. Otherwise capture-page asks the site to take a screenshot while a wp-admin tab is open.

Will it break my layout?

Writes are validated against each widget's real controls, and a rejected value writes nothing. The design judgement is still yours: check the page at desktop and phone widths before publishing.

Try it on staging first.

Install the free plugin, connect Claude Desktop, and run the read-only half of this prompt before anything on the site changes.