Why Substack Writers Need Their Own Website

Why Substack Writers Need Their Own Website

Substack is a distribution tool, not a digital home

Writers should keep a self‑hosted website as the primary source of truth and use Substack only for distribution. Substack’s convenience and built‑in monetisation are attractive, but the platform owns the domain (unless you link a custom one) and can change policies, pricing, or shut down without warning. A personal website on a domain you control guarantees long‑term visibility, SEO control, and exportability of your content.

Why platforms become digital sharecropping

Relying on a third‑party platform makes you a tenant, not a homeowner. History shows that platforms—Facebook, Tumblr, Medium, and now Substack—can alter rules or disappear, leaving creators stranded. As Elizabeth Tai writes, “When you build your audience entirely on someone else’s platform, you aren’t a homeowner. You are a tenant. Or worse, a digital sharecropper.”

“Substack is a single point of failure that relies on partners like Stripe for any kind of financial linkage.” – thataccount (HN)

“If you write all your stuff in a location you control, and syndicate that out to the popular platform of the day, you can minimize your loss.” – dsr_ (HN)

“The ad revenue model of websites is dying.” – real‑hacker (HN)

These comments reinforce the core warning: platform dependence can jeopardise both content and income.

The POSSE (Publish‑Own‑Site‑Syndicate‑Elsewhere) workflow

Publish on your own site first, then push to Substack (or any other service). This approach lets you keep the canonical URL, SEO metadata, and full export rights while still benefiting from Substack’s email list and discovery network.

“I publish everything to my personal blog first, then once a week I copy and paste it all into a Substack newsletter… Substack doesn’t have an API for composing a newsletter, but their rich‑text editor DOES accept copy‑pasted data – the universal API.” – simonw (HN)

“I take my post link and add it to Substack note to push people to the blog. Substack is not great for what I like to do.” – kwholley63 (comment)

“I’ve been on WordPress since 2009… there seems no good reason to move elsewhere.” – Chris Amies (comment)

Implementing POSSE can be as simple as:

  1. Write a draft on your website (static site, WordPress, Ghost, etc.).
  2. Export or copy the HTML/Markdown.
  3. Paste into Substack’s editor for the newsletter.
  4. Share the Substack link on social media, but keep the website URL as the canonical reference.

Real‑world examples of long‑term ownership

John Scalzi’s 28‑year‑old WordPress.com blog demonstrates the durability of self‑hosted sites. He treats social media as traffic sources, not as the home of his work:

“This site acts as my own institutional memory… all the posts I ever placed on the former Twitter are now entirely lost to time, since I have gone in and purged my entire timeline there. This site, however, endures.” – John Scalzi (comment)

Other writers cited in the discussion echo the same sentiment:

  • Jim Grey notes that an independent blog “is not subject to those forces” and remains fully exportable.
  • PlusBrothers migrated from Buttondown to a self‑hosted site to retain full ownership of content and conditions.
  • Seb Run Nature (French) writes that a personal domain “is an investment that pays off with the years.”

Counterpoints: When Substack adds real value

Substack excels at audience reach, email distribution, and low‑friction monetisation. For many creators, especially those without an existing audience, the platform’s network effects are decisive.

“Substack gives a really nice exposure… you can get a few thousand subscribers on Substack just by being consistent and interacting with other people.” – f311a (HN)

“Substack solved distribution (and community, and bookkeeping, un‑distribution etc) and it solved getting paid for my writing… It is worth much more than its fees.” – simonsarris (HN)

“I keep a personal blog since 2012… Substack helped me attract over ~2.3k subs to date.” – rafaquintanilha (HN)

These points are valid: Substack reduces the technical barrier to building a mailing list and handling payments. However, the author stresses that even when Substack is used for these purposes, the website should remain the canonical location.

Practical steps to start (or revive) your own site

  1. Choose a low‑cost host. $5‑$10 / month for shared WordPress hosting or a cheap VPS (e.g., Hetzner) is sufficient for most writers.
  2. Register a domain. $10‑$15 / year from a registrar; treat it as a yearly rent rather than ownership, but it gives you full control.
  3. Pick a CMS that fits your workflow. WordPress.com, Ghost, Hugo, Jekyll, or static‑site generators all work; the key is exportability (XML/JSON/Markdown).
  4. Set up RSS and email capture. Services like Revue, Buttondown, or self‑hosted Mailtrain can feed your subscriber list.
  5. Implement POSSE. Write on the site, then syndicate to Substack, Bluesky, X, or newsletters.
  6. Back up everything. Export your posts and subscriber list regularly; Substack’s export tools are limited, so keep a local copy.

Community consensus from the discussion

Position Representative comment Takeaway
Strongly for a personal site “A website with your own domain is still one of the best long‑term assets a writer can build.” – John Articles Ownership outweighs convenience.
Platform‑first but with a site “I publish everything to my personal blog first, then copy‑paste to Substack.” – simonw Hybrid approach works.
Platform‑only “Substack gives a really nice exposure… you can get a few thousand subscribers.” – f311a Substack can be primary for growth, but risk remains.
Open‑source alternatives “Leaflet, Offprint, Pckt are open platforms that don’t lock you in.” – acmnrs Consider decentralized publishing tools.
Skepticism about SEO/traffic “Google search is dead; discovery mechanisms are changing.” – danschuller Traffic strategies evolve; owning a site still matters for control.

Overall, the community agrees: use Substack as a distribution channel, not as your digital home.

Bottom line

A personal website is the only durable foundation for a writer’s online presence. Substack (or any other platform) can amplify reach and simplify payments, but it should sit on top of a self‑owned domain that you can export, redesign, and keep alive regardless of platform policy changes.

Further reading

  • Elizabeth Tai, What I learned from one year of Substack (2023) – a candid look at Substack’s network effects and pitfalls.
  • David Bourne, Digital Sharecropping – the historical analogy of platform dependence.
  • Simon Willison, Blog‑to‑Newsletter copy‑paste tool – a practical POSSE utility.
  • Leaflet.pub, Offprint.app, Pckt.blog – open‑source publishing platforms that avoid lock‑in.

Take action today: register a domain, set up a simple blog (WordPress.com is free to start), and begin publishing your drafts there. Then link your Substack newsletter to the same posts. Your content will survive any future platform shake‑up, and you’ll retain full control over your audience and revenue.

References

Sources