How to connect a custom domain to Vercel (and why it matters for AI PMs)

Apr 19, 2026

Most AI builders I know obsess over model choice, evals, and prompt tuning, then ship on a Vercel preview URL nobody remembers. That's backwards.

The domain is the part of your product that survives redesigns, rewrites, and re-platforming. If you want to be taken seriously as a builder, moving a product to your own domain is one of the cheapest credibility upgrades you can make. And yet it's the step most people skip, because it looks like plumbing, not product.

This post is the fix. Half tutorial, half argument for why you should care.

What a custom domain actually is

A custom domain is a web address you own and control: yourname.com instead of yourname.vercel.app. You rent it from a registrar, point it at your hosting provider with DNS records, and everything your users see lives under your brand instead of someone else's.

Why custom domains matter (the AI PM lens)

Ownership beats platform dependency. Vercel is great, but your URL is theirs. If they change pricing, sunset a product, or just go down for an afternoon, your deep links break. A custom domain decouples your brand from your infra. You can migrate from Vercel to Cloudflare to self-hosted without a single user noticing.

Trust signals compound. Users click links more confidently on a real domain. Hiring managers take your portfolio more seriously when it's yourname.com, not a random subdomain. Investors don't take demos on a vercel.app URL past the first meeting. None of this is strictly logical. All of it is real.

SEO and discoverability. Google treats custom domains as authoritative sources. Search results, LinkedIn previews, and shared tweets all show your domain. Over a year, the traffic delta is significant.

Personal brand compounding. Every blog post, project page, and side experiment under one domain builds a single body of work. A scattered graveyard of vercel.app URLs does not. If you're targeting AI PM roles, this compounding is the entire game.

Concrete example: look at the people who land PM offers at AI-first companies. Check their sites. Almost none are on vercel.app. That isn't coincidence. It's signal.

Prerequisites

  • A domain, purchased from a registrar (Namecheap, Cloudflare, GoDaddy, Porkbun, pick whichever)
  • A Vercel account with a deployed project
  • Access to your registrar's DNS settings
  • About ten minutes

Step-by-step

1. Open your project in Vercel. Go to Settings > Domains.

2. Add your domain. Type your domain (yourname.com) and click Add. Vercel will ask whether to redirect www.yourname.com to the root or vice versa. Most modern setups prefer the root and redirect www to it.

3. Copy the DNS records Vercel shows you. For the apex domain:

Type: A
Name: @
Value: 76.76.21.21

For the www subdomain:

Type: CNAME
Name: www
Value: cname.vercel-dns.com

4. Paste those records into your registrar's DNS panel. Every registrar has one. On Namecheap it's Advanced DNS, on Cloudflare it's the DNS tab, on GoDaddy it's Manage DNS. Delete any parked or default records that conflict.

5. Wait for propagation. DNS usually updates within 1 to 30 minutes. Vercel automatically issues a Let's Encrypt SSL certificate once it detects the correct records. You'll see a green checkmark in the dashboard.

6. Verify. Open an incognito window and visit yourname.com. If you see your project, you're done. If not, run dig yourname.com in your terminal or check dnschecker.org to see whether your records have propagated globally.

Quick mental model

[user types yourname.com]
        │
        ▼
[DNS lookup at registrar]
        │
        ▼
[A record points to Vercel's IP]
        │
        ▼
[Vercel matches domain, routes to project, serves site]

Common mistakes

  • Double-proxying through Cloudflare. If your registrar is Cloudflare, keep the proxy status off (grey cloud, not orange) during initial setup. Vercel can't issue SSL if Cloudflare is terminating TLS first. Turn the proxy on later if you want Cloudflare's CDN benefits.
  • Wrong record type on the apex. CNAME doesn't work at the root (@) unless your registrar supports CNAME flattening. Cloudflare does; most don't. Use an A record.
  • Forgetting to delete parked records. Registrars often auto-add a parking page A record pointing to their own servers. Delete it or your domain will resolve to the wrong place.
  • SSL stuck pending. If the cert doesn't issue within 30 minutes, your DNS is still wrong. Double-check the records, then remove and re-add the domain in Vercel.
  • Browser cache weirdness. After everything works, your browser may still show the old site. Hard refresh, or test in incognito.

Pro tip

Decide on a subdomain strategy from day one. Use writing.yourname.com for your blog, talks.yourname.com for talks, api.yourname.com for small tools you ship. You're not cramming everything into a single site. You're building a constellation of projects under one brand, and that's what compounds.

The PM insight

The temptation is to dismiss domain setup as infra work that engineers handle. That's exactly the wrong frame.

Your domain is a surface-area decision. It sits in the same category as naming your product, picking your primary CTA, or choosing your X handle. It shapes how people discover, remember, and link to you.

More importantly, it's a small rehearsal for a much bigger product skill: owning your distribution instead of renting it. AI products today are especially bad at this. Everyone's shipping agents and wrappers on top of OpenAI's plumbing, chasing Twitter traffic they don't own, and skipping the unglamorous work of building a durable brand surface.

The PMs who will win in AI over the next five years are the ones who treat distribution as a first-class product concern, not something the marketing team fixes at launch. A domain is the cheapest, most permanent piece of that surface you can buy. Thirty minutes of work, ten dollars a year, and you've got a piece of the internet that's yours for as long as you renew it.

When you set up your own domain, you're practicing that muscle on yourself. Caring about what users see. Knowing who owns what. Thinking about how things compound over time. The lessons scale directly to the AI products you'll build or manage next.

Conclusion

A custom domain is a thirty-minute task with a multi-year payoff. It's a terrible use of engineering complexity and a great use of product judgment.

Do it once, point every future project at it, and stop renting your credibility from someone else's subdomain.