Your emails go to spam when the receiving mailbox provider doesn't trust the mail enough to put it in the inbox. When I diagnose a spam problem, I check four causes first: failed authentication, a spam complaint rate that's too high, a dirty or newly imported list, or a sudden change in how or what you send.
Those causes are written down in the providers' own rules. Google's Email sender guidelines tell senders to keep the spam rate reported in Postmaster Tools below 0.1% and never reach 0.3%, and since May 5, 2025 Outlook.com sends non-compliant high-volume mail to Junk when SPF, DKIM, or DMARC isn't in place.
This is the fast diagnostic version, the one I run when a client messages me "we're in spam, help." You'll match your symptom to a likely cause, work through five checks in order, and finish with a 14-day recovery plan, so you fix the real problem instead of guessing.
Let's start with your symptom.
In this article
- Match your symptom to the likely cause
- Step 1: Confirm it's really the spam folder
- Step 2: Check authentication in three minutes
- Step 3: Check your complaint rate and blocklists
- Step 4: Find what changed in the last 14 days
- Step 5: Fix the content and unsubscribe signals
- The 14-day recovery plan
- FAQ
- Final Thoughts
Match your symptom to the likely cause
Before touching anything, write down exactly what you're seeing. The pattern of the problem usually points straight at the cause, and it saves you from rewriting subject lines when the real issue is a DNS record.
| What you see | Most likely cause | First thing to check |
|---|---|---|
| Spam at Gmail, Yahoo, and Outlook at once | Authentication failure or blocklisting | Message headers and the domain scanner |
| Spam at Gmail only | Gmail spam rate or domain reputation | Google Postmaster Tools |
| Junk at Outlook or Hotmail only | Microsoft authentication rules or IP reputation | Bounce codes like 550 5.7.515 and Microsoft SNDS |
| Started right after a big send | Volume spike or list import | Send log for the last 14 days |
| Only one campaign hit spam | Content, links, or a new template | That campaign's links and HTML |
| Hard bounces jumped too | Stale or purchased addresses | List source and bounce report |
Pro tip: Ask the person who reported the problem which mailbox provider they use. "Our CEO's Gmail" and "every customer on Outlook" are completely different investigations.
Step 1: Confirm it's really the spam folder
"Delivered" in your email platform only means the receiving server accepted the message. It says nothing about whether the message landed in the inbox, the Promotions tab, or spam.
So test placement directly. Send the campaign to a few seed addresses you control at Gmail, Outlook, and Yahoo, and note where each copy lands.
Why not just trust open rates? Apple Mail Privacy Protection preloads images for many Apple Mail users, so opens can look healthy while Gmail subscribers never see the email.
Clicks and seed tests are the honest signals. A click rate that halves overnight while sends stay flat is one of the clearest spam folder warnings you'll get, even before anyone complains.
Promotions is not spam. If Gmail drops your newsletter into the Promotions tab, that's sorting, and the fix is different from (and far less urgent than) a spam folder problem.
Then open the copy and read the authentication results. In Gmail, click the three dots and choose "Show original," and you'll see a summary of SPF, DKIM, and DMARC with a PASS or FAIL next to each.
Weak diagnosis: "Open rates dropped from 38% to 19%, so the subject lines must be off."
Strong diagnosis: "Seed copies land in spam at Gmail and Outlook, and Show original says DMARC: FAIL. The problem is authentication, so copy can wait."
Step 2: Check authentication in three minutes
If the header says FAIL on DMARC, or SPF and DKIM both fail, stop everything else. No subject line or list cleanup will rescue mail that can't prove it came from your domain.
Run your sending domain through the free domain scanner, which checks SPF, DKIM, DMARC, and MX in one pass. If a record is missing or broken, the SPF checker and DMARC checker show exactly what's wrong with each record.
The failures I find most often during a spam fire drill are these:
- A New Tool That Was Never Added to SPF: Marketing switched platforms or added a help desk tool, and nobody updated the SPF record.
- DKIM Signing on the Platform's Domain, Not Yours: The email is signed, but with the platform's shared domain, so DMARC alignment fails.
- No DMARC Record at All: Google, Yahoo, and Microsoft all expect at least
p=nonefrom bulk senders. - Too Many SPF Lookups: More than 10 DNS lookups breaks SPF entirely, even when every sender is listed.
Fixing each of these takes DNS changes rather than marketing changes. My full walkthrough on email authentication with SPF, DKIM, and DMARC covers each record, alignment, and how to move DMARC from monitoring toward enforcement.
Pro tip: If you're on Klaviyo or a similar platform, check that you've set up a branded sending domain. Shared sending domains are fine for testing, but once you're a real sender you want your own domain carrying DKIM and reputation.
On the Klaviyo accounts I run through my Klaviyo agency work, this is one of the first things I check, because no flow or subject line test fixes mail that's riding someone else's reputation.
Step 3: Check your complaint rate and blocklists
If authentication passes and mail still lands in spam, the next suspect is complaints. Every "Report spam" click tells the provider your mail is unwanted, and it takes very few of them to cause trouble.
Verify your domain in Google Postmaster Tools and look at the spam rate graph for the last 30 days. Google wants that rate under 0.1%, and if it reaches 0.3% or higher, you have to stay below 0.3% for seven days in a row before Google's mitigation support will help.
For Microsoft, enroll your sending IPs in Smart Network Data Services to see filtering results and complaint data. Then run the blacklist checker against your domain and sending IP.
If a blocklist shows up, fix the cause first and request removal second. Listings that get removed without fixing the cause come right back.
Complaints and blocklists both feed your sender reputation, and my guide to email sender reputation shows how to check and fix it.
Read the bounce codes before you guess
Your email platform's bounce report often names the problem outright. Providers return a code and a short reason with every rejected message, and most people never open that report.
A Microsoft bounce reading 550 5.7.515 Access denied, sending domain does not meet the required authentication level means Outlook rejected the mail because authentication failed. Gmail rejections that mention authentication or "unsolicited mail" point at the same two suspects: DNS records or reputation.
Pro tip: Export the last 7 days of bounces and sort by reason text rather than by count. One repeated reason across thousands of addresses is a sender problem, while scattered "mailbox full" or "user unknown" lines are just list decay.
List decay is a cleaning job, not an emergency. My guide to email list cleaning covers what to remove first and how to suppress the rest without losing buyers.
Step 4: Find what changed in the last 14 days
Spam problems rarely appear out of nowhere. Something changed, and the job here is to find it.
I pull the send log and look for any of these changes in the two weeks before placement dropped:
- Volume Spike: Did you send to 3x your normal audience, maybe a "send to everyone" holiday blast?
- New List Source: Was a CSV imported, a webinar list added, or a partner list merged in?
- New Sending Setup: Did you change platforms, add a dedicated IP, or switch the From domain?
- Long Silence, Then a Blast: Did you go quiet for months and then mail the whole list at once?
Weak recovery: Keep sending the weekly promo to the full list and hope placement bounces back.
Strong recovery: Pause sends to anyone who hasn't opened or clicked in 90 days, mail only recent engagers for two weeks, and validate the imported list before it touches another campaign.
If the cause was a new dedicated IP or a new domain, slow down and follow a proper email warmup schedule. A cold IP blasting full volume looks exactly like a spammer to every filter out there.
Pro tip: Never mail a purchased or scraped list, not even "just once." Those addresses never opted in, they generate complaints, and many contain spam traps that land you on blocklists.
Step 5: Fix the content and unsubscribe signals
Content is usually the last cause, not the first, though it still matters. Filters look at links, images, and how easy it is to leave your list.
| Content signal | Why filters flag it | The fix |
|---|---|---|
| Link shorteners like bit.ly | They hide the destination, which phishers love | Use full branded links |
| Image-only email | Text hidden in images dodges filters | Keep real HTML text and alt text |
| Subject that oversells | Misleading lines drive spam complaints | Match the subject to the body |
| Hard-to-find unsubscribe | Frustrated readers hit "Report spam" instead | Visible link plus one-click unsubscribe header |
| Broken or mismatched links | Looks like a hijacked or careless sender | Test every link before sending |
Here's an example of the subject line problem:
Weak: FINAL WARNING!!! Your account will be CLOSED
Strong: Your invoice for October is ready
The strong one says exactly what's inside, so nobody feels tricked when they open it. My email subject lines best practices go further on writing lines that are specific without sounding alarming.
Google requires one-click unsubscribe on marketing mail from bulk senders and expects unsubscribes to be honored within about two days. If your footer hides the unsubscribe link, readers will find the spam button instead.
If you're worried about specific words, my list of spam trigger words explains which phrases matter and which ones are myths. Run your next subject line through the subject line tester before it goes out.
The 14-day recovery plan
Once you know the cause, recovery is mostly patience and discipline. Here's the cadence I use after the fix goes in:
- Day 0: Fix the root cause (DNS records, suppress the bad import, or turn off the problem template). Pause sends to unengaged contacts.
- Day 1: Send only to people who opened or clicked in the last 30 days. Recheck headers on seed copies.
- Day 3: Review Postmaster spam rate and bounce rate. Widen to the 60-day engaged segment if numbers hold.
- Day 7: Widen to 90-day engagers and run a short re-engagement email for the quiet group.
- Day 14: Suppress anyone who stayed quiet, then return to normal cadence with the engaged list.
Expect a slow climb rather than an overnight fix. Minor issues often settle within a couple of weeks of clean sending, while a blocklisting or heavy complaint history can take a couple of months.
Once your placement recovers, my guide on how to improve email deliverability and avoid spam covers the habits that keep it there.
If you'd rather have someone else run this diagnosis, the paid Email DDx audit and fix checks authentication, reputation signals, and flows and gives you a ranked fix list. For a self-serve version, work through the deliverability checklist.
FAQ
Why did my emails suddenly start going to spam?
Something changed: a volume spike, a list import, a new platform or domain, or a burst of complaints from one campaign. Use the 14-day change check above to find it, and check headers to rule out an authentication break.
Why are my emails going to spam in Outlook but not Gmail?
Microsoft enforces its own high-volume sender authentication rules and IP reputation checks. Look for 550 5.7.515 bounces, confirm DMARC alignment, and check your IPs in SNDS.
How do I stop my emails going to spam for one recipient?
Ask them to move your message to the inbox and add your address to their contacts. That helps for that one person, but if more than a handful of people report it, run the full diagnosis.
Can my email platform be the reason I'm in spam?
Sometimes, if you're on a shared IP pool or a shared sending domain that another sender damaged. That's the exception, though, so rule out your own authentication, complaints, and list changes before you blame the platform or pay to switch.
Do spam trigger words still matter?
Much less than authentication, complaints, and list quality. A single word rarely sends mail to spam on its own, but shouty, misleading subject lines do drive complaints.
Final Thoughts
You came here to find out why your emails are going to spam, and now you have the order to check it in: confirm placement with seed tests and headers, fix authentication, check complaint rate and blocklists, find what changed, then clean up content and unsubscribe. Most cases I see are solved by the first three steps.
Your next step is to send one campaign to a Gmail and an Outlook seed address today, open "Show original," and run your domain through the domain scanner. If anything comes back FAIL, fix that before you send another campaign.
Russ
