We remember the first time HighLevel changed the interface and a “simple” domain connection suddenly felt like defusing a bomb. You are trying to move fast, launch funnels, and start making money with AI, but one wrong DNS setting and your pages do not go live. In this guide, we will walk you through the exact process we use to connect a subdomain to a HighLevel sub-account, verify it, and make sure your funnels and websites are actually linked to the right domain.
Introduction: What you are about to do (and why it matters)
Connecting your domain is not just “technical admin”. It is the switch that turns your funnel from a draft inside HighLevel into a real asset you can sell, scale, and automate.
If your goal is to escape the 9 to 5 with an AI powered agency model, you cannot afford pages that fail to load, broken links, or a domain that never verifies. This step is foundational, because everything else in HighLevel depends on your domain being correctly connected.
What you need before you start
To connect a domain or subdomain to a HighLevel sub-account, you need three things ready: access to the right HighLevel sub-account, access to your domain’s DNS provider (like GoDaddy or Cloudflare), and the exact DNS values HighLevel tells you to add.
If you are using a subdomain (recommended for most agency setups), your DNS provider should create a CNAME that points your chosen host (like “go” or “www”) to HighLevel’s target value. HighLevel’s own setup guide confirms a common CNAME target for subdomains is sites.ludicrous.cloud.
Step-by-step: Connect a subdomain inside HighLevel
Open the correct HighLevel sub-account
You must be inside the sub-account where the funnel, website, or blog will live, because domains are connected at the sub-account level in the workflow shown.Go to Settings, then Domains
In the new interface, we go to the bottom-left Settings area, then find the Domains option in the left menu.Choose “Connect a domain” and select what you are connecting
HighLevel gives multiple connection options, and the path we use for funnels, websites, stores, blogs, and webinars is the option labeled for those assets.Enter your domain and choose a subdomain approach
We typically connect a subdomain for HighLevel funnels even if the root domain already has a main website, for example using “go.yourdomain.com” while keeping “yourdomain.com” elsewhere.
Manual vs Dynamic domain connection (which should you pick?)
HighLevel offers two methods: manually adding DNS records, or a dynamic method where you log into the registrar style connection. The walkthrough here uses the manual method first because it is universal and works whether your domain is on GoDaddy, Cloudflare, or another provider.
If you want the least guesswork, manual is usually the most predictable because you can see the exact record, host, and target values you set.
Step-by-step: Add the correct DNS record (Cloudflare example)
HighLevel offers two methods: manually adding DNS records, or a dynamic method where you log into the registrar style connection. The walkthrough here uses the manual method first because it is universal and works whether your domain is on GoDaddy, Cloudflare, or another provider.
If you want the least guesswork, manual is usually the most predictable because you can see the exact record, host, and target values you set.
Step-by-step: Add the correct DNS record (Cloudflare example)
Open your DNS provider and find DNS records
In Cloudflare, we open the domain, go to the DNS section, and add a new record. The same concept applies in GoDaddy or other registrars, as long as you are editing the authoritative DNS where the domain is actually managed.Add a CNAME record for your subdomain
HighLevel’s support documentation states that for subdomains you can add a CNAME record where Host or Name is only the subdomain part (for example “www” or “go”), and Value or Target is sites.ludicrous.cloud.
In the example walkthrough, the CNAME is set to host “go” and points to sites.ludicrous.cloud to route traffic to where HighLevel sites and funnels are hosted.
Proxy status and TTL (do this carefully)
In the walkthrough, we turn off Cloudflare proxy status for this record, leaving it as DNS only, then keep TTL on auto.
Cloudflare explains that proxy status changes how Cloudflare treats DNS queries, and it specifically notes that CNAME records used to verify a domain for a third-party service should not be proxied. That guidance aligns with keeping this record DNS only when you are trying to verify a domain connection.
Save the record
Once the CNAME record is saved, you are ready to verify inside HighLevel.
Step-by-step: Verify the domain in HighLevel (and what “instant” really means)
Back in HighLevel, click “Verify records” after your DNS record is created. In the example, verification is normally instant, but it can sometimes take longer depending on DNS propagation.
HighLevel’s whitelabel domain documentation also references that DNS changes may take time to propagate and mentions up to 30 minutes in some situations, so if verification does not happen immediately, waiting and re-checking is often the correct next move.
How to confirm your funnel and website are linked to the domain
Once HighLevel shows the domain connected, it should become selectable and usable inside your Sites and Funnels areas. In the walkthrough, we confirm by opening the funnel, seeing the domain applied, then copying the URL into the browser to confirm it loads the intended page.
We then repeat the check for the website by going to the website settings and confirming the domain appears there too, which ensures the pages are linked to your connected domain.
Troubleshooting: The issues most people miss
Do not add both an A record and a CNAME for the same host
HighLevel’s support article warns not to create both record types for the same hostname, and explains that verification fails if HighLevel cannot find the expected CNAME or A record for that host.
Make sure Host or Name is only the subdomain
HighLevel explicitly clarifies that Host or Name should be only the subdomain portion, not the full domain, like “www” for www.yourdomain.com.
If you use Cloudflare, keep verification records DNS only
Cloudflare’s documentation states that CNAME records used for third-party verification should not be proxied, which is a common cause of “it looks right but won’t verify” headaches.
Unique strategy: Why we prefer subdomains for fast monetization
If you are building an AI automation or lead gen offer, subdomains let you launch client facing funnels in HighLevel without touching a client’s main website setup. That means less friction, faster deployment, and fewer internal approvals, which is exactly what you need when you are trying to replace your salary quickly.
It also makes it easier to systemize delivery across clients, because your process becomes repeatable: connect subdomain, verify, apply domain to funnel, test live URL, then move on to lead flow and automations.
Helpful next steps
If your goal is to make money with AI and HighLevel, domain connection is step one, but you will get paid when your lead flow and automations are tight.
Here are related posts already published on our site that can help you build the rest of the machine:
If you want a packaged, step-by-step path for turning this into an income engine, The Instant AI Agency is EXACTLY what you need.
Conclusion
If you follow the steps above, you will have a verified subdomain connected to your HighLevel sub-account, and your funnels and websites will be live on your custom domain instead of a temporary link.
What part of domain setup trips you up most right now: finding the right DNS screen, getting the CNAME right, or passing verification inside HighLevel?
