Every ESP puts unsubscribe links somewhere different—here's why
The cursor hovers over a tiny grey link at the bottom of an email, half-hidden between the footer and a physical address rendered in six-point sans-serif. That link’s placement wasn’t an accident—it’s a calculated bet on spam filters, reader behaviour, and compliance risk.
Where your ESP puts the unsubscribe link changes how readers and filters respond
Every platform defaults to a different location—and each one signals something distinct to inbox algorithms.
Substack positions unsubscribe links below the content but above footer metadata. Beehiiv embeds them inside a styled footer module. Kit places them as text-only links at the very bottom. ConvertKit mirrors Kit’s approach. Mailchimp buries them in a greyed-out footer block that’s easy to overlook. Each choice trades visibility against complaint rates, and none of them publishes why they picked that spot.
Spam filters from Gmail, Outlook, and Yahoo don’t just check for the presence of an unsubscribe mechanism—they measure how easily a human can find it. A link hidden in footer clutter raises suspicion. A prominent one signals transparency. But operators optimising for retention sometimes want the link less visible, banking on reader inertia. That tension—between deliverability, compliance, and churn—explains why platforms differ so wildly. The article below breaks down what each major ESP does, how List-Unsubscribe headers interact with footer links, and what complaint-rate thresholds actually trigger domain penalties.
TACTIC
When spam complaints stack up faster than you think
Most operators assume a handful of complaints won’t matter. But inbox providers calculate complaint rates as a percentage of delivered mail—and a tenth of one percent is enough to flag your entire domain. Gmail and Yahoo both enforce thresholds that treat 0.1% as a warning zone and 0.3% as grounds for bulk-folder routing or blocks. If you’re sending 10,000 emails a week, ten complaints can push you over the line. The math is unforgiving, and most ESPs won’t warn you until damage is done.
FROM THE ARCHIVE
How Beehiiv’s ad network decides who gets approved
Applying to the Beehiiv Ad Network isn’t automatic—editors review your content, subscriber count, engagement patterns, and niche before approving. The process takes anywhere from a few days to three weeks, and there’s no published minimum threshold. Operators report being approved with as few as 2,500 subscribers and rejected with 15,000, depending on category and open rates. If you’re planning to monetise through Beehiiv’s ads, timeline expectations and content positioning matter more than raw list size.
WORTH READING
Why caching speeds WordPress up—until you flush it mid-traffic
WordPress object caching stores database query results in memory so repeat requests don’t hammer MySQL. It’s fast, effective, and invisible until you purge the cache during peak hours—then every visitor triggers fresh queries, CPU spikes, and page-load delays pile up. Most managed hosts enable object caching by default and handle purges gracefully, but self-hosted setups using Redis or Memcached need careful timing. Flushing cache after deploying a plugin update or changing a template can turn a performance win into a ten-minute slowdown.
Know someone who would like this? Forward today’s email—every operator we reach is one closer to running an online business with a little less friction.