Duplicating and moving pages

Documentation / Pages and navigation

Duplicate a page when you need a separate starting point. Move it when the existing page belongs in another collection. These operations have different effects on identity and structure.

Create a separate copy

Open the page metadata and choose Duplicate this page. Enter New URL Path, then confirm with Duplicate. The copy receives fresh identifiers. Review the new page's title, access, template, and links before treating it as finished.

A duplicate is not a live synchronization relationship. Later edits to the original page do not automatically update an independent copy. A retained template reference or embedded content reference can still introduce shared dependencies, so check what the copied page inherits.

Move between collections

Use Move To to select another collection. The current interface limits this operation to the main content language. It moves the page and its child pages, placing the moved page at the target collection's top level.

Review the branch before confirming. A collection can have a different base path, ordering model, or default template. Moving the branch can therefore change more than its position in the admin list.

Validate both sides

Reopen the source and destination collections. Confirm that a duplicate exists as an additional page, or that a moved branch is no longer in its original location. Open the destination page and test internal links, media, resolved URLs, and template-controlled content.

Cross-website transfers are a separate operation with additional context and permissions. Do not assume the same-site Move To control performs them.

See Agentic editing and connections for authorized cross-website operations and Templates and reusable content for retained dependencies.