How to connect a custom domain to Systeme.io

Connecting your own domain is what turns a Systeme.io site into your site. The free plan includes one custom domain, so this works without upgrading. The process has three parts: add the domain in Systeme.io, add DNS records where your domain is managed, and redirect the bare domain to the www version.

Before you begin

• Know where your DNS is managed. That is usually your registrar (GoDaddy, Namecheap, IONOS, and so on), unless you moved your nameservers to a service like Cloudflare. If you are not sure, look up your domain's nameservers with any WHOIS or DNS lookup tool.
• Decide whether you want the root domain (www.yourdomain.com) or a subdomain (for example, go.yourdomain.com). This guide covers the root domain. Systeme.io has a separate help article for subdomains.
• If the domain currently runs another website, plan the switch. Systeme.io's help center notes that a domain can only be used for one website.

Part 1: Add the domain in Systeme.io

1. Click your profile picture, then Settings, then Custom domain.
2. Click Add domain.
3. Enter your domain starting with www, for example www.yourdomain.com, and save.
4. A popup shows two CNAME records. Keep this window open or copy both records somewhere safe.

The two records look like this (these are examples from Systeme.io's help center; yours will be different):

The first record points your www address at Systeme.io. The second proves you control the domain so a security certificate can be issued.

Part 2: Add the records at your DNS provider

Log in where your DNS lives, open the DNS records (sometimes called the DNS zone or Advanced DNS), and add both CNAME records exactly as shown.

Registrar notes

• GoDaddy: DNS → DNS Records → Add New Record → type CNAME.
• Namecheap: Domain List → Manage → Advanced DNS → Add New Record → CNAME Record.
• Cloudflare: DNS → Records → Add record → CNAME. Set the Proxy status to DNS only (grey cloud), as Systeme.io's Cloudflare guide instructs.
• Hostinger: Systeme.io's Hostinger guide adds an extra step (CAA records) before the CNAMEs. Follow that article if your DNS is at Hostinger.

The trailing dot

Systeme.io shows targets ending in a dot. Most providers accept that. Its help center notes that some hosts, Hover being the example given, do not, and that this can make the domain keep losing its "Ready to use" status. If your provider rejects the dot or the status flips back, remove the trailing dot.

Part 3: Redirect the bare domain to www

Visitors will type yourdomain.com without the www. That bare (root) domain needs to forward to www.yourdomain.com.

• Most registrars: use the forwarding or redirection feature to send yourdomain.com to www.yourdomain.com.
• Hostinger: Systeme.io's guide says to create an ALIAS record on the root pointing to the same target as your www CNAME.

There is one catch worth knowing. Systeme.io's help center says registrar forwarding usually works only for plain http addresses, not https. If you need https on the bare domain, it recommends a DNS provider with CNAME flattening, like Cloudflare, or root-level CNAMEs, like Namecheap. On Cloudflare, a redirect rule from the root to www handles this cleanly.

Part 4: Check, wait, then set your homepage

1. Use a DNS checker (Systeme.io suggests dnschecker.org) and search the full record name, including your domain.
2. Expect propagation to take 24 to 48 hours, and domain approval in Systeme.io to take a few hours.
3. When the domain shows as ready, set which page loads at the root: clear the URL path field in the settings of your website, blog, funnel page, or creator store and save.

Troubleshooting

• Status never turns ready: recheck spelling of both records, character for character. A missing underscore at the start of the second record is a common slip.
• Conflict when saving the record: your provider may already have a record on that name (often a default "parked" page). Systeme.io's advice is to ask your host what the conflicting record is for and whether it is safe to remove.
• Email stopped working: you probably removed MX records by accident. Website records (CNAMEs) and email records (MX) are independent. Restore the MX records from your email provider's instructions.
• Bare domain shows a certificate warning: that is the http-only forwarding limitation above. Move DNS to a provider that supports https redirects.

Do not want to touch DNS?

Systeme.io offers a free DNS setup service. Its page describes the process as contacting support and providing login details for your domain registrar. Only you can decide whether you are comfortable sharing those credentials. If you do, consider changing the password afterwards.

Questions