Publications are leaving Substack, Ghost, and Beehiiv to run newsletters on their own infrastructure. The reason comes down to one thing: SEO control. When your newsletter lives on a third-party platform, you do not control the sitemap, canonical tags, or URL structure. Search engines index your content on someone else's domain, and that limits your ability to build domain authority over time.

Why Substack Became a Problem

For publications trying to fix search indexation, a platform you cannot configure becomes the first thing to replace. Substack is a black box: you cannot control the sitemap, you cannot set real lastmod dates, and the URL lives on a domain that is not yours. When you are trying to eliminate variables in your SEO strategy, a platform you cannot configure is usually the first candidate for replacement.

The newsletter and the blog become the same thing, on your own domain, where you own every header and every tag. Publications that have made the switch report that organic search traffic to their newsletter content starts growing within weeks of migration. The technical signals that search engines care about become controllable again.

The cost of staying on a platform is hidden. You lose the ability to optimize your meta tags, you cannot add structured data for rich results, and you depend on a third party for any technical improvements to how your content appears in search results. Every month you stay on a platform you do not control is a month you are not building equity in your own infrastructure.

The Setup: Same Stack as Your Blog

Many publications now use Astro, a static site generator, to run both the blog and newsletter from the same codebase. Content lives as markdown files with frontmatter for title, description, and structured data. There is no database and no CMS in the path. Each post renders to static HTML at build time, which makes the system fast and durable.

The frontmatter also feeds JSON-LD structured data automatically. You write once, and the content works for both readers and search engines without any extra effort. The blog is not a separate system. It uses the same Astro build, the same Tailwind tokens, and the same deploy pipeline as the rest of the site. A single repository handles everything.

Adding a new article is as simple as creating a markdown file, adding it to the content collection, and pushing. The build takes seconds. There is no database to query, no CMS to log into, no plugins to update. For publications used to fighting with complex CMS interfaces, this simplicity is refreshing.

The Reading Experience You Actually Want

Once you own the renderer, small things become possible. Sidenotes float next to the line they reference on wide screens. On mobile, they collapse to tappable references. The reading UI is yours to shape, not something a platform theme decides for you.

Custom typography, code syntax styling, and TL;DR blocks come from the same source as the article itself. You do not fight a platform theme to get the layout you want. For a publication that talks about tooling and technology, that matters more than it sounds. The investment in owning your stack pays off in ways that are hard to predict in advance.

Owning the renderer also means JSON-LD structured data becomes trivial. The TL;DR and FAQ already live in frontmatter, so embedding them in structured data is a few lines at render time. You write once, and both the page and the rich search result get the same content. These details compound. A publication that controls its own reading experience can experiment with formats that platforms do not support.

Sending: Resend Handles the Heavy Lifting

Email delivery runs on Resend. New subscribers come through a form on your own domain that posts to an API route and adds them to the audience. The sending domain has SPF, DKIM, and DMARC authentication, so mail lands in the inbox instead of spam. Each campaign is a small Node script that builds the email HTML per recipient and sends with a delay between messages to stay polite.

Every send carries a List-Unsubscribe header and an unsubscribe link. The script skips anyone already unsubscribed. The audience data lives in Resend, not on your own server. This separation means you do not have to manage email infrastructure yourself, but you still own the relationship with your subscribers.

For publications with under 10,000 subscribers, the cost is negligible. As the audience grows, you scale the sending volume without moving to a different platform or renegotiating rates. The economics are predictable and transparent.

Analytics on Your Own Dashboard

PostHog handles analytics on your own infrastructure. Open rates, click paths, and subscriber journeys all appear in one dashboard you control. No platform can change what data you see or how you see it. The analytics setup also feeds into content strategy. Understanding which articles drive the most newsletter signups helps inform what to write next.

That data belongs to you, not to a platform. Monthly costs are modest. Domain registration, hosting on Vercel or Cloudflare Pages, and an email service plan come to roughly $20-50 per month for a publication with under 50,000 subscribers. The economics work better than a typical platform subscription once you cross that threshold.

The Tradeoff You Are Making

Owning the stack means owning the responsibility. You maintain uptime, apply security updates, and monitor rendering performance. For a team with even one developer who understands deployment pipelines, this is manageable. The tradeoff is worth it for publications that want full control over their content, audience data, and technical SEO signals.

If your newsletter is a core part of your business, owning the infrastructure means owning your destiny. The publications making this work are not just the large ones. Small independent newsletters with 1,000 to 5,000 subscribers have successfully migrated and reported that the technical overhead is lower than expected. The key is starting simple and adding complexity only when it delivers measurable value.

Sources

Want to improve your marketing results? Visit XerAds for proven strategies that drive real results.