Most newsletters stack six header links—readers ignore half
The coffee shop on Eighth Avenue has three chalkboards behind the counter, each listing a dozen options in pastel cursive. Most customers squint for five seconds, then order an Americano. Choice proliferates until it paralyses.
Most newsletters stack six header links—readers ignore half of them
Data shows header links behave nothing like body links, and placement decides whether anyone clicks at all.
Most newsletter templates ship with a header navigation bar, and most operators fill every slot: About, Archive, Subscribe, Advertise, Shop, Support. The assumption is that more options mean better service. The data tells a different story. Header links earn dramatically lower click-through rates than in-body links—often ten times lower—and once you exceed four or five links, engagement drops sharply for everything past the third position.
The difference comes down to intent. Readers arrive at your email to consume the issue in front of them, not to browse a directory. Header links work best when they anticipate a narrow set of high-intent actions: unsubscribe, update preferences, visit your main archive. Anything else competes for attention without earning it. Placement matters, too. Left-aligned links outperform centred navigation, and the first two positions capture the majority of clicks. If you’re carrying seven links in your header today, you’re training readers to ignore the entire row.
The piece below breaks down click behaviour by position, compares header and body link performance, and offers a framework for deciding which links belong above the fold and which belong nowhere at all.
TACTIC
Your archive search is invisible—here’s what each platform actually offers
Most readers who want to find an old issue will search your archive before they email you. Most newsletter platforms make that impossible. Substack buries search behind two clicks and indexes only titles. Beehiiv offers full-text search but hides it on mobile. Ghost requires a third-party plugin. If you’ve published two years of content and nobody can find it, you’re losing referral traffic, backlink opportunities, and repeat visits. The breakdown below maps what each platform provides, where search sits, and how to patch the gaps when native tooling fails.
READER QUESTION
What to measure when privacy features block your open-rate pixel
Mail Privacy Protection pre-loads images, so your email platform reports opens that never happened. Readers on Apple Mail, Hey, and Proton all trigger false positives. Open rates used to tell you whether your subject line worked; now they tell you which inbox providers your subscribers use. The article below walks through three alternative signals—click rate, reply rate, and list churn—that privacy tools can’t fake, and explains how to weight each one when you’re deciding whether to keep or kill a content experiment.
FROM THE ARCHIVE
Where WordPress REST API rate limits actually live
Core WordPress doesn’t throttle API requests—but your host does, your firewall does, and half a dozen plugins do. If you’re running headless WordPress, syncing content to a mobile app, or triggering automations via REST API, you’ll eventually hit a wall you didn’t know existed. The symptoms look identical—429 responses, silent failures, partial syncs—but the fix depends entirely on which layer is doing the throttling. The guide below maps every common choke point, explains how to identify which one is blocking you, and shows when raising the limit is safe versus when it invites abuse.
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.