Projects, websites and funnels
One domain project with shared resources and independently edited and published children.
One project represents one domain
Workspace → Project/domain → Website and Funnels. A project contains at most one website and multiple funnels, subject to your plan. Free includes one project, one website, one funnel and 1,000 shared monthly visitors; building uses your external AI/MCP client.
Create the project before connecting DNS. Its preview address lets you build and review first. Connect one primary domain in Domain settings; a domain cannot belong to another project. Configure www to redirect to the primary hostname. Funnels use paths on the primary domain in this release.
Manage the project
Open Dashboard → Projects, then your project. The overview shows its website, funnels, domain, shared visitor usage, child traffic and recent activity. Open a child to edit pages or its funnel map. Use the editor’s Website or funnel switcher to move between children; discard or save pending edits before switching.
- CRM and Contact fields: one project contact store and reusable custom fields.
- Forms & calendars: create shared resources and attach the same resource to different children.
- Images, Videos & embeds: one shared project library.
- Commerce: connect providers once; each child owns its purchase placements and journey transitions.
- Tracking & attribution: shared defaults with child/page overrides.
- Domain, Pages & routes, Publication history and Settings & team: domain ownership, route reservations, publishing and project permissions.
Independent designs and drafts
Each website/funnel keeps its own pages, navigation, typography, CSS, header/footer choices, revisions and publication status. When adding a funnel, Start with the website’s visual style explicitly snapshots the website’s design direction. Later changes are independent; this does not create a live branding dependency. Choose a journey template or start from scratch.
Reserve unique paths
Every child reserves paths in the project route registry. Funnel prefixes such as /free-guide/ keep thank-you pages distinct. Creation, editing and publication reject conflicting paths. When renaming a published path, review the suggested redirect in Pages & routes. Incoming published links, redirects and funnel destinations can block removing a child; reconcile them before removal.
Publish one child
A domain serves one immutable combined release composed of the currently published website and funnels. Publishing or restoring a child preserves its siblings’ published revisions and leaves their drafts untouched. Readiness checks cover routes, resources, transitions and connected-domain status before the release switches atomically. A failed publish preserves the existing live release. Unpublished content is available through private previews.
For agents: read get_project for the current project.published_release_id, preview the exact child revision, obtain the user’s approval, then call publish_project_child with siteId, revisionId, expectedReleaseId and confirmation publish:siteId:revisionId. For rollback, use action rollback and confirmation rollback:siteId:revisionId. Read the latest state after a conflict; do not blindly repeat with a stale release ID.
Agent workflow
- Connect MCP/OAuth or use a workspace-scoped API key. Existing site-bound credentials retain their child restrictions and cannot administer shared project resources.
- Use list_projects/get_project, or create_project with an idempotent requestId and name.
- Create the website with create_project_child (type website); create funnels with type funnel, a unique prefix, a journey template and optional inheritBranding.
- Read get_site and get_revision for the returned child. Generate complete frontend source with your external AI and call submit_source using its expectedVersion. Poll get_run, then inspect preview_site.
- Use project resource, CRM, asset, tracking, domain and route operations for shared configuration. Use child tools for source, visual editing, typography, funnel connections and conversion reporting.
- Read the API library for the exact input/response contracts and scopes; operations enforce workspace membership, project permissions and credential restrictions in the database.
Existing sites
Existing websites become a project’s website. Existing funnels become funnel children with the website slot available. Mixed website/funnel content is allocated using its actual page relationships, preserving original revisions and explicit public/source maps. Review migration readiness and the staged comparison before switching delivery. Conflicts and unsupported source reconstruction require resolution; original delivery remains active while unresolved. Migration does not silently grant an existing site-bound agent access to new siblings or shared administration.
Shared traffic, attributed work
The project visitor allowance is shared across the website and funnels. Child traffic reports show visitors and page views; the same visitor may appear in multiple children, so child totals are not the quota total. Private previews are excluded. AI work and its model costs stay attributed to the child that requested it.