Elizabeth Tai published a post in June 2026 arguing that Substack writers are making a strategic mistake by treating Substack as their home on the internet — and 379 upvotes on Hacker News plus nearly 200 comments confirmed she hit a nerve. The argument isn't new, but what makes it timely is that Substack has matured enough that real careers are now built exclusively on it, which means the stakes of getting this wrong have grown substantially. The biggest pitfall isn't just "what if Substack shuts down" — it's that by the time most creators realize they've been building on rented land, the SEO equity, brand identity, and distribution leverage they could have built on an owned property is already locked inside someone else's domain.

For the audience this site cares about — freelancers using newsletters as client pipelines, agencies running thought-leadership content, solo founders building in public — the implications go beyond content creators. This is a business infrastructure question dressed up as a publishing debate.

What is this actually about?

Substack launched in 2017 as a tool that made it dead simple to charge readers for email newsletters. It handled payments, email infrastructure, subscriber management, and gave writers a clean, minimal publishing interface. The pitch was compelling: no technical overhead, built-in monetization, and eventually a discovery layer that could surface new writers to interested readers.

By 2026, Substack has expanded well past newsletters. It now hosts podcasts, video, a Twitter-like social feed called Notes, and a chat feature for subscriber communities. For a writer who wants to build an audience with minimal friction, it remains genuinely excellent. The email deliverability is strong. The payment infrastructure is reliable. The discovery mechanisms — recommendations between publications, the Substack reader app, algorithmic suggestions — do drive real subscriber growth for many writers.

Here's what Substack is not: it is not a website you own.

When you publish on Substack, your content lives at yourname.substack.com. You can attach a custom domain — say, yourname.com — so that URL shows your domain in the browser bar. But the content is still hosted on Substack's servers, rendered by Substack's templates, and indexed by search engines in a way that ties your authority to Substack's infrastructure choices, not yours. You cannot install custom plugins, modify your site's HTML structure in meaningful ways, implement advanced schema markup, add custom landing pages for lead magnets, run A/B tests on your opt-in flows, or integrate deeply with tools like HubSpot, Intercom, or a custom CRM.

The custom domain feature gives the appearance of ownership without most of the substance.

Elizabeth Tai's core argument is straightforward: if your newsletter is your business — or a meaningful part of your business — you need a website that serves as your actual headquarters. Not because Substack is predatory or bad, but because concentrating your entire digital presence on a platform you don't control introduces compounding fragility.

What changed recently that sharpens this argument is Substack's growing emphasis on its own social layer. Notes, the in-app chat, and the Substack reader have all pushed the platform toward becoming an ecosystem writers are expected to participate in as a platform, not just publish to. The more that ecosystem grows, the more creators who live only on Substack will find their growth becomes dependent on Substack's algorithmic decisions, recommendation policies, and business model pivoting — none of which they have any influence over.

Why this matters right now

The "don't build on rented land" maxim has been circulating in creator and indie hacker circles since at least 2012. So why is this post hitting differently in 2026?

Three specific things have changed. First, Substack's paid creator base has grown large enough that many writers now earn meaningful income there — some are making this their primary profession. When the stakes were low, the platform risk was tolerable. At real income levels, it's a business continuity question.

Second, Substack's terms of service have evolved. The platform has made increasingly assertive content moderation decisions, including deplatforming writers without uniform policy application. Whether you agree with those specific decisions or not, the pattern reveals that Substack retains ultimate control over who publishes and who doesn't. Any creator whose income depends on uninterrupted access should find that fact concentrating.

Third, the SEO situation has quietly become more damaging than most creators realize. Search traffic has emerged as one of the most valuable and durable discovery channels in publishing. Writers who published exclusively on Substack for years have accumulated inbound links, Google authority, and keyword rankings — but all of that equity is tied to substack.com (or in the custom domain case, to Substack's infrastructure). If you ever leave, you cannot take your search equity with you the way you can export your email list. Your subscriber CSV is portable. Your Google rankings are not.

Twelve months ago this might have seemed abstract. Today there are writers who've built four- and five-figure monthly subscriber counts on Substack and are only now realizing that if they want to move to Ghost or a self-hosted setup for better control, they face a genuinely painful transition where much of their organic discoverability resets.

The timing of this HN post also coincides with a broader creator economy moment where platforms that once seemed friendly to creators — Twitter, YouTube, Patreon, Facebook Groups — have all demonstrated, at various points, that their interests and creator interests eventually diverge. Substack, for all its genuine strengths, is a VC-backed company with investors who will eventually need a return. That structural fact matters.

Practical implications for small teams

The conversation around this topic tends to default to individual writers, but the implications for small teams and agencies are distinct and in some ways more urgent.

The freelance writer with no portfolio site. A freelance writer using Substack as both their newsletter and their portfolio is making a specific mistake: clients who Google them find a Substack page that may or may not reflect their actual capabilities, skills, or service offerings. Substack's design is optimized for readers, not for potential buyers of services. There's no way to add a proper "Hire Me" page, a client-oriented case study section, or a booking widget without hacking together awkward workarounds. The writer who uses Substack exclusively is essentially giving every prospective client a reading experience when what they need is a sales experience. An independent site, even a minimal one, solves this cleanly — and a Substack newsletter can link to it on every issue.

The agency using a newsletter for thought leadership. Agencies are increasingly using newsletters as a core business development tool — publishing industry insights to keep their brand visible to potential clients between project cycles. If that newsletter lives exclusively on Substack, the agency is in an odd position: they've told clients they're sophisticated digital marketers, but they don't own the domain where their most sustained public-facing content lives. More practically, the agency can't run proper conversion tracking, can't A/B test their email opt-in offers, and can't tie newsletter engagement data into a CRM in any meaningful automated way. These aren't vanity concerns — they're the difference between a newsletter that generates leads and one that generates impressions.

The solo founder building in public. Solo founders documenting their journey through Substack often gain genuine audiences. The problem surfaces when the founder eventually has something to sell — a course, a SaaS product, a community, consulting services. Substack has basic paid subscription tooling, but it's not built for anything more complex: no product pages, no checkout flows beyond subscriptions, no integration with course platforms, no affiliate tracking. At some point every founder-creator hits this ceiling and realizes they need a proper site. Starting that site from zero, after years of building an audience that knows you as your Substack URL, is harder than doing it from the beginning.

The content-driven small team managing multiple voices. A small editorial team — say, a two- or three-person media operation or content agency — publishing on Substack runs into the same multi-author problem every Substack publication eventually faces: the platform is fundamentally designed for individual writers. Team bylines, granular author pages, editorial workflows, and content management at any meaningful scale feel bolted-on. A proper CMS with a newsletter layer handles this far better, and building on owned infrastructure means the team's accumulated content becomes an asset on a domain they control rather than data on Substack's servers.

The niche community builder running events. Writers who build Substack audiences often evolve toward events, live sessions, or offline gatherings. Substack has chat and comments, but no event management, no ticketing, no RSVP workflows. Every time a community builder tries to layer an event on their Substack operation, they're pasting together external tools — Eventbrite, Luma, Notion — with no central hub. A proper website becomes the obvious coordinating layer that these scattered tools can point back to.

How to respond and act on this

The good news is that the minimum viable response to this problem is not a full site rebuild. The goal isn't to abandon Substack immediately — for many writers, Substack's discovery layer and email infrastructure are genuinely valuable and shouldn't be surrendered lightly. The goal is to stop treating Substack as your home base.

Start with a domain and a minimal personal site. If you don't own your domain, get one today. Namecheap and Porkbun are both reliable and inexpensive. Even a single-page site on Carrd (~$19/year for a custom domain Pro plan) is an enormous improvement over nothing. That page should include who you are, what you do, where to find your newsletter, and a clear contact or hire method. This is the floor, not the ceiling.

Decide on a CMS tier based on your actual needs. For pure writers who want more control without developer overhead, Ghost Pro (starting around ~$9/mo) is the most Substack-adjacent experience — clean writing interface, built-in email, paid subscriptions, and proper site architecture. It's what Substack would be if the priority were creator control rather than platform growth. For teams who need more flexibility and are comfortable with slightly more complexity, WordPress (self-hosted with a decent host like Cloudways, Kinsta, or WP Engine) remains the most flexible option. For agencies or founders who care deeply about visual design and want a no-code experience, Webflow is worth the learning curve.

Don't migrate your Substack archive immediately, or possibly ever. This is the decision most people get wrong. Migrating years of Substack posts to a new domain causes a traffic dip during the transition — Google has to reindex everything and update its understanding of where the canonical content lives. For most writers, the better approach is to: keep the Substack as an archive with a redirect or "also available at" notice, point the custom domain to your new site, and publish new content on the owned site going forward. You lose no existing email subscribers. You gain a proper home base for all future content.

Export your email list today, even if you're not migrating. Substack makes this easy: go to your dashboard, export subscribers. Save the CSV somewhere you control. Do this monthly as a habit. Your email list is the one genuinely portable asset in this situation — protecting it costs five minutes and has essentially zero downside.

Set up a parallel email tool for serious monetization. If your newsletter is generating real revenue or you're building a serious business around it, consider running Kit (formerly ConvertKit) or Beehiiv as your email infrastructure, even if you continue publishing on Substack. This gives you segmentation, automation, and proper CRM-style capabilities that Substack simply doesn't offer. Cross-posting to Substack for the discovery layer while owning the actual relationship in a separate tool is a legitimate hybrid strategy.

Audit your inbound links. If you've been on Substack for more than a year, Google Search Console (free, set it up if you haven't) will show you which of your posts have earned inbound links. Those are the posts worth prioritizing when you eventually want to migrate — they carry the most SEO equity and should get the most careful redirect treatment.

Comparison: platforms for building an owned newsletter + website

Tool Best for Free plan Starting price Key differentiator
Substack Discovery-focused pure writers Yes Free (10% of paid subs) Network recommendations; simplest onboarding
Ghost Pro Writer-creators wanting control with newsletter built in No ~$9/mo Clean writing UX; no platform take on subs
Beehiiv Newsletter-first growth with monetization Yes ~$49/mo (Scale) Ad network; referral programs; growth tools
WordPress.com Flexibility without self-hosting Yes ~$4/mo Huge plugin ecosystem; blogging heritage
WordPress (self-hosted) Maximum control; technical teams Yes (hosting separate) ~$5–15/mo hosting Full extensibility; own all your data
Webflow Design-forward teams and agencies Yes (limited) ~$14/mo Visual-first CMS; no-code but powerful
Kit (ConvertKit) Creators who want email automation without a full CMS Yes ~$25/mo Automation depth; landing page builder
Carrd Minimal personal landing page Yes ~$19/yr Fastest path to a real web presence

Our take: for most writers currently on Substack who want to take the first step, the Carrd-plus-Kit combination (total outlay around $40-50/year) is the most practical entry point. It gives you an owned domain, a clean personal page, and serious email infrastructure without requiring you to migrate anything or give up Substack's discovery benefits. Ghost Pro is the right next tier for writers who want a unified experience. WordPress self-hosted is best for teams with a technical person who can manage it.

What the HN community is saying

The Hacker News discussion around this story ran to nearly 200 comments, and the conversation split into several distinct camps that are worth understanding because they reflect genuine, unresolved tensions.

The most upvoted perspective was essentially: "This applies to every platform, not just Substack." Commenters pointed to the pattern of Twitter/X's decline affecting writers who'd built their audience there, YouTube's demonetization controversies, and Medium's repeated pivots that stranded early writers. The consensus in this thread was that platform dependency is a structural problem, not a Substack-specific one — which is true, but also misses the specific ways Substack creates dependency that differ from, say, Twitter.

A significant minority of commenters pushed back with legitimate skepticism: "The discovery benefit is real, and abandoning Substack means abandoning organic growth." Several working writers in the thread noted that Substack recommendations drove the majority of their subscriber growth, and building an independent site doesn't replace that acquisition channel. This is a real point that the original post somewhat glosses over. Moving to an owned site doesn't automatically bring readers — you still need discovery, and Substack's ecosystem genuinely provides that in ways an independent WordPress blog does not.

Practitioners in the thread — people who'd actually migrated or run hybrid setups — offered the most nuanced takes. The hybrid approach (keeping Substack for discovery, cross-posting or linking to an independent site for the canonical content) appeared multiple times as the working solution. A few commenters noted that Ghost's deep Substack import tool has made migration substantially easier than it was two years ago, which changes the risk calculus.

The skeptical technical contingent raised a fair point about SEO: for most small newsletters, organic search isn't actually a meaningful traffic source regardless of which platform they use. Most Substack writers' readers come from social shares, recommendations, and word of mouth — not Google. This doesn't make owning your domain wrong, but it does mean the SEO argument isn't as universally urgent as it might seem.

What was notably absent from the thread: serious defenders of Substack's platform terms. Even commenters who argued writers should stay on Substack for discovery purposes generally agreed that having an independent site was worth doing. The disagreement was about urgency and prioritization, not principle.

Risks and things to watch

The "get off Substack" argument carries its own risks and hidden costs that deserve honest treatment.

The migration SEO cliff. Moving a Substack publication with years of content and inbound links to a new domain is not a painless operation. Even with proper 301 redirects, Google's transition period can take three to six months, during which organic traffic may drop significantly. For writers who've built meaningful search traffic — a minority of Substack writers, but a real group — this is a concrete business risk that needs to be planned for, not minimized.

The discovery moat disappears if you leave. Substack's recommendation algorithm and in-app reader represent real distribution. Writers who leave lose this entirely. An independent Ghost or WordPress site has zero native discovery infrastructure. This means the migration decision is actually a two-part question: where will your content live, and where will you acquire new readers? These need separate answers.

Cost escalation on alternatives. Ghost Pro, Beehiiv, and serious WordPress hosting are all meaningfully more expensive than Substack for writers who aren't generating paid subscription revenue. Substack is genuinely free for writers without paid subscriptions. The alternatives start at $9-50/month. For early-stage writers still building their audience, this is a real consideration — though the Carrd + Kit combo keeps costs minimal.

Technical debt and maintenance. Running a self-hosted WordPress site means dealing with updates, security patches, plugin conflicts, and occasional inexplicable breakage. For writers who want to write, not manage web infrastructure, this overhead is real. Ghost Pro and Webflow reduce this, but no platform eliminates it entirely. The choice isn't just "Substack vs. freedom" — it's "Substack's constraints vs. a different set of constraints."

The audience confusion problem. If your readers know you as your Substack URL and you change domains, some portion of them will be confused regardless of how clearly you communicate the change. Not disastrously so, but expect some friction and some churn in the weeks following a migration.

Beehiiv is also a platform you don't own. Several HN commenters and many creators treating Beehiiv as the "safe" alternative are making the same structural mistake. Beehiiv is VC-backed, growing rapidly, and subject to the same eventual business model pressures as Substack. Moving from Substack to Beehiiv solves some problems (better analytics, better monetization tooling) but does not solve the fundamental platform dependency issue.

Frequently asked questions

If Substack lets me use a custom domain, isn't that good enough for ownership?

A custom domain on Substack is substantially better than publishing at yourname.substack.com — it means your brand is in the URL and you don't have to retrain your audience if you ever move. But it doesn't change the underlying ownership situation. Your content is still on Substack's servers, rendered by their templates, and subject to their terms of service. You also cannot fully control the site's technical architecture — meta tags, canonical URL handling, structured data markup, and page templates are all managed by Substack. Custom domain is a meaningful improvement, not a substitute for actual ownership.

Can I just export my Substack posts to a new site later if I need to?

You can export the content, yes — Substack provides a full export of your posts. But "content" and "web presence" are different things. What you cannot take with you is your search ranking history, the inbound link equity pointing to your Substack URLs, and your post-level analytics. Ghost has a direct Substack importer that handles most of the content migration reasonably well. The redirect setup — making sure all your old Substack post URLs properly redirect to their new locations — requires either technical comfort or paying someone to do it correctly.

What's the minimum viable website for a writer currently on Substack?

A single-page Carrd site on a custom domain, listing who you are, what your newsletter covers, a link to subscribe (which can still go to Substack), and a contact method. Total setup time is about two hours. Total annual cost is around $20 for the Carrd Pro plan plus $10-15 for a domain. This doesn't give you a full blog, advanced SEO capabilities, or email independence — but it gives you a home base you control and dramatically improves how you appear to prospective clients, collaborators, and professional contacts.

Is Ghost actually a better newsletter platform than Substack?

For independent control, yes. Ghost gives you full ownership of your site's code and structure (self-hosted version), built-in email newsletters, paid membership support where Ghost takes 0% (compared to Substack's 10%), and a clean writing experience that's genuinely comparable to Substack's. What Ghost doesn't have is Substack's discovery network. Ghost Pro (the managed hosting option) removes the infrastructure maintenance headache but keeps you reliant on Ghost's hosting. Ghost's open-source nature means you could always export and self-host, which is a meaningful long-term hedge.

I have 10,000 subscribers on Substack. Is migrating worth the disruption?

At that scale, the disruption is real but manageable with proper planning. The right approach: export your subscriber list, set up your new site, and do a careful redirect setup before publicly announcing the move. Keep your Substack active during the transition period to catch any readers who missed the announcement. Expect 3-6 months for Google to fully recognize the canonical content move. The calculus also depends heavily on how much of your audience came via Substack recommendations versus other sources — if recommendations drove most of your growth, staying on Substack while adding an independent site is probably smarter than a full migration.

What about Beehiiv as a Substack alternative?

Beehiiv is a genuinely superior newsletter platform to Substack in several specific ways: better analytics, a built-in ad network for writers who don't want paid subscriptions, better referral program tooling, and stronger email deliverability metrics. It does not, however, solve the platform dependency problem. Beehiiv is funded by VC investors and will eventually face the same business model pressures as Substack. The right framing is: Beehiiv is a better Substack, not a replacement for an owned website.

How does this affect writers who aren't trying to monetize their newsletter?

If your newsletter is a pure creative or community project with no professional or commercial dimension, the urgency here is lower. The SEO and client-acquisition arguments don't apply. What does still apply is the basic fragility concern — if Substack changes its terms, acquires new ownership, or pivots its product, you'd lose your platform with varying amounts of warning. Having a backup domain with a simple site and an exported subscriber list is cheap insurance regardless of whether you're monetizing.

Does running a website alongside Substack actually add that much work?

Depends on the approach. A Carrd landing page adds essentially zero ongoing maintenance. A Ghost or WordPress blog where you cross-post your newsletter essays adds perhaps 15-20 minutes per issue — you're writing the same content, just publishing it in two places. The overhead scales with your ambitions: if you want a full editorial site with custom categories, author bios, and event listings, that's a real project. If you just want a professional home base that points to your newsletter, it's genuinely a one-time setup cost.

Final verdict

Elizabeth Tai's argument is correct, and the HN community's engagement with it confirms that this concern has moved past theoretical into practically urgent for a meaningful slice of working creators and content-driven small businesses.

Our analysis is that the stakes vary significantly by use case, and the response should be calibrated accordingly. For freelancers who use their newsletter as a professional calling card, an independent website isn't optional — it's the missing piece between publishing good content and converting that content into client opportunities. Clients who land on a Substack page versus a professional yourname.com site have a meaningfully different impression of who they're dealing with. The site doesn't have to be elaborate; it has to exist and be clearly yours.

For agencies and small teams running content marketing through Substack, the platform's limitations on conversion tracking, CRM integration, and team workflows are probably costing more in missed attribution and manual workaround time than the cost of running a proper CMS. The right setup here is an owned site handling the content hub and conversion infrastructure, with newsletters deployed through a tool that integrates properly with the rest of the business stack.

For solo founders building in public, the strongest argument is long-term optionality. A founder who publishes everything on Substack and later wants to launch a product has to retrofit a website on top of an already-established audience that knows them at a Substack address. That's a harder problem than building the independent site in parallel from the beginning.

The one camp where the urgency is genuinely lower: early-stage writers who are still in the audience-building phase and relying on Substack recommendations for discovery. For those writers, the practical recommendation is to grab your domain and set up a minimal presence now, but don't invest in a full migration until you've built enough of an audience that the platform lock-in risk outweighs the discovery benefit. The hybrid setup — Substack for distribution and discovery, an independent domain as your canonical home — is not a cop-out. It's the operationally smart answer for most people in this situation.

What we'd be skeptical of is the "just move to Beehiiv" response that's common in these discussions. Beehiiv is a better newsletter tool in several respects, but it's the same category of answer: a platform you rent, with its own terms, its own future business model uncertainty, and its own constraints. The actual answer to this problem is always the same: own a domain, control your email list, choose platforms deliberately for what they're good at rather than defaulting to them as a home base.

The cost of acting on this is genuinely low. A domain, a minimal site, and a monthly subscriber export habit costs less than $100/year and an afternoon of setup. The cost of not acting is diffuse and slow-moving until it suddenly isn't — which is exactly the kind of risk that never feels urgent until it's already too late to address cleanly.