The third way to create a site - clone makes a near-exact copy of a live site into a tenant, as drafts, with no keyword research and no generated copy.
Loading the guide...
Help us make the guides more useful.
0 helpful · 0 not helpful
Cloning is the third way to fill a new client site, alongside porting and generating. It makes a near-exact copy of a live site into a tenant: real content, real chrome, real images, as drafts you own and can edit.
Reach for clone when you want a plain, faithful copy of a site into the platform quickly, without the parity-report takeover workflow of a port and without the keyword plan and rewritten copy of a generate run.
Given a live URL and a target tenant, cloning brings over:
Every page lands as a draft. The tenant is created for you if it does not exist yet.
Cloning is deliberately plainer than the other two flows:
From the platform repo, with your CMS running:
The tenant is found or created by slug, the pages are captured and persisted as drafts, and the capture workspace is discarded afterward.
There is no bare seedly command on your machine; the CLI runs through pnpm from the platform folder. Clone signs in as you with a session token in PAYLOAD_TOKEN and stops without one. SETUP/operations/adding-a-tenant.md in your download shows how to copy that token from your browser, including the Windows form of the command.
| You want to | Use |
|---|---|
| Take over a client's existing site with a measured, gap-by-gap review | Port |
| Build a fresh site from a client's brand inputs, in their voice | Generate |
| Make a quick, faithful copy of a live site as editable drafts | Clone |
The cloned pages are ordinary builder pages from here on. Review them, adjust anything the capture did not carry perfectly, re-embed forms, set the brand and custom domain, then publish and deploy on your own schedule. Nothing goes live until you deploy.