Standardize a CTA block across your pages

ContentIntermediate~15 min

Before you start

A connected site with content reads on and the block update write ability enabled for the write pass. The agent needs edit access to the block. The call to action must already live in one synced block.

A call to action that lives in a synced block is a gift until the day it goes out of date. The offer changed, the button points at an old URL, the wording is off, and because it is one block placed across the site, you want to fix it in exactly one place and have every page follow.

This does that one edit carefully. It reads the current block, shows you precisely what will change, and saves only after you approve, because a synced block updates everywhere the moment you save it.

The prompt
My [book a demo] call to action lives in one synced block that shows up across the
site, and the wording and button link are both out of date. I want to fix the
block once.
Read first. List the synced blocks, find the [book a demo] one, and show me its
current markup. Then show me the exact new markup you propose, the copy and the
button URL side by side with what is there now. Remember this block is synced, so
whatever we save shows up everywhere it is placed at once.
I will approve the exact markup before anything saves. Only after I say go, update
the block. Keep the old markup in your reply so I can paste it back if the new
version is wrong.

Why this is safe to run

Listing the blocks and reading the current markup are reads, so you see both what is there now and the exact markup that would replace it before a single save. That preview matters more here than usual, because a synced block updates every page it sits on the instant you save, and the prompt makes that plain.

The write is a single call against one block, and nothing else on the site is edited. The block update ability stays off until you enable it, the call is checked against the capability of the user you bound the agent to, and it lands in the Activity Log. Because the read pass returns the old markup and the reply keeps it, reverting is just saving that original markup again.

Already connected? You do not have to paste this. Ask your agent for the “standardize a CTA block across your pages” recipe, or just describe the call to action you need to update, and it runs the same read-first flow on your own site.

How it works

  1. List the synced blocks and find the call-to-action one you want to fix.
  2. Read its current markup so you can see exactly what is there.
  3. Show the exact new markup side by side with the old copy and button URL.
  4. Wait for your approval, and note that a synced block updates everywhere it is placed at once.
  5. Update the one block, keeping the old markup in the reply so it can be pasted back.

Questions

How many pages does this touch?
One block. Because the call to action is a synced block, editing it once updates every page it is placed on at the same time, which is exactly why the recipe previews the new markup before saving.
What if the new version is wrong?
The read pass returns the old markup and the recipe keeps it in the reply, so putting the block back is a matter of saving that original markup again.