How to Connect a Subdomain to a Multi-Page Website in GoHighLevel

Attaching a subdomain to a single landing page in GoHighLevel is easy. But mapping that same subdomain across a multi-page website often breaks navigation menus, slugs, and SSL certificates if your routing settings are off by one step. I ran into this exact headache while moving a client’s 14-page marketing site from WordPress over to HighLevel under resources.clientdomain.com.

Below, I’ll walk through how to configure your DNS host, attach the subdomain inside your HighLevel sub-account, bind it to your multi-page site, set your default homepage and 404 paths, and fix relative navigation links so visitors never hit an orphaned step.

Websites vs Funnels: How GoHighLevel Handles Subdomain Routing

HighLevel treats Funnels and Websites completely differently under the hood. Funnels use strict sequential step ordering where each step gets its own path URL. Websites rely on an open tree structure where every page exists as a standalone sibling under a shared domain root.

When you map a subdomain like hub.yourdomain.com to a Website:

• The root URL (hub.yourdomain.com/) maps directly to whichever page you assign as the homepage in your site settings.
• Every additional page inherits the subdomain prefix followed by its individual page slug (like hub.yourdomain.com/pricing or hub.yourdomain.com/contact).
• Internal links between pages can use relative URLs (/about) instead of full domain strings.

If you mistakenly bind your subdomain to an individual funnel step instead of the parent website container, clicking subpages will throw 404s or loop back to your root domain. If you’re building standalone conversion funnels rather than a full site, check our guide on how to connect a custom domain and subdomain to GoHighLevel funnels.

Step 1: Create the CNAME Record at Your DNS Host

Before touching HighLevel, you need an active CNAME record pointing your target subdomain to HighLevel’s edge routing server. Log in to your DNS provider (Cloudflare, DNSimple, Namecheap, Route 53, GoDaddy, etc.).

Add a new DNS record with these values:

• Type: CNAME
• Name/Host: Your subdomain prefix (e.g., portal, info, or resources)
• Target/Value: flash.funnels.msgsndr.com
• TTL: Auto or 300 seconds (5 minutes)

If you use Cloudflare, switch the proxy status to DNS Only (Grey Cloud) during initial domain verification. Leaving Cloudflare’s orange cloud active during verification can stall SSL provisioning inside HighLevel.

Here is what I run in my terminal to verify DNS propagation before moving on:

dig +short CNAME resources.yourdomain.com @8.8.8.8

If that command returns flash.funnels.msgsndr.com., the DNS has propagated and HighLevel is ready to talk to it.

Step 2: Add the Subdomain in HighLevel Settings

Once the DNS resolves, register the subdomain inside your HighLevel sub-account:

1. Log in to your HighLevel sub-account.
2. Go to Settings (bottom-left gear icon) > Domains.
3. Click the blue Add Domain button.
4. Type your full subdomain (e.g., resources.yourdomain.com). Don’t include https:// or trailing slashes.
5. Click Continue.

HighLevel will query your DNS record against flash.funnels.msgsndr.com. If the CNAME is live, you’ll see a green checkmark indicating successful verification. A modal will ask to link the domain to an existing site. You can pick your website here or close it and map it manually in the next step.

If your verification hangs on “Pending”, see our troubleshooting steps for fixing GoHighLevel domain SSL pending and DNS errors.

Step 3: Bind the Subdomain to Your Multi-Page Website

Adding the domain in account settings doesn’t automatically route traffic to your multi-page site. You have to assign it inside the Website settings panel:

1. Head to Sites > Websites in the left sidebar.
2. Click on the multi-page website project you want to publish.
3. Click the Settings tab at the top of the website dashboard.
4. Find the Domain dropdown menu.
5. Select the subdomain you just added (e.g., resources.yourdomain.com).

Here is what that configuration looks like inside the site settings:

[Website Settings]
Site Name = Resources Portal
Domain = resources.yourdomain.com
Path = /
Favicon = https://assets.cdn.msgsndr.com/favicon.png
Head Tracking Code = 

Hit Save at the bottom. HighLevel will now route all incoming requests on that subdomain to this site structure.

Step 4: Configure Homepage, 404 Handling, and Page Slugs

A multi-page site needs proper slug management so visitors landing on resources.yourdomain.com hit your real index page instead of a blank screen.

1. Define the Homepage

Inside Sites > Websites > [Your Website] > Settings, check the Home Page field. Select the exact page that should render at the root URL (/). If you leave this blank, visitors who enter just the subdomain will see a generic 404.

2. Set Page Slugs

Click the Pages tab in your website dashboard. Each row displays its internal title and URL slug. Click the three dots (…) next to a page and choose Settings to customize the slug:

• Homepage: Keep the path blank or set it to home.
• About Page: Set path to about (resolves to resources.yourdomain.com/about).
• Services: Set path to services (resolves to resources.yourdomain.com/services).
• Contact: Set path to contact (resolves to resources.yourdomain.com/contact).

Never add slashes inside HighLevel’s path input box. Type contact, not /contact or /contact/.

3. Configure the 404 Error Page

Under website Settings, pick a dedicated 404 page from the Error (404) Page dropdown. Build a simple page named “404” with a search bar or a button back to the homepage. If a visitor mistypes a URL, HighLevel will serve this page while keeping the subdomain intact in the browser address bar.

Step 5: Fix Multi-Page Navigation Menus and Internal Links

The most common bug when mapping a subdomain to a multi-page site is broken menu links. If you cloned pages from a funnel or imported templates, menu items often point to old absolute staging URLs like https://api.leadconnectorhq.com/... or hardcoded root domains.

Open your global header or navigation menu inside the builder:

1. Select the Navigation Menu element.
2. Click on each menu item (Home, About, Pricing, Contact).
3. Set the Redirect Type to Go to page or Website URL.
4. If using Website URL, use relative paths instead of absolute URLs:

 
Home
 
Features
 
Pricing
 
Contact Us

Using relative paths (like /features) ensures that if you ever swap subdomains or change domains later, every link keeps working without having to update dozens of buttons manually. For official guidelines on domain configuration and site elements, refer to the HighLevel Domain Setup Documentation.

Troubleshooting Common Subdomain Issues

Here are the three errors I hit most often when attaching subdomains to multi-page sites in HighLevel:

1. Subdomain Shows “Invalid Request” or Funnel 404

This happens when the subdomain is registered under Settings > Domains, but hasn’t been selected in the Website Settings dropdown. HighLevel knows the domain belongs to your account, but doesn’t know which site to serve. Go to Sites > Websites > [Your Site] > Settings and make sure the domain is selected.

2. SSL Certificate Shows “Pending Verification” Past 15 Minutes

If you’re managing DNS via Cloudflare, check your SSL/TLS encryption mode under SSL/TLS > Overview. Make sure it’s set to Full or Full (strict). Also confirm the CNAME record proxy icon is toggled off (Grey Cloud / DNS Only) during initial certificate generation. Learn more about managing CNAME entries in the Cloudflare DNS Documentation.

3. Secondary Pages Redirect to the Root Domain

If clicking resources.yourdomain.com/pricing redirects you to yourdomain.com/pricing, you’ve got an aggressive redirect rule or duplicate slug mapping. Go to Settings > URL Redirects inside HighLevel and delete any conflicting wildcard redirects forwarding traffic away from your subdomain. If you need to route apex traffic too, check our guide on setting up root domain and WWW redirects in GoHighLevel.

Frequently Asked Questions

Can I connect multiple subdomains to the same multi-page website?

No. A single Website inside HighLevel can only be mapped to one primary domain or subdomain at a time. If you need multiple subdomains serving the same content, create URL Redirects under Settings > URL Redirects to forward the secondary subdomain to the primary one.

Can I use an A Record instead of a CNAME for a subdomain?

For subdomains, HighLevel requires a CNAME pointing to flash.funnels.msgsndr.com. A records (pointing to 34.68.234.4) are designed for root apex domains (e.g., example.com). Using an A record for a subdomain can cause SSL renewal failures down the line.

Does adding a subdomain affect my main website hosted elsewhere?

No. Adding a CNAME record for a specific subdomain (like hub.client.com) only routes requests for that exact subdomain prefix to HighLevel. Your apex domain (client.com) and other subdomains stay untouched on their existing hosts.

How do I whitelabel the entire app under a subdomain instead of a website?

App whitelabeling is handled at the agency level under Agency Settings > Company, pointing a CNAME to app.msgsndr.com. That’s totally separate from customer-facing websites. Follow our complete tutorial on how to set up a custom whitelabel domain in GoHighLevel for agency portal routing.

Next Steps

Now that your subdomain is live and routing properly to your multi-page site, make sure you configure your site-wide tracking scripts and metadata. If your site includes lead generation forms or dynamic scheduling, learn how to map form submission data to custom fields in GoHighLevel to capture attribution data directly from your new subdomain pages.