Why Emails Go to Spam: 25 Common Causes and Simple Fixes
When an email lands in spam, it is tempting to blame one word, one link, or one unlucky send. Usually the cause is a pattern. Inbox providers are trying to protect people from unwanted mail, and they use many signals at once.
The useful question is not “which spam word did I use?” It is “what would make a recipient or provider doubt that this message is wanted and genuine?” The fixes below start with the highest-impact causes.
Do not change everything at once. Make one sensible change, send to a small engaged group, and watch the results. That makes it possible to learn what actually helped.
Start here
1–5: Fix identity before copy
Missing SPF, missing DKIM, missing DMARC, a From domain that does not align with authentication, and a changing sender address all make it harder to prove who sent a message. Fix these records first. Your email platform can provide values, but domain DNS changes are usually made where the domain is registered.
6–10: Stop sending to bad addresses
High hard-bounce rates, bought lists, old unengaged contacts, invalid imports, and sending without confirmed permission are five versions of the same problem: the list is not a real audience. Remove hard bounces, validate imports, and give old contacts a clear chance to stay subscribed before regular mail resumes.
11–15: Make your sending pattern believable
A sudden volume spike, erratic sending, a brand-new domain sending heavily, too many messages in a week, and no separation between promotions and account mail can all look risky. Start small, use a regular rhythm, and avoid treating every subscriber as someone who wants every update.
16–20: Remove reasons to complain
Misleading subject lines, baiting people with “Re:” or “Fwd:”, no visible unsubscribe link, irrelevant offers, and a hard-to-recognise sender all create complaints. A complaint is much worse than an unsubscribe. Be clear about who you are and what the reader will get.
21–25: Check message quality and links
Suspicious link domains, broken links, image-only emails, hidden text, and poor mobile rendering make mail look unsafe or careless. Use readable text, descriptive links, a plain-text version, and one or two clear actions. Test on a phone before sending.
Make a recovery plan
Pause the lowest-quality part of your list rather than sending more to “fix” engagement. Send your best, most useful message to subscribers who recently engaged. Review bounces and complaints.
After the basics are repaired, build volume back slowly. Reputation recovers through better behaviour over time, not a single rescue campaign.
The details that make the difference
Spam words are not the main problem
Words such as “free” or “sale” do not automatically send an email to spam. A legitimate retailer can use both. The problem is deception and unwanted mail.
Replacing every normal sales word with strange spelling makes your message less trustworthy, not more deliverable.
Segmentation is a spam fix
If someone only signed up for product updates, a weekly company newsletter may be irrelevant. Segment by what people requested, what they bought, or what they have recently done. Relevance produces fewer complaints, and fewer complaints improve long-term delivery.
A clean unsubscribe is a win
When somebody opts out, let them go. Do not require a password, survey, or three-page form. A preference centre can be useful, but it must not obstruct the unsubscribe.
People who no longer want mail are not a conversion opportunity.
Do not hide behind a shared IP
A good email platform manages the shared infrastructure, but it cannot make unwanted mail wanted. Your domain’s reputation still follows your list and sending behaviour. Focus on what you control: permission, content, volume, and authentication.
Test headers, not only design
Send a test to a Gmail account and inspect the message details. Look for SPF and DKIM passing and for the sending domain you expect. A polished template can still fail basic authentication, which is why design review alone is not enough.
Know when to ask for technical help
If DNS records are confusing, ask the person who manages your domain or your email platform support. Do not paste random records from a blog. A wrong DNS record can break existing company email, so document what is already there before making changes.
A practical workbook for this guide
Read the following sections as a working session, not more theory. Each one turns the advice above into a decision you can make this week.
Put “1–5: Fix identity before copy” into practice
Do not try to improve everything at once. During your next working session, write down what is true today, choose one small change, name the person responsible, and set a date to check the result. Here is the principle to apply: Missing SPF, missing DKIM, missing DMARC, a From domain that does not align with authentication, and a changing sender address all make it harder to prove who sent a message.
Fix these records first. Your email platform can provide values, but domain DNS changes are usually made where the domain is registered. Read it against a real campaign or real customer, not an imaginary perfect example.
Then make the smallest safe change you can measure. Record what happened, including what did not work. That record turns a good idea into a repeatable habit and makes the next decision easier for the whole team.
Put “6–10: Stop sending to bad addresses” into practice
Do not try to improve everything at once. During your next working session, write down what is true today, choose one small change, name the person responsible, and set a date to check the result. Here is the principle to apply: High hard-bounce rates, bought lists, old unengaged contacts, invalid imports, and sending without confirmed permission are five versions of the same problem: the list is not a real audience.
Remove hard bounces, validate imports, and give old contacts a clear chance to stay subscribed before regular mail resumes. Read it against a real campaign or real customer, not an imaginary perfect example. Then make the smallest safe change you can measure.
Record what happened, including what did not work. That record turns a good idea into a repeatable habit and makes the next decision easier for the whole team.
Put “11–15: Make your sending pattern believable” into practice
Do not try to improve everything at once. During your next working session, write down what is true today, choose one small change, name the person responsible, and set a date to check the result. Here is the principle to apply: A sudden volume spike, erratic sending, a brand-new domain sending heavily, too many messages in a week, and no separation between promotions and account mail can all look risky.
Start small, use a regular rhythm, and avoid treating every subscriber as someone who wants every update. Read it against a real campaign or real customer, not an imaginary perfect example. Then make the smallest safe change you can measure.
Record what happened, including what did not work. That record turns a good idea into a repeatable habit and makes the next decision easier for the whole team.
Put “16–20: Remove reasons to complain” into practice
Do not try to improve everything at once. During your next working session, write down what is true today, choose one small change, name the person responsible, and set a date to check the result. Here is the principle to apply: Misleading subject lines, baiting people with “Re:” or “Fwd:”, no visible unsubscribe link, irrelevant offers, and a hard-to-recognise sender all create complaints.
A complaint is much worse than an unsubscribe. Be clear about who you are and what the reader will get. Read it against a real campaign or real customer, not an imaginary perfect example.
Then make the smallest safe change you can measure. Record what happened, including what did not work. That record turns a good idea into a repeatable habit and makes the next decision easier for the whole team.
Put “21–25: Check message quality and links” into practice
Do not try to improve everything at once. During your next working session, write down what is true today, choose one small change, name the person responsible, and set a date to check the result. Here is the principle to apply: Suspicious link domains, broken links, image-only emails, hidden text, and poor mobile rendering make mail look unsafe or careless.
Use readable text, descriptive links, a plain-text version, and one or two clear actions. Test on a phone before sending. Read it against a real campaign or real customer, not an imaginary perfect example.
Then make the smallest safe change you can measure. Record what happened, including what did not work. That record turns a good idea into a repeatable habit and makes the next decision easier for the whole team.
Put “Make a recovery plan” into practice
Do not try to improve everything at once. During your next working session, write down what is true today, choose one small change, name the person responsible, and set a date to check the result. Here is the principle to apply: Pause the lowest-quality part of your list rather than sending more to “fix” engagement.
Send your best, most useful message to subscribers who recently engaged. Review bounces and complaints. After the basics are repaired, build volume back slowly.
Reputation recovers through better behaviour over time, not a single rescue campaign. Read it against a real campaign or real customer, not an imaginary perfect example. Then make the smallest safe change you can measure.
Record what happened, including what did not work. That record turns a good idea into a repeatable habit and makes the next decision easier for the whole team.
Put “Spam words are not the main problem” into practice
Do not try to improve everything at once. During your next working session, write down what is true today, choose one small change, name the person responsible, and set a date to check the result. Here is the principle to apply: Words such as “free” or “sale” do not automatically send an email to spam.
A legitimate retailer can use both. The problem is deception and unwanted mail. Replacing every normal sales word with strange spelling makes your message less trustworthy, not more deliverable.
Read it against a real campaign or real customer, not an imaginary perfect example. Then make the smallest safe change you can measure. Record what happened, including what did not work.
That record turns a good idea into a repeatable habit and makes the next decision easier for the whole team.
Put “Segmentation is a spam fix” into practice
Do not try to improve everything at once. During your next working session, write down what is true today, choose one small change, name the person responsible, and set a date to check the result. Here is the principle to apply: If someone only signed up for product updates, a weekly company newsletter may be irrelevant.
Segment by what people requested, what they bought, or what they have recently done. Relevance produces fewer complaints, and fewer complaints improve long-term delivery. Read it against a real campaign or real customer, not an imaginary perfect example.
Then make the smallest safe change you can measure. Record what happened, including what did not work. That record turns a good idea into a repeatable habit and makes the next decision easier for the whole team.
Put “A clean unsubscribe is a win” into practice
Do not try to improve everything at once. During your next working session, write down what is true today, choose one small change, name the person responsible, and set a date to check the result. Here is the principle to apply: When somebody opts out, let them go.
Do not require a password, survey, or three-page form. A preference centre can be useful, but it must not obstruct the unsubscribe. People who no longer want mail are not a conversion opportunity.
Read it against a real campaign or real customer, not an imaginary perfect example. Then make the smallest safe change you can measure. Record what happened, including what did not work.
That record turns a good idea into a repeatable habit and makes the next decision easier for the whole team.
Put “Do not hide behind a shared IP” into practice
Do not try to improve everything at once. During your next working session, write down what is true today, choose one small change, name the person responsible, and set a date to check the result. Here is the principle to apply: A good email platform manages the shared infrastructure, but it cannot make unwanted mail wanted.
Your domain’s reputation still follows your list and sending behaviour. Focus on what you control: permission, content, volume, and authentication. Read it against a real campaign or real customer, not an imaginary perfect example.
Then make the smallest safe change you can measure. Record what happened, including what did not work. That record turns a good idea into a repeatable habit and makes the next decision easier for the whole team.
Put “Test headers, not only design” into practice
Do not try to improve everything at once. During your next working session, write down what is true today, choose one small change, name the person responsible, and set a date to check the result. Here is the principle to apply: Send a test to a Gmail account and inspect the message details.
Look for SPF and DKIM passing and for the sending domain you expect. A polished template can still fail basic authentication, which is why design review alone is not enough. Read it against a real campaign or real customer, not an imaginary perfect example.
Then make the smallest safe change you can measure. Record what happened, including what did not work. That record turns a good idea into a repeatable habit and makes the next decision easier for the whole team.
Put “Know when to ask for technical help” into practice
Do not try to improve everything at once. During your next working session, write down what is true today, choose one small change, name the person responsible, and set a date to check the result. Here is the principle to apply: If DNS records are confusing, ask the person who manages your domain or your email platform support.
Do not paste random records from a blog. A wrong DNS record can break existing company email, so document what is already there before making changes. Read it against a real campaign or real customer, not an imaginary perfect example.
Then make the smallest safe change you can measure. Record what happened, including what did not work. That record turns a good idea into a repeatable habit and makes the next decision easier for the whole team.
A simple checklist
- Authentication passes on a live test email.
- The From address is familiar and consistent.
- Imports are permission-based and checked for bad addresses.
- Inactive contacts are not treated like new subscribers.
- Every campaign has a visible unsubscribe link.
- Links, layout, and landing pages work on mobile.
The short version
Spam placement is not a mystery box. Prove your identity, use a healthy list, send at a steady pace, and give people a truthful reason to care. Fix those four areas first; they solve more than any list of forbidden words.
Continue learning
Related Cresca resources
External references