GoHighLevel Email Deliverability Pre-Launch Checklist — HL Growth Partner, Dr Priya Jaganathan

GoHighLevel Email Deliverability: The Pre-Launch Checklist Most Agencies Skip (2026)

May 28, 2026

GoHighLevel Email Deliverability: The Pre-Launch Checklist Most Agencies Skip (2026)

Most Australian agencies set up GoHighLevel, connect an email integration, and send. Then they wonder why open rates are low, contacts stop engaging, or — worst case — a domain ends up on a blocklist. The problem is almost never the message. It is the infrastructure underneath it.

This checklist walks through every layer of GHL email deliverability before you send a single campaign: domain selection, DNS authentication, choosing the right sending integration, warm-up, list hygiene, and the content signals that quietly route you to spam. Get this right once and it compounds. Get it wrong and you are cleaning up reputation damage for months.

Choosing your sending domain

Do not send marketing email from your root domain (e.g., yourbusiness.com.au). If that domain gets flagged or lands on a reputation blocklist, it affects every email you send — including transactional and internal. Instead, use a dedicated subdomain for outbound marketing: something like mail.yourbusiness.com.au or email.yourbusiness.com.au.

The subdomain is isolated. If its reputation degrades, your root domain is unaffected. You can also burn it down and start fresh without touching your primary brand identity. Set this up in your domain registrar or DNS provider before touching anything inside GHL.

For agencies managing multiple client sub-accounts, each client should have their own sending subdomain. Sharing a sending domain across clients means one bad list poisons everyone on that domain.

Configuring SPF, DKIM, and DMARC correctly

These three DNS records are the baseline of email authentication. Inbox providers use them to verify that the email claiming to be from your domain was actually authorised by you. Missing or misconfigured records are the single most common cause of deliverability failures in GHL setups.

DNS Record Purpose Recommended Value / Check
SPF (TXT) Lists the mail servers authorised to send on behalf of your domain Include Mailgun's SPF entry (include:mailgun.org) or LC Email's equivalent. Keep to a single SPF record — multiple TXT records for SPF will break validation.
DKIM (TXT or CNAME) Cryptographic signature proving the message wasn't altered in transit Copy the DKIM key exactly from GHL's email settings (or from your Mailgun domain dashboard) and add it as instructed. A miscopied record — even one wrong character — will fail.
DMARC (TXT) Tells inbox providers what to do when SPF or DKIM fails, and sends you reports Start with p=none and an rua reporting address so you can monitor before enforcing. Move to p=quarantine once you have a clean baseline. Use v=DMARC1; p=none; rua=mailto:[email protected] as a starting point.
Custom tracking domain (CNAME) Routes GHL click and open tracking through your domain rather than a generic GHL domain Set up in GHL under Settings → Email Services → Custom Tracking Domain. This avoids shared-domain reputation spillover on tracked links.
MX records Required for your sending domain to receive bounce-back and reply messages If your sending subdomain is not set up to receive email, some inbox providers will lower trust. Point MX to your root domain's mail handling or a catch-all.

After adding all records, use a tool like MXToolbox or mail-tester.com to verify each one resolves correctly. DNS propagation can take up to 48 hours — check again before your first send rather than immediately after saving the records.

Mailgun vs LC Email: which should you use?

GoHighLevel gives you two paths for sending email: LC Email (GHL's built-in sending service) and Mailgun (a third-party SMTP integration you configure separately).

LC Email is the simpler option. It requires less configuration and is managed inside GHL without an external account. The trade-off is less visibility into delivery data and fewer controls over sending infrastructure. For low-volume sub-accounts sending newsletters or automation sequences under a few thousand contacts, LC Email can work well — particularly when the account is new and the team is not technical.

Mailgun gives you a dedicated sending domain, detailed logs, bounce handling, and more granular control. For agencies running high-volume campaigns, onboarding sequences, or managing deliverability seriously across multiple clients, Mailgun is the better foundation. You can see exactly what bounced, why, and when. You can also separate transactional and marketing streams.

If you are comparing GHL's email capabilities against other platforms, see the GHL vs Mailchimp comparison for Australian businesses and the GHL vs ActiveCampaign breakdown for a fuller picture of where each platform sits on deliverability infrastructure.

Warming up a new sending domain

A brand-new domain or subdomain has no sending reputation. Inbox providers have never seen it before. If you import 10,000 contacts and blast a campaign on day one, you will almost certainly trigger spam filters — even with perfect DNS configuration.

Warm-up is the process of building reputation incrementally:

  1. Start with your most engaged contacts — people who have recently opened or clicked your emails, or opted in within the last 30–60 days.
  2. Begin with small volumes. There is no universal number, but starting in the low hundreds per day and doubling every few days over two to four weeks is a reasonable approach for most Australian SME lists.
  3. Monitor engagement signals tightly during warm-up: open rate, click rate, bounce rate, and spam complaints after each send.
  4. Only increase volume when signals are healthy. A complaint rate above 0.1% or bounce rates above 2–3% is a signal to stop and investigate, not push through.
  5. If you are sending appointment reminders or transactional flows alongside campaigns, keep them on a separate subdomain so warm-up does not affect operational messages. GHL's workflow automations for reminders — like the ones covered in GHL appointment reminder workflows — benefit from a clean, always-on sending reputation that is insulated from bulk campaign volume.

List hygiene before the first send

The list you send to is as important as the domain you send from. A list full of invalid, unengaged, or purchased addresses will generate hard bounces and spam complaints that destroy a new domain's reputation before it has a chance to build one.

Before importing any list into GHL:

  • Run it through an email verification service (ZeroBounce, NeverBounce, or similar). Remove invalid, role-based (info@, admin@), and catch-all addresses.
  • Segment by recency. Contacts who have not engaged in 12 months or more should be excluded from your initial sends entirely. Re-engagement campaigns are a separate exercise run from an already-warm domain.
  • Never import purchased lists. They are full of spam traps — addresses maintained by inbox providers specifically to identify senders with poor list practices. Hitting one can get your domain or IP blocklisted immediately.
  • In GHL, use tags and smart lists to isolate your warm segment. You can build a smart list filtered by date added or custom field to keep warm-up sends clean and auditable.

Content patterns that trigger spam filters

Authentication and list hygiene get your email to the inbox door. Content is what inbox providers look at once the envelope passes. The following patterns increase spam filter scoring:

  • Spam trigger words in subject lines. Words like "free", "guaranteed", "no risk", "act now", and anything that reads like a late-night infomercial. Write subjects the way you would write them to a colleague.
  • Heavy image-to-text ratios. An email that is mostly images with minimal text is a common spam pattern. Aim for a reasonable balance — actual readable text in the HTML, not just alt-text on images.
  • Missing or broken unsubscribe links. GHL includes these by default in campaign emails. Do not remove them. In Australia, you are also legally required to include them under the Spam Act 2003.
  • Link shorteners or unrelated redirect domains in body links. Use your own domain for tracking links (see custom tracking domain above) and avoid third-party link shorteners in email — they are flagged by default.
  • Large HTML with excessive inline styling or invisible text. Spammers use hidden text to game keyword filters. Keep your HTML clean and don't include invisible content.
  • Inconsistent From name and domain. The From name, From address, and Reply-To should all align and be consistent across sends. Switching these frequently degrades reputation signals.

Monitoring after launch

Deliverability is not a set-and-forget task. Once you are sending, these are the signals to watch:

  • Bounce rate. Separate hard bounces (invalid address — permanent) from soft bounces (temporary delivery failure). GHL will automatically suppress hard bounces, but if your hard bounce rate on a send is above 2%, the list needs cleaning.
  • Spam complaint rate. Google's Postmaster Tools gives you complaint rate data for Gmail recipients. Keep this below 0.1%. Above 0.3% and Gmail will start routing you to spam by default.
  • Open rate trends. A sudden drop in open rates — particularly on segments that previously engaged — can indicate inbox routing changes. It does not always mean spam folder, but it warrants investigation.
  • DMARC reports. If you set up a rua reporting address in your DMARC record, you will receive XML reports showing authentication pass/fail rates. Tools like Postmark's DMARC Digests or dmarcian make these readable. Review them monthly at minimum.
  • Blocklist checks. Run your sending domain and IP through MXToolbox's blacklist check periodically. If you appear on a major list, find out why before simply requesting removal.

Common mistakes to avoid

  • Setting up DNS once and never checking it again. Records can break after a domain migration, a registrar change, or a DNS provider update. Verify authentication every time anything in your domain setup changes.
  • Using the same subdomain for transactional and marketing email. Separate them. Campaign traffic is noisy and variable — it should not affect the reputation of the domain sending appointment confirmations and receipts.
  • Importing everyone into GHL on day one and sending immediately. This is the most common deliverability failure pattern. Warm the domain, clean the list, then scale.
  • Ignoring the custom tracking domain setting in GHL. Without it, your tracked links go through a shared GHL domain. If anyone else on that shared domain behaves badly, your click-tracking links are tainted by association.
  • Setting DMARC to p=reject before understanding your sending streams. If you have any legitimate sending source not yet authenticated — a third-party booking system, an invoice platform, another CRM — p=reject will silently drop those emails. Start with p=none, review your reports, then tighten enforcement progressively.

If you want your GoHighLevel email infrastructure set up so it actually lands in the inbox, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

Do I need Mailgun to use GHL email in Australia?

No. GoHighLevel's native LC Email service works without a separate Mailgun account. However, if you are running high-volume campaigns, managing multiple clients, or need detailed delivery logs and bounce diagnostics, Mailgun gives you significantly more control. Many Australian agencies start with LC Email and migrate to Mailgun as volume and complexity increase.

How long does domain warm-up take?

For most small to mid-size Australian lists — up to 20,000–30,000 contacts — a structured warm-up typically takes three to six weeks. The timeline depends on your daily volume increases, how engaged your early segments are, and how your sending reputation builds with each inbox provider. Do not rush it. A poor warm-up creates reputation debt that takes longer to repair than it would have taken to do it properly.

What happens if my sending domain ends up on a blocklist?

First, stop sending from that domain immediately. Identify the cause — typically a high complaint rate, spam trap hits, or a sudden volume spike. Fix the underlying issue (clean the list, review content, reduce volume) before requesting removal. Most blocklist operators provide a removal request process, but they will re-list you quickly if the behaviour continues. In severe cases it may be faster to start fresh with a new subdomain than to rehabilitate the existing one.

Can I use GHL email to send to a list I purchased?

You can technically import any list into GHL, but sending to a purchased list will almost certainly damage your sending reputation. Purchased lists contain invalid addresses, spam traps, and contacts who have never consented to hear from you. In Australia, sending unsolicited commercial email also raises issues under the Spam Act 2003, which requires express or inferred consent. The deliverability risk and the legal exposure are both real. Only send to lists you have built with explicit opt-ins.

How do I check if my SPF, DKIM, and DMARC records are set up correctly in GHL?

After adding your DNS records, send a test email to a tool like mail-tester.com or use MXToolbox's email header analyser. These tools parse the authentication results from the email header and show you whether SPF, DKIM, and DMARC each passed or failed. Inside GHL, the email settings screen will also show a verification status for your configured sending domain — look for green checkmarks against each record type before sending to a live list.

Dr PriyaJaganathan

Dr PriyaJaganathan

Dr Priya Jaganathan is a Go High Level Certified Admin, trusted CRM consultant based in Australia, and a keynote speaker at SaaSpreneur Sydney and Level Up 2025 in Dallas.

Back to Blog