Custom domain or platform subdomain? When the free address stops being enough
By Domain Yoga · Last updated July 28, 2026
If your project has an audience you’d mind losing — or a realistic chance of growing one — buy a custom domain and connect it to the platform you’re already on. Nothing else has to change: your newsletter stays on Substack, your store stays on Shopify, your site keeps deploying to Vercel. The only thing you’re changing is which address the internet accumulates links, bookmarks, and habits against — one the platform lends you, or one you own and can point anywhere, for a low double-digit sum each year. If, on the other hand, the project is a hobby, an unvalidated experiment, or a developer portfolio where username.github.io quietly works in your favour, the free subdomain is a legitimate answer — and a full section below defends it in earnest. The detail that decides which half applies to you: what a domain changes, what it costs, and what happens to your old links on the day you leave — which ranges from “handled automatically” to “orphaned forever” depending on the platform.
What actually changes when you move off the free address?
Three things change, and one important thing doesn’t.
The address becomes property instead of a loan. yourname.substack.com is namespace inside Substack’s domain: it exists under Substack’s terms and lasts exactly as long as your relationship with the platform does. A registered domain has you as the registrant; keep paying the annual fee and it’s yours indefinitely, across platforms and hosts you haven’t thought of yet.
Your links start compounding in your favour. Every mention, backlink, and bookmark points at an address. On a subdomain, that equity accrues to something you can’t take with you. On your own domain, you can repoint the same address at a new host without asking a single reader to update a bookmark.
Email becomes possible. [email protected] requires owning yourname.com — no platform subdomain gets you there, for reasons covered below.
What doesn’t change: the platform. Connecting a custom domain is not leaving. You keep the hosting, the tooling, and — on Substack specifically — the discovery network, a point handled below because it’s the most common false trade-off in this decision.
And one thing we can’t tell you, because nobody honestly can: how much a custom domain improves trust or conversion, as a number. We looked for a rigorous, independent study isolating that effect and found none. The specific percentages circulating in this space — “15–25% more conversions,” a “34% CTR boost” — trace back to vendor and SEO content-farm blogs with no disclosed methodology, no sample size, no primary data. Two of the most-repeated stats are worse than unsourced. One is attributed to the Baymard Institute, whose actual published research is about checkout trust in general — 17% of shoppers cite a lack of trust in the site as a reason for abandoning a purchase — and says nothing whatsoever about domains versus subdomains. The other is a Verisign “trust index” credited with a 35% edge for .com; we can find no published basis for that figure, though Verisign did run a real trust-index marketing campaign back in the early 2000s, which is presumably where the borrowed authority comes from. What can honestly be said is the mechanism: a bespoke address removes one visible signal that a project is casual or temporary. That’s plausible, loosely supported by general trust-signal research, and attached to no defensible number. Anyone who quotes you one is reciting someone’s marketing.
What happens to your readers and links if you leave later?
This is where the platforms genuinely differ, and the unevenness is the real story — “can I move later without losing everything?” has a different answer on every free address.
All official-docs rows below were checked July 28, 2026.
| Platform | Redirect off the free subdomain when you leave? | Confidence |
|---|---|---|
| Shopify | Yes — set a custom domain as primary and Shopify auto-redirects the old myshopify.com address to it | Official docs |
| Substack, domain connected before leaving | Reported to keep redirecting after departure — undocumented, not guaranteed | One practitioner account |
| Substack, no domain ever connected | No — you.substack.com cannot be redirected anywhere; old links are orphaned | Practitioner-documented; absent from Substack’s help center |
| GitHub Pages | While a custom domain is configured, username.github.io 301s to it — but the redirect lives with the site. Keep a stub repo and its CNAME file alive to preserve it | Observed behaviour; GitHub documents only apex/www redirects |
| Vercel | No stated mechanism; .vercel.app names are first-come-first-served, not reservable or portable | Official docs (no mechanism documented) |
| Notion | Unverified — we found no documentation of exit behaviour either way | Official pages describe connecting, not leaving |
Shopify is the generous end: connect a domain, set it as primary, and the old myshopify.com links redirect automatically, effective almost immediately. Even there, the subdomain never becomes yours — it’s a forwarding label, not an asset; close the store entirely and, per secondary guides (Shopify’s own docs don’t spell this out), the name stays locked to the deactivated account.
Substack is the middle case: your exit story hinges on a decision made long before you have any reason to care. It charges a one-time $50 fee per publication to unlock custom domains — per its own announcement, checked July 28, 2026; pay once, then add and remove domains at no additional cost. Pay it and connect a domain, and Substack redirects you.substack.com to your address — in at least one documented case, that redirect kept working six months after the writer moved the publication to Ghost. Both halves of the caveat matter: it’s one account, of behaviour Substack doesn’t document, and the source itself notes Substack could stop honouring it once your DNS no longer points its way. Never pay the $50, and the punitive branch applies: no redirect anyone has been able to find, no forwarding option, nothing. On the evidence available, fifty dollars once is what appears to separate “my old links follow me” from “my old links are dead” — which is a good argument for connecting a domain early, and a poor one for treating that redirect as a guarantee you can bank on.
GitHub Pages is better than its own documentation suggests. While a custom domain is configured, GitHub 301-redirects username.github.io to it — you can watch that happen on numpy.github.io or pytorch.github.io right now, even though the docs describe only apex-to-www redirects. The catch is that the redirect is a property of the live site rather than a permanent forwarding record: delete the repo and it dies with it. Leaving a stub repo with its CNAME file in place preserves the redirect indefinitely, which works for exactly as long as you remember the stub exists. Vercel offers nothing comparable — a .vercel.app name isn’t even reservable. Notion we can only report as unknown: we found no documentation pointing either way, so plan as though no redirect exists rather than assuming one does.
Leaving without redirects is a domain migration done badly — see rebrand without losing SEO for what a proper one involves — except the redirects aren’t available at any price.
Can you get a real email address without a domain?
No — and the why matters, because “I need a proper email address” is how many people discover the domain question hiding inside a different one.
Email addresses are namespaced by domain. [email protected] can only be minted by whoever controls yourname.com; no service can sell you an address on a domain you don’t own. That’s how DNS and mail routing work, so the platforms couldn’t help even if they wanted to, and none do: of the five we researched (Substack, GitHub Pages, Vercel, Shopify, Notion), none provides a mailbox on its free subdomain. The furthest any goes is Substack’s reply-forwarding, which sends reader replies to an inbox you already own elsewhere — it doesn’t create an address. Vercel says it plainly in its docs: it provides no mail service for domains.
Substack deserves singling out, because it is easy to assume the $50 custom-domain unlock buys a sending address too. It does not. Substack’s own help centre answers the question flatly: connecting a custom domain does not get you a Substack inbox, and your newsletter is always sent from an @substack.com address regardless. If sending from your own domain matters — and for a newsletter building a brand it often does — that is a platform question, not a domain question. Beehiiv and Ghost support a custom sending domain; Substack doesn’t, at any price.
The confusion often runs the other way, too: people assume they need to buy an “email plan” and a domain somehow comes with it. The domain comes first; the mailbox is a separate layer on top, and usually the cheap part — Google Workspace if you want the full suite, or low-cost routes like Zoho Mail. (Cloudflare Email Routing is free and useful, but it forwards only — it won’t let you send from the address.) (Zoho’s free tier sometimes gets cited as a way around this, but per the roundups describing it, it requires a domain you already own.) Once you own the name, setting up email on your domain is an afternoon’s work.
What does a domain actually cost — and does waiting make it cheaper?
For a standard .com: around $10–11 a year at an at-cost registrar — Cloudflare Registrar states outright that it adds no markup, so you pay what the registry and ICANN charge between them, which is exactly what puts a hard floor under that figure (see the next paragraph) — around $11–15 at mid-market registrars like Namecheap — higher at renewal than at signup — and commonly $20–22 a year at renewal at legacy registrars like GoDaddy. (The Namecheap and GoDaddy ranges are from third-party aggregators, not pages we fetched ourselves; treat them as ballpark.) Budget against the renewal price, never the first-year promo — a separate trap we’ve measured in first-year vs renewal domain pricing. Other extensions run both cheaper and dearer — which TLD should you use covers that choice — and registrar choice moves the price as much as the TLD does, which is what our registrar guide for indie hackers is for.
Waiting does not make it cheaper. It makes it very slightly more expensive, on a public schedule: Verisign, the sole registry operator for .com, raises its wholesale price 7% — from $10.26 to $10.97 a year — on November 1, 2026, under an ICANN agreement running through November 30, 2030 that permits increases of up to 7% in each of the final four contract years. That’s a published contract, not marketing spin, and it puts a slowly rising floor under every registrar’s retail price. Nobody should rush to buy over a seventy-cent wholesale bump; the point is that there is no discount for patience.
There is one cost the enthusiasm usually leaves out, and it’s the strongest honest argument against buying casually: a domain you stop paying for is worse than a domain you never bought. Let a registration lapse and it moves through a grace period into redemption, where reinstating it typically costs $80–100 rather than the renewal price, and then it drops — at which point anyone can register it, including people who noticed it had inbound links pointing at it. Every reader, backlink and bookmark you accumulated then resolves to a stranger’s page, which is a worse outcome than the orphaned links you were trying to avoid. Owning is an asset for exactly as long as auto-renew is on and the card on file still works.
The real cost of waiting isn’t at the registrar at all. It accrues on the subdomain, invisibly: backlinks pointing at an address you can’t keep, readers who memorised it, published collateral you can’t recall. On a platform with strong redirects — Shopify, or Substack if you paid the $50 early, with the caveat above — that pile stays cheap to move. On a platform with weak or no redirects, every month of growth makes “switch later” strictly more expensive than “switch now” — and the bill arrives all at once.
Does your platform charge extra for connecting one?
Sometimes — and the answers surprise people. The domain itself is a registrar bill; what your platform charges to let you use it is a separate line. All rows checked July 28, 2026; pricing decays, so verify before deciding.
| Platform | Custom domain on the free tier? | Platform fee for connecting | Note |
|---|---|---|---|
| Substack | Yes, free publications included | $50, one-time, per publication | Substack’s own announcement |
| GitHub Pages | Yes | None | Free HTTPS included |
| Vercel | Yes, on the free Hobby plan | None | Up to 50 domains per project — but Hobby is personal, non-commercial use only |
| Netlify | Yes, with SSL | None | Per Netlify’s own pricing page |
| Shopify | No free tier exists at all | No fee beyond the domain itself | Any paid plan; entry level is now Basic — the cheap Starter plan is closed to new stores |
| Notion | No — free plan gets notion.site only | Paid plan required, plus $8/mo (annual) or $10/mo (monthly) per domain | The standout compounder |
| Beehiiv | Its own pricing page says yes | None | Third-party writeups conflict — verify |
| Ghost(Pro) | No free tier (trial only) | Included on paid plans | — |
| Squarespace | No free plan (trial only) | No extra fee; annual plans bundle a free domain for year one | Year-one bundle — see “free” domains below |
| Wix | No — free plan is user.wixsite.com/site | Paid plan required | Per support pages; couldn’t fetch current pricing directly |
| WordPress.com | No — free plan is yoursite.wordpress.com, with ads | None beyond the plan; annual plans bundle a free domain for year one | Aggregator-corroborated — verify |
(Linktree also gates custom domains behind a paid tier — reporting converges on its top Premium tier, and its own custom-domain help page 404s at the time of writing, so check pricing directly before you count on a cheaper plan.)
The pattern: where a platform gates the feature, either the connection is free but you must already be a paying customer for other reasons, or there’s a specific charge for the connection itself. Several gate nothing at all — GitHub Pages, Vercel, Netlify and beehiiv host you free and connect your domain free.
Notion is the row worth re-reading. Eight dollars a month sounds modest until you notice it stacks: paid plan first, then $8/month (billed annually; $10 monthly) per connected domain on top. The connection alone runs at least $96 a year — somewhere between five and ten times the price of the domain it connects, depending on your registrar. If your project lives on a free Notion site and matters enough to deserve a custom address, the domain question quietly doubles as a platform question.
Substack’s structure deserves the opposite callout. Fifty dollars once, not per year — less in year one than Notion’s connection fee alone, and less over a couple of years than a legacy registrar’s renewals on the domain itself. Per the redirect section above, it also appears to be the same purchase that decides whether your old links survive your departure. An unusually honest way to charge for a feature.
When is the free subdomain genuinely the right call?
Often. We sell domain-name generation, which makes this the section to hold us to — the cases where we think you shouldn’t buy, stated as plainly as the ones where you should.
Pure hobby projects. The entire portability argument assumes there’s something to port. No audience to protect and no accumulating links means there is nothing the domain insures. If it unexpectedly matters later, you start the clock then — skip the purchase without guilt.
Unvalidated experiments. If you genuinely don’t know whether the thing survives past month three, spending nothing and accepting a possible migration cost later is economically correct, not negligent. Domains are cheap insurance — but insurance on something you’re not sure will exist next quarter is optional, not obviously wise. If you’d rather run the test with a real address from day one, that’s the workflow in naming for validation — a middle path, not a requirement.
Developer portfolios on username.github.io. For a technical audience — hiring managers, fellow developers — the platform subdomain is arguably a positive signal: legible evidence you can use git and CI, which a bespoke domain doesn’t prove and can even obscure. That’s our argument, not a study finding, but it’s the one audience where the free address reads as competence rather than thrift.
Academic and personal pages. An institutional or platform subdomain can carry more implicit trust than a personally registered domain, because it implies a vetting the personal domain doesn’t: a university page says someone let you in; yourname.com says you paid a registrar.
Substack, if the network is why you’re there — except that trade-off doesn’t exist. The strongest-sounding argument for staying on you.substack.com is the discovery machine: Substack’s own product blog put Recommendations at more than 34 million subscriptions across the platform back in October 2024 — the platform’s marketing number, not independently audited, and stale besides, but the mechanism is real. The catch: as far as anyone outside Substack can tell, it isn’t an argument for the subdomain at all. Substack doesn’t document how custom domains interact with Recommendations either way — so don’t take our word for it, because debunking this myth plainly serves our interest. Look at the evidence instead. Astral Codex Ten, Noahpinion and The Free Press all run on custom domains, all are still served by Substack, and all remain conspicuous inside its network. That’s the check we’d want a sceptical reader to run on us: don’t stay on the subdomain to protect a network the domain doesn’t appear to threaten.
If your project fits this section, not buying is the right decision, and the leaving-later table above will still be here on the day that changes.
What about “free” domains?
Two different traps share the label, and they fail in different ways.
“Free forever” TLDs have collapsed once already. For years, Freenom gave away registrations on five country-code TLDs — .tk (Tokelau), .ml (Mali), .ga (Gabon), .cf (Central African Republic), and .gq (Equatorial Guinea). Then Meta sued — filed December 2022, withdrawn and re-filed in March 2023 in Northern California federal court — alleging cybersquatting and trademark infringement tied to phishing abuse on those domains. Within weeks of that first filing, Freenom halted new registrations, blaming “a technical issue.” In November 2023, ICANN terminated Freenom’s registrar accreditation for failing to cure compliance breaches. Then, over roughly seventy-two hours in February 2024, about 12.6 million .tk, .cf and .gq domains — some 98.7% of its resolving inventory — simply stopped resolving; days later Freenom settled with Meta on undisclosed terms and announced it was exiting the domain business entirely. Every site, link, and email address on them: gone, through no fault of the people using them. As of this writing there is no confirmed relaunch of a public free-registration channel for those TLDs (Tokelau’s telecom operator has discussed .tk’s future with the operator of New Zealand’s .nz registry, but nothing has shipped). The lesson isn’t that five TLDs were cursed. It’s that “free forever” meant no one’s business depended on keeping your domain alive — so no one did.
“Free domain with hosting” bundles are a pricing structure, not a scam. The standard shape: the domain is free for year one, then renews at the vendor’s standard rate — commonly somewhere in the $10–35 range depending on the TLD. Same teaser mechanics as any first-year promo, same defence: budget against the renewal. Two mechanics to know before accepting one: ICANN policy locks gTLD domains against transfer to a different registrar for 60 days after registration (and again after a registrant change or prior transfer) — industry-wide, not a vendor trick, and it doesn’t block DNS changes or renewals, only moving registrars. And confirm you’re listed as the registrant, not the hosting company; bundles typically do register you as owner, but it varies, and it’s the difference between owning a domain and holding a coupon.
So which should you do?
Buy the domain and connect it now if any of these are true: strangers find and share your work; you take, or plan to take, money; you need an email address on your own name; or you’re on a platform whose exit story punishes waiting — per the table above, especially Substack without the $50 unlock, and to a lesser degree everywhere that isn’t Shopify. Stay on the free subdomain if you’re in the counter-case section: hobby, unvalidated experiment, github.io portfolio, academic page.
One rule sharper than “it depends”: buying protects the name; connecting protects the links. Registering a domain and letting it sit reserves your brand, but every week of publishing on the subdomain still stacks links against an address you can’t keep. If the project is live and growing, do both together — and on Substack, connecting early appears to be what makes the exit redirect possible at all, with the caveat above that this is reported behaviour rather than documented policy.
If you do buy, spend the first hour well — the first hour after registering a domain is the checklist. And once you own one, a different question eventually opens: whether your next project belongs on a subdomain of the domain you now own, or on a fresh registration — that’s subdomain or new domain, a decision for people who already own domains, which you’ll have just become.
If what’s stopping you is that every name you think of is taken, that’s the part we build for. A Domain Yoga search returns around 250 availability-checked, brandability-ranked name ideas for $2–5 — no subscription, and credits never expire. And if this article talked you out of buying a domain for now, good: the free address is sometimes the right one, and the names will still be here when it stops being enough.