WPBakery splits a page’s words across two places. Running text in a Text Block is the element’s inner content. A Custom Heading’s text, a button’s label and its link are settings stored inside the shortcode’s opening tag. That split is why a generic search and replace either misses a button label or mangles the shortcode around it.
This prompt has the agent check where the words live before it picks the tool.
On our [About] page (id [18]) I want the heading [Our story] to read[How we work], and the button at the bottom to say [See our services]and link to [/services/].
Read the page with wpbakery-get-page-content and include_structure, andfind both elements. For each, tell me its index, tag and where its words arestored. Look each tag up with wpbakery-list-elements, and tell me the settingname that holds the heading text, the button label and the button link, andwhether wpbakery-update-element can write it.
Show me every old value beside the new one and wait for my go. Then change thesettings with wpbakery-update-element, using the index and the tag andfingerprint from the outline, one element per call, reading the outline againbetween calls. If any change is plain body text in a text block instead, usewpbakery-replace-text for it. Give me the restore_revision_id from eachwpbakery-update-element write. wpbakery-replace-text returns none, so beforeit runs, list the page's revisions with list-revisions and note the newestone, then tell me which revision to restore if I want that change undone.Read the page back at the end to confirm.Why this is safe to run
The outline and the settings lookup are reads. The agent finds out which setting holds the words, and whether the tool may write it, before it proposes a change. A link goes in as url, title, target and rel, the form WPBakery’s own link field uses, rather than as a raw encoded string.
Update a WPBakery element is a single-element write. It refuses a stale index or fingerprint, a setting the element does not have or that cannot be written, an already encoded value, and anything that would add or remove an element. Square brackets, percent-encoded brackets and data-* attributes in body text need a user who may post unfiltered HTML, and even then text that would add an element is refused. WPBakery’s own save filter still runs.
When revisions are on, an element update returns restore_revision_id (a text replace does not, so its restore point comes from List revisions) for Restore revision, which now works on WPBakery pages while WPBakery is active. Every tool here starts off, runs as the user you bound the agent to, and is recorded in the Activity Log.
Already connected? Ask your agent for the “change a heading or button on a WPBakery page” recipe, or tell it which words to change, and it runs the same flow on your own site.