Why Are My Emails Going to Gmail Spam? (2026 Checklist)

I learned this the hard way. After a weeks-long pause, I sent to my list — nothing fancy, a normal send — and Gmail ate it. Not bounced: delivered straight into the spam folder, thousands of copies, silently. The subscribers never saw it, I never got a signal, and my open rates cratered for months. The list looked alive on paper. The messages were going somewhere they couldn't be opened. That's the trap this checklist exists to prevent: spam folder placement is a silent list-death, and by the time you notice, the damage is weeks old.

Diagnose in this order. It matters — the most common cause is also the cheapest to check, and people waste weeks on content tweaks when the problem is a broken record.

1. Authentication first (takes 10 minutes)

Gmail's documented hierarchy is the same in every 2026 deliverability roundup I checked (vendor checklists from kickbox.com ~5 days ago and sender.net ~1 day ago, both crawled October 9, 2026): authentication, then reputation, then list quality, then content. Check it in that order.

SPF, DKIM, DMARC — all three, passing. A quick summary of what each does: SPF says which servers may send for your domain, DKIM signs each message so it can't be altered in transit, DMARC ties the two together with an alignment requirement to your From: domain (per sender.net's diagnostic playbook, crawled yesterday). The specific failure mode I see most: DKIM passes but DMARC alignment fails, because the signature domain doesn't match the From: domain. A green "SPF pass" line in a header report is not the same as a passing setup — alignment is the part that actually counts.

Check, don't assume. Run your domain against public DNS records — SPF record present with every sending service included, DKIM key live, DMARC record present at p=none or stricter. I describe this as "checked against public DNS records" deliberately: a DNS lookup shows you what the world sees, which is what Gmail sees.

The "suddenly" trigger. If mail started landing in spam overnight, one common cause is Gmail's tightening enforcement. Multiple third-party roundups report that Gmail moved from merely filtering non-compliant mail to rejecting it starting November 2025 (saleshandy.com FAQ, crawled 20 hours ago — treat the date as third-party-reported, not Google's official language). If nothing else changed on your end, a broken or missing SPF/DKIM/DMARC setup combined with that enforcement wave is the first thing to verify.

2. Reputation second (Google Postmaster Tools)

Once authentication passes, check your standing. Google Postmaster Tools shows domain reputation and spam-complaint rates. Here is Google's actual published guidance (Email sender guidelines, which apply to bulk senders of 5,000+ messages/day to Gmail): aim to keep spam rates reported in Postmaster Tools below 0.10%, and avoid ever reaching 0.30% or higher. Note what this means and doesn't: 0.10% is Google's recommended target, 0.30% is the ceiling at which Gmail starts classifying more of your mail as spam — not a target, not a safe band, and certainly not a guarantee of inbox placement at any rate. The widely quoted "keep it under 0.3%" checklist line is the ceiling restated as advice; the real ask is ten times stricter.

A reputation problem has one fix: send less, to engaged people, until the numbers recover — there is no shortcut.

3. List quality third (the pre-send screen)

A reputation problem is usually a list problem wearing a costume. Before any campaign, screen the list the same way a pre-send screen would:

• deliverable / risky / catch-all / disposable / invalid — the five screening categories, one flag per address with a reason.
• Suppress what you can't send to cleanly: bounces pile up on resumed lists, and Gmail's own complaint rate is computed on recipients who still exist.

One honest boundary: mailbox-level SMTP probing is not part of a standard pre-send screen — we don't sell stages we haven't built. The offline screen (syntax, disposable, role, duplicate, suppression) catches the rot you can catch without sending anything.

4. Content last

Content is the least common real cause and the most common thing people "fix" first. If authentication passes, reputation is clean, and the list is screened, then look at links, images, and spam-like patterns. Not before.

One concrete content check: run your subject line and body through the free spam trigger word checker to catch wording spam filters have historically flagged. It scans copy only — it does not replace the checks above.

The 30-second version

Authentication (SPF/DKIM/DMARC aligned, checked against public DNS) → reputation (Postmaster Tools, spam rate under Google's 0.10% target — 0.30% is the ceiling, not the goal) → list quality (screen into deliverable / risky / catch-all / disposable / invalid) → content. In that order.

Want the screen run for you?

A ListProof pre-send audit is the 7-day done-for-you version of this checklist: a pre-send screen of your list with every flagged address reported with its reason, your sender setup (SPF/DKIM/DMARC) checked against public DNS records, and a stated prediction figure before you send. If the prediction is wrong, we re-run the analysis free — within 30 days of receiving the findings. Manual invoice; current pricing on request.