Email Message Testing: 7 Checks to Run Before Your Next Campaign Goes Out
By SendBridge Team · Published Oct 22, 2026 · 6 min read · Marketing
The email is written, the segment is loaded, and the send button is one click away. Nobody outside the team has read it, and a sent email cannot be recalled.
Email message testing is the set of checks that show whether an email will be understood, display correctly, reach the inbox, and earn a click before it goes to your list. The seven checks below take a few hours in total. They catch problems a subject line A/B test never will, such as an unclear offer or a missing unsubscribe header.
1. Can a cold reader state the offer in five seconds?
A reader who has never seen the email should be able to say what is being offered and what to do next after five seconds of skimming. Ask three people outside your team to look at the email for five seconds, hide it, and answer those two questions. Wrong or hesitant answers point to the sentence that needs rewriting. Internal reviewers cannot run this test, because they already know the product.
When outside readers are hard to find, a message testing platform can run the same test on a simulated audience matched to your segment. Articos is one such tool. The company reports that its method recovered 86% of the themes in published expert findings across 46 studies, a benchmark it ran itself. Treat the output as a hypothesis, and send high-stakes messages past a few real customers as well.
2. Does the subject line survive truncation?
A subject line has to make sense in the shortest preview an inbox will show. One guide lists default display limits of 70 characters in Gmail, 46 in Yahoo Mail, 54 to 73 in Outlook, and 41 to 64 on iPhone. Put the word that carries the meaning inside the first 40 characters.
The preheader is the second line of the preview, and it should finish the thought the subject line started. A preheader that repeats the subject wastes the space, and one left empty lets the client pull in whatever text comes first, often "View in browser." Send a test to your own phone and read both lines together as a subscriber would.
3. Does the email ask for one thing?
An email works best when it asks for one action. Highlight every sentence that tells the reader to do something, then count the distinct actions. Two competing asks, such as "book a demo" and "read the report," split attention and muddy the results.
Check the button text too. "Book the audit" tells the reader what happens after the click, while "Click here" tells them nothing. If the email has a secondary link, make it visibly quieter than the primary button, or move it to the footer.
4. Does the copy fit the segment receiving it?
Segment fit means the email speaks to the problem the receiving group actually has. Read the draft as the least informed person on the list and write down the first objection that comes to mind. If the email does not answer it, either the copy or the segment is wrong.
Personalization needs its own check. Send the email to a seed account with every merge field blank. A greeting that reads "Hi ," or a sentence with a hole in it is easy to catch now and embarrassing to catch after 20,000 sends. Set a fallback value for each field before launch.
5. Does the email render and link correctly?
Rendering problems appear only on devices you test. Send the email to seed accounts in Gmail, Outlook, and Apple Mail on a phone. View it with images off, in dark mode, and in the plain-text version, since clients differ in how they handle each.
Then click every link. Confirm each one lands on the right page, carries the right tracking parameters, and loads on mobile. Test the unsubscribe link last, since a broken one is also a compliance problem, which the next check covers.
6. Will the email pass the Gmail and Yahoo sender rules?
Senders who reach more than 5,000 Gmail addresses a day must meet Google's bulk sender requirements: authenticate with SPF, DKIM, and DMARC, support one-click unsubscribe, and keep the spam rate in Postmaster Tools below 0.30%, with Google advising senders to aim for under 0.10%. Google allows the DMARC policy to be set to none.
Yahoo asks bulk senders for SPF and DKIM, a DMARC policy of at least p=none, a one-click unsubscribe header, and a spam complaint rate below 0.3%. It also expects unsubscribes to be honored within 2 days. Before sending, confirm that authentication passes and that the unsubscribe header works. Smaller senders fall below the volume threshold, but the same hygiene protects their reputation.
7. Which metric will pick the winner, and does the list support the test?
Decide the success metric before the send, and choose one that holds up. Apple's Mail Privacy Protection inflates open counts. In 2022, SparkPost reported that unique opens rose about 12 percentage points for most senders after the change, and its engineers called individual opens unsafe as a trigger. Clicks and conversions are steadier measures.
List size sets what a test can detect. Using a standard two-proportion calculation at 95% confidence and 80% power, a click rate moving from 3% to 4% needs about 5,300 recipients per variant, and a move from 2% to 2.3% needs about 36,700. A list of 20,000 split in half gives 10,000 per variant, which is enough for the first test and far short of the second. Small lists should test large differences, such as a different offer, and fix the sample size before sending to avoid stopping early.
How do the seven checks fit together?
The checks differ in what they catch and in how long they take, so most teams run them in a fixed order.
| Check | What it catches | How to run it | Time |
|---|---|---|---|
| 1. Five-second read | Unclear offer | Three outside readers or a simulated audience | 15 to 30 minutes |
| 2. Subject and preheader | Truncation, repeated text | Preview on phone and desktop | 10 minutes |
| 3. Single ask | Competing actions | Highlight every call to action | 10 minutes |
| 4. Segment fit | Wrong objection, broken merge fields | Blank-field seed send | 20 minutes |
| 5. Render and links | Layout and link errors | Seed accounts, images off, dark mode | 30 minutes |
| 6. Sender rules | Authentication and unsubscribe failures | Header and Postmaster Tools check | 15 minutes |
| 7. Metric and sample size | Underpowered test, misleading opens | Calculator before the send | 15 minutes |
Time estimates are the author's rough figures for one email.
What can pre-send testing not tell you?
Pre-send testing cannot predict your open rate, click rate, or revenue, and simulated audiences cannot verify rendering or inbox placement. They also cannot judge claims that need legal review, such as pricing terms or regulated statements. Human readers remain the benchmark for anything high stakes.
The aim is narrower: remove the avoidable mistakes so that your live results reflect the message and not a typo, a broken link, or a confusing offer. Keep a record of what each check found, and the list gets shorter and sharper after every send.