Email Deliverability Checklist for Small Businesses
A sending checklist for DNS, list quality, verification, consent, suppression, and sender reputation.
Deliverability is the difference between sending email and reliably reaching people who want to hear from you. Small businesses often treat it as a problem only after opens drop or complaints spike.
Basic setup
- Send from a real domain.
- Configure SPF, DKIM, and DMARC.
- Use a consistent from name and reply address.
- Set up bounce and complaint handling.
- Keep unsubscribe links obvious.
- Avoid using old or unclear lists.
List quality
Verify risky or old addresses before sending. Suppress invalid, bounced, unsubscribed, and complained contacts. Track source and consent so future decisions are not guessing.
Sending behavior
Warm up new domains and providers conservatively. Avoid sudden spikes. Watch recipient domains such as Gmail, Yahoo, and Outlook separately because problems can appear unevenly.
Tools I would use
Google Postmaster Tools should be set up for domains sending meaningful volume to Gmail. It gives a view into reputation and delivery-related signals.
Microsoft SNDS can be useful when Outlook/Hotmail delivery matters and sending volume is large enough to make the signal meaningful.
SendGrid, Mailgun, or Amazon SES event webhooks should feed bounces, complaints, deliveries, opens, clicks, and suppressions back into the system of record.
DeBounce, NeverBounce, ZeroBounce, or Bouncer can help clean risky lists before a campaign.
DMARC reporting tools are worth adding when the business needs visibility into authentication, spoofing, or domain alignment issues.
Resonance is being built around this problem: not just seeing delivery data, but using it to decide when to send, hold, throttle, or change recipient mix.
Content risk
Aggressive claims, misleading subject lines, low-value offers, and irrelevant messages can create complaints even when the list is technically valid.
How I would watch it
Treat deliverability as a feedback loop. DNS, provider health, contact verification, engagement, content, and recipient-domain behavior should all influence when to send, hold, throttle, or change audience mix.
That is the direction behind Resonance: safe sending decisions based on signals, not hope.