Most agencies selling you email services are selling you content calendars and design templates. They're building your flows, crafting your subject lines, and obsessing over your copy. They're not touching your email infrastructure.
Here's the problem: an email deliverability audit is a systematic process of evaluating all of the elements of your email marketing program, and most agencies skip the technical layer entirely. They'll spend weeks on your welcome email sequence while your domain reputation craters because nobody set up SPF, DKIM, and DMARC correctly.
If you're talking deliverability, none of that means anything unless you're focusing at the domain level. Your beautifully crafted emails land in spam because of what happens in the 200 milliseconds between you hitting "send" and your subscriber's inbox deciding where to route it.
This checklist exists because your Klaviyo deliverability best practices could be perfect. Your email inbox placement checklist could be comprehensive. But if your DNS records are misconfigured and your sender reputation is tanked, nobody's reading a single word.
The Dirty Secret About Agency-Delivered Email Programs
Your email infrastructure setup only matters if you're asking the right questions. According to r/Emailmarketing ↗, "if you're talking deliverability, none of that means anything unless you're focusing at the domain level." Most agencies audit open rates and click rates. They skip the foundation. And if your domain reputation is trash, your emails go to spam, no matter how good your copy is.
Email infrastructure is the set of software and hardware components that are triggered as soon as you write an email and hit the send button. This is where your deliverability lives or dies. Technical infrastructure decisions like choosing email service providers directly affect sender reputation, your subject lines don't matter if your emails never reach the inbox.
The agencies selling you email services are selling you content calendars and design templates. They're building your flows, crafting your subject lines, and obsessing over your copy. But they won't spend ten minutes on your DNS records. That's not a strategy. That's an email deliverability audit waiting to fail.
The Domain-Level Truth That Changes Everything
Here's where most Shopify brands get wrecked. They're running one domain for everything, sending, tracking, and replies. That's not a strategy. That's a disaster.
Separating your sending domain from your tracking domain prevents reputation contamination when one gets flagged. You send transactional and marketing emails from send.yourbrand.com. You track opens and clicks with track.yourbrand.com. When one gets blacklisted, the other survives. This is basic email inbox placement checklist hygiene that most agencies ignore because they don't want to explain DNS records.
Set up SPF, DKIM, and DMARC correctly. Without these, your emails look like spam to every major inbox provider.
Your from-address domain affects how ESPs score you. Use Google Workspace for all mailboxes, don't use cheaper alternatives that have worse reputation. Cheaper email providers have garbage sender scores. Gmail and Yahoo notice. Your deliverability tanks, your revenue drops, and you spend months trying to fix damage you could have prevented by spending $6/month on the right infrastructure.
SPF, DKIM, and DMARC: The Authentication Trifecta You Can't Ignore
What SPF actually does (and common misconfigurations)
SPF (Sender Policy Framework) tells receiving mail servers which servers are allowed to send email on your domain's behalf. When you set up SPF, you're creating a DNS record that lists every server authorized to touch your outbound email, from your primary sending platform to any auxiliary tools.
The problem: most agencies configure SPF once at launch and never touch it again. Then you add Klaviyo, or a SMS tool, or a review platform, and each one adds another server to the list. Duplicate mechanisms break SPF. Too many lookups exceed the 10-lookup limit and everything fails silently.
Your email deliverability audit should verify that your SPF record has zero duplicate mechanisms and that every server listed actually needs to be there.
DKIM: Why Digital Signatures Matter for Inbox Placement
DKIM adds a cryptographic signature to your emails. It's a digital tamper-proof seal, receiving servers verify the signature against your public key in DNS and know the email wasn't modified in transit.
Without DKIM, your emails look unsigned and anonymous to receiving servers. With it, your domain has a verifiable identity. This is core to any proper email infrastructure setup, yet it's the step most generalist agencies skip when they "set up" your Klaviyo account.
DMARC: The Policy That Tells ISPs How to Handle Your Unauthenticated Emails
DMARC is where most DTC brands get it wrong. This protocol tells receiving servers what to do when an email fails authentication, meaning it didn't come from your authorized SPF servers or didn't have your DKIM signature.
Most brands set DMARC to p=none, which tells servers "do nothing." That's not protecting your domain. You need either p=quarantine (send failures to spam) or p=reject (block them entirely).
You need to set up SPF, DKIM, and DMARC correctly, and that last one actually requires a real policy. Switch to p=quarantine or p=reject and you'll see the difference in your email inbox placement checklist within 30 days.
The Klaviyo (and ESP) Configuration Mistakes Killing Your Deliverability
Most agencies set up your ESP the same way they set up everyone's ESP. Default configurations. Generic DKIM signatures. And then they wonder why your emails land in spam.
When you migrate ESPs, whether from Klaviyo to another platform or vice versa, you risk breaking your authentication chain. ESP migrations impact data, workflows, and deliverability, and moving platforms without proper authentication setup is a deliverability disaster waiting to happen.
Default ESP-provided DKIM signatures share reputation with thousands of other senders. Custom DKIM signatures give you full control over your domain reputation. You're building equity in your own domain, not renting space in someone else's.
Set up SPF, DKIM, and DMARC correctly, and focus at the domain level, because if you're talking deliverability, none of that means anything unless you're focusing at the domain level.
Warm-up Sequences for New Sending Domains
Never send to your full list on day one. Start with 500–1,000 highly engaged subscribers. Gradually increase volume over 4–6 weeks while monitoring your inbox placement.
Volume Ramping Strategies That Don't Trigger Spam Filters
Sudden volume spikes signal spam behavior to ISPs, your email infrastructure audit must include a ramping protocol for new domains. Scale in increments of 20–30% weekly. If open rates dip, slow down. ISPs are watching.
Your Inbox Placement Checklist: What to Audit Right Now
DNS Record Verification (TXT, MX, SPF, DKIM, DMARC)
Your email infrastructure setup isn't just about content, it's about authentication. Set up SPF, DKIM, and DMARC correctly to establish domain credibility with inbox providers. If you're talking deliverability, none of that means anything unless you're focusing at the domain level.
DNS propagation takes 24-72 hours, so any changes require re-verification before testing outcomes.
List Hygiene and Engagement Thresholds
Inactive subscribers erode your sender reputation over time. Engagement-based filtering means subscribers who haven't interacted with your emails in 60-90 days signal to providers that your content lacks value. Your email inbox placement checklist must include recency thresholds and automated suppression rules.
ISP-Level Inbox Placement Testing
An email deliverability audit is a systematic process of evaluating all of the elements of your email marketing program, including where your emails actually land with Gmail, Outlook, and business domains. You can't fix what you can't measure.
Run placement tests across major ISPs before sending anything mission-critical.
What Most Agencies Get Wrong (And What to Demand Instead)
Most agencies deliver aesthetic audits, design, copy, send frequency. They hand you a report with prettier templates and call it done. But here's what they skip: your email infrastructure setup determines whether your messages land in the inbox at all.
An email deliverability audit isn't a one-time setup, it requires periodic verification as DNS records shift and ISP policies evolve. According to r/Emailmarketing ↗, if you're talking deliverability, none of that means anything unless you're focusing at the domain level.
The Checklist Question Most Agencies Can't Answer
Ask your agency this: "Show me your DNS records and authentication status." If they can't pull it up in two minutes, they haven't touched your infrastructure. Real email inbox placement checklist work means checking SPF, DKIM, and DMARC setup. That's the baseline.
How to Verify Your Setup Without Trusting Their Word
You don't have to. Free tools exist, MXToolbox, Google Postmaster Tools. Any agency worth your money teaches you to read them yourself.
Fix Your Infrastructure, Then Scale Your Revenue
Your emails can't generate revenue if nobody receives them. Brands with strong email revenue didn't just write better subject lines. They built technical systems that actually let their content land in the inbox.
A proper email deliverability audit isn't optional maintenance, it's the foundation everything else depends on. Your Klaviyo deliverability best practices mean nothing if your emails are hitting spam. Get the infrastructure right first, then scale your revenue.
Run this audit today:
- Check your DNS records
- Verify SPF, DKIM, and DMARC authentication
- Separate your sending domains from your primary domain
- Ramp volume gradually
Need someone to walk you through it? Book a quick strategy call and we'll show you exactly what's broken, then fix it.
