How to Warm Up Google Workspace Email on a New Domain

Warm up Google Workspace email on a new domain for 3–4 weeks before full outreach, starting at 3–5 emails per user per day and rising slowly. If you skip DNS, mailbox access, or per-user limits, Gmail may treat the domain as risky before it has history. This guide gives the setup, ramp, checks, and stop signals.

Google Workspace warm-up is not only a mailbox task. You need domain authentication, correct Gmail access, safe user creation, and a sending plan that treats every user as a separate sender. For broader timing, keep this beside our email warm-up schedule and new domain warm-up plan.

How do you warm up Google Workspace email?

Google Workspace gives you reliable infrastructure, not instant sender trust. A new domain has little history. A new user also has no normal pattern of sent mail, replies, opens, or inbox placement.

Warm-up builds that pattern gradually. Your first goal is not volume. It is predictable delivery behaviour.

For a new Google Workspace domain, plan 3–4 weeks. Existing domains with clean history often need about 14 days. New domains need longer because Gmail and other providers have fewer signals.

Set up one domain, authenticate it, create users, warm each user, and only then add campaign volume. If you need more total sending, add mailboxes instead of forcing one mailbox to send too much.

Use these limits unless your own delivery data says to slow down:

Cold outreach usually fails because teams scale too early, not because they wait too long.

Use this launch checklist before the first campaign from a new Google Workspace domain:

How do you authenticate the domain?

Do not warm up a Google Workspace mailbox before DNS is correct. Authentication is the base layer for every mailbox on the domain.

You need three records: SPF, DKIM, and DMARC. SPF says Google is allowed to send for your domain. DKIM signs mail with a domain key. DMARC tells receivers how to treat mail that fails authentication and gives you a path to stricter policy later.

For Google Workspace, your SPF TXT record is usually:

v=spf1 include:_spf.google.com ~all

Publish only one SPF record at the root domain. If you already use another sender, merge it into the same SPF record. Multiple SPF TXT records can cause SPF failure.

Set DKIM inside Google Admin console:

1. Go to admin.google.com.
2. Open Apps.
3. Choose Google Workspace.
4. Open Gmail.
5. Go to Authenticate email.
6. Select the domain.
7. Generate a new record.
8. Add the TXT record at your DNS host.
9. Return to Admin console and start authentication.

Google’s DKIM setup documentation is the primary reference if the menu changes: set up DKIM for Google Workspace.

For DMARC, start with monitoring, not rejection:

v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

The reporting address is optional, but useful. Use an address or service that can handle reports. Move toward quarantine or reject later, after you know legitimate mail passes SPF or DKIM alignment.

You can also check records with our free SPF checker, DKIM checker, and DMARC checker. These do not replace Google Admin console, but they catch common DNS mistakes quickly.

How should mailbox access work?

Many Google Workspace warm-up problems are not caused by spam filtering. They are caused by admin settings that block the tool from connecting.

First decide how the warm-up tool will connect.

OAuth is usually cleaner for Google Workspace because the user signs in with Google and grants a specific scope. BobWork Email Warm-up supports Google sign-in with the gmail.modify scope. Google shows an unverified-app notice because BobWork has not completed the CASA audit.

IMAP is the other route. It can work, but admins often block it.

Check the organisation setting first:

1. Go to admin.google.com.
2. Open Apps.
3. Choose Google Workspace.
4. Open Gmail.
5. Go to End User Access.
6. Review POP and IMAP access.
7. Apply the setting to the correct organisational unit.

Then check the user mailbox:

1. Open Gmail as the user.
2. Click the gear icon.
3. Choose See all settings.
4. Open Forwarding and POP/IMAP.
5. Confirm IMAP is enabled if your tool needs it.

If you use IMAP with an app password, the account normally needs 2-Step Verification. App passwords may be unavailable for some security configurations. Check Google’s current help page before assuming every account can use one.

If OAuth or IMAP fails, do not keep retrying. Failed authentication can look like account trouble. Fix the Admin console setting, confirm the user can open Gmail, then reconnect once.

BobWork also supports Google Workspace through IMAP with an app password. It does not support Outlook or Microsoft 365 yet, because Microsoft requires OAuth for that path.

What ramp should new domains use?

A new domain needs a slower plan than an existing Google Workspace domain. The first month should build reputation, not maximise meetings booked.

Use this timeline when the domain is new, DNS is fresh, and users have little or no sending history.

This is not a promise that every domain is ready on day 28. It is a safe operating plan. If spam placement rises, pause increases for a few days.

BobWork’s engine starts at 3 emails per day, adds 2 per day, and caps at 30 per day by default. Sends are spread from 09:00 to 18:00 in the mailbox’s own time zone, with weekends at 30%. That matches the shape you want for a new domain.

About 40% of warm-up mail receives a reply, and threads end after three messages. The content is plain text, has no links or images, and uses short office-style messages. Warm-up should not look like a campaign.

If you use BobWork, the free shared warm-up network handles sending, replies, and spam rescue automatically. You can also switch to a private pool per account in Mailbox pool → Pool mode if you prefer only your own mailboxes to warm each other. Private pools need at least two mailboxes.

For a first-use walkthrough, read what to expect when warming up.

How should each user ramp?

Do not think of Google Workspace volume only at the domain level. Gmail also sees individual user behaviour.

If you create five users on Monday, each user still needs a ramp. Do not send 250 cold emails from one mailbox because the domain has five mailboxes. That makes one sender look abnormal.

Use this operating pattern:

• one real person or role per mailbox;
• one mailbox per sending identity;
• slow increases per user;
• similar daily patterns, not identical schedules;
• no sudden jump after a quiet weekend;
• no campaign blast from a mailbox warmed for only a few days.

During warm-up, keep real outreach simple. Use plain text. Avoid heavy links, large images, URL shorteners, attachments, and aggressive sales formatting. Personalise enough that recipients have a reason not to mark spam.

If you use tracking links, understand the trade-off. Open and click tracking can add redirected links and tracking domains. On a fragile new domain, fewer moving parts are safer.

Your per-user target after warm-up is usually no more than 30–50 real outreach emails per day. Some domains can do more later. Many should not. If you need 300 daily sends, use more mailboxes and domains rather than one overloaded user.

Keep warm-up running at 10–15 messages per day during campaigns. Do not stop it the day real outreach starts. Warm-up is background activity that keeps signals visible.

For mailbox-level detail, use our Gmail warm-up guide. Google Workspace uses the same mailbox behaviour, with more admin controls around access and authentication.

What should you monitor?

You need two kinds of monitoring: provider-level dashboards and mailbox-level evidence.

Google Postmaster Tools helps you read domain-level signals for mail sent to Gmail users. Add and verify your domain, then watch authentication, spam rate, domain reputation, IP reputation if available, and delivery errors. Google explains the dashboards in its Postmaster Tools documentation.

For sender requirements, Google’s primary reference is its email sender guidelines. The key number is complaint rate. Keep spam complaints below 0.1%, and avoid 0.3% or higher.

Postmaster Tools may not show useful data at very low volume. That is normal. Early in warm-up, mailbox-level placement can be more actionable.

BobWork measures spam landings directly in the receiving mailbox. Its spam rate is the share of a sender’s warm-up mail that receiving mailboxes found in Spam over seven days. It does not use third-party seed lists.

In BobWork, a mailbox is ready for outbound when it has warmed for at least 7 days, has a 7-day spam rate of 10% or less, and has received at least 30 warm-up emails. Health is shown as Healthy, Watch, At risk, or Blocked.

Blocked means login or permission failed. Do not treat that as a deliverability issue. Fix OAuth, IMAP, app password, or mailbox access first.

You should also watch normal campaign metrics. Bounces, low replies, sudden unsubscribes, and direct complaints all matter. Warm-up cannot compensate for poor lists or irrelevant messages.

If Gmail delivery is already failing, use our Google Workspace spam fix guide before increasing volume.

What should you fix before scaling?

When warm-up mail lands in spam, slow down. Do not add more users to hide the problem.

Start with authentication. Check that SPF passes. Confirm DKIM is signing with your domain. Confirm DMARC exists and aligns with either SPF or DKIM. A domain can have records published and still fail alignment.

Next, check access and sending behaviour. New users should not all send the same message at the same minute. Avoid copied campaign templates across many users. Use natural spacing and keep each mailbox within its own ramp.

Then inspect the content. Remove unnecessary links. Avoid spam-like claims, pressure language, and misleading subject lines. For cold outreach, a short message with one clear reason is safer than a designed newsletter.

Check the recipient list too. Old scraped lists cause bounces and complaints. Gmail complaint rates matter more than your internal send target. If recipients mark you as spam, no warm-up schedule will save the campaign.

BobWork’s rescue behaviour only touches warm-up mail carrying its own hidden header, or a known subject for Zoho API senders. Warm-up mail found in Spam is moved to Inbox, marked read, labelled Warm-up, and archived after 24 hours. Real mail is never read, moved, or answered.

If a BobWork mailbox rises above a 5% spam rate, pause it for a few days. Fix DNS, volume, content, and list quality before restarting. For a deeper explanation of causes, read why emails go to spam.

The safest workflow is simple. Authenticate first. Connect mailboxes correctly. Warm each user. Start outreach slowly. Increase only when the evidence says the mailbox is healthy.

If you want the daily warm-up pattern handled for you, BobWork Email Warm-up is free with no credit card and no time limit for up to 10 mailboxes per account. It supports Google Workspace, uses a shared warm-up network by default, and lets you switch to a private pool per account if you prefer.

Frequently asked questions