Custom Domains in HighLevel

Updated: February 6, 2026  | 
Author: Bill Stilwell

This post covers the full custom domain setup process, the difference between subdomains and root domains, how SSL works, how to assign domains to funnels and the Client Portal, and the agency workflow for client sub-account domain configuration.

Reading time: about 8 minutes.

What Are Custom Domains in HighLevel?

Custom domains allow you to connect a domain you already own to HighLevel-hosted assets – funnels, websites, and the Client Portal.

Without a custom domain, HighLevel-hosted pages are served from a subdomain of the HighLevel platform – something like yourname.gohighlevel.com or a similar platform-branded URL. This is functional but it exposes the underlying platform to visitors and does not reflect the business’s brand in the URL.

With a custom domain, the same pages are served from offers.yourbusiness.com, booking.yourbusiness.com, or yourbusiness.com itself. The visitor sees only your brand in the address bar.

Configure custom domains at Settings, then Domains in any HighLevel sub-account.

Why Custom Domains Matter

For most visitors, the URL is not consciously examined – but it does contribute to trust and credibility.

A URL that shows the business’s own domain looks intentional and professional. A URL that contains a third-party platform name tells the visitor the business is using someone else’s infrastructure – which is not inherently bad, but it is a signal that the business has not taken the step of branding its online presence end to end.

For agencies delivering client work, custom domains are a basic deliverable. Presenting a client’s funnel on a branded domain rather than a generic HighLevel URL is the difference between a complete implementation and an unfinished one.

There is also a practical benefit: branded URLs are shorter, more memorable, and easier to include in marketing materials than long platform subdomains.

Subdomains vs. Root Domains

The most common approach for connecting a domain to HighLevel is using a subdomain.

A subdomain is a prefix added before the main domain – for example, offers.yourdomain.com, booking.yourdomain.com, or go.yourdomain.com. The CNAME record for a subdomain only affects that specific prefix, leaving the root domain and all other subdomains completely unaffected.

Your main website at yourdomain.com continues to work exactly as before.

A root domain is the base domain without any prefix – yourdomain.com. Connecting a root domain to HighLevel requires an A record (or ALIAS record on some DNS providers) pointing to HighLevel’s servers.

This is more complex and typically requires that the root domain is not already in use for another purpose, since pointing the root domain to HighLevel would redirect all traffic from that domain to HighLevel’s platform.

For most users – especially those whose main website is hosted elsewhere – a subdomain is the correct and safest approach. Pick a clear, short subdomain that makes the purpose obvious to visitors.

DNS Records Required

When you add a domain in HighLevel’s Domains settings, the platform displays the DNS records needed to complete the connection.

For a subdomain, a CNAME record is required. The CNAME record maps the subdomain to a HighLevel-provided address.

Copy the name/host value (the subdomain prefix) and the destination value (the HighLevel CNAME target) exactly as shown in HighLevel and add them in your DNS provider.

For a root domain, an A record pointing to HighLevel’s IP address is typically required. Some DNS providers support ALIAS or ANAME records that function like CNAME but work for root domains – check your specific provider for the correct record type.

The records must be added at wherever your domain’s DNS is managed – typically the domain registrar (GoDaddy, Namecheap, Google Domains) or a DNS management service like Cloudflare if you have transferred DNS there.

After adding the records, return to HighLevel’s domain settings and check verification status. Once HighLevel detects the correct DNS records, the domain is marked as verified and ready to use.

Automatic SSL

HighLevel automatically provisions an SSL certificate for every verified custom domain. No manual SSL setup, no separate certificate purchase, no configuration required.

Once the domain is verified, HTTPS is active and the SSL padlock appears in visitors’ browsers when they access pages on that domain. This is handled entirely by HighLevel’s infrastructure.

SSL is important for two reasons. First, HTTPS is a browser trust signal – pages without SSL are flagged by browsers as “Not Secure,” which increases abandon rates on lead capture forms and booking pages.

Second, HTTPS is a minor Google ranking signal for indexed pages.

Assigning Domains to Funnels and Websites

After verification, a custom domain must be explicitly assigned to a funnel or website before it takes effect.

For funnels: open the funnel in the Funnel Builder, go to the funnel’s settings (usually accessed from the funnel list), and find the domain assignment field. Select the verified custom domain from the dropdown.

Save the setting. The funnel pages are now accessible at that custom domain.

For websites: open the website builder, go to website settings, and assign the custom domain. The process is the same as for funnels.

Multiple funnels can share the same custom domain with different URL paths. offers.yourdomain.com/spring-promo and offers.yourdomain.com/referral-offer can each route to different funnels while using the same connected domain.

Custom Domain for the Client Portal

The HighLevel Client Portal supports custom domain assignment so clients access the portal at a branded URL rather than a default HighLevel portal address.

Configure the Client Portal custom domain in the Client Portal settings within the sub-account. Once configured, clients who log in see the portal at the business’s own domain – for example, client.youragency.com – rather than a generic HighLevel URL.

For agencies, this is particularly important. A white-labeled client portal at the agency’s own domain is part of a complete, professional client delivery.

The client never sees a HighLevel URL anywhere in the experience.

Agency Usage – Client Sub-Accounts

Each HighLevel sub-account manages its own custom domains independently.

For an agency with 20 client sub-accounts, each client’s funnels and portals use that client’s own domain – connected in that specific sub-account’s Settings, then Domains. The agency’s domain is used for the agency’s own sub-account.

Each client’s domain is connected and managed only within that client’s sub-account.

This per-sub-account structure means domain configuration is self-contained for each client and does not cross-contaminate between accounts. Adding or removing a domain in one sub-account has no effect on any other sub-account.

What Can You Do With It?

• Brand every funnel URL with your own domain: Replace the default HighLevel subdomain URL with a branded address – offers.yourbusiness.com, book.yourbusiness.com – that looks intentional and professional in every link shared.
• White-label the Client Portal for clients: Give clients access to their portal at a branded URL that shows only the business’s or agency’s name – no HighLevel branding in the address bar.
• Connect a booking calendar page to a memorable branded URL: A booking page at book.yourpractice.com is more shareable and memorable than a long HighLevel default URL – easier to put on a business card, in an email signature, or in a social profile bio.
• Keep main website traffic separate from HighLevel funnels: Using a subdomain (offers, go, book, etc.) keeps the HighLevel assets clearly separated from the main website while maintaining brand consistency across both.
• Improve conversion rate on landing pages: Branded, HTTPS-secured URLs reduce browser security warnings and visitor skepticism on lead capture and booking pages – both of which can meaningfully affect conversion rates.
• Deliver complete client implementations: For agencies, presenting a client’s funnel on their own domain is the difference between a finished deliverable and one that still has loose ends.

Key Definitions

Use Cases by Industry

Marketing Agencies

An agency onboards a new client and sets up a lead generation funnel in HighLevel. As part of the client delivery, the agency configures the client’s custom domain – connecting offers.clientbusiness.com to the funnel and client.clientbusiness.com to the Client Portal.

The client’s ads link to branded URLs. The client portal is accessed at a domain that looks like it belongs to the client.

The HighLevel platform is invisible to the client’s customers throughout the entire experience.

Result: A complete, professional client delivery where every URL is branded. The implementation looks purpose-built for the client rather than a platform with the client’s logo dropped on top.

Coaches and Consultants

A business coach uses HighLevel for lead funnels and a client-facing portal. They connect start.theircoachingbrand.com to their main opt-in funnel and configure the Client Portal at members.theircoachingbrand.com.

Every URL a prospect or client encounters shows the coach’s brand. Links shared on social media, in email newsletters, and in podcasts all point to the coach’s own domain – reinforcing the brand consistently across every touchpoint.

Result: Brand consistency from first ad impression through client portal access – all URLs show the coach’s brand, not a platform name.

Real Estate Agencies

A real estate agency connects homes.theiragency.com to their HighLevel funnel for buyer leads and sell.theiragency.com to their seller lead funnel. Two different subdomains, two different funnels, one connected domain in HighLevel settings.

Each URL is short enough to use in print materials, social bio links, and SMS messages. The long HighLevel default URL it replaced would not have been practical in any of those channels.

Result: Multiple campaign URLs that are short, brandable, and shareable across all channels – replacing long platform subdomains that were impractical for offline use.

E-learning and Course Creators

A course creator uses HighLevel for a lead magnet funnel and connects free.theircourse.com as the custom domain. The Client Portal, where students access course content, is connected to learn.theircourse.com.

The course brand appears in every URL across the entire student journey – from the lead magnet opt-in to the course access portal. No third-party platform branding appears anywhere in the student experience.

Result: A seamless branded student experience. The course feels like a proprietary platform rather than a white-labeled third-party tool.

Service Businesses – Booking Focus

A home services company connects book.theircompany.com to their HighLevel booking calendar page. This URL is printed on business cards, vehicle wraps, and door hangers.

It is short, descriptive, and immediately clear about what the page does.

The previous HighLevel default booking URL – 40+ characters long – was impractical for any offline material. The custom domain makes the booking page shareable across every channel.

Result: A bookable URL short enough for a business card, a van wrap, and a door hanger – turning every physical marketing touchpoint into a direct booking entry point.

Who Is This For?

How to Connect a Custom Domain

Step 1: Go to Domains in Settings

In the sub-account, go to Settings, then Domains.

This is where all custom domains for the sub-account are managed.

Step 2: Add the domain

Click Add Domain. Enter the subdomain or domain – for example, offers.yourdomain.com.

Click Add or Continue to generate the required DNS records.

Step 3: Copy the DNS records

HighLevel displays the DNS records needed to verify the domain. Copy the values exactly – the record type, the name/host, and the destination/value.

Keep this browser tab open while you add the records at your registrar so you can copy the values accurately.

Step 4: Add the records at your DNS provider

Log into your domain registrar or DNS management service. Navigate to the DNS settings for your domain.

Add the CNAME record with the host and value from HighLevel. Save the record.

Different registrars have different interfaces but the concept is the same: you are adding a record that says “when someone requests this subdomain, send them to HighLevel’s servers.”

Step 5: Wait for propagation and verify

Return to HighLevel’s domain settings. Check the verification status.

It may take anywhere from a few minutes to a few hours for the records to propagate and be detected by HighLevel.

Do not proceed to assignment until HighLevel shows the domain as verified.

Step 6: Assign the domain to a funnel or website

For funnels: open the funnel settings and select the verified custom domain from the domain dropdown. Save.

For websites: open the website settings and assign the domain. For the Client Portal: configure the custom domain in Client Portal settings.

Step 7: Confirm SSL is active

Visit the custom domain URL in a browser. Confirm the SSL padlock appears and the URL shows https://.

SSL is provisioned automatically – if the padlock does not appear immediately after domain verification, wait 15 to 30 minutes and refresh.

Step 8: Test the full page load

Visit the custom domain URL on both desktop and mobile. Confirm the correct funnel or website loads.

Submit a test form if the page has one to confirm it works correctly under the new domain.

Step 9: Update shared links

Update any previously shared links – in email signatures, social media bios, ad campaigns, and marketing materials – to the new custom domain URL.

How Does It Connect to HighLevel?

• Funnel Builder: Custom domains are assigned to funnels in the funnel settings – the custom domain URL replaces the default HighLevel subdomain for all funnel pages. Building funnels in HighLevel without a custom domain leaves the implementation visually incomplete from a branding standpoint.
• Client Portal: The Client Portal supports custom domain assignment – clients access the portal at the business’s branded URL. For agencies, a custom Client Portal domain is a standard part of a white-labeled delivery.
• QR Code Generator: QR codes generated in HighLevel can link to custom domain URLs – a booking page at book.yourdomain.com is a better QR code destination than a long HighLevel platform URL. The QR Code Generator works with any URL regardless of whether a custom domain is used.
• Email Campaigns: Links in HighLevel email campaigns can point to custom domain funnel pages – maintaining brand consistency between the email sender domain and the landing page domain improves deliverability and trust.
• Availability Management: Booking pages with custom domains are more shareable in contexts where the URL itself matters – business cards, social bios, print materials. The custom domain makes the calendar booking page URL practical for offline distribution.

Common Questions

What are Custom Domains in HighLevel?

The ability to connect a domain you own to HighLevel funnels, websites, and the Client Portal – so pages are served from your branded domain rather than a HighLevel subdomain URL. Configured at Settings, then Domains.

Where do I set up a Custom Domain in HighLevel?

Go to Settings, then Domains in the sub-account. Click Add Domain, enter the subdomain or domain, copy the DNS records, add them at your registrar, and wait for verification.

What DNS records do I need to connect a custom domain to HighLevel?

A CNAME record for subdomains pointing to the HighLevel-provided destination. An A record or ALIAS record for root domains.

The exact values are displayed in HighLevel’s Domains settings when you add the domain.

Can I use a custom domain for HighLevel funnels?

Yes. Once verified, assign the domain in the funnel settings. The funnel pages are then accessible at the custom domain URL.

Can I use a custom domain for the HighLevel Client Portal?

Yes. Configure it in the Client Portal settings within the sub-account. Clients access the portal at the branded URL.

How long does it take for a custom domain to work in HighLevel after setting up DNS?

Typically a few minutes to a few hours. Up to 48 hours in some cases depending on the DNS provider and TTL settings.

HighLevel shows verification status once the records are detected.

Does HighLevel provide SSL for custom domains?

Yes. SSL certificates are provisioned automatically for all verified custom domains. HTTPS is active without any manual configuration – it just works once the domain is verified.

Can I use one custom domain for multiple funnels in HighLevel?

Yes. One custom domain can serve multiple funnels with different URL paths – offers.yourdomain.com/promo-a and offers.yourdomain.com/promo-b routing to different funnels under the same connected domain.

Can I connect a subdomain specifically for HighLevel without affecting my main website?

Yes. A CNAME record for a subdomain only affects that specific subdomain.

The root domain and all other subdomains are completely unaffected. Your main website continues to work normally.

Can agencies use custom domains for client sub-accounts in HighLevel?

Yes. Each sub-account has its own Domains settings. Each client’s domain is connected and managed within that client’s sub-account independently – no cross-account domain sharing or interference.

To Wrap It Up

Custom domain setup is one of the first things to do after building a funnel or website in HighLevel. It is a one-time technical task – add the DNS record, wait for propagation, verify – that improves every interaction the funnel or website has with visitors from that point forward.

The practical impact is real. A branded HTTPS URL converts better than a long platform subdomain on a lead capture page.

It is more practical on a business card. It is more trustworthy in an ad destination.

It is more consistent with the brand experience across all other channels.

For agencies, it is a non-negotiable part of delivery. Presenting a client’s funnel on a HighLevel subdomain is like presenting a website that still has the theme developer’s name in the title tag.

It is functional, but it is not finished.

The only technical barrier is access to DNS settings at the domain registrar. If that access is available, the setup itself takes under 20 minutes.

Here is how to get started:

1. Decide on the subdomain to use – offers, go, book, start, or any other short prefix that matches the funnel’s purpose
2. Go to Settings, then Domains in the sub-account and click Add Domain
3. Enter the subdomain – for example, offers.yourdomain.com
4. Copy the CNAME record name and value from HighLevel
5. Log into your domain registrar’s DNS management and add the CNAME record
6. Return to HighLevel and check verification status – refresh periodically
7. Once verified, open the funnel settings and assign the custom domain
8. Visit the URL in a browser and confirm HTTPS and the correct funnel loads
9. Update any previously shared links to the new custom domain URL

If you use Cloudflare for DNS, make sure the CNAME record is set to DNS only (gray cloud) rather than Proxied (orange cloud) during initial setup. Cloudflare’s proxy can interfere with SSL provisioning in some configurations.

Switch to proxied after the SSL certificate is active if you want Cloudflare’s CDN and security features.