What Publishers Traded When They Moved to Email

The newsletter pivot promised ownership. The fine print was harder to read.

Between 2015 and 2020, a generation of writers and editors moved their core publishing work from the open web into inboxes. The instigation was real: platform algorithms had made social referral traffic unpredictable, Google Reader's shutdown on 1 July 2013 had quietly thinned the feed-reading audience, and the advertising economy was concentrating inside Facebook and Google rather than distributing outward to publishers. Email felt like the answer — a direct channel, a list you owned, a relationship no algorithm could reprice overnight. The pivot was rational. It was also a trade, and most of the things surrendered were invisible at the point of sale.

What the inbox cannot do

The first and least-discussed cost is linkability. An article published on the web has a URL. That URL can be cited, archived, quoted in academic papers, indexed by search engines, and discovered by readers three years after publication. A newsletter sent to forty thousand inboxes has none of that, unless the publisher separately maintains a web archive — which most do not, or do imperfectly, or do on the Substack or Mailchimp domain rather than their own. The content exists in forty thousand local copies and nowhere retrievable by anyone who was not already subscribed at the moment of sending.

Search indexing is the corollary problem. An essay distributed purely by email generates no PageRank signal, attracts no organic search traffic, and accumulates no inbound links because no one outside the subscriber list can find it to link to it. The writer earns an audience through the list and only through the list. Growth becomes a function of word-of-mouth forwarding and platform-specific recommendation systems — Substack's own discovery feed, beehiiv's referral mechanics, Ghost's member-referral tooling — rather than the open web's ambient, compounding discoverability. A well-crafted RSS feed, by contrast, surfaces content to aggregators, to search crawlers, and to any reader that performs feed autodiscovery from a site's HTML. The newsletter pivot did not merely change the distribution channel; it eliminated an entire category of how new readers find work.

The subscriber list itself, so often described as the publisher's primary asset, carries a structural opacity that the feed audience never had. A feed subscription is a pull request: the reader's reader polls the publisher's endpoint, and the relationship is mediated by an open protocol. The publisher knows how many items were fetched; the subscriber knows exactly what they subscribed to and can cancel it by deleting an OPML entry. Email is asymmetric. The platform — Substack, Mailchimp, beehiiv, Buttondown — mediates the relationship, stores the list, processes delivery, and determines what the publisher can and cannot see about their audience's behaviour. Even where the publisher can export that list, the export is a snapshot; the platform retains the engagement history, the segmentation intelligence, and in many cases the deliverability infrastructure. "Owning your list" means owning a CSV of addresses, not the full relationship those addresses represent.

The open-rate illusion

Then there is measurement — and here the email pivot's metrics tell a story that grew more complicated over time. Open rates were email's killer feature against RSS, where engagement tracking was always thin. A feed reader fetching a conditional GET from a server reveals almost nothing about whether a human read the content. Email's tracking pixel, by contrast, could tell a publisher roughly how many subscribers opened each issue, when, and on what device. That data shaped editorial decisions, revenue pitches to sponsors, and valuations for acquisition conversations.

Apple Mail Privacy Protection, which Apple deployed in iOS 15 and macOS Monterey in September 2021, dismantled this measurement apparatus by pre-fetching tracking pixels before a user opens a message, masking IP addresses, and logging opens against Apple's proxy servers rather than the sender's. The effect was immediate and severe: open rates for lists with significant Apple Mail audiences inflated to figures that no longer corresponded to actual human opens. Publishers who had built their sponsor rate cards around open-rate benchmarks suddenly held data they could not defend. The metric email had over RSS turned out to be fragile in exactly the way feed-based reach was always fragile — it was a proxy, not a count.

Specifications are argued over in rooms like this one. Atom's took a working group two years; RSS 2.0's had a single author and a closing date.Photo: Kindel Media / Pexels

Deliverability introduced a second layer of opacity. An RSS feed either serves or does not serve; the protocol has no concept of a spam folder. Email delivery passes through filters operated by Google, Microsoft, Apple, and every corporate mail server an enterprise subscriber happens to use. A publisher can conform to DMARC, SPF, and DKIM authentication standards and still find that a particular ISP's heuristics are quietly binning thirty percent of sends. Deliverability is a specialised discipline with its own consultants, and the bill for getting it wrong is paid silently — not in bounce notices but in sends that simply never arrive.

The revenue argument, and its limits

None of this negates the real gains. Direct subscription revenue — the paid tier model that Substack popularised at scale after its 2017 founding and that Ghost, beehiiv, and others refined — delivered something RSS never plausibly offered: a clean, publisher-controlled payment relationship with readers. Affiliate links and sponsorships had always existed in feed-based publishing, but the infrastructure for recurring reader revenue at the individual-creator level was absent from the feed world. Email's intimacy — the sense that a newsletter arrives rather than waits — also correlates with higher willingness to pay. These are genuine structural advantages, not marketing copy.

Deliverability is a specialised discipline with its own consultants, and the bill for getting it wrong is paid silently — not in bounce notices but in sends that simply never arrive.

The risk is in what gets built on top of them. A newsletter operation that grows its paid list to twenty thousand subscribers and builds its editorial calendar, its revenue projections, and its brand identity entirely inside an email service has made a platform bet that looks like ownership but functions like tenancy. When Mailchimp restructured its free tier in 2019, moving from a contact-based model to an audience-based one that changed the pricing calculus for smaller publishers, the affected operators had no recourse. When Twitter reduced the referral traffic that drove newsletter signups, the acquisition engine for those same operators suffered in ways they had not budgeted for. The parallel in the RSS world — feed readers going dark, aggregators changing their ranking logic — existed too, but the protocol layer itself remained neutral ground nobody could reprice.

What the trade actually was

The pivot from feed-based publishing to email was not a move from an open system to a closed one, because the feed world was never as fully open in practice as it was in specification. It was a move from one set of trade-offs to a different, less legible set. The open web offered linkability, indexability, and protocol-level portability at the cost of thin engagement data and no native revenue path. Email offered intimacy, measurable attention, and a payment infrastructure at the cost of search invisibility, measurement fragility, and platform dependency dressed up as independence.

The IndieWeb's POSSE principle — publish on the canonical domain first, syndicate everywhere second — captures what the migration wave mostly skipped: the discipline of treating the open URL as primary and the inbox as one of several distribution channels. Publishers who kept the web archive current, maintained a full-text RSS feed alongside the email send, and built their subscriber lists against their own domain rather than a platform subdomain retained most of the gains and shed most of the costs. They were, in the 2015–2020 moment, a minority. Whether they remain one is the interesting question for the next decade.