Revset
Book a Free Audit

30-minute call · No obligation

HomeGHL HubCRM & ContactsFixing Broken Email Links: A GoHighLevel CNAME Guide
REVSET LABS · EXPERT GUIDE·CRM & Contacts

Fixing Broken Email Links: A GoHighLevel CNAME Guide

1,018 words·4 min read·Updated 28 April 2026·beginner·
Arsalan ZaffarArsalan ZaffarLinkedIn

👉 Start your 30-day GoHighLevel free trial.

Start 30-Day Free Trial
Quick Answer

To fix email links that do not open in GoHighLevel, you must correctly configure your CNAME records for the email sending domain within your DNS provider. Ensure the 'Host' field of the CNAME record omits the root domain. This process typically takes 10-20 minutes, not including DNS propagation time.

Key Takeaways
  • Always omit your root domain from the CNAME 'Host' field (e.g., use 'email.mg' instead of 'email.mg.yourdomain.com').
  • Verify CNAME records within GoHighLevel's **Email Services** settings after making changes in your DNS provider.
  • Allow up to 48 hours for DNS propagation, though it often completes within minutes.
  • Use a dedicated subdomain (like 'mg.yourdomain.com') for email sending to isolate and manage email-specific DNS records.
  • Test your email links thoroughly by sending a new test email after any CNAME configuration changes.

When recipients click links in your GoHighLevel emails and nothing happens, the most common culprit is an incorrectly configured CNAME record for your email sending domain. GoHighLevel uses CNAME records to authenticate your domain for email sending and to track link clicks. If these records are set up improperly, especially by including your root domain, GoHighLevel cannot properly route or track the links, making them appear broken. Correcting these records is crucial for reliable email communication and accurate analytics.

Preparing to Fix Your CNAME Records

Before you dive into modifying DNS records, ensure you have all necessary access and information. You will need login credentials for your GoHighLevel account and your domain's DNS provider (e.g., GoDaddy, Namecheap, Cloudflare). Identify the specific domain you use for sending emails within GoHighLevel. Having this ready streamlines the entire process.

1
Log in to GoHighLevelOpen your web browser and log in to your GoHighLevel account. You need administrative access to view and manage email service settings.
2
Access Email ServicesFrom the left-hand menu, click on Settings. Then, navigate to Email Services to view your configured email sending domains.
3
Identify Your Sending DomainLocate the specific domain listed under Email Services that you are using for sending emails. Note the domain name for which you need to fix the CNAME records.

⚠️ Incorrectly altering DNS records can disrupt other services linked to your domain. Proceed with caution and follow steps precisely.

🔥 Pro Tip

Keep your DNS provider login handy. It saves time during the configuration process.

Step-by-Step CNAME Correction in Your DNS Provider

This section guides you through correcting the CNAME records directly within your domain's DNS provider. The key is to ensure the 'Host' or 'Name' field of your CNAME record is configured correctly, specifically by omitting the root domain from the record itself. This is the most common mistake leading to broken email links.

1
Log in to Your DNS ProviderAccess your domain registrar or DNS hosting provider (e.g., GoDaddy, Namecheap, Cloudflare). Log in to the account that manages your email sending domain.
2
Navigate to DNS ManagementFind the section for DNS management or DNS settings for your domain. This is often labeled as DNS Records, Zone File Editor, or Manage DNS.
3
Locate Existing CNAME RecordsReview your existing CNAME records. You are looking for records related to your email sending subdomain, typically starting with 'mg', 'replies', or 'support'.
4
Edit or Add the CNAME Record (Critical Step)Modify the existing CNAME record or add a new one. For the 'Type' field, select CNAME. For the 'Value' or 'Points to' field, enter 'mailgun.org' (or the specific value GoHighLevel provides).
5
Correct the 'Host' or 'Name' FieldThis is the most crucial step. In the 'Host' or 'Name' field, enter only the subdomain portion, *omitting your root domain*. For example, if your full email sending domain is `mg.yourcompany.com`, you enter `email.mg`. If it's `replies.yourcompany.com`, you enter `email.replies`. If it's `support.yourcompany.com`, you enter `email.support`.
6
Save Your ChangesClick Save, Add Record, or Update to apply your changes. Confirm any prompts to ensure the new CNAME record is stored.

⚠️ Do not include your full domain name in the 'Host' field. For example, if your domain is 'yourdomain.com', and GoHighLevel asks for 'email.mg', input 'email.mg' and *not* 'email.mg.yourdomain.com'.

🔥 Pro Tip

If unsure about the exact 'Host' value, GoHighLevel's Email Services section provides the precise CNAME records you need to set up for your domain. Copy them exactly.

Try GoHighLevel Free

Start your 30-day GoHighLevel free trial

Everything in this guide is in your free trial. 30 days, no credit card — the platform behind 78+ revenue systems.

Start 30-Day Free Trial

Some links are affiliate links — if you sign up we may earn a commission, at no extra cost to you. We only recommend GoHighLevel because we build on it every day.

Verifying Your CNAME Records in GoHighLevel

After updating your CNAME records in your DNS provider, it's essential to verify them within GoHighLevel. This step confirms that GoHighLevel recognizes the changes and your email sending domain is correctly authenticated. DNS changes can take time to propagate across the internet, so patience is key.

1
Return to GoHighLevel Email ServicesGo back to your GoHighLevel account. Navigate to Settings → Email Services.
2
Check Verification StatusLook at the status next to your email sending domain. It should eventually change from 'Pending' to 'Verified' or 'Active'.
3
Refresh or Re-Verify (If Needed)If the status remains 'Pending' for an extended period, try refreshing the page or clicking any 'Verify' button provided within GoHighLevel for that domain. Remember DNS propagation can take minutes to hours.

⚠️ If the status does not change to 'Verified' after several hours, re-check your CNAME entries in your DNS provider for any typos or incorrect formatting.

🔥 Pro Tip

Use an online DNS lookup tool (like whatsmydns.net) to check if your CNAME records have propagated globally before expecting GoHighLevel to verify them.

Once your CNAME records are verified in GoHighLevel, the final crucial step is to test your email links. This confirms that the fix was successful and your recipients will experience a seamless journey when clicking on your content.

1
Create a New Test EmailCompose a new test email within GoHighLevel. Include a link to a webpage or offer that you want to test.
2
Send the Test EmailSend this test email to an address you can access. Avoid using old drafts or emails that were sent before the CNAME fix.
3
Click and Verify the LinkOpen the received test email and click on the link. Confirm that it opens correctly in your browser and directs you to the intended destination.
🔥 Pro Tip

Test links on different devices and email clients (e.g., Gmail, Outlook, mobile) to ensure broad compatibility.

Troubleshooting Common Issues

⚠️ My CNAME status in GoHighLevel remains 'Pending'.
Check your DNS provider for any typos in the CNAME record's 'Host' or 'Value' fields. Ensure you've waited sufficient time for DNS propagation (up to 48 hours, though often faster). Re-verify the domain in GoHighLevel after checking.
⚠️ Links still don't open even after GoHighLevel shows 'Verified'.
Clear your browser cache and cookies, then re-test by sending a brand new email. Ensure the email you are testing was sent *after* the CNAME verification. If the issue persists, contact GoHighLevel support with screenshots of your DNS records.
⚠️ My DNS provider automatically adds my root domain to the CNAME 'Host' field.
Some providers automatically append the root domain. If you input `email.mg` and it appears as `email.mg.yourdomain.com`, this is usually correct. The problem arises when you *manually* input the root domain in addition to the subdomain, creating `email.mg.yourdomain.com.yourdomain.com`. Always check the final saved record.
⚠️ GoHighLevel shows multiple CNAME records needed, but I only have one for 'mg'.
GoHighLevel often requires two CNAME records for full email functionality (e.g., one for tracking, one for Mailgun). Ensure both are added. Consult the exact records GoHighLevel provides under Settings → Email Services for your domain.

Common Mistakes to Avoid

  • Including the full root domain in the CNAME 'Host' or 'Name' field (e.g., entering 'email.mg.yourdomain.com' instead of just 'email.mg').
  • Typos in the CNAME 'Value' or 'Points to' field (e.g., 'mailgun.org' vs. 'mailgun.com').
  • Not waiting long enough for DNS propagation after saving changes in your DNS provider.
  • Attempting to use a CNAME record for your root domain directly (e.g., 'yourdomain.com'), which is generally not supported for email sending CNAMEs.
  • Testing old emails instead of sending a fresh test email after implementing DNS changes.

Frequently Asked Questions

QWhat exactly is a CNAME record and why is it important for GoHighLevel emails?
A CNAME (Canonical Name) record is a type of DNS record that maps an alias name to a true or canonical domain name. For GoHighLevel emails, CNAMEs are essential for two main reasons: domain authentication and link tracking. They allow GoHighLevel (via Mailgun) to send emails on behalf of your domain, improving deliverability. They also enable GoHighLevel to track clicks on links within your emails, providing valuable analytics without breaking the links.
QHow long does it take for CNAME changes to become active (DNS propagation)?
DNS propagation refers to the time it takes for changes to your DNS records to update across the internet's servers. While it can sometimes be instantaneous, it typically takes anywhere from a few minutes to several hours. In rare cases, it might take up to 48 hours for changes to fully propagate globally. It's advisable to wait at least 1-2 hours before expecting GoHighLevel to verify the records.
QWhat if my DNS provider's interface doesn't have a 'Host' or 'Name' field, or it's different?
DNS provider interfaces vary significantly. The 'Host' or 'Name' field might be labeled as 'Subdomain', 'Record', or simply be the first input field for the record. The 'Value' or 'Points to' field might be 'Target' or 'Data'. If you're unsure, consult your DNS provider's help documentation or support, or refer to common guides for your specific provider (e.g., GoDaddy DNS settings, Namecheap CNAME setup).
QCan I use the same CNAME records for multiple GoHighLevel sub-accounts or locations?
No, CNAME records are specific to a single domain and often to a single service instance. Each GoHighLevel location or sub-account that sends emails from a unique domain will require its own set of correctly configured CNAME records. If you're using the same domain across multiple locations, you'll need to configure unique subdomains (e.g., `mg1.yourdomain.com` for location 1, `mg2.yourdomain.com` for location 2) and their corresponding CNAMEs.
QBesides CNAMEs, are there other reasons GoHighLevel email links might not open?
While CNAME issues are the primary cause, other factors can occasionally affect email links. These include: outdated browser cache, network firewalls blocking access to tracking domains, or the target URL itself being broken or incorrect. Always ensure the link destination is valid and accessible, and test with a fresh browser session. If CNAMEs are verified and links still fail, check your email content for malformed URLs.
Try GoHighLevel Free

Start your 30-day GoHighLevel free trial

Everything in this guide is in your free trial. 30 days, no credit card — the platform behind 78+ revenue systems.

Start 30-Day Free Trial

Some links are affiliate links — if you sign up we may earn a commission, at no extra cost to you. We only recommend GoHighLevel because we build on it every day.

Arsalan Zaffar
Arsalan Zaffar
Revset Labs · Revenue Systems · 78+ GHL Builds

Arsalan writes GHL guides from real build experience — 78+ systems, $9.2M in client pipeline. Wharton, CXL & Google certified.

Connect on LinkedIn
Tags:GoHighLevelEmail MarketingDNSCNAME RecordsTroubleshootingEmail Deliverability