Deliverability testing guide
Test the send path before you increase volume.
Use a focused deliverability testing workflow that checks authentication, message risk, inbox placement, and monitoring without turning review into a maze.
Folderly guide
Clear decisions before volume.
Use this as a practical planning checklist. Keep the message useful, keep the setup verifiable, and avoid adding complexity before the sending path is ready.
4
checks before send
1
risk log
0
volume guesses
Overview
Deliverability testing should find the blocker, not create another dashboard.
Start with authentication, then review content, links, sender reputation, and inbox placement. Treat testing as a decision point: fix the send path, narrow the audience, or keep volume low.
Verify authentication
Confirm SPF, DKIM, and DMARC alignment before judging copy or campaign performance.
Review message risk
Look for spam-like wording, link density, misleading subjects, and weak unsubscribe handling.
Check inbox placement
Use test sends or seed checks to see whether the message reaches primary inbox, promotions, or spam.
Watch the sender
Track bounces, complaints, reply quality, and reputation changes before adding volume.
Workflow
Keep the review sequence short.
Step 1
Test setup first
Check DNS authentication, sending domain alignment, tracking links, and unsubscribe paths.
Step 2
Send a controlled sample
Use a small test group or seed list to inspect placement and rendering before campaign launch.
Step 3
Record the fix
Log the issue, owner, and next action so testing produces a decision instead of repeated checks.
Pre-send deliverability testing checklist
What should I test before a cold email campaign?
Check authentication, message wording, links, unsubscribe handling, sender reputation, and inbox placement before increasing volume.
Can deliverability testing ensure inbox placement?
No. Testing reduces uncertainty and surfaces likely blockers, but inbox placement still depends on sender history, recipient behavior, and provider filtering.
When should I retest deliverability?
Retest after DNS changes, new domains, large copy changes, list changes, sudden bounce increases, or any unexplained drop in replies.