Google Workspace Cold Email Setup Mistakes That Kill Inbox Placement

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. Emails hit spam, open rates are low, and nothing seems to work the way the guide promised. The setup itself is the problem — but it's not obvious where.

The most common setup mistakes

1. Not setting up DMARC at all

All senders need SPF or DKIM. But even below the bulk sender threshold, Google recommends always setting up all three authentication records. Not having DMARC removes a layer of trust signaling and means you're flying blind on authentication failures. Add at minimum: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com. Verify with the DMARC lookup.

2. Skipping custom tracking domain setup

When your outreach tool tracks opens and clicks through a shared domain like track.outreachtool.com, your reputation is tied to every other user on that domain. If anyone on that shared domain is sending spam, it affects your deliverability. Set up a custom CNAME and verify it's not proxied through Cloudflare using the tracking domain checker.

3. 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. Best practice is to use a separate domain for cold outreach — one clearly related to your brand but isolated from your main domain. Check your main domain's health with the burn score calculator.

4. 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. Use the warmup readiness checker before activating any inbox for campaigns.

5. No PTR record verification for custom SMTP

Google requires that the sending IP has a valid reverse DNS record that resolves to a hostname, and that hostname must resolve back to the same IP. This is handled automatically by Google Workspace, but if you are using any third-party sending infrastructure, verify with the rDNS checker.

6. Redirect not configured on sending domain

Sending domains should redirect to a real website. A domain that doesn't respond to HTTP requests looks like spam infrastructure. Check both root and www redirects with the redirect checker.

Step-by-step audit

Run through the full launch checklist before sending from any domain. It covers auth, tracking, redirect, warmup status, and placement testing in one pass.

Additionally: send a plain text test email to a personal Gmail account, open the original message, and verify you see spf=pass, dkim=pass, and dmarc=pass. This is the single fastest way to confirm everything is working end-to-end.

Repair or replace?

If you caught these issues early and have not sent many cold emails yet, repairing the setup is straightforward. Fix the configuration, warm up properly, and you should be fine.

If you have 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 that need to maintain client campaign timelines, WarmInboxes provides prewarmed Google Workspace inboxes on properly configured domains so you do not have to wait another 4–6 weeks to start over.