When You Must Actually Buy a Domain

You can launch on a `*.vercel.app` or `*.web.app` URL for free. So when does an indie site really need a paid domain? Here is the honest answer.

Buying a domain feels like a milestone — but a lot of indie builders buy too early, before they have anything anyone will visit. And some launch on a subdomain forever, then wonder why nobody trusts the site. This walks through when the $12 really matters.

Background

In 2026 every major host gives you a free subdomain — yoursite.vercel.app, yoursite.web.app, yoursite.netlify.app, yoursite.pages.dev. They are perfect for prototypes and side projects nobody will see. The moment you want SEO, email, brand recall, or any kind of monetization, the cost of staying on a free subdomain quickly exceeds the $10 to $15 per year for a real one.

How to tell

  • You plan to submit the site to Google and care about ranking — search engines treat platform subdomains as cohabitants of the host, not standalone sites.
  • You want email at the domain (hi@yoursite.com) — impossible on a free subdomain.
  • You will apply for AdSense, affiliate programs, or any payment provider — most require a custom domain.
  • You are building a brand or product people will refer to in conversation — yoursite.vercel.app is forgettable.
  • You expect to migrate hosts later — owning the domain lets you switch without breaking inbound links or SEO.

Quick verdict

Buy a domain the moment one of: you submit to Google, you accept payments, you advertise the URL anywhere offline, or you plan to keep the project past 90 days. Stay on the free subdomain only for genuine throwaways.

Step by step

  1. Decide your name. A clean .com is the safest. .ai, .dev, .app are fine if .com is gone.
  2. Check availability across registrars — Namecheap, Cloudflare Registrar, Porkbun, Squarespace Domains. Pricing differs meaningfully.
  3. Buy from a registrar that charges renewal close to cost (Cloudflare and Porkbun are usually cheapest). Avoid registrars that low-ball year one and triple year two.
  4. Enable WHOIS privacy at purchase — free at most registrars in 2026, do not pay extra.
  5. Set DNS to point at your host (A record for root, CNAME for www — covered in our DNS articles).
  6. Add the domain to your host (Vercel / Firebase / Netlify / Cloudflare Pages). Wait for SSL provisioning.
  7. Update everywhere the URL appears — Search Console, sitemap, canonical tags, hardcoded references, social profiles.
  8. Set a calendar reminder one month before renewal. Auto-renew is on by default but cards expire.

Common pitfalls

  • Buying a domain before you have something to put on it — pay $12, ship nothing, forget to cancel in year two.
  • Picking a clever spelling that nobody can dictate over the phone — flickr worked once; you are not Flickr.
  • Going for a cheap TLD (.xyz, .online) because .com is taken — spam associations make trust harder to build.
  • Buying from a registrar that does not let you transfer out easily — read the transfer policy first.
  • Forgetting to renew. Domains lapse, then get sniped by speculators, then cost $2000 to recover.

Who this is for

Anyone planning to keep a project alive past three months, market it publicly, or earn money from it.

When to skip this

Pure experiments, internal tools, or weekend hackathons where the URL only lives in your bookmarks.

FAQ

  • How much should a domain cost?: A standard .com is $10 to $13 per year at Cloudflare or Porkbun. .ai is $50 to $80. .dev and .app are $12 to $20. Anything wildly outside those bands is a markup.
  • Should I buy multiple TLDs to protect the brand?: Only if the brand has real value. Most indies are fine with one .com. Buy more later if you take off.
  • Can I transfer a domain after buying?: Yes, after a 60-day ICANN lock from purchase. Get an auth code from the old registrar and initiate transfer at the new one.
  • Is .io still trustworthy?: Yes in 2026, though the British Indian Ocean Territory wind-down created some uncertainty earlier. .com is still safer for long-term branding.

Tags: #Indie dev #Domain #Website planning #Getting started