The launch banner from spring is still at the top of the home page, and the FAQ you want people to see sits below three other sections. On a builder page, fixing that usually means dragging blocks around in the visual editor and hoping nothing gets nested in the wrong column.
This prompt does it as a short list of single moves and removals, each one confirmed and each one leaving a restore point.
I want to tidy the [home] page (id [5]). Take out the [spring launch banner]section, and move the [FAQ] section so it sits directly [after] the[testimonials] section.
Tell me which builder owns the page, then read it with the page content tooland include_structure. List the top-level sections in order with their index,tag and a few words of their text, so we can name them precisely.
Make no change until I approve the plan. Then do one change per call: firstthe move, then the removal, each with the index, tag and fingerprint from theoutline and the page fingerprint from the last read or write. Read the outlineagain after each change, because indexes shift. If a removal is refusedbecause there would be no way back, stop and tell me why. At the end, listevery restore_revision_id in order.Why this is safe to run
The plan is built from a read, so you approve moves and removals named by index and by a few words of their content, and the agent cannot act on a guess. Every write checks the page fingerprint and the element’s own fingerprint, so a page that changed in the meantime is refused with nothing saved.
Each builder’s nesting rules apply to a move: a container takes rows, a row takes columns, and a move into the element itself or one of its own children is refused. A removal takes the element and everything inside it and leaves every other byte of the page as it was. On WPBakery the fingerprint covers the whole element, so a section that gained content since the read is refused, and the page’s generated CSS is rebuilt after each change.
Remove is the riskier of the two, so the plugin makes it prove there is a way back first. Each write returns restore_revision_id, and Restore revision brings the page back to before that change. These edits are not in the Changes tab. All the tools here start off, are checked against the user you bound the agent to, and land in the Activity Log.
Already connected? Ask your agent for the “reorder or remove sections” recipe, describe the order you want, and it runs the same one-change-at-a-time flow on your own site.