Connect a custom domain to your LaunchMyStore

Markdown

View as Markdown

Connect a custom domain to your LaunchMyStore

Connecting a custom domain (like yourbrand.com) replaces the default storename.launchmystore.io URL with your own brand. This guide walks through pointing an existing domain at your store, the DNS records you need to add, and how to troubleshoot common issues.

Before you start

You connect a domain you already own (register one with any provider first — GoDaddy, Namecheap, Cloudflare, Google Domains, etc.), then point it at LaunchMyStore by updating its DNS records. The whole process takes a few minutes plus DNS propagation time.

Step 1 — Add the domain in your admin

  1. Sign in to app.launchmystore.io.

  2. Go to Settings > Domains.

  3. Click Connect (or Set up) to open the connect panel.

  4. Enter your domain without http:// or https://. For a root domain, enter yourbrand.com (the www. prefix is added for you); for a subdomain, enter the full name such as shop.yourbrand.com.

  5. Click Verify & Connect. LaunchMyStore then shows the exact DNS records to add.

Step 2 — Update DNS at your domain provider

Open the DNS records for your domain in your admin (Settings > Domains, then the DNS configuration view for that domain) and copy the values shown there. For a standard store the configuration is:

Record type

Host / Name

Value / Points to

TTL

CNAME

www (for a root domain) or the subdomain label, e.g. shop

my.launchmystore.io

1 hour

TXT

The verification host shown in your Domains panel

The verification value shown in your Domains panel

1 hour

The TXT record confirms you own the domain and is required before the SSL certificate can be issued. Always copy the exact host and value from your Domains panel — the verification record is unique to your store.

Notes

  • For a root domain (e.g. yourbrand.com), LaunchMyStore uses the www version as the connected address and automatically redirects the bare root to it. Add the CNAME on the www host.

  • Most providers do not allow a CNAME directly on the root (@) host — that is why the CNAME goes on www. If your provider supports CNAME flattening, ALIAS, or ANAME records (Cloudflare, DNSimple), you can also point the root at my.launchmystore.io with one of those record types.

  • Delete any existing A, AAAA, or CNAME records on the same host that point to a previous provider, to avoid conflicts.

Provider-specific quick guides

GoDaddy

  1. Sign in and go to My Products > DNS next to your domain.

  2. Delete any existing record on the www host.

  3. Add a CNAME: Host www, value my.launchmystore.io, TTL 1 hour.

  4. Add the TXT record exactly as shown in your LaunchMyStore Domains panel.

  5. Click Save.

Namecheap

  1. Sign in > Domain List > Manage.

  2. Open Advanced DNS.

  3. Delete any existing record or URL Redirect on the www host.

  4. Add a CNAME Record: Host www, target my.launchmystore.io.

  5. Add the TXT Record exactly as shown in your Domains panel.

  6. Save with the green checkmark.

Cloudflare

  1. Sign in > pick your domain > DNS.

  2. Delete existing records on the www host (and on the root if you use CNAME flattening).

  3. Add a CNAME on www pointing to my.launchmystore.io. (You can also use CNAME flattening on the root to the same target.)

  4. Add the TXT verification record exactly as shown in your Domains panel.

  5. Set SSL/TLS mode to Full (Strict), and turn the proxy (orange cloud) off for the connected records.

Other providers

The steps are very similar everywhere: remove conflicting records on the host, add the CNAME to my.launchmystore.io, add the TXT verification record, and save. DNS panel names vary slightly between providers.

Step 3 — Verify and issue SSL

After saving DNS, return to Settings > Domains in your admin. You can use Check All Domains to re-check status. DNS propagation usually completes in 5–30 minutes but can take up to 24 hours. Once the records are detected:

  • LaunchMyStore automatically issues a free SSL certificate for your domain

  • HTTPS is forced — visitors landing on http:// are redirected to https://

  • Your store loads on the connected domain. (Your first visit may briefly show a blank page while the certificate finishes provisioning — just reload.)

Set your primary domain

If you have multiple domains pointed at your store, set one as primary in the Domains panel. All other domains 301-redirect to it for SEO consistency.

Troubleshooting

  • Domain still not verified after a while? Use dnschecker.org to confirm the CNAME and TXT records have propagated globally.

  • "Connection not secure" in the browser? SSL provisioning can take a little while after the records are detected. Reload the page, or contact support if it persists.

  • www works but root doesn't (or vice versa)? Recheck the CNAME on www, and that the root is set to redirect to www (or uses CNAME flattening if your provider supports it).

  • Old site still showing? Clear your browser cache, or test in incognito.

If you are still stuck, contact [email protected] with your domain, the records you set, and a screenshot of your DNS panel.

FAQ

Can I keep my email on the old domain provider?

Yes. Only the records you point at LaunchMyStore need to change. MX records for email stay intact. You can continue to use Google Workspace, Microsoft 365, or any other email provider.

Is SSL included?

Yes. LaunchMyStore issues a free SSL certificate automatically once your domain verifies. Renewal is automatic and you never have to touch it.

How long does DNS propagation take?

Typically 5 minutes to 30 minutes, but global propagation can take up to 24 hours. Use dnschecker.org to track it.

Can I use a subdomain like shop.yourbrand.com?

Yes. Add the subdomain in Settings > Domains, then add a CNAME record on the subdomain label (e.g. shop) pointing to my.launchmystore.io, plus the TXT verification record shown in your Domains panel.

What happens to my free .launchmystore.io subdomain after I connect a custom domain?

It continues to work. Once you set a primary custom domain, traffic is directed to your custom domain for a consistent brand experience.

Was this article helpful?