Coachful
CoachfulHelp

How to verify domain ownership in Coachful

By Coachful10 min readUpdated Apr 20, 2026

Learn exactly how to verify domain ownership in Coachful — add the right DNS records, troubleshoot common errors, and get your custom domain live with auto-SSL in minutes.

What's covered
  • Why domain ownership verification matters
  • TL;DR — Quick answer
  • Before you start: what you'll need
  • Step-by-step: how to verify domain ownership in Coachful
  • Apex (root) domains — special handling
  • SSL certificate activation

Why domain ownership verification matters

When you connect a custom domain to your Coachful workspace — say, coaching.yourbrand.com or www.yourbrand.com — Coachful needs to confirm that you actually control that domain before it starts routing traffic and provisioning your SSL certificate. Without verification, anyone could claim any domain, and your visitors could end up somewhere unexpected. The process takes about five minutes once you know what to do, and this guide walks you through every step.

Domain ownership verification in Coachful works by asking you to add a specific DNS record to your domain registrar (GoDaddy, Namecheap, Cloudflare, Google Domains, Squarespace Domains, etc.). Once Coachful detects that record, it marks your domain as verified, activates auto-SSL via Let's Encrypt, and starts serving your coaching website on your own branded URL.

TL;DR — Quick answer

  • Go to Dashboard → Website → Custom Domain and enter your domain.
  • Coachful gives you a CNAME or TXT record to add at your DNS registrar.
  • Add the record, wait up to 48 hours for DNS propagation (usually under 30 minutes).
  • Return to Coachful and click Verify — once confirmed, your SSL certificate activates automatically.

Before you start: what you'll need

Gather these three things before you touch any settings:

  1. Access to your domain registrar. This is wherever you originally purchased the domain — GoDaddy, Namecheap, Cloudflare, Google Domains, etc. You need login credentials and permission to edit DNS records.
  2. Your Coachful workspace. You must be on a Scale plan (or legacy Pro plan) to connect a custom domain. Growth plan workspaces use the default {slug}.coachful.co subdomain. Upgrade your plan if you need this feature.
  3. The domain you want to connect. Decide upfront whether you're using a root/apex domain (yourbrand.com) or a subdomain (coaching.yourbrand.com). Both work; the DNS record type differs slightly.
Pro tip: If you manage DNS through Cloudflare, make sure the proxy status (the orange cloud) is set to DNS only (grey cloud) for the record you add. Cloudflare's proxy can interfere with Coachful's SSL provisioning until verification completes.

Step-by-step: how to verify domain ownership in Coachful

Step 1 — Open Custom Domain settings

Log in to your Coachful dashboard at app.coachful.co/sign-in. In the left sidebar, navigate to Website → Settings → Custom Domain. If you don't see the Website section, you may be in the wrong workspace or on a plan that doesn't include custom domains.

Step 2 — Enter your domain

Type your full domain name into the input field — for example, www.yourbrand.com or coaching.yourbrand.com. Include the subdomain prefix (www or otherwise) exactly as you want it to appear in the browser address bar. Click Add Domain to continue.

Step 3 — Copy your verification record

Coachful will display one or two DNS records you need to add:

  • A CNAME record pointing your domain to Coachful's servers (e.g., cname.coachful.co).
  • Optionally, a TXT record for ownership verification with a unique token tied to your workspace.

Copy both the Name/Host value and the Value/Target value for each record. You'll paste these into your registrar in the next step. Keep this browser tab open — you'll need it again shortly.

Step 4 — Add the DNS records at your registrar

The exact navigation varies by registrar, but the pattern is the same everywhere:

  1. Log in to your domain registrar (e.g., Namecheap, GoDaddy, or Cloudflare).
  2. Find the DNS Management or DNS Records section for your domain.
  3. Add a new CNAME record:
    • Type: CNAME
    • Name/Host: Paste the value Coachful gave you (e.g., www or coaching)
    • Value/Target: cname.coachful.co (or whatever Coachful shows)
    • TTL: 3600 (or "Automatic" / "Default")
  4. If Coachful also provided a TXT record, add it the same way, using the exact Name and Value shown.
  5. Save your changes.

Step 5 — Wait for DNS propagation

DNS changes don't take effect instantly — they propagate across global name servers. Most registrars apply changes within 5–30 minutes, though the official maximum is 48 hours. You can check propagation status in real time using a free tool like whatsmydns.net — search for your domain and select "CNAME" to see which regions have picked up the record.

Step 6 — Verify in Coachful

Once DNS has propagated, return to Website → Settings → Custom Domain in your Coachful dashboard. Click the Verify Domain button. Coachful checks for the DNS records you added and, if found, marks your domain as verified. Your status badge changes from Pending to Active and SSL provisioning starts immediately — usually completing within two minutes.

Already set up a custom domain and want to build a high-converting coaching website on it? Coachful's drag-and-drop website builder lets you publish landing pages, program sales pages, a blog, and a link-in-bio — all under your own branded domain with zero code.

Apex (root) domains — special handling

If you want to use a root domain without a subdomain — like yourbrand.com rather than www.yourbrand.com — there's an important DNS limitation to know: CNAME records cannot be set on the root/apex of a domain according to the DNS specification. Most modern registrars work around this with proprietary record types:

  • Cloudflare: CNAME Flattening — just add a CNAME at @ and Cloudflare handles it automatically.
  • Namecheap: Use an ALIAS record at the @ host.
  • GoDaddy: Use a CNAME on @ — GoDaddy resolves this correctly behind the scenes.
  • Route 53 (AWS): Use an A record ALIAS pointing to Coachful's hostname.

When in doubt, using www.yourbrand.com and setting up a redirect from the apex is the most reliable approach and sidesteps these edge cases entirely. Coachful's platform will serve your site correctly either way once verification passes.

SSL certificate activation

Coachful provisions SSL certificates automatically using Let's Encrypt — you don't need to buy or upload a certificate. The moment domain verification succeeds, Coachful requests a certificate for your domain. This typically completes in under two minutes, after which your site will be accessible over https:// with a valid, browser-trusted certificate. Auto-renewal happens in the background before expiry; you never need to manage it manually.

If you visit your domain right after verification and see a browser warning about an insecure connection, wait two or three minutes and hard-refresh. The certificate is almost certainly still provisioning.

Using Michelle to troubleshoot domain issues

If verification fails or you're unsure whether you've added the right records, ask Michelle — Coachful's built-in AI assistant. Open the Michelle panel from your dashboard and type something like "Why is my custom domain not verifying?" or "What DNS records do I need to add for my domain?". Michelle can pull up your workspace's specific verification records and walk you through what's missing, saving you a support ticket.

Pro tips for a smooth setup

Use a subdomain for your coaching workspace, even if you own the apex domain. Pointing coaching.yourbrand.com (or app.yourbrand.com) to Coachful keeps your root domain free for a separate marketing site or corporate website — no conflicts, no downtime risk.
  • Don't delete old records immediately. If your domain was previously pointing to another service, leave those records in place until Coachful verification succeeds and you've confirmed everything works. Then remove the old records.
  • Lower TTL before changing records. If you're migrating an active domain, change your TTL to 300 seconds (5 minutes) 24 hours before making changes. This makes propagation much faster and reduces downtime.
  • Avoid proxies during verification. Disable Cloudflare's proxy (orange cloud → grey cloud) for the record until Coachful marks the domain as verified. You can re-enable the proxy afterward if needed, though it's usually unnecessary since Coachful handles SSL.
  • Check for conflicting records. If a CNAME record already exists for the same hostname (e.g., a www CNAME pointing to an old site), you must delete the old record before adding the Coachful one. Two CNAME records on the same name will cause both to fail.

Troubleshooting common domain verification problems

"Domain not verified" after 48 hours

First, confirm the record was actually saved at your registrar — navigate back to DNS management and look for the record you added. It's surprisingly common to exit without saving. Second, use MXToolbox or whatsmydns.net to run a live CNAME lookup on your domain. If the CNAME doesn't appear, the record wasn't saved or the registrar hasn't propagated it yet. Copy the exact values from Coachful again and re-add the record, making sure to save.

SSL certificate shows "Not Secure" after verification

Wait 3–5 minutes after domain verification completes — Let's Encrypt certificate issuance takes a moment. If the warning persists beyond 10 minutes, open Website → Settings → Custom Domain and look for a Reissue Certificate or Refresh SSL option. If that still fails, contact Coachful support with your domain name and workspace slug.

Cloudflare proxy blocking verification

If you use Cloudflare, the orange proxy cloud intercepts requests before they reach Coachful, which can prevent both verification and SSL provisioning. Go to your Cloudflare DNS dashboard, find your domain's record, and click the orange cloud icon to toggle it to grey (DNS only). Retry verification in Coachful. Once the domain is verified and SSL is active, you can re-evaluate whether you need Cloudflare's proxy — in most cases, Coachful's own infrastructure makes it unnecessary.

CNAME on root domain returning an error

Some registrars refuse to save a CNAME on the @ (root) host because it violates RFC 1912. Use one of the workarounds described in the apex domains section above — ALIAS records, CNAME Flattening, or simply redirect the apex to www and point www to Coachful. Nearly all registrars support A-record-based apex redirects.

Verification succeeded but the site shows a Coachful error page

Domain verification confirms DNS ownership — it doesn't mean your website is published. Head to Website → Builder in your Coachful dashboard and make sure you have at least one page published. If your site is live but you see a generic error, check that the domain is correctly assigned to your workspace under Website → Settings → Custom Domain and that the status reads Active, not Pending or Error.

Domain already in use by another Coachful workspace

Each domain can only be connected to one Coachful workspace at a time. If you see an error saying the domain is already in use, it may have been added to a previous or test workspace. Sign in to that workspace, go to Website → Settings → Custom Domain, and remove the domain before adding it to your current workspace. If you no longer have access to that workspace, contact Coachful support to release the domain.

Ready to launch your coaching website on a custom domain?

Verifying your domain is the foundational step that turns your Coachful workspace into a fully branded coaching business — your name, your URL, your SSL certificate, zero technical headaches. Once verification is done, your coaching programs, booking pages, lead-magnet funnels, and community spaces all live under a domain your clients recognize and trust.

If you haven't set up your workspace yet, start your free trial at Coachful and have a custom-branded coaching site live in under an hour. Already a member? Sign in to your Coachful dashboard and head to Website → Settings → Custom Domain to get started right now.

Frequently asked questions

How long does domain verification take in Coachful?
Most domain verifications complete within 5–30 minutes after you add the DNS records at your registrar. In rare cases, full DNS propagation can take up to 48 hours depending on your registrar and TTL settings. You can monitor propagation in real time at whatsmydns.net.
Which Coachful plan do I need to use a custom domain?
Custom domains are available on the Scale plan (and the legacy Pro plan). Workspaces on the Growth plan use a Coachful subdomain ({slug}.coachful.co) by default. You can upgrade your plan at any time from Dashboard → Billing.
Do I need to buy an SSL certificate for my Coachful custom domain?
No. Coachful automatically provisions and renews a free SSL certificate via Let's Encrypt as soon as your domain ownership is verified. You don't need to purchase, upload, or manage any certificate yourself.
Can I use my root (apex) domain like yourbrand.com instead of www.yourbrand.com?
Yes, but standard DNS rules prevent CNAME records on an apex domain. Workarounds include using Cloudflare's CNAME Flattening, an ALIAS record (Namecheap), or redirecting the apex to www. Coachful works with any approach that correctly resolves to Coachful's servers.
What DNS records do I need to add to verify my domain in Coachful?
Coachful typically requires a CNAME record pointing your hostname to cname.coachful.co, and sometimes an additional TXT record with a unique verification token. The exact records are displayed in your Dashboard → Website → Settings → Custom Domain screen after you enter your domain.
Can I connect the same custom domain to multiple Coachful workspaces?
No. Each custom domain can only be active on one Coachful workspace at a time. If you need to move a domain from one workspace to another, remove it from the original workspace first, then add it to the new one.
Why does my domain say 'verified' but my coaching site still isn't loading?
Verification confirms DNS ownership but doesn't automatically publish your site. Make sure you have at least one page published in Website → Builder, and that the domain status shows Active (not Pending or Error) in Website → Settings → Custom Domain. If the issue persists, try a hard refresh or clear your browser cache.
Was this article helpful?