Mailbox providers
Why Are My Google Workspace Emails Going to Spam?
Workspace mail usually lands in spam because DKIM was never turned on, SPF is missing Google's include, or there's no DMARC. Here's how to fix each.
On this page
When email sent from Google Workspace lands in spam, the cause is almost always one of three things on your own domain: DKIM was never turned on in the Admin console, your SPF record doesn't include Google, or you have no DMARC record. Fix those first. If authentication is clean, the next suspects are what you're sending (bulk or cold email from user mailboxes), a compromised account, and other tools sending as your domain without authentication.
Workspace gets mail flowing as soon as your MX records point at Google. It does not finish the work that proves to other mailbox providers that the mail is really yours. That part is manual, and it's the step people skip. For the broader version of this problem, including Microsoft 365, see why business email goes to spam.
Check this first: read one message's headers
Before changing anything, send a message from your Workspace account to a personal Gmail address (or anyone who'll forward you the original). In Gmail, open it, choose More, then "Show original." The summary at the top shows SPF, DKIM and DMARC results. You want:
- SPF: PASS with your domain
- DKIM: PASS with
d=example.com(your domain, not a Google domain) - DMARC: PASS
The header analyzer will lay it out if the raw text is hard to read, and the email checker will check your published records. Whatever fails tells you where to start.
Common causes (most likely first)
1. DKIM was never started
This is the most common gap. In the Admin console you have to generate a DKIM key, publish it in DNS, and then go back and click Start authentication. Lots of domains have the DNS record published and never clicked the button, or never did either. Without it, mail isn't signed with your domain. (Google appears to sign with a default Google-owned domain in that case, but that signature doesn't align with your From address, so it doesn't help DMARC.)
Google's setup documentation also says you may have to wait 24 to 72 hours after turning on Gmail before you can generate the key, and up to 48 hours after publishing it before DKIM starts working.
2. SPF is missing, duplicated or over the limit
Google's recommended record for a domain that only sends through Workspace is:
v=spf1 include:_spf.google.com ~all
Problems come in three flavors: no record at all, two separate SPF records (only one is allowed, and two breaks both), or a record that has accumulated so many includes for other tools that it exceeds the 10 DNS lookup limit. The SPF analyzer counts lookups for you, and SPF lookup limit explains how to get back under it.
3. No DMARC record
DMARC ties SPF and DKIM to the domain in your From address. Google's sender guidelines require all senders to have SPF or DKIM, and anyone sending more than 5,000 messages a day to Gmail to have SPF, DKIM and DMARC. Even below that volume, a missing DMARC record is a weak signal. Start with p=none and a reporting address; the DMARC generator will build it.
4. Other tools sending as your domain
Your CRM, help desk, invoicing system, website contact form and marketing platform may all send "from" your domain. If any of them aren't set up with DKIM for your domain, their mail fails DMARC, and recipients learn to distrust your domain overall. Your DMARC aggregate reports will list every source sending as you.
5. Using Workspace mailboxes for bulk or cold email
Workspace is built for person-to-person email. Google caps each user at 2,000 messages a day (500 for trial accounts), and if a user exceeds a limit they can be blocked from sending for up to 24 hours. Well before you hit the cap, though, sending the same message to hundreds of people who didn't ask for it generates spam reports, and those count against your domain. That's how a sales team's outreach sequence ends up dragging down everyone's regular mail. Newsletters and promotions belong on a proper sending platform with authentication set up for your domain and one-click unsubscribe.
6. A compromised account
If one user's password was phished, their account may be sending spam you never see. Signs include bounces for messages nobody remembers sending, a user suddenly hitting sending limits, or Google suspending a user's ability to send. Check the Admin console's email log search and security alerts, reset the password, and enforce 2-step verification.
7. A new domain with no history
A domain registered last month has no reputation at all, and filters are cautious with it. Authentication helps, but only time and normal, wanted mail build trust. See new domain going to spam.
How to fix it, step by step
- Turn on DKIM. Admin console, Apps, Google Workspace, Gmail, Authenticate email. Select the domain, generate a new record (2048-bit if your DNS host supports it; the default selector is
google), publish the TXT record at your DNS host, then return and click Start authentication. Repeat for every domain and alias domain you send from. - Fix SPF. Publish a single record that includes
_spf.google.complus the other services that legitimately send for you. Remove services you no longer use. Stay under 10 lookups. - Publish DMARC. Add a
_dmarc.example.comTXT record withp=noneand aruaaddress you'll actually read. - Authenticate your other senders. Go through each tool from your DMARC reports and set up DKIM with your domain in each one.
- Move bulk mail off user mailboxes. Newsletters, announcements and outreach to large lists go through a dedicated platform, ideally on a subdomain so their reputation is easier to manage.
- Secure accounts. Enforce 2-step verification and review recent sending activity for any user who triggered a limit.
How to confirm it's fixed
Repeat the header test: send to a personal Gmail address and an Outlook.com address, and confirm SPF, DKIM and DMARC pass with your domain. Watch your DMARC aggregate reports for a week or two to make sure nothing else is failing. If you send enough mail to personal Gmail accounts, verify your domain in Google Postmaster Tools to see spam rate and authentication data; Google notes data may be missing on low-volume days. Placement often improves within days of fixing authentication, though a domain with a poor history can take longer.
How to keep it from coming back
Make authentication part of onboarding any new tool: before it sends as your domain, it gets DKIM and gets added to SPF if needed. Read your DMARC reports monthly. Once every legitimate source passes, move toward an enforcing DMARC policy so nobody else can send convincing mail as you. And keep your Workspace mailboxes for the conversations they're designed for.
If recipients are seeing a red or yellow banner rather than a spam placement, that's a related but different problem: see Gmail security warnings.
When to get help
If headers show a clean pass and mail still goes to spam at several providers, the issue is reputation, not setup, and that's harder to diagnose from the outside. That's a good time to bring in someone who does this daily. Get in touch.
FAQ
Does Google Workspace set up SPF and DKIM automatically?
Not fully. If you bought your domain through Google or a Google partner some records may already be in place, but in most cases you have to add the SPF record and generate and start DKIM yourself in the Admin console.
My emails go to spam in Outlook but not Gmail. Is that a Workspace problem?
It can still be authentication, since Microsoft checks the same records, but it's often reputation or Microsoft-specific filtering. See why Outlook goes to junk.
Can I send my newsletter from Gmail in Workspace?
You can for a small list, but it's the wrong tool. You'll run into daily sending limits, you won't have proper unsubscribe handling, and complaints land on your main domain. Use an email marketing platform authenticated for your domain.
How long after fixing DKIM will my emails stop going to spam?
Google says DKIM can take up to 48 hours to start working after you publish the record. Placement usually improves soon after, but if your domain built up a poor reputation while unauthenticated, recovery can take a few weeks of steady, wanted mail.
Sources
Related guides
- Gmail Spam Rate Threshold: What 0.1% and 0.3% Really MeanGmail requires a spam rate below 0.3% and recommends below 0.1%, measured on inbox-delivered, DKIM-signed mail in Postmaster Tools. Here's what that means.
- Gmail Warnings: 'This Message Seems Dangerous' and 'Be Careful With This Message'Gmail shows these banners when it suspects phishing, spoofing or unauthenticated mail. As a sender, fix authentication, then look at links and content.
- How to Get Delisted by Microsoft (Outlook.com and Microsoft 365)Microsoft runs separate block lists for Outlook.com and Microsoft 365, each with its own removal process. Match your bounce code to the right one, then ask.
- Why Are Yahoo and AOL Blocking My Emails?Yahoo and AOL block or defer mail over complaints, weak authentication, bad lists, sudden volume spikes and poor IP reputation. Here's how to find which one.
- Why Do My Emails Go to Junk in Outlook and Hotmail?Outlook junks mail that fails authentication, comes from a low-reputation IP, or draws complaints. Here's how to read Microsoft's verdict and fix the cause.
- Why Is iCloud (Apple Mail) Blocking My Emails?iCloud blocks mail that fails authentication, comes from a poorly rated IP or domain, or trips its content filters. Read the bounce first, then fix the cause.
Still stuck?
Some deliverability problems take an experienced eye to untangle. Tell me what you're seeing and I'll tell you what I'd check first. The first 30-minute call is free.