The short answer

Start with the original message headers, not a list of “spammy words.” Ordinary email can land in spam because the sender is not authenticated, the domain or sending service has a poor or undeveloped reputation, the message came through forwarding, recipients did not expect it, or the content and links resemble unwanted bulk mail.

One message in one person’s spam folder does not prove a domain-wide problem. Find the pattern first, then fix the cause you can demonstrate.

Determine the size of the problem

Send a normal, personal test message to accounts you control at Gmail, Microsoft, and another provider. Do not use a newsletter template or send the same test to a large list.

Record:

Ask the recipient to mark the message “not spam” only when it is genuinely wanted. That can help the recipient’s mailbox learn, but it does not repair broken authentication across the domain.

Read the authentication results

In Gmail, use “Show original.” Other providers offer a message-source or header view. Look for:

• SPF: PASS or failure.
• DKIM: PASS or failure.
• DMARC: PASS or failure.
• the domain used for each result.
• the actual sending service or IP.
• the visible From address and Return-Path.

The word PASS is not the end of the analysis. DMARC also cares whether the authenticated domain aligns with the domain the reader sees in the From address.

Use this repair order:

1. Identify every legitimate service that sends using the domain.
2. Confirm that each service has its own supported authentication setup.
3. Maintain one valid SPF record rather than publishing several competing records.
4. Enable DKIM signing at each supported sender.
5. Monitor DMARC reports before moving to a strict enforcement policy.

Google’s sender guidelines require SPF or DKIM for all mail sent to Gmail accounts and require SPF, DKIM, and DMARC for high-volume senders. Yahoo’s sender requirements likewise call for SPF or DKIM for all senders and a low spam-complaint rate. These requirements can change, so the provider pages should be checked during publication review and ongoing maintenance.

Identify the real sending path

Your domain may send through more systems than you realize:

• ordinary mailbox provider.
• website contact form.
• store or payment platform.
• scheduling and invoicing tools.
• customer relationship manager.
• newsletter platform.
• help desk.

A perfectly configured Google Workspace mailbox does not authenticate a WordPress plugin or invoice app automatically. The headers show which system delivered the message. Fix that sender rather than editing every record on the domain.

Examine recipient expectation

Even technically authenticated mail can be unwanted. Ask:

• Does the recipient know who you are?
• Did she ask for this message or reasonably expect it?
• Are you sending the same first-contact message to many people?
• Are old, purchased, scraped, or poorly maintained addresses involved?
• Did complaints or bounces increase recently?
• Is the From name honest and recognizable?

If the message is promotional, use a permission-based email platform and follow the rules for commercial email. A normal inbox is not a loophole for sending an unwanted campaign.

Pause bulk mail if you see a sudden complaint or bounce increase. Remove invalid sources and correct the audience and permission process before trying to “warm” the domain with more sending.

Clean up content without chasing myths

Content matters, but there is no magic blacklist of ordinary words that guarantees spam placement. Focus on signals that make a message look deceptive or risky:

• a display name that impersonates a person or company.
• a From address that differs unexpectedly from Reply-To.
• shortened or mismatched links.
• a newly registered link domain unrelated to the sender.
• large or unusual attachments.
• an image-only message with little readable context.
• a misleading subject line.
• hidden text or tricks intended to defeat filters.
• a signature containing several unnecessary tracking or image links.

For a personal test, send a plain message with one clear subject, a few natural sentences, no attachment, and a normal signature. If it reaches the inbox while the original does not, add elements back one at a time. That is a diagnostic test, not permission to hide the nature of the message.

Treat a new domain gently

A new domain has little sending history. Begin with the ordinary correspondence the business actually needs. Keep volume consistent with the size of the business, send to people who expect the mail, and remove failed addresses promptly.

Do not buy an old domain solely for its supposed reputation, rotate domains to escape filtering, or send fake conversations to manufacture engagement. Those tactics avoid the real problem and may create a worse one.

If the business is changing providers, authenticate the new service before sending campaigns. Monitor the first real mail closely and keep the old system available long enough to diagnose transition issues.

Build a deliverability evidence sheet

For each failed test, record:

This gives the provider something useful if you need support. “My emails go to spam” gives it almost nothing.

Sources and further reading

• Google: Email sender guidelines
• Yahoo: Sender best practices and requirements

If you send newsletters or campaigns

The Email Marketing System can help you build permission, authentication, list care, and monitoring into the email program instead of treating deliverability as a last-minute fix.

A free next step

Not sure which business fits you yet?

The free Freedom Path Assessment can help you compare your strengths, schedule, income goals, and preferred way of working before you commit to a business direction.

Take the Freedom Path Assessment Free

Related Questions

• How do I read and send my domain email from Gmail or Outlook?
• Why can I send business email but not receive it, or receive it but not send it?
• How do I move business email to a new provider without losing mail or breaking delivery?
• Which business email provider should I choose: Google Workspace, Microsoft 365, or another option?