Why Are My Emails Going to Spam (Gmail Edition)

"Why are my emails going to spam in Gmail?" is one of the most common deliverability questions I get. The honest answer is that it's almost always one of five things, and you can diagnose which one in about 30 minutes if you know where to look. This guide walks through the diagnosis in order — authentication first, then reputation, then list quality, then content.

If you're using Google Workspace specifically, the same diagnostic order applies, with a few Workspace-specific gotchas covered below.

Start Here: Open Postmaster Tools

Google Postmaster Tools is the single most useful diagnostic for "why is Gmail spamming my mail." It shows:

• Domain reputation (Bad / Low / Medium / High)
• IP reputation (Bad / Low / Medium / High)
• Spam rate as judged by Gmail
• Authentication pass rates (SPF, DKIM, DMARC)
• Delivery errors by category

If you don't have Postmaster Tools set up for your sending domain, do that first. It takes 10 minutes and gives you actual Gmail data instead of guesses.

What the reputation tells you:

Reputation	What It Means	What To Do
High	You're in the inbox	Maintain current practice
Medium	Mixed placement	Tighten list hygiene, watch complaints
Low	Most mail going to spam	Authenticate, reduce complaints, sunset inactive
Bad	Almost all mail going to spam	Pause, diagnose root cause, recover

Cause 1: Authentication Failing

Gmail's first filter is authentication. Mail that fails SPF, DKIM, or DMARC alignment goes to spam much more aggressively than authenticated mail. Common authentication issues:

SPF Record Missing or Broken

Check your domain's SPF record:

dig TXT yourdomain.com | grep spf

For Google Workspace, the include directive must be present:

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

If you also send from other services, all of them must be in SPF (and the 10-DNS-lookup limit must hold — see SPF flattening).

DKIM Not Configured or Misaligned

Check that DKIM records exist:

dig TXT google._domainkey.yourdomain.com

If you're sending through Workspace, the selector is typically google._domainkey. For ESPs, selectors vary — check your ESP's documentation.

DKIM alignment means the d= in the DKIM signature matches the From domain. If you send from: [email protected] but the DKIM signs as d=mailgun.org, alignment fails — and DMARC with it.

DMARC Policy Wrong or Missing

Check your DMARC record:

dig TXT _dmarc.yourdomain.com

A defensible DMARC record:

v=DMARC1; p=quarantine; rua=mailto:[email protected]; aspf=r; adkim=r

If you have p=reject and either SPF or DKIM is failing alignment, your legitimate mail gets rejected and bounces. See our DMARC setup guide for the correct configuration.

Practitioner note: The single most common cause of "Workspace emails going to spam" I see is SPF missing the Workspace include after switching DNS providers. Someone migrated DNS, the SPF record didn't carry over correctly, and suddenly every Workspace email fails SPF. Check it monthly if you have any DNS changes. Mail-Tester catches this in 30 seconds.

Cause 2: Sender Reputation Damaged

If authentication passes but mail still goes to spam, reputation is the next suspect. Postmaster Tools shows you directly. Causes of damaged reputation:

• Sudden volume increase (you sent 50K when you usually send 5K)
• Sending to old/stale list (re-engagement to dormant subscribers spikes complaints)
• Complaint rate above 0.1% (Gmail's threshold)
• Sending from new domain without warmup (no reputation yet)
• Recent placement decline that became self-reinforcing

Recovery from damaged reputation takes weeks, not days. The fix:

1. Pause bulk sending temporarily
2. Send only to highly engaged subscribers (clicked in 7 days)
3. Maintain perfect compliance — one-click unsubscribe, proper footer
4. Monitor Postmaster Tools daily
5. Gradually expand recipient pool as reputation recovers

For a new domain without warmup, see the domain warmup guide — there's no shortcut, but the schedule works.

Cause 3: List Quality Problems

A list full of old, unengaged, or unverified addresses produces the engagement patterns that hurt deliverability:

• Low open rates
• Few clicks
• More complaints relative to opens
• Hard bounces on stale addresses
• Hits on spam traps

The fix is list hygiene:

• Sunset subscribers who haven't opened in 90-180 days
• Verify the list with an email validation service
• Remove role addresses (info@, admin@) for B2C marketing
• Confirm consent for the entire list (any non-opted-in addresses are liability)

A smaller, more engaged list will outperform a larger stale list every time. The math: 30K active subscribers at 25% open beats 100K stale subscribers at 8% open in revenue, deliverability, and ISP signaling.

Cause 4: Content Patterns

Gmail's filter looks at content too, though less aggressively than older spam filters. Common content triggers:

• All-caps or excessive punctuation in subject lines
• Image-only emails with no text content (see image-to-text ratio)
• Spam trigger phrases
• Excessive tracking links
• Broken or suspicious links
• Mismatched friendly-from and actual sender

For content-driven spam placement, the diagnostic is "does similar content from other senders also get filtered?" If yes, change the content. If no, the issue is reputation or authentication masquerading as content.

Practitioner note: When clients change their email content and inbox placement improves, the actual improvement is usually engagement (recipients engage with the new content), not the content directly. Gmail rewards engagement. A more engaging email lifts placement even with otherwise-identical headers. This is why "rewrite to be less spammy" often works — the better-written version gets opened and clicked, which signals Gmail to elevate placement.

Cause 5: Google Workspace Specifics

If you're sending from Google Workspace specifically, additional issues to check:

Per-User Sending Limits

Workspace users have a 2,000-recipient daily limit. Marketing volumes pushed through a single user account get throttled and flagged.

Fix: don't send marketing volume from individual Workspace mailboxes. Use an ESP. See bulk email guide.

Aliases and From Addresses

If you send from [email protected] as a Workspace alias, but DMARC alignment is configured for the primary user account, mail can fail DMARC.

Fix: use full Workspace user accounts for distinct sending personas, not aliases.

Forwarding Loops

If your domain has email forwarding configured (catch-all or specific addresses), forwarded mail can hit spam at the destination.

Fix: avoid catch-all forwarding for marketing or important transactional mail.

A Quick Diagnostic Sequence

When mail is going to Gmail spam, run through this in order:

1. Mail-Tester — score 9+/10? If no, fix the issues it identifies
2. Postmaster Tools — Medium+ reputation? If no, work on reputation recovery
3. Authentication check — SPF, DKIM, DMARC all passing? If no, fix DNS
4. List engagement audit — what % of list opened in 90 days? If under 20%, clean
5. Recent send history — did anything change recently? Volume, content, list source
6. Content review — anything obviously triggering filters? Spam phrases, broken links

Most "going to spam" problems resolve at step 1-3. Steps 4-6 catch the remainder.

If you've worked through this list and Gmail placement is still bad, you likely need help from someone who can pull DMARC aggregate reports and analyze sending logs in detail. Book a deliverability audit and I'll work through the full diagnostic with your real data.

Sources

• Google: Email Sender Guidelines
• Google: Postmaster Tools Help
• Google: Workspace SPF Configuration
• RFC 7489: DMARC Specification
• M3AAWG: Sender Best Common Practices

---

v1.0 · May 2026