SOP 272: GoHighLevel Whitelabeling & Custom Branding
This SOP walks you through branding GoHighLevel as your own: setting a whitelabel login domain with SSL, applying logos/colors, and configuring LC Email with a verified sender domain.
Last Updated / Reviewed: 11/13/2025
Execution Time: 30–45 minutes hands-on (+30–60 minutes DNS wait)
🚀 Goal: Whitelabel GoHighLevel with your domain, branding, and authenticated sender email.
🤞 Ideal Outcome: Branded HTTPS login at your subdomain with logos/colors applied and LC email domain verified; test email shows SPF/DKIM pass and tracked links resolve.
🤔 Why this is important: A branded platform improves client trust and keeps your agency front-and-center. Done once, it reduces ongoing support friction around logins and email deliverability.
🧐 Where this is done GoHighLevel (agency view and sub-account), your DNS provider dashboard, and an external email inbox.
🗓️ When this is done: During new agency setup or rebranding before onboarding clients.
👨 Who does this: GoHighLevel agency admin with DNS access.
__⚠️Prerequisites or requirements: __You need agency admin access in GoHighLevel and a DNS host login for the chosen domain.
Click here to get the most up-to-date version of this SOP
Prepare subdomains and brand assets
In this step, you’ll choose the domain pieces and visuals that make GoHighLevel look like your own platform. Picking the right login subdomain and email sender domain now saves time and effort later, and having your logos, colours, and policy links ready ensures a smooth branding setup.
01▸ Decide the app login subdomain (e.g., app.yourdomain.com).
02▸ Decide the sender domain (yourdomain.com or a dedicated subdomain like mg.yourdomain.com)
03▸ Gather assets such as the main logo, login logo, favicon (32x32), brand hex color, support email/URL, and URLs for Privacy Policy and Terms.
Create app login CNAME at DNS host
Example: If your domain is brightdentalgroup.com, you want your clients to log in to GoHighLevel via app.brightdentalgroup.com.
01▸ Sign in to your DNS provider account (e.g. GoDaddy.com, Cloudflare.com, etc.).
02▸ Look for something called DNS Settings, Zone Editor, or DNS Records.
03▸ Add a CNAME record for the app subdomain. Create a new record with Host=app, Type=CNAME, and TTL=default or 5 minutes.
04▸ Click save, add record, or apply changes (depending on your DNS provider).
05▸ In the GoHighLevel agency settings, go to "Domains & URL Redirects" and click "Connect a domain". Copy the exact target value and paste it into the CNAME or domain target field, e.g. app.yourdomain.com.
06▸ Set proxy to DNS Only. If you use Cloudflare, click the orange cloud icon to turn it OFF. This sets the record to DNS only to avoid redirect issues.
07▸ Confirm the CNAME points to GoHighLevel. Your login subdomain (e.g., app.yourdomain.com) should now point to GoHighLevel. SSL (helps secure the connection between your website or app and the user’s browser) may take up to 24 hours to issue.
Configure whitelabel domain and branding GoHighLevel
01▸ Switch to "Agency View".
02▸ Go to "Settings" → "Company", then "Whitelabel" and enter your full whitelabel domain, e.g. https://app.yourdomain.com. Click "+Add Domain", then "Continue".
03▸ Next, authorize the domain and confirm domain field shows your subdomain without errors.
04▸ Once verified, GoHighLevel automatically installs an SSL certificate for security. Wait a few minutes for the status to show “SSL Active” or “Secured”.
SSL provisioning can take minutes up to 24 hours. Confirm SSL status updates to "Secure/Active."
05▸ Next, add branding details such as company logo, favicon, color, agency name, support email, and URLs for privacy policy and terms.
06▸ Test your domain. Visit https://app.yourdomain.com and confirm the GoHighLevel login loads over HTTPS with your branding. The page should show your logo, colors, and no certificate warnings.
Add sender domain via LC email (GoHighLevel agency view)
01▸ Switch to "Agency view" → "Settings" → "Email Services" → a pop-up will appear, click "Create Dedicated Domain".
02▸ Enter the domain name, e.g. lc.yourdomain.com and click "Add & Verify", then "Continue".
03▸ Leave this page open so you can copy DKIM, SPF, and tracking records in the next step.
Publish LC email DNS records and verify
Now that you’ve added your sender domain to LC email, the next step is publishing the DNS records it provides. These records (DKIM, SPF, and tracking/bounce CNAMEs) prove you own the domain, secure your emails against spoofing, and allow link tracking on your brand. Once set up and verified, your emails will be sent from your domain with proper authentication, boosting deliverability and trust.
01▸ Log in to your DNS host, e.g. Cloudflare, GoDaddy, etc.
02▸ Add DKIM CNAME record(s) at your DNS host exactly as shown in "LC Email" (TTL default).
03▸ Add SPF TXT record (or include) exactly as shown in "LC Email" (TTL default).
04▸ Add tracking/bounce CNAME record(s) exactly as shown in "LC Email" (TTL default; proxy OFF if on Cloudflare).
05▸ DNS updates may take a few minutes to a few hours to spread globally. You can check progress at https://dnschecker.org.
- Enter your domain name.
- Check each record type (TXT or CNAME) to confirm they’re visible.
06▸ Now, go to GoHighLevel "Email Services" page where you've left open earlier → click "Verify Domain". You should see a status update for each DNS record.
07▸ Repeat clicking "Verify Domain" until all DNS records show as "Verified" in the "LC Email" Domains list. It may take 30–60 minutes for DNS propagation. Wait until every record shows "Verified."
08▸ Send a test email from your verified domain, e.g. hello@yourdomain.com. Check if the email sends successfully and there are no “via msgsndr.com” or “unverified sender” messages that appear. Emails should also land in the inbox (not spam).
Set default LC email and send a test
01▸ Switch to your test location (sub-account) in GoHighLevel.
02▸ Go to "Settings" → "Email Services" and select your dedicated domain.
Note: Make sure your verified sender domain (e.g. yourdomain.com) appears here. If you see “Not Connected,” go back and verify your DNS records first.