Skip to content
Save 20% on every snapshot, funnel and workflowBrowse the catalogue
Email Marketing

GoHighLevel Email Setup in 2026: Domain, DNS and Warming Done Properly

Set up a dedicated sending domain in GoHighLevel: SPF, DKIM, DMARC, a warming schedule that works, and the mistakes that put your first campaign in spam.

Imogen HartleyUpdated6 min read
GoHighLevel email setup and DNS

Key takeaways

  • Use a dedicated subdomain, never the shared default and never your root domain.
  • SPF, DKIM and DMARC are all required, not optional, for bulk sending in 2026.
  • Warming takes three to four weeks. There is no shortcut that works.
  • Send to your most engaged contacts first so early signals are positive.
  • Bounce rate above a few percent will damage the domain quickly.
Contents
  1. Why a dedicated domain
  2. The DNS records you need
  3. Setting it up
  4. Warming the domain
  5. What puts you in spam
  6. Checking it actually works

Email deliverability in GoHighLevel is decided almost entirely before you send anything. Domain choice, DNS authentication and warming determine whether your campaigns reach an inbox. Subject lines and copy matter far less than any of these.

The good news is that it is a finite setup task. Do it once, properly, and it keeps working.

Why a dedicated domain

Out of the box, a sub-account can send from a shared domain. That means your reputation is pooled with every other account using the same one. Someone else's bad list becomes your spam placement, and you have no control and no visibility.

A dedicated sending domain isolates you. Your reputation is yours, good or bad, and you can actually influence it.

Use a subdomain, not your root domain. Something like mail.yourdomain.com. It inherits some trust from the root domain while keeping marketing sending separate from your normal business email. If a campaign goes badly, your day-to-day mail is not caught in the fallout.

The DNS records you need

RecordWhat it doesRequired
SPFLists which servers may send for your domainYes
DKIMCryptographically signs messages so they cannot be alteredYes
DMARCTells receivers what to do when SPF or DKIM failsYes, for bulk sending
Return-path or CNAMEAligns bounce handling with your domainYes, as specified by HighLevel
BIMIDisplays your logo in supporting inboxesOptional

All three of SPF, DKIM and DMARC are now effectively mandatory. Google and Yahoo tightened their requirements for bulk senders, and mail that fails authentication is increasingly rejected rather than filtered to spam.

A note on SPF: you get one SPF record per domain. If one already exists because you use Google Workspace or Microsoft 365, you merge the new include into it rather than adding a second record. Two SPF records is a configuration error that fails validation entirely, and it is a very common mistake.

Setting it up

  1. Choose the subdomain. mail. or send. or go. Keep it short and obviously yours.
  2. Add it in the sub-account. Settings, then Email Services, then add a dedicated domain. HighLevel generates the records you need.
  3. Add the records at your DNS provider. Copy them exactly. A trailing dot or a missing character invalidates the whole record.
  4. Add DMARC. Start with a monitoring policy: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com. This reports without rejecting anything, which is what you want at the start.
  5. Verify in HighLevel. Propagation is usually minutes and occasionally up to 48 hours. Do not re-enter the records repeatedly while waiting.
  6. Set the from address and reply-to. Use a real, monitored mailbox. noreply@ hurts engagement and irritates people who reply anyway.
  7. Tighten DMARC later. After a few weeks of clean reports, move to p=quarantine. Do not start there, or you will silently quarantine legitimate mail you had forgotten about.

Warming the domain

A brand new domain has no reputation. Sending ten thousand emails on day one from an unknown domain is the clearest possible spam signal, and recovering from it is far harder than warming properly in the first place.

PeriodDaily volumeSend to
Days 1 to 320 to 50Your most engaged contacts only
Days 4 to 7100 to 200Recently active contacts
Week 2500 to 1,000Active within 90 days
Week 32,000 to 5,000Broader active segment
Week 4Full volumeYour normal list

Two rules while warming. Send to your most engaged contacts first, because early opens and replies are the positive signals that build reputation. And watch the numbers rather than the calendar: if bounce rate climbs above a couple of percent or opens fall off a cliff, hold volume steady rather than continuing to double.

What puts you in spam

  • Unauthenticated domain. Missing or broken SPF, DKIM or DMARC. This is the first thing to check and the most common single cause.
  • Sending to an old list. A list nobody has emailed in two years is full of dead addresses. High bounce rates damage a domain quickly.
  • Purchased lists. Never. Spam traps sit in these deliberately, and hitting one blacklists the domain.
  • Poor engagement. Providers watch whether people open, reply and move messages out of spam. Consistently low engagement teaches them nobody wants your mail.
  • Image-heavy, text-light emails. A single large image with no meaningful text is a classic spam pattern.
  • No unsubscribe link. Legally required in most jurisdictions and expected by every filter.
  • Link shorteners. Same problem as in SMS. Use full URLs on your own domain.
  • Sudden volume spikes. Going from 500 a day to 50,000 looks exactly like a compromised account.

Checking it actually works

Before running a real campaign, verify rather than assume.

  1. Send to yourself at several providers. Gmail, Outlook and Yahoo behave differently. Check where each one lands.
  2. View the message headers. Look for SPF, DKIM and DMARC all passing. In Gmail this is under "Show original".
  3. Run a deliverability test tool to check for blacklist listings and configuration mistakes before volume sending.
  4. Read the DMARC reports. They arrive at the address in your DMARC record and show what is failing authentication, including sending sources you may have forgotten about.
  5. Watch the first real campaign closely. Open rate below your normal range usually means placement, not copy.

Do this before the client's first campaign, not after. A domain that lands in spam on its first send carries that reputation for weeks, and no amount of subject line testing fixes an authentication problem.

Email sequences already written

Every snapshot ships with its nurture, reminder and reactivation sequences written for the industry, so once your domain is warm there is something worth sending.

Browse snapshots

Frequently asked questions

Do I need a dedicated sending domain in GoHighLevel?

Yes, if you care about deliverability. Sending from the shared default domain means your reputation is pooled with every other account using it. A dedicated, authenticated domain is the single highest-impact deliverability decision you will make.

Should I send from my main domain or a subdomain?

A subdomain such as mail.yourdomain.com or send.yourdomain.com. It inherits some reputation from the root domain while isolating marketing sending, so a problem with a campaign does not damage your normal business email.

What is DMARC and do I need it?

DMARC tells receiving servers what to do with mail that fails SPF and DKIM checks. Major providers including Google and Yahoo now require it for bulk senders, so yes. Start with a monitoring policy of p=none, review the reports, then tighten to quarantine once you are confident nothing legitimate is failing.

How long does email warming take?

Three to four weeks to reach meaningful volume from a brand new domain. Start at a few dozen sends a day to your most engaged contacts and roughly double every few days while watching open and bounce rates. Rushing this is the most common cause of a domain that never recovers.

Why are my GoHighLevel emails going to spam?

In order of likelihood: the domain is not authenticated, the domain is new and unwarmed, you are sending to an old or purchased list with high bounces, the content is heavy on links and images relative to text, or engagement is poor so providers have learned nobody wants the mail.

Sources

  1. HighLevel help centre: dedicated sending domain
  2. Google: email sender guidelines

Skip the build. Import a working GoHighLevel account instead.

Industry-ready snapshots with funnels, pipelines, calendars and automations already wired. Delivered within 24 hours, installable on every sub-account you manage.

Browse snapshotsSchedule a call

Mentioned in this article

Keep reading

All articles