Email Deliverability: Why Your Emails Land in Spam (and How to Fix It)
You can write a perfect email that never gets seen. Here's the practical side of deliverability — authentication, sender reputation, engagement, and list hygiene — and the fixes that actually move it.

The worst email problem is invisible: you write something genuinely useful, press send, and it arrives in the promotions tab — or the spam folder — for half your list without an error, bounce, or complaint. You'll never see it happen. The metrics will just sag a little every month and you'll blame the subject lines.
Deliverability is the system that decides where your email lands, and it runs on four layers: technical authentication, sender reputation, engagement history, and list quality. None of them are optional, and they fail in that order — a new sender with broken authentication is invisible before they've annoyed anyone. This article covers the layers in the order worth fixing them, plus the habits that keep them healthy. The stakes are rising: mailbox providers have tightened their bulk sending requirements in recent years, so practices that were tolerable a few years ago now measurably cost you the inbox.
Layer one: authentication — the passport your email must carry
Every email you send gets checked at the door for three documents. SPF (a DNS record listing which servers may send mail for your domain), DKIM (a cryptographic signature proving the message wasn't altered in transit), and DMARC (a policy telling receiving servers what to do when the first two fail). Together they answer one question: is this email really from the domain it claims to be from?
Authentication failure doesn't make your email spam because providers think you're shady — it makes it unverifiable, and unverifiable mail from an unknown sender goes to the folder. The fixes are unglamorous and one-time: add the SPF and DKIM records your email platform generates, publish a DMARC policy (start in monitoring mode so you can see who's failing before you enforce), and check that your From address domain matches the domain you authenticated. The DMARC.org project maintains the reference documentation, and every major email platform walks you through setup. An afternoon of DNS work removes an entire class of invisible failure.
While you're at it, register with the providers' postmaster tools — Google Postmaster Tools is the one that shows your domain reputation as Gmail sees it. Most senders have never logged in; it's the dashboard that explains half of your "why did opens drop?" mysteries.
Layer two: sender reputation — your credit score for email
Mailbox providers keep a per-domain (and per-IP) reputation built from everything you've ever sent: how often recipients mark you as spam, how many bounce, whether authentication passes, and — increasingly dominant — how recipients engage. Like a credit score, it accumulates slowly, drops fast, and follows you around.
The behaviors that damage it are specific and avoidable: sudden volume spikes (mailing five times your normal rate, especially with a cold list — this is why "we're back after a six-month hiatus!" blasts crater deliverability), high bounce rates from stale addresses, spam complaints above the small fractions providers tolerate, and purchased or scraped lists, which violate the terms of every legitimate platform and every FTC rule against misleading mail. If your sending has been messy for years, expect recovery to take weeks-to-months of clean behavior — reputation systems are built to be slow to forgive, because that's what makes them meaningful.
Layer three: engagement — the layer you influence every send
Here's the uncomfortable truth: authentication is a floor, reputation is a history, but engagement is the live vote, and the voters don't vote often. Do people open, reply, move you to primary, or — the strongest signal of all — fish you out of spam and read you anyway? Versus: ignore you for months, delete without opening, or unsubscribe at volume.
This is why deliverability is really an editorial problem wearing a technical costume. The sender whose welcome sequence gets replies has a structural deliverability advantage over the sender with identical infrastructure and nothing worth answering. It's also why the dead-subscriber cleanup we describe in how to grow an email list is a deliverability tactic, not just a vanity-metrics one: continuing to mail people who ignore you is the single clearest way to tell providers that your mail is unwanted.
Practically: send at a cadence you can sustain with content worth opening, make replies easy (ask questions, answer them), segment so people mostly get mail relevant to them, and re-engage or suppress the disengaged before your next big campaign — a smaller, warmer send converts better and protects the reputation your next send needs.
Layer four: list hygiene — the quiet compounding factor
Every dead address is a liability with a countdown: addresses that stop existing turn into hard bounces, addresses that stop caring turn into reputation drag, and addresses that were never real (the typo'd and fake ones people type into forms) were never going to open anything. The hygiene routine that prevents all three: double-check for obvious typos at the moment of signup (a confirmation email does this and verifies real interest), suppress hard bounces immediately, and run the annual re-engagement pass described in the list-growth guide — one honest "still want to hear from us?" email, then suppress the silence.
Diagnosing an actual problem
If opens have dropped, check in this order: Postmaster Tools for a domain-reputation dip (external cause — your history), then authentication (check-all-three; platforms break silently when you connect a new tool that sends "from" your domain without SPF/DKIM), then your last few sends (did cadence, content, or list change?), then list engagement (how much of your list hasn't opened in 90 days?). The order matters because the layers fail in that order.
The honest summary: deliverability is earned infrastructure. The technical layer is a weekend; the behavioral layer is a practice — sustainable cadence, content worth reading, and a list you keep honest. That's the same shape as every other durable system in business, which is exactly why our method builds it as daily actions rather than quarterly firefighting. The 28-day email marketing challenge runs deliverability week that way, and the free first chapter shows the format first.
The deliverability checklist you can run this afternoon
If you suspect a problem, work this top to bottom — the checks are ordered by how often each one is the culprit. One: confirm all three authentication records exist and pass — your email platform has a dedicated diagnostic page for this, and you want green checkmarks on SPF, DKIM, and DMARC, not just "no errors." Two: log into Google Postmaster Tools and look at domain reputation over 90 days; a dip usually coincides with a specific send you'll recognize on sight. Three: look up your last campaign's spam-complaint and bounce rates in your platform — small fractions are tolerated, and the tolerance is genuinely small. Four: mail yourself at Gmail, Outlook, and Yahoo, and look not just at the folder but at the From name, the images, and the links as a skeptical recipient would. Five: count what fraction of your list hasn't opened anything in 90 days — above roughly a third, and the cleanup described in the list-growth guide is no longer optional hygiene; it's your deliverability repair.
The whole checklist takes an hour the first time and twenty minutes ever after. Book it monthly and deliverability stops being a mystery that happens to you — it becomes a system with a dashboard, which is the only kind of system that stays fixed.
If you're starting a brand-new list
New senders get one reputation: blank. Spend the first month earning a gentle one — authenticate immediately, keep daily volume low, mail only the people who knowingly signed up, and let the engagement curve build before your first big campaign. Providers treat steady, modest, well-received sending as the sign of a legitimate sender; they treat day-one volume from an unauthenticated domain as the opposite, and first impressions in mailbox filtering, like most first impressions, are slow to revise.


















