Skip to content

Connecting a domain to a project

Once a domain is added and active, connecting it to a project takes seconds. One domain can serve several projects — each on its own subdomain.

In your project: Settings → Domains.

  1. Click Add custom.
  2. Pick the domain from the dropdown (it lists your active domains).
  3. Subdomain — leave empty to use the bare domain (mysite.com), or type one (appapp.mysite.com).
  4. Click Connect.

That’s it — no re-publish needed. Genesis copies your published site to the new address and it goes live immediately, HTTPS included.

  • The Open site button, your project’s published URL, and your SEO plumbing (sitemap, canonical URLs, social-share tags) all switch to the custom domain.
  • Your original …genesis.estage.com address keeps working — same site, both addresses. Share the custom one.

Each subdomain is its own mapping, so one domain can host your whole ecosystem:

AddressProject
mysite.comMain site
blog.mysite.comA separate blog project
app.mysite.comYour web app

A subdomain can only be mapped to one project at a time — connecting an occupied one shows “already mapped”; disconnect it from the other project first.

A module of one project can also take its own subdomain — app.mysite.com, store.mysite.com — each with its own home page, with the AI scoping its edits to the module it’s working in.

If a project has several addresses, one is marked Primary — that’s what the Open site button and the published URL show. The bare domain wins over www automatically; you can change the primary in the Domains tab.

Click next to the mapping in Settings → Domains. The custom address stops serving the site (the Genesis address keeps working as a fallback). The domain stays in your workspace, ready to reconnect anywhere.

Nothing changes in your workflow: edit, then Publish — the new version goes live on the custom domain and the Genesis address simultaneously.