Google Workspace Deliverability Problems: Causes, Fixes, and Recovery

Google Workspace is the dominant platform for cold email infrastructure — which means Google's spam filters are specifically tuned to recognize cold email patterns from GWS accounts. This guide covers every common GWS deliverability problem, what causes each one, and how to fix it.

Category 1: Initial setup problems

DKIM not enabled

The most common GWS setup error. DKIM doesn't activate automatically when you set up GWS — you must enable it in the Admin Console and publish the DNS record. Without DKIM, every email from the domain fails signature verification.

Fix: Google Admin Console → Apps → Google Workspace → Gmail → Authenticate email. Enable DKIM, then publish the provided TXT record to your DNS. The selector is google. Verify with the DKIM checker.

Wrong SPF record

GWS requires: v=spf1 include:_spf.google.com ~all. Operators sometimes use an outdated or incorrect include, or accidentally include both GWS and another provider without merging the records.

Fix: Use the SPF checker to verify. If the include is wrong, update the record. If there are multiple SPF records, merge them.

Domain too new

Google applies extra scrutiny to domains that start sending immediately after creation. The recommended minimum age before cold email is 30 days; 60 days is more conservative and safer.

Fix: Wait. There's no shortcut for domain age. Use the time to complete the rest of setup and warmup correctly.

Category 2: Warmup and sending problems

Sending too fast in early weeks

New GWS inboxes that hit their maximum limit (15/day) on week 1 trigger Gmail's anomaly detection. The safe ramp is 3 → 7 → 12 → 15 per day over 4 weeks.

Fix: Use the sending limit planner to configure the correct per-week limits. If you're already over-sending, pause for 3–5 days and resume at the correct volume.

Too many inboxes per domain

Running 5–10 inboxes on a single GWS domain concentrates spam signals at the domain level. Gmail sees the domain sending much higher volumes than any individual inbox account suggests.

Fix: Maximum 3 inboxes per domain. For higher volume needs, add more domains rather than more inboxes per domain.

Warmup tool interactions only

Warmup tools that exchange emails only between warmup tool accounts build thin reputation signals. Gmail's filters are sophisticated enough to recognize mechanical warmup patterns.

Fix: Supplement tool-based warmup with real email interactions — even just a few real exchanges with actual contacts during the warmup period significantly improves reputation quality.

Category 3: Campaign-triggered problems

High bounce rates

Sending to unverified or stale lists from a GWS inbox damages the sending address reputation quickly. Google tracks bounce rates at the sender level.

Fix: Verify email lists before every campaign. Remove bounced addresses immediately. Keep hard bounce rate below 2%.

Spam complaints

When recipients mark your email as spam in Gmail, it directly signals to Google that your domain's email is unwanted. Google aggregates this data at the domain level.

Fix: Improve list quality and targeting. Ensure unsubscribe works. Consider checking Google Postmaster Tools if you have enough volume — it shows complaint rates.

Low engagement

Gmail tracks what happens to emails from your domain. If nobody opens, nobody replies, and nobody marks as not-spam — Gmail learns your email isn't wanted.

Fix: Better targeting reduces this over time. Short-term, there's no quick fix for engagement history.

Category 4: Recovery

Recovery for auth-only issues

If the spam placement was caused by broken DKIM or SPF — fix the record, wait 24–48 hours for propagation, then retest. Recovery is fast (days, not weeks).

Recovery for reputation damage

If auth is fine but placement is spam, it's reputation damage. The recovery process:

1. Pause sending on the affected domain for 2 weeks
2. Fix any auth issues identified in the diagnosis
3. Submit blacklist delisting requests if listed
4. Resume at 20–30% of normal volume
5. Ramp slowly over 6–8 weeks
6. Retest with a placement test every 2 weeks

When to replace GWS inboxes

Replace when: the domain is blacklisted on Spamhaus, has a 6+ month history of aggressive sending, has documented spam complaints, and campaigns need to continue. Use the repair-or-replace calculator to make the call.