Cross-website page copying and transfers

Documentation / Agentic editing and connections

Beeboo's transfer_pages tool moves page subtrees between roots on one website. It is not a cross-website copy or move command. A request to reuse content on another website therefore needs an explicit source-and-destination plan rather than an assumed single transfer action.

Read both websites first

Confirm access to each site and identify their domains, languages, roots, templates, and shared design. Read the source page and its descendants. Inventory internal page references, images, form IDs, collection listings, and template dependencies. A page that renders correctly on its source site may rely on resources that do not exist on the destination.

Ask for a proposed copy without deletion. Approve destination paths and availability, and identify which translations are included. Create destination content with new identities through supported page-creation and update tools; do not assume source page IDs or site-specific form and template references can be reused unchanged.

Verify before removing a source

Inspect every copied page at the destination, including mobile rendering, navigation, translated routes, and links. Rewrite internal references to the destination pages where appropriate. Keep the source intact until the copy is complete and approved. Deleting source content is a separate operation with its own permission and link review.

Transfers within one website

For transfer_pages, read both root versions first. Supply source and destination root IDs, their expected versions, and the selected page IDs. Descendants and language variants move together. The tool preserves IDs and relative slugs and reports path changes; it does not create redirects or repair listing references automatically.

Transfers are not atomic. After a partial error, inspect both roots before retrying. Home pages and conflicting destination routes are protected. See pages and navigation and collections and content trees.