How do you fix “emails going to spam after Google update”?
Updated July 3, 2026
If your mail started landing in Gmail spam folders, you're almost certainly missing one of Google's sender requirements (enforced since February 2024), which demand authenticated mail from everyone and SPF, DKIM, DMARC, one-click unsubscribe, and a low spam rate from bulk senders.
Why this happens
In February 2024, Google and Yahoo switched email authentication from best practice to entry requirement. Every sender must now pass SPF or DKIM, have valid forward and reverse DNS, and keep spam complaint rates low. Senders of roughly 5,000+ messages a day to Gmail face the full list: both SPF and DKIM, a DMARC record (p=none is enough to start), alignment between the From domain and the authenticated domain, one-click unsubscribe headers on marketing mail, and a spam rate under 0.3% in Postmaster Tools.
Enforcement rolled out gradually (temporary errors first, then increasing rejection and spam-foldering), which is why many senders saw deliverability degrade months after the announcement rather than overnight. Mail that had coasted for years on decent content and no authentication suddenly started failing the new floor checks.
The pattern we see most: a domain sends through several services, one or two of them were never authenticated, and DMARC either doesn't exist or exists with misalignment nobody noticed. Gmail doesn't tell senders which requirement they're failing (the mail just quietly lands in spam), so the fix is working through the checklist rather than guessing.
How to fix it
- 1
Audit every service sending as your domain
List them all: mail platform, marketing tool, CRM, helpdesk, billing, app servers. Each one needs authentication individually. The senders people forget (notification services and app servers) are usually the ones failing.
- 2
Get SPF and DKIM passing for every source
Add each provider's include: to your SPF record (watching the 10-lookup limit) and enable DKIM signing with your domain in each provider's settings. DKIM must sign with your domain, not the provider's default, for DMARC alignment.
- 3
Publish a DMARC record
Add a TXT record at _dmarc.yourdomain.com with at least v=DMARC1; p=none; rua=mailto:your-reports-address. This satisfies Google's bulk-sender requirement immediately and starts the report flow that shows you what's really passing and failing.
- 4
Add one-click unsubscribe to marketing and bulk mail
Bulk messages need the List-Unsubscribe and List-Unsubscribe-Post headers (RFC 8058) so Gmail can show its one-click unsubscribe, and you must honor requests within two days. Most reputable email platforms have a setting for this. Turn it on.
- 5
Check your spam rate in Postmaster Tools
Register your domain with Google Postmaster Tools and watch the spam-rate graph. Stay under 0.3%, ideally under 0.1%. If you're above it, tighten list hygiene: remove stale addresses, drop purchased lists, and stop mailing people who never engage.
- 6
Verify and monitor
Send tests to Gmail and confirm spf=pass, dkim=pass, and dmarc=pass in “Show original”. Then run your domain through our DMARC checker to confirm the records are valid, and keep reading your DMARC reports. They show per-source pass rates across all your mail, not just test messages.
Verify the fix
Run the check that corresponds to this error. You'll see the same red/amber/green verdicts mailbox providers effectively apply.
Open the DMARC checker →Preventing it next time
Google's requirements aren't a one-time hurdle: a new sending tool, an expired DKIM key, or a creeping spam rate can put you back in the spam folder months after you've “fixed” everything. DMARCPath monitors your DMARC reports and DNS records continuously and alerts you in plain English when a source stops authenticating, so you catch the regression the day it happens instead of when a customer asks why your emails stopped arriving.
Frequently asked questions
- I send fewer than 5,000 emails a day. Do these rules apply to me?
- The full bulk-sender list doesn't, but the floor does: all senders need passing SPF or DKIM, valid DNS, and low spam rates. And the 5,000 threshold counts messages to Gmail per day from your whole domain, so growing senders cross it sooner than they expect.
- Is p=none really enough for the DMARC requirement?
- Yes: Google requires a DMARC record to exist, and p=none qualifies. Treat it as the starting point though: p=none gives you reports and compliance, while moving to quarantine or reject over time is what actually stops spoofing.
- My SPF, DKIM, and DMARC all pass, so why is mail still going to spam?
- Authentication is the entry ticket, not the whole game. Check your spam rate in Postmaster Tools, your sending volume patterns, list quality, and whether marketing mail has one-click unsubscribe. Reputation problems put authenticated mail in spam too.
Catch this before your customers do
DMARCPath watches your domain's authentication continuously and alerts you the day something breaks, not the week a customer mentions your emails stopped arriving. One domain free.
Start monitoring free →