AWeber placement testing with seed addresses.

AWeber has been in the email business since 1998. Their shared IP pool is one of the longest-standing in the industry and their reputation management is consistently good. For small businesses, solopreneurs and bloggers, AWeber just works — right up until the day the shared pool catches a bad neighbour and your Tuesday broadcast lands in Promotions for the first time in a year. Seed addresses are how you notice before your open rate does.

AWeber's shared IP pool and what moves it

AWeber sends from a shared IP pool that it has curated for decades. New accounts warm into the pool gradually; existing accounts benefit from the pool's age. The pool has a pretty strong baseline reputation at Gmail, Outlook and Yahoo. But a shared pool is still a shared pool. The things that shift it are outside your control:

• A high-volume sender on the pool gets a complaint spike — a customer segment misinterpreted a promo, clicked Spam in bulk.
• A shared-pool sender gets a domain blacklist hit that drags the IP reputation adjacent.
• Gmail rolls out a classifier update that penalises a pattern present across many pool senders.
• A shared-pool sender pushes a spam-trap-heavy list and the pool takes collateral damage.

You cannot do anything about any of this. AWeber's deliverability team does, and they are good at it, but the correction takes hours or days. Seeds are how you know sooner than your real-list open rate will.

Adding seeds as AWeber subscribers

AWeber calls everything a list. Subscribers live on lists, broadcasts go out to lists, automations trigger off list membership. Seed setup is a one-time operation.

1. Generate seed addresses. Use the free placement tool. 20+ fresh seeds spanning Gmail, Outlook, Yahoo, Fastmail, ProtonMail, Mail.ru, Yandex.
2. Create a list. In AWeber, My Lists → Create a List. Call it seeds. Use your real sending identity — same From name, From address, reply-to — so the seed test measures the same authentication as your real sends.
3. Disable confirmed opt-in. AWeber defaults to double opt-in. For the seeds list, disable it — you are importing your own monitored mailboxes, they are not signing up.
4. Add seeds as subscribers. Use the AWeber import tool. Paste the CSV. AWeber imports as Subscribed. Assign a custom tag seed.
5. Exclude seeds from real broadcasts. When broadcasting to real lists, if any seeds accidentally exist on those lists (they should not, because you put them on a separate list), filter by tag is not seed.

The per-broadcast seed workflow

1. Write the real broadcast. Target your real list, write subject, preheader, content. Save as draft. Do not send.
2. Duplicate. Use AWeber's Copy Broadcast feature. Rename to [SEED] <subject>. Switch the target list to seeds.
3. Schedule the seed broadcast 10 minutes before the real one. Short enough that pool conditions stay the same, long enough to read results and decide.
4. Read placement. Refresh the placement tool result page. Gmail / Outlook / Yahoo results come in fastest, Mail.ru / Yandex can lag 3–5 minutes.
5. Ship or pause. Green at the providers that cover your real audience? Let the real broadcast go. Red? Cancel the scheduled real broadcast, fix, reseed.

Reading shared-IP reputation shifts in seeds

The power of weekly seed-testing on AWeber is not per-broadcast — it is the week-over-week trend. Keep a simple spreadsheet: date, subject, Gmail placement, Outlook placement, Yahoo placement, content type (broadcast vs autoresponder, promotional vs content).

Over eight weeks you will see baseline noise: a few percent bouncing around Primary / Promotions at Gmail, steady Inbox at Outlook, steady Inbox at Yahoo. When the pool reputation drifts, you see a sudden jump — say, Gmail Primary drops from 72% to 31% for your regular content broadcast with identical template and subject format. That is the shared-pool signal. It is not your fault, there is nothing to fix on your end, and it usually recovers within 48–72 hours as AWeber's deliverability team responds.

But knowing it happened, and when it recovered, is operationally useful: you can delay the promotional send to Thursday, you can explain to your client why Tuesday's open rate was down, and you can track whether it is becoming a pattern (it usually is not).

Authentication on AWeber

AWeber supports custom authentication — DKIM under your own domain, custom return-path for SPF alignment. The setup is in Account Settings → Authentication and takes a few DNS CNAME records.

On AWeber specifically, the custom DKIM setup is more impactful than on some newer ESPs because the shared pool is older and carries more legacy signal. Seeds confirm it: seed before you configure custom DKIM, seed again 48 hours after the DNS has settled. The Outlook Junk-to-Inbox delta is usually the clearest improvement.

Frequently asked questions