Every Emovart site starts out at https://your-slug.emovart.studio. Connecting a custom domain swaps that for an address on your own domain, typically a subdomain such as help.yourcompany.com or docs.yourcompany.com. The whole process takes about ten minutes: one CNAME record on your side, one field in the console — verification and the SSL certificate are handled for you automatically.
1. Find your domain's DNS record settings
Log in to wherever your domain is managed — a registrar like Namecheap or GoDaddy, or a DNS provider like Cloudflare — and look for the section called DNS, DNS records, or Zone editor.

Every provider's screen looks a little different, but they all let you add a record with a type, a name, and a value — and that's all we need.

2. Add a new CNAME record
Create a new record with these values:
- Type: CNAME
- Name: the subdomain you want, e.g.
help(some providers expect the fullhelp.yourcompany.com) - Value / Target:
cname.emovart.studio - TTL: the default is fine

On Cloudflare, set the record to DNS only (gray cloud) rather than Proxied (orange cloud) while the domain is being set up — proxying hides the record from our checks and blocks certificate issuance. You can experiment with re-enabling it once everything is live.
3. Connect Emovart to your custom domain
Back on emovart.studio, open Settings → Help Centers, select your site, and go to the Custom domain section.

Enter the full domain — for example help.yourcompany.com — and click Connect. Emovart checks the CNAME, provisions an SSL certificate, and switches your site over as soon as both are ready.

4. Verify your domain (not always necessary)
In most cases verification happens silently in the background. If your DNS provider hasn't propagated the new record yet, the console shows the domain as Pending with a Verify button you can press to re-check at any time.


👍 Automatic canonical
Your default your-slug.emovart.studio address keeps working after the switch — handy for testing — but every page automatically declares your custom domain as its canonical URL. Search engines only ever index the custom domain, so duplicate content is never a concern.
Subpath support in Emovart
A quick word on yourcompany.com/help (subpath) versus help.yourcompany.com (subdomain):

The CNAME flow above gives you a subdomain, and that's what we recommend — setup is automatic and certificates are managed for you. Serving your help center under a subpath is possible too, but it requires a reverse proxy on your main domain that forwards /help traffic to your Emovart site. If you want to go that route, message us through the Contact button and we'll walk you through the right proxy configuration for your stack.