Replace a leftover block with a core block, page by page

Say twelve pages still hold an old plugin’s call-to-action block, and each needs the same fix: a core group with a heading, a line of text and a button. By hand that is twelve trips through the editor. A full-page rewrite would mean trusting the agent with every other block on those pages.

Start from the list made by find pages with blocks your site no longer has. Replace block changes one block per call, and the agent stops for your yes on each page and checks the block name before it writes.

Replace the leftover [old-plugin/cta] blocks with a core block. Here is
the list of pages and paths from the find-pages run: [paste the table].

1. The replacement is a core/group holding a core/heading, a
   core/paragraph and a core/buttons block with one core/button. Check
   that each of these block types is registered and read the attributes
   they accept, so the markup is valid.
2. For each page, in order:
   - read the page as raw block markup and confirm the block at that path
     is [old-plugin/cta]
   - write the new block, reusing that block's own heading and button text
     and link
   - show me the old markup and the new markup side by side, and wait
3. When I say go for a page, replace only that block, passing the path and
   the expected block name so the call refuses if the page has changed.
   Tell me about any content warnings the tool returns.
4. Read the page again and confirm the new block is at that path.

Keep a copy of every old block in your reply. At the end, list pages
replaced, refused (with the reason) and skipped.

Why this is safe to run

The reads come first, and every write is one Replace block call you approved for that page. Pass the expected block name, and a page that changed since the list was made is refused rather than overwritten. The old markup stays in the chat. If a page’s existing markup cannot be saved back cleanly, the call refuses too, and that page is one to fix in the editor.

Replace block is off until you switch it on, it is checked against the edit access of the connected user, and each call lands in the Activity Log. With revisions on, every page keeps its earlier version in its history.

Already connected? Ask your agent to replace the leftover blocks it found, one page at a time, and approve each swap as it comes.