Email deliverability is your ability to reach the inboxes of people who expect your messages. For a small business, the practical goal is not to chase a perfect score; it is to make your identity clear, send wanted email consistently, and spot problems before invoices, leads, or customer updates go missing. Use this checklist in order.
1. Check your domain’s technical foundation
Run a free Beacon domain check before changing DNS. Review SPF, DKIM, DMARC, and relevant blocklist signals. Keep the result as your baseline.
- Maintain exactly one SPF TXT record and ensure it covers every authorized sender.
- Enable DKIM in your mailbox provider, marketing platform, support system, and any transactional sender.
- Publish DMARC and begin in monitoring mode when you are still finding senders.
- After each DNS change, send a test message and inspect the actual authentication results in its headers.
If you are unsure how to read SPF, start with our SPF record guide; it is safer than copying an example from another business.
2. Make a complete sender inventory
Write down every tool that can send as your domain: Google Workspace or Microsoft 365, CRM, newsletter platform, ecommerce receipts, booking app, billing system, form tool, and help desk. Include the person or team responsible and the DNS records it needs. Forgotten systems are a common source of DMARC failures and customer-facing delivery issues.
3. Send only to people who expect it
Permission is part of deliverability. Use clear signup language, preserve evidence of consent where appropriate, and set expectations for frequency and content. Do not buy or scrape lists. Suppress hard bounces, honor unsubscribes promptly, and re-confirm older contacts instead of treating an inactive list as ready for a big campaign.
4. Use recognizable messages
- Use a consistent From name and address that identify your business.
- Make the subject line match the message and the signup promise.
- Include your business identity and an easy unsubscribe method in marketing mail.
- Avoid misleading urgency, image-only emails, or links through unrelated domains.
- Test the message on desktop and mobile before sending a large campaign.
5. Manage volume and engagement
Large, abrupt sending changes can create trust problems. If you have a new domain, a new platform, or a long-inactive list, begin with recently engaged recipients and increase volume deliberately. Separate marketing and transactional streams where your provider allows it. Watch bounces, complaints, replies, and clicks—not only opens, which can be unreliable as a measurement.
6. Diagnose poor results with evidence
When a customer says “your email went to spam,” capture the provider, approximate time, sending system, and full headers if possible. Ask whether the issue affects one mailbox or a broader segment. Then check authentication, list quality, content, and recent sending changes. Do not respond by changing random DNS settings; an SPF or DMARC change can affect legitimate mail. For the full sequence, read why emails go to spam.
7. Protect the brand from impersonation
Inbox placement and spoofing overlap at authentication. Once you know all legitimate senders, use DMARC reports and progress toward an appropriate policy. Learn how policy choices work in this DMARC policy guide. Stronger enforcement before sender discovery is complete can block an important system, so validate first.
8. Put an owner and cadence behind it
Set a quarterly review, plus an immediate review after a vendor migration, domain move, DNS change, or new sending tool. Record who owns the domain registrar, DNS, email provider, and each sender. After the initial cleanup, Beacon’s ongoing monitoring can help surface monitored domain-health changes rather than leaving you to find them only after delivery is affected.
9. Separate an urgent delivery problem from a routine campaign problem
Reset-password, invoice, and appointment messages are more time-sensitive than a newsletter. If those messages fail, temporarily send a small number of real tests to the mailbox provider where the issue was reported and check the provider’s status information. Do not “fix” a transactional problem by routing it through a personal inbox or by turning off authentication. Preserve the normal business identity and find the specific sender, DNS, or provider issue.
For a promotional campaign, pause the next large send if complaints or bounces rise unexpectedly. Review the source of the list, the consent language, recent segmentation changes, and whether a new sender or link domain was introduced. This makes the response proportionate and protects the transactional mail customers rely on.
Example: a simple 30-minute audit
A service business uses Microsoft 365 for personal mail, a booking tool for confirmations, and a newsletter platform. First it runs a domain check, then lists the three senders. It verifies one SPF record, enables DKIM in each service, publishes DMARC monitoring, and sends one real test from each. It removes hard bounces from the newsletter list and schedules a check after the next campaign. This is more useful than trying to optimize every word of an email before confirming the basic identity setup.
Frequently asked questions
Is authentication enough to stay out of spam?
No. It establishes legitimate identity. Permission, complaints, list hygiene, message relevance, and sending behavior still matter.
How often should I use this checklist?
Review it before a major campaign and whenever you add or replace a sender; perform a broader review at least periodically so old DNS assumptions do not linger.