What is seed list testing for inbox placement?

Before you send a campaign to your real list, wouldn't it be nice to know whether it would actually land in the inbox? That's exactly what seed list testing is for.

Seed list testing means sending your email to a set of monitored test addresses (the "seeds") that are spread across the major mailbox providers. You send your campaign to these seeds the same way you'd send to real subscribers. Then the testing service checks each mailbox and reports back where your message landed: inbox, spam folder, or blocked entirely.

Services like GlockApps and Validity Everest (formerly 250ok) maintain seed lists across Gmail, Outlook, Yahoo Mail, and dozens of other providers including corporate mail environments. The result is a placement breakdown by mailbox provider, usually shown as a percentage. Inbox at Gmail: 94%. Spam at Outlook: 8%. That kind of thing.

Here's what a typical test run looks like in practice:

1. You set up your campaign as normal in your sending platform.
2. You add the seed addresses to your send list (the service provides these).
3. You send a test version or your actual campaign to that combined list.
4. Within a few minutes to a couple of hours, the service reports where each seed message landed across each provider.

As a rough benchmark, an overall inbox placement rate above 90% is generally considered healthy. Between 80% and 90% is a signal worth investigating. Below 80% and you have a real problem to solve before sending to your full list.

That said, seed testing has a real limitation worth knowing about. Seed addresses don't have the engagement history of your actual subscribers. They've never opened your emails, never clicked, never replied. Mailbox providers like Gmail weigh per-user engagement heavily when filtering, so a seed result is more of a directional read than a perfect prediction. If your real subscribers actively engage with your emails, your actual placement could be better than the test shows. If they're mostly disengaged, it could be worse.

Think of seed testing as a pre-flight check. It won't catch every issue, but it will catch the obvious ones: authentication failures, blocklist hits, content flags. That's worth knowing before you pull the trigger on a big send.

If you want to go deeper on reading what the results actually mean, the next step is learning how to interpret those placement reports. And if you're curious how seed testing differs from a plain spam score check, that's a useful distinction to understand too.