Copy a page to another connected site

Rebuilding a page on a second site by hand is the kind of chore that eats an afternoon. You copy the blocks over, then realize the images are still pointing at the first site, so you download and re-upload each one, fix the URLs, and hope you did not miss a synced block that was pulling content in from somewhere you forgot.

This prompt does the carry for you across two sites the agent is connected to. It reads the source page and its images, re-uploads the images into the target site’s own library so the copy does not hotlink back, and lands the whole thing as a draft. Nothing on the source is touched, and nothing goes live until you say so.

Copy [the Services page, id 51] from [Site A] over to [Site B], which you are
also connected to. Land it on Site B as a draft, do not publish it, and do not
change anything on Site A.

Read the source page first, including any synced (reusable) blocks it pulls in,
and note the images it uses. On Site B, upload those images into its own Media
Library so the copy does not hotlink back to Site A, then rebuild the page
content against the new image URLs and save it as a draft.

Tell me anything that could not come across, like a PDF or other non-image
attachment, and hand me the draft link on Site B so I can review and publish it.

Why this is safe to run

The source side is read-only. Reading the page, listing its synced blocks, and opening each one changes nothing on Site A, so the original is never at risk during the copy. This one needs both sites connected to the same agent, since the read happens on one and the write on the other.

Everything the agent writes lands on the target as a draft. It re-uploads the images into Site B’s own Media Library so the copy stands on its own rather than hotlinking Site A, then assembles the page as an unpublished draft you review before it goes live. The honest limit is the upload ability: it handles images only, so non-image attachments like PDFs do not travel, and the agent tells you what it had to leave behind. Write abilities stay off until you enable them on the target, each call is checked against the capability of the user you bound the agent to there, and the new draft is logged in that site’s Activity Log.

Already connected to both? Skip the paste. Ask your agent for the “copy a page to another connected site” recipe, name the source page and the target, and it carries the page over as a draft for you to publish.