Publishing and domains
Connect and verify a custom domain
Point your domain at the platform, verify DNS safely, and understand what happens while certificates issue.
step 1
Add the domain in settings
Start inside the admin domain screen so the platform can create the right verification expectations before you change DNS.
- Use the exact hostname you want visitors to type.
- Keep your current site live until DNS is ready to switch.
- Avoid adding wildcard records unless your DNS provider requires them.
step 2
Update DNS at your provider
Follow the record names shown in the app. DNS propagation can be quick, but provider caches and certificate issuance may take longer.
- Copy record names and values exactly.
- Use an A record at @ for a bare domain and a CNAME for a subdomain; DNS does not allow a CNAME at @.
- Remove conflicting old A, AAAA, or CNAME records, including parked or forwarding records.
- Wait for verification before sending high-value traffic.
step 3
Verify, then tell search engines
The platform rechecks domain state and certificate health. Once the domain is active, your entire site lives on it: every page, your contact card, favicon and share images, plus sitemap.xml, robots.txt, llms.txt and llms-full.txt, with no platform branding anywhere. Your pages name the domain as their canonical address, so search engines consolidate onto it.
- Use Verify after DNS changes.
- Watch for active SSL before launch announcements.
- Add the domain to Google Search Console as a new property and submit its sitemap.xml.
- Keep registrar access available during launch week.