Google Workspace Cold Email Setup Mistakes That Kill Inbox Placement
Most cold email setup guides give you the minimum steps but leave out the details that actually matter. Here's what they miss.
You set up Google Workspace for cold email. You followed a guide, configured DNS, maybe did some warmup. But inbox placement is poor from the start. The setup itself is the problem — but it's not obvious where.
Why This Happens
Most cold email setup guides give you the minimum steps but leave out the details that actually matter for deliverability. Small mistakes in configuration compound. A slightly wrong SPF record plus a weak DKIM key plus no warmup plus shared tracking domains plus HTML templates equals spam placement — even though each individual shortcut seemed minor.
Here are the most common setup mistakes:
Not setting up DMARC at all. All senders need SPF or DKIM. But even below the 5,000-per-day bulk sender threshold, Google recommends always setting up all three. Not having DMARC removes a layer of trust signaling. Check with the DMARC lookup.
Skipping custom tracking domain setup. When your outreach tool tracks opens and clicks through a shared domain, your reputation is tied to every other user on that domain. If anyone on that shared domain is sending spam, it affects your deliverability. Check with the tracking domain checker.
Sending cold email from your primary business domain. If your cold outreach triggers spam complaints, those complaints damage the reputation of the domain you use for all other business email. Use a separate domain for cold outreach, isolated from your main domain.
Starting outreach before warmup is complete. A 3-day warmup is not warmup. New inboxes need 2–4 weeks of gradual volume increase with positive engagement signals before they are ready for cold campaigns. Verify readiness with the warmup readiness checker.
Not verifying PTR records. Google requires valid forward and reverse DNS records for sending IPs. Check with the rDNS checker.
Step-by-Step Diagnosis
Audit your DNS records using the DNS checker. Check SPF, DKIM, and DMARC. Verify that SPF has 10 or fewer lookups, DKIM key is at least 1024 bits (preferably 2048), and DMARC record exists with at least p=none.
Check your tracking domain. If it's a shared domain, set up a custom tracking CNAME. Verify it's not proxied through Cloudflare (should be grey cloud, not orange) using the tracking domain checker.
Verify you're sending from a dedicated cold outreach domain, not your primary business domain.
Review your warmup timeline. Did you go from zero to full production in less than two weeks? That's likely a factor. Use the sending limit planner to set up the correct ramp.
Send a plain text test email to a personal Gmail account. Check headers for SPF, DKIM, and DMARC pass status. Check which tab it lands in. Run a full inbox placement test.
The Fix Path
Fix any DNS issues first. Get all three authentication methods passing with the correct configuration.
Set up a custom tracking domain with a CNAME record pointing to your outreach tool's tracking infrastructure.
If you're sending from your primary domain, stop. Set up a secondary domain, configure DNS, and warm it for 2–4 weeks before sending cold outreach.
Use the launch checklist to verify everything before your first send — it covers all setup elements in one place.
When to Replace Instead of Repair
If you caught these issues early and haven't sent many cold emails yet, repairing the setup is straightforward. Fix the configuration, warm up properly, and you should be fine.
If you've been sending cold email from a poorly configured setup for weeks and your domain reputation is now damaged, you may need to start fresh on a new domain. For agencies needing to maintain client campaign timelines, WarmInboxes provides prewarmed Google Workspace inboxes on properly configured domains so you don't have to wait another month to start over.
Mistakes That Make This Worse
- Using the same domain for cold email and client-facing business email
- Skipping DMARC because you're "below 5,000 sends"
- Using a shared tracking domain and never checking it
- Assuming that because DNS "looks right" it is right — without checking message headers for actual pass/fail status
Run the checks first
Before replacing anything, run a free inbox placement test. You might find the issue is DNS, not the domain — and save yourself a week of unnecessary work.