GoHighLevel Email Deliverability: Dedicated Domains, Warm-Up, and Fixes

Set up LC Email dedicated sending domains, assign domains by email type, warm up properly, and monitor reputation so your HighLevel emails land in the inbox.

Why Deliverability Is an Infrastructure Problem First

You can write the best subject line in the world, but if your email lands in spam or never arrives at all, none of it matters. GoHighLevel email deliverability is an infrastructure problem before it is a copy problem. Every workflow, campaign, and appointment reminder you send through the platform depends on your sending domain, DNS records, warm-up history, and reputation. If you skip those steps, your GoHighLevel follow-up automations will trigger on schedule and send nothing that reaches an inbox.

By default, HighLevel sends your emails through shared infrastructure. HighLevel keeps the From address you configured but rewrites the actual sending address into a plus format, something like test+gohighlevel.com@mg.msgsndr.com. Recipients see that refactored address in the message details. Your reply-to address is unaffected, so replies still reach your inbox. But the shared sending domain means you share sending reputation with other senders on that infrastructure. Google notes that the activity of any sender on a shared IP affects the reputation of all senders on it. A dedicated domain keeps your domain reputation your own. Even with a dedicated domain, you still share the sending IP unless you add a dedicated IP, which HighLevel positions for very high-volume senders.

A dedicated sending domain changes that. It lets you send emails that appear to come directly from your brand, protects your sender reputation, and gives you full control over authentication records. This post walks through the entire process: choosing and setting up a dedicated sending domain in LC Email, assigning different domains by email type, warming up new domains using HighLevel's fixed-stage model, monitoring reputation with Google Postmaster Tools, and fixing deliverability problems when they arise. HighLevel updates these screens often, so check the current help articles for the latest menu paths and features.

LC Email vs Custom SMTP

HighLevel offers two ways to send email: LC Email, which is the platform's native sending service, and Custom SMTP, where you connect a third-party provider. Creating a dedicated domain in-app is an LC Email feature. Custom SMTP users don't have that option. With a Custom SMTP provider, you are responsible for setup and troubleshooting, and support's ability to help with compliance and deliverability is limited. The rest of this guide assumes you are using LC Email.

Choosing Your Sending Subdomain

The first decision is which subdomain to use. HighLevel's guidance recommends a unique subdomain not used for any other purpose to protect your root domain reputation. Common examples include mail.yourbrand.com, emails.yourbrand.com, or no-reply.yourbrand.com. The root domain can be used only if it is not already in use with Google Workspace or another email provider. If Workspace sends and receives mail on your root domain, you must use a subdomain. Adding the root domain to HighLevel would conflict with the existing MX records that route mail to Workspace. The subdomain keeps HighLevel's sending infrastructure separate from your primary email service.

You can create as many subdomains as you like and assign different ones for different types of email. Picture a two-location med spa that wants to separate transactional appointment reminders from marketing campaigns. They might use calendar.medspa.com for appointment emails and promo.medspa.com for campaigns. Each subdomain gets its own DNS records, its own warm-up timeline, and its own reputation. If one subdomain develops a poor reputation, it does not automatically damage the others.

The From address you configure in HighLevel must be on the same organizational domain as the sending subdomain. If your sending subdomain is mail.yourbrand.com, your From address can be sender@yourbrand.com or sender@mail.yourbrand.com, but it cannot be user@otherbrand.com. This alignment is required for DMARC authentication.

Your reply-to address is independent. You can set reply-to to your root domain inbox, such as support@yourbrand.com, so that replies land in your main inbox even though the email was sent from mail.yourbrand.com. This strategy protects your root domain reputation while keeping replies centralized. The From address authenticates the send, and the reply-to address routes the conversation.

Abstract 3D scene of a glossy green sphere orbited by smaller saffron and lilac spheres, each sending its own stream of small envelopes, representing separate sending subdomains

Step-by-Step Setup: Adding a Dedicated Sending Domain

Once you have chosen your subdomain, the setup process is straightforward. Navigate to Settings, then Email Services, then the Dedicated Domain and IP tab. Click Add Domain and enter your subdomain. HighLevel will generate five DNS records that you must add to your DNS host: two TXT records for SPF and DKIM, two MX records, and one CNAME record. HighLevel's help article explains how to set up a dedicated sending domain, including DNS instructions for common providers.

The SPF record is a TXT record with the value v=spf1 include:mailgun.org ~all. This tells receiving servers that Mailgun is authorized to send email on behalf of your subdomain. The DKIM record is also a TXT record, but the host and value are unique to your domain. Copy the DKIM values exactly from the HighLevel screen. Multiple DKIM records for the same domain are not supported.

The two MX records have the values 10 mxa.mailgun.org and 10 mxb.mailgun.org. These route inbound mail for the subdomain to Mailgun. The CNAME record host is "email." followed by your subdomain prefix. Copy the value exactly from the platform screen.

HighLevel can auto-configure the records, or you can add them manually when auto-configuration isn't available. Manual setup is common with providers like Cloudflare, GoDaddy, or Namecheap. Log in to your DNS host, navigate to the DNS management page for your domain, and create each record with the host, type, and value exactly as shown in HighLevel. DNS propagation can take up to 24 hours, though it is often faster. After adding the records, return to HighLevel and click Verify. If verification still fails after propagation, force verification again and then contact your DNS host.

Common errors include "Domain already pointing to email server!" which means the subdomain has existing MX or SPF records connected to another email service. Remove those records before verifying in HighLevel. Another error is caused by wildcard DNS records, such as a wildcard A record or CNAME that catches all subdomains. Wildcard records can interfere with verification. Temporarily remove the wildcard, verify the domain in HighLevel, then add the wildcard back. Alternatively, add the five records manually for each subdomain you plan to use.

Once the domain is verified, HighLevel automatically generates an SSL certificate for the subdomain. Now you can set headers for the domain. Click the three-dot menu next to the domain, choose Set Headers, and enter your From Name and From Email. The From Name is the display name recipients see, such as "Sarah from Acme Consulting." The From Email must be an address on the same organizational domain, such as sarah@yourbrand.com or sarah@mail.yourbrand.com. Save the headers.

Adding a DMARC Record

DMARC is a TXT record that tells receiving servers how to handle emails that fail SPF or DKIM authentication. Add a TXT record at the host _dmarc in your DNS. HighLevel's sending guide shows an example policy of p=reject. Google requires DMARC for bulk senders and allows a policy of none. HighLevel's spam troubleshooting article suggests v=DMARC1; p=none; on both the root and the sending subdomain when diagnosing DMARC failures.

The p=none policy means that emails failing DMARC will still be delivered. This is the safest starting policy. Once you have confirmed that all legitimate mail is passing DMARC, you can change the policy to p=quarantine, which sends failing mail to spam, or p=reject, which blocks it entirely. If you are troubleshooting DMARC failures, set the policy to none temporarily while you diagnose the issue, then tighten it once authentication is working.

You can add DMARC at the root domain, the subdomain, or both. If you plan to change an existing root DMARC policy, check with whoever manages the root domain's mail before making changes.

Domain Configuration: Assigning Domains by Email Type

After you have verified one or more dedicated sending domains, the next step is to assign them to specific email types. This is done in the Domain Configuration panel, which you will find under Sub-Account Settings, Email Service, SMTP Service, Dedicated Domain and IP, then the Domain Configuration tab. Domain Configuration is separate from default headers, which HighLevel describes as the From Name and From Email fallback applied when DMARC alignment fails on a domain. HighLevel lets you assign a validated domain to each of four email types: Workflows, Email Campaigns, Bulk Action Emails, and Manual 1-to-1 emails. Any type you do not assign will fall back to the default domain.

The default domain is the catch-all. If you have only one dedicated sending domain, set it as the default. If you have multiple domains, choose the one you want to handle any email type that is not explicitly assigned. Without a default domain, unassigned sends may fall back to HighLevel's shared infrastructure, which defeats the purpose of setting up a dedicated domain in the first place. Always designate a default before launching campaigns.

Domain Configuration also includes Frequency Settings, which allocate a percentage of your scheduled emails across the domains you've added. The percentages must total 100 percent. For example, if you have two domains and you want to send 70 percent of your scheduled emails through the first domain and 30 percent through the second, you would set those percentages to 70 and 30. Frequency splits are useful when you want to send more volume through a domain with a stronger reputation and limit exposure for a newer domain. You can reduce a domain's allocation without stopping sends entirely, which helps you manage reputation risk during warm-up or recovery.

Changes to Domain Configuration apply only to new sends. Emails that are already queued or in progress will continue to use the domain that was assigned when the workflow or campaign was triggered.

Calendar Domains

Calendar emails, which include appointment confirmations, reminders, and reschedule notifications, can have their own dedicated sending domains. This setting lives under Domain Configuration, then Calendar. You can add up to five domains and distribute sends across them by percentage. Only domains created at the sub-account level are selectable for calendar emails. This feature is available for LC Email only.

Separating calendar emails onto their own domain is a good idea for agencies or businesses that send high volumes of appointment reminders. HighLevel's stated reason is protecting deliverability for time-sensitive appointment communications.

Payment and Invoice Domain

HighLevel's changelog added a section under Payment and Invoices settings to set a dedicated sending domain for payment-related communications, for brand consistency and deliverability.

A Sample Domain Map

Imagine an agency with twelve sub-accounts, each representing a local service business. The agency sets up three subdomains: one for 1-to-1 and calendar emails, one for workflow automations, and one for marketing campaigns. The 1-to-1 and calendar domain is mail.agencybrand.com, which handles appointment reminders, manual emails from the inbox, and payment receipts. The workflow domain is auto.agencybrand.com, which sends follow-up sequences, lead nurture, and re-engagement workflows. The campaign domain is promo.agencybrand.com, which sends newsletters and promotional blasts. Each domain is warmed up separately, and each has its own reputation. If a campaign on promo.agencybrand.com triggers spam complaints, it does not affect the appointment reminders sent from mail.agencybrand.com. This is a suggestion, not a requirement. You can use a single domain for everything, or you can create a unique domain for each sub-account. The right strategy depends on your volume, your email types, and your risk tolerance.

Agency Rollout: Sharing Domains and Migrating Sub-Accounts

If you are an agency managing multiple sub-accounts, you can set up a dedicated sending domain at the agency level and share it with sub-accounts that do not have their own domain. By default, the agency's default dedicated domain is shared with any sub-account that has no dedicated domain of its own. This is convenient for small sub-accounts that do not send enough volume to justify their own domain. However, HighLevel's guidance is clear: do not share sending domains across sub-accounts if you can avoid it. Each sub-account should have its own dedicated domain to keep reputation isolated. If one sub-account sends spam or generates complaints, that problem stays contained instead of spreading to the deliverability of other sub-accounts.

A sub-account-created domain cannot be shared with the agency or other sub-accounts. Only agency-level domains can be shared. If you want to give a sub-account its own domain, you must create and verify the domain within that sub-account's settings.

To migrate sub-accounts from shared sending infrastructure or Mailgun to LC Email with a dedicated domain, go to Agency Settings, Email Services, Location Settings. You will see a list of all sub-accounts with a filter to show which email provider each one is using. You can edit a sub-account individually by clicking the pencil icon, then choosing LeadConnector as the provider and selecting a dedicated domain or the agency default. For bulk migration, use the filter to select all sub-accounts using a particular provider, click Manage, then Migrate to LC, and choose the domain. Be aware that in-flight sends during migration may be affected. Plan migrations during low-traffic periods, such as late at night or over a weekend, to minimize disruption.

Agency Rollout Checklist

Here is a checklist for agencies rolling out dedicated sending domains across multiple sub-accounts:

  • Audit current sending: identify which sub-accounts are using shared infrastructure, Mailgun, or Custom SMTP.
  • Decide on domain strategy: one agency-level domain shared across all sub-accounts, or unique domains per sub-account, or a hybrid approach where high-volume sub-accounts get their own domain and low-volume sub-accounts share an agency domain.
  • Create and verify domains: add each subdomain in HighLevel, configure DNS records, and verify.
  • Set headers: configure From Name and From Email for each domain.
  • Add DMARC records: ensure each root domain or subdomain has a DMARC policy.
  • Configure Domain Configuration: assign domains to email types and set frequency splits if using multiple domains.
  • Enable warm-up: start the warm-up process for each new domain before migrating live traffic.
  • Migrate sub-accounts: use the bulk migration tool or migrate individually during low-traffic windows.
  • Monitor: check bounce rates, spam rates, and Google Postmaster data daily for the first two weeks after migration.
  • Document: record which domain is assigned to which sub-account and which email types, so you can troubleshoot quickly if deliverability drops.
Abstract 3D staircase of green glass steps with stacks of white envelopes growing taller on each step toward a warm saffron glow, representing gradual email warm-up

Warm-Up: The Fixed-Stage Model

A brand-new sending domain has no reputation. If you immediately send thousands of emails from a domain that has never sent mail before, inbox providers will treat it as suspicious and route most of it to spam or block it entirely. Warming up a domain means gradually increasing send volume over several weeks so that inbox providers learn to trust the domain. HighLevel uses a fixed-stage warm-up model with predefined daily limits.

The warm-up process is divided into fifteen stages. Each stage has a daily sending limit. Progression to the next stage happens only when you reach the full daily limit of the current stage. If you send fewer emails than the stage limit on a given day, the domain stays in that stage. The limit does not block sending. You can send more emails than the stage limit, and they will go out, but hitting the full daily limit is what triggers progression to the next stage. Here are the stages and daily limits:

  • Stage 1: 1,000 emails per day
  • Stage 2: 2,500 emails per day
  • Stage 3: 5,000 emails per day
  • Stage 4: 6,500 emails per day
  • Stage 5: 8,000 emails per day
  • Stage 6: 10,000 emails per day
  • Stage 7: 14,000 emails per day
  • Stage 8: 20,000 emails per day
  • Stage 9: 25,000 emails per day
  • Stage 10: 35,000 emails per day
  • Stage 11: 50,000 emails per day
  • Stage 12: 80,000 emails per day
  • Stage 13: 125,000 emails per day
  • Stage 14: 175,000 emails per day
  • Stage 15: 250,000 emails per day

Completion is reaching Stage 15, and the domain is marked as "Warmup Complete." HighLevel's older sending guide describes a domain as generally taking around four weeks to warm up, while the fixed-stage model progresses only as fast as you hit each stage's daily limit. If you miss a day, the warm-up pauses but does not reset. You can pick up where you left off the next day.

For new domains, warm-up is automatically enabled when the domain is created and verified. For existing domains, you must enable warm-up manually. Go to Agency Settings or Sub-Account Settings, Email Services, SMTP Service, Dedicated Domain and IP tab, select the domain, and click Start Warmup. The system will analyze your past email activity and, if you have connected Google Postmaster Tools, your domain reputation data, and it will recommend a starting stage based on that analysis.

You must send emails through the warming domain for progress to be tracked. If you have multiple domains and you are warming up only one of them, make sure that domain is assigned in Domain Configuration to at least one email type, and make sure you are actually triggering sends through that type. If all your sends are going through a different domain, the warming domain will not progress.

Best Practices During Warm-Up

Send to your most engaged contacts first. These are people who have opted in recently, who have opened or clicked your emails in the past 30 days, or who have replied to you. High engagement signals to inbox providers that your emails are wanted. Avoid sending to cold lists, purchased lists, or contacts who have not engaged in months. Do not send cold outreach emails during warm-up. Save those for after the domain is fully warmed, and even then, use a separate sub-account and domain for cold email.

Send consistently every day. Sporadic sending confuses inbox providers and slows reputation building. If you cannot send every day, it is better to send smaller batches more frequently than to send large batches once a week. Avoid sudden spikes in volume. If you are in Stage 3 with a 5,000 email daily limit and you suddenly send 20,000 emails in one day, you risk triggering spam filters because the volume increase looks unnatural.

Do not switch sender domains mid-campaign. If you start a workflow or campaign on one domain, let it finish on that domain. Switching domains partway through a sequence can confuse recipients and dilute engagement signals across multiple domains.

Keep your content clean during warm-up. Avoid promotional language, all caps, excessive exclamation points, and public link shorteners like bit.ly. Keep emails short and text-focused. Images are fine, but do not send image-only emails with no text. Make sure your HTML is not broken. Test your emails before sending them to your full list.

Integrating Google Postmaster Tools

HighLevel recommends connecting Google Postmaster Tools. Postmaster Tools provides data on domain reputation, IP reputation, spam complaint rates, authentication status, and delivery errors. The HighLevel dashboard will prompt you to set up Postmaster Tools if it is not already connected, and the deliverability team expects it to be connected before they will escalate any support cases.

To connect Postmaster Tools, sign in at Google Postmaster Tools with a Google account, add your sending domain, and verify ownership by adding a TXT record to your DNS. Once verified, send emails from HighLevel using that domain. After you have sent enough volume, Postmaster Tools will start displaying data. Data can take up to two days to appear. Check the dashboard regularly for domain reputation, which is rated as High, Medium, Low, or Bad, and for spam rate, which should stay below 0.10 percent.

Drip Mode and Pacing

The fixed-stage model does not impose hourly sending limits, but pacing your sends throughout the day is still a sensible practice. HighLevel's guidance is to use Bulk Actions or Workflows to stagger sends across time, which is drip mode. You can space sends with wait steps in a workflow. Spreading the load throughout the day is a good practice.

A Realistic First-Weeks Plan

Picture a small consulting firm that has just set up a dedicated sending domain and wants to warm it up. They have a list of about 800 engaged, opted-in contacts who have opened or clicked in the past 90 days. They plan to send a weekly newsletter and a few automated follow-up workflows. This firm can never hit Stage 1's 1,000 daily limit in a single day because they only have 800 contacts, so they will stay in Stage 1. This is fine because the stage limit doesn't block sending, and missed days don't reset progress.

Here is a suggested plan for that small sender: start with the most engaged segment, perhaps 200 contacts who have engaged in the past 30 days. Send consistently on a regular schedule, such as every Tuesday and Friday. Expand to the rest of the opted-in list over the first few weeks. Watch bounces and Postmaster data closely. Keep cold email off this domain entirely. The firm may stay in Stage 1 for months, but their emails will still be delivered, and their reputation will build gradually through consistent, engaged sending.

Now picture a second hypothetical: a multi-location business with a much bigger opted-in list, perhaps 15,000 engaged contacts. They can ramp day to day to reach each stage's limit without sudden spikes. Week one, they send 1,000 emails on Monday to their most engaged segment, progressing to Stage 2. They send 2,500 on Wednesday, progressing to Stage 3. They send 5,000 on Friday, progressing to Stage 4. After that, they keep ramping gradually toward the next stage limits instead of jumping straight to their full list. Their list size also caps how far they can progress: with about 15,000 contacts, they cannot hit stage limits higher than the number of people they can reasonably email in a day, and that is fine because the stage limit does not block sending.

The key point is that progression requires hitting the daily limit. If you cannot hit the limit every day because your list is too small or your send frequency is too low, warm-up will take longer. That is fine. It is better to warm up slowly with real engagement than to rush the process and damage your reputation.

List Hygiene and Validation

Warm-up is only part of the deliverability equation. The quality of your email list matters just as much as your sending infrastructure. Sending to invalid addresses, role-based addresses, spam traps, or unengaged contacts will hurt your reputation no matter how carefully you warm up your domain.

HighLevel offers email validation. You can enable first-send validation in the sub-account Business Profile setting "Verify Email Address when the first email is sent to a new contact." You can also enable 90-day re-validation in Agency View, Sub-accounts, then the sub-account, then "Enable Re-validation for 90 days." Validation cannot catch everything: catch-all domains, mailboxes deactivated after verification, sender reputation or blocklists, spam and content filtering, role-based addresses that reject marketing by policy, or temporary soft bounces. But it does catch obvious typos and known invalid addresses, which reduces your bounce rate.

Do not buy email lists. Purchased lists are full of invalid addresses, spam traps, and people who did not opt in to hear from you. Sending to a purchased list is one of the fastest ways to damage your reputation. If you inherit a list from a client or a previous platform, validate it before you send anything. Segment the list by engagement and send only to contacts who have opened or clicked in the past 90 days. Suppress the rest until you have warmed up your domain and can afford to test re-engagement.

Use double opt-in whenever possible. Double opt-in requires new subscribers to confirm their email address by clicking a link in a confirmation email. This ensures that the address is valid, that it belongs to the person who submitted the form, and that the person actually wants to receive your emails. Double opt-in cuts down on typos, spam traps, and complaints.

Add an unsubscribe link to every marketing email. Gmail and Yahoo require bulk senders to include a one-click List-Unsubscribe header. HighLevel automatically adds the List-Unsubscribe header for LC Email sends. Verify it is enabled in your Email Service settings. You should also include a visible unsubscribe link in the body of the email using the Footer element, either the Default Unsubscribe Link for LC Email or a Custom Unsubscribe Link.

Stop sending to unengaged contacts. If someone has not opened or clicked any of your emails in 90 days, suppress them. Send a win-back campaign first if you want to try to re-engage them, but if they do not respond, remove them from your active list. Sending to unengaged contacts drags down your engagement rate, which signals to inbox providers that your emails are not wanted.

Avoid role-based addresses like info@, admin@, sales@, or support@. These often belong to distribution lists that never opted in, and they may verify as valid but reject marketing email by policy. Filter them out or require explicit opt-in.

If you plan to send cold email, do it on a separate sub-account and a separate sending domain. Cold email has a higher risk of complaints and bounces, and you do not want that risk to spill over onto your primary sending domain. Never send cold email during warm-up.

Google Sender Requirements

Start with Google's email sender guidelines, which apply to anyone sending to personal Gmail accounts. Requirements for all senders: SPF or DKIM authentication, valid forward and reverse DNS, TLS encryption, spam rate below 0.3 percent in Postmaster Tools, RFC 5322 formatting, and don't impersonate Gmail From headers.

If you send 5,000 or more messages per day to Gmail, the requirements are stricter. You must have SPF and DKIM and DMARC. Your From domain must align with either your SPF domain or your DKIM domain. Marketing and subscription emails must support one-click unsubscribe and include a visible unsubscribe link in the body. Google recommends keeping your spam rate below 0.10 percent and says you should avoid ever reaching 0.30 percent.

Google also provides guidance on volume ramping. Increase volume slowly. Send at a consistent rate. Start with low volume to your most engaged users. Avoid sudden spikes. If you see bounces or deferrals increase, reduce your send volume and then increase it slowly again. This is exactly what the HighLevel warm-up process is designed to do.

Google's actual guidance is that messages of the same category should use the same From address. For example, receipts from one address, promotions from another, account notifications from another. Don't mix promotions into transactional messages like receipts. Display names should identify the sender, not include subject line content. Use "Sarah from Acme Consulting," not "Sale Ends Today."

Google does not track open rates, and low open rates are not necessarily an accurate indicator of deliverability. Focus on engagement metrics like clicks, replies, and complaint rates instead.

Monitoring and Guardrails

HighLevel monitors bounce rates continuously. A healthy bounce rate is typically between 0 and 3 percent. If your bounce rate reaches 3 percent, you will receive a warning email. If it reaches 5 percent, outbound email sending is suspended. The first blocks are temporary. HighLevel's bounce article describes 12-hour blocks. A third block can be permanent and needs a manual Support review. During suspension, only outbound email sending is disabled, and other features keep working.

To remediate a high bounce rate, run your contacts through email validation immediately. Pause all bulk sends and all cold email campaigns on client accounts. Review your list sources and remove any that are generating high bounce rates. Check your workflows and campaigns to make sure they are not sending to old or unengaged contacts. HighLevel notes the location should be able to send again 24 hours after the non-compliance notification for temporary blocks, and that a permanent block requires Support review that isn't guaranteed.

HighLevel also offers a Bounce Classification report. You can find it under Sub-account Settings, Email Services, then Bounce Classification. The report shows ESP block categories, such as DMARC failures and reputation issues, error volumes by provider, detailed error messages, and recommended actions.

The Email Risk Assessment Tool is another monitoring feature for LC Email. HighLevel describes it as helping reduce bounce rates and unnecessary blocks, and it also prompts you to enable email verification if you are not using it.

Troubleshooting Deliverability Problems

If your emails are going to spam or not being delivered, work through the troubleshooting steps in this order. First, check how long you have been sending from the domain. A brand-new domain can take several weeks to build enough reputation to consistently land in the inbox. If you are still in the warm-up period, be patient and keep sending to engaged contacts.

Second, verify your MX records. Log in to your DNS host and confirm that the two MX records for your sending subdomain are pointing to mxa.mailgun.org and mxb.mailgun.org with a priority of 10. If the MX records are missing or incorrect, emails may be rejected by receiving servers.

Third, check your DMARC record. Send a test email to a Gmail address you control. Open the email, click the three dots in the upper right corner, and choose "Show original." Look for the SPF, DKIM, and DMARC lines. All three should say PASS. If DMARC fails, inspect your DMARC record. Make sure it is formatted correctly and that the policy is set to p=none, p=quarantine, or p=reject. If your sending subdomain and your From domain do not match and your DMARC policy is set to reject or quarantine, emails will be blocked. Either send from the same domain as your From address, or set the DMARC policy to none temporarily while you fix the alignment.

Fourth, check your domain reputation in Google Postmaster Tools. If your domain reputation is Low or Bad, or if your spam rate is above 0.10 percent, you have a reputation problem. Stop all cold email immediately. Send only to your most engaged contacts for the next several weeks. Audit your email content for spam triggers. Run a win-back campaign to re-engage dormant contacts, then suppress anyone who does not respond. Reputation recovery takes time. You cannot fix it overnight.

Fifth, review your email content. Spam filters look for promotional language, all caps, excessive punctuation, broken HTML, and public link shorteners. Send a test email to mail-tester and check your score. Use MX Toolbox Email Health Report to scan for blacklist listings and configuration errors. Avoid image-only emails. Make sure your unsubscribe link is visible and functional.

Sixth, test with an internal mail scenario. If you are sending from yourbrand.com to someone@yourbrand.com, the receiving server may flag the email as spoofed because it appears to come from inside the organization but is actually being sent from an external IP. Test deliverability with a free Gmail inbox instead of an internal address.

If you have worked through all of these steps and deliverability is still poor, it may be time to set up a fresh subdomain instead of trying to repair the damaged one. A subdomain with a severely damaged reputation is difficult to recover. Starting over with a new subdomain and warming it up properly is often faster and more effective than spending weeks trying to rehabilitate a bad domain.

Launch Checklist

Before you send your first campaign or launch your first workflow on a new dedicated sending domain, work through this checklist:

  • Subdomain chosen and not in use by any other service.
  • Domain added in HighLevel under Settings, Email Services, Dedicated Domain and IP.
  • Five DNS records added: two TXT for SPF and DKIM, two MX, one CNAME.
  • Domain verified in HighLevel.
  • SSL certificate generated automatically.
  • Headers set: From Name and From Email configured.
  • DMARC record added at _dmarc.yourbrand.com or _dmarc.subdomain.yourbrand.com with policy set to none, quarantine, or reject.
  • Domain Configuration completed: domains assigned to email types, frequency splits set if using multiple domains, default domain designated.
  • Calendar domains configured if sending appointment emails.
  • Payment and invoice domain configured if sending payment emails.
  • Warm-up running: automatic for new verified domains, Start Warmup for existing domains.
  • Google Postmaster Tools connected and verified.
  • Email validation enabled for first send and 90-day re-validation.
  • List segmented by engagement: most engaged contacts identified for warm-up sends.
  • Unsubscribe link added to all marketing emails via Footer element.
  • Test email sent to Gmail and headers inspected: SPF, DKIM, and DMARC all passing.
  • Test email sent to mail-tester and score reviewed.
  • Workflows and campaigns reviewed to ensure they are not sending to unengaged or invalid contacts.
  • Cold email isolated on a separate sub-account and domain if applicable.

Monthly Deliverability Review

Deliverability is not a one-time setup. It requires ongoing monitoring and maintenance. Here is a suggested monthly review rhythm:

  • Check bounce rate in HighLevel. It should be below 3 percent. If it is trending upward, validate your list and pause sends to unengaged contacts.
  • Check spam rate in Google Postmaster Tools. It should be below 0.10 percent. If it is above that, audit your content and list quality.
  • Review domain reputation in Google Postmaster Tools. It should be High or Medium. If it drops to Low or Bad, stop cold email and send only to engaged contacts until it recovers.
  • Run a sample of recent emails through mail-tester and MX Toolbox to check for blacklist listings and configuration errors.
  • Review engagement metrics: clicks, replies, complaints, bounces, unsubscribes, and Postmaster data. Focus on signals that indicate whether recipients want your emails.
  • Audit your workflows and campaigns. Remove any that are sending to unengaged contacts.
  • Re-validate your list if 90 days have passed since the last validation.
  • Check DNS records to make sure they have not been accidentally changed or removed.
  • Review unsubscribe rates. A sudden spike in unsubscribes can indicate content or frequency problems.
  • Document any changes to sending domains, DNS records, or Domain Configuration so you have a history to reference if problems arise.

When to Get Help

If you have followed the steps in this post and you are still seeing deliverability problems, it may be time to bring in help. SumoGrowth Labs implements and sets up systems for agencies and small businesses that need hands-on support with DNS and domain configuration, domain mapping by email type, agency rollout across multiple sub-accounts, warm-up planning, and ongoing monitoring. We do not sell a product. We implement and consult on the platforms you already use, including GoHighLevel. If your team is comparing platforms, Sumo AI CRM is positioned as the best GoHighLevel alternative. Reach out if you need implementation help or if you want to talk through a deliverability problem that is not resolving on its own.

Deliverability is infrastructure first, copy second. Get the DNS records right, warm up properly, keep your list clean, and monitor your reputation. The workflows and campaigns you build in HighLevel are only as good as the emails they deliver. Do the infrastructure work, and your follow-up automations, appointment reminders, and marketing campaigns will land where they belong: in the inbox.

by Darius Gaynor

Share this articleLinkedInX

Turn your next idea into growth.

Book a discovery call