At some point the same block of content, a signup callout, a disclaimer, a promo strip, gets pasted into a dozen pages by hand. Then the wording changes, and now you are hunting for every copy and fixing each one, missing three. A synced block solves it: edit once, and every page that references it updates together. The catch is the migration, moving all those hand-pasted copies onto the one block.
This does that migration for you. It finds the copies, makes the single block, and swaps each page over once you approve the plan.
The same [signup callout] is pasted by hand into a bunch of my landing pages andevery copy has drifted. I want it turned into one synced block and rolled out so Ionly maintain it in one place.
Work read-first. Search my pages for the ones that contain [the callout] and showme the list. Check the existing synced blocks so we do not make a duplicate. Readone page that has a clean copy and show me the exact markup you would save as thenew synced block.
Wait for my go. Once I approve the block, create it, then update each page insmall batches to swap its pasted copy for a reference to the synced block, andshow me each batch before it saves. Do not touch anything else on the page. Listevery page you changed. Each edit keeps a revision, so we can roll any page backif a swap looks wrong.Why this is safe to run
The planning pass is reads. Searching for the pages, listing the synced blocks you already have, and reading a clean copy of the snippet all write nothing, so you approve both the exact block markup and the list of pages before anything is created or changed.
The write half happens in two clearly separated moves you control: creating the one synced block, then swapping each page’s inline copy for a reference to it. Nothing else on a page is touched, and because every page edit is saved as a WordPress revision, any page can be rolled back to how it was. The create and update abilities stay off until you enable them, every call is checked against the capability of the user you bound the agent to, and every write lands in the Activity Log with the page it changed.
Already connected? You do not have to paste this. Ask your agent for the “promote repeated content into a synced block” recipe, or just describe the snippet you keep pasting everywhere, and it runs the same read-first flow on your own site.