Ship to a Public URL

Why it matters

A product sitting in an AI builder’s preview window is not real yet — it only exists for you. The Make gate is a working thing live at a public URL, because “live” is what makes it testable by anyone, anywhere, without you sitting next to them explaining what to click. This lesson is the moment your project leaves your laptop and joins the actual internet.

Deploying is more mechanical than creative, which is a nice change of pace: you push your project to a host like Vercel or Amplify, or use your builder’s own publish button, and it gives you a working link. Then you connect a domain — a real, memorable web address instead of a long generated one — so the link is something you would actually put in a message to a friend or in your outreach next module.

A parent buys the domain. That is not a suggestion, it is how domain registration works — you need to be an adult to purchase one, and a parent’s name and payment method will be attached to it. Sit down with them for this part; it takes a few minutes.

Once your domain is live, you add analytics: a small, honest way to see if anyone besides you has visited. That number will matter a lot more once you start doing outreach in the Launch stage.

What to watch for

Getting started with Vercel

• Watch for the exact sequence: connect your project, deploy it, then attach a custom domain to the deployment.
• Notice how little configuration is actually required to get from “code” to “live URL.”
• Skip any advanced settings the video mentions that you do not recognize from your own builder; stick to the deploy-and-domain steps.

DNS Explained in 100 Seconds

• Watch for the core idea: DNS is just a lookup table that turns your domain name into the address of your server.
• Notice the mention of records like A and CNAME; you will see these exact names in your registrar’s dashboard.
• Skip trying to memorize every record type; you only need to recognize the one your host tells you to add.

Start with Claude

Deployment errors are usually short and specific. Bring Claude the exact message instead of a general “it’s not working.”

I'm deploying my Make First project to a public URL and connecting a custom domain. Here's my host, my builder, and the exact error or screenshot I'm stuck on: [paste details].

Ask me what step I'm on — deploying the project, buying the domain, or connecting DNS — before you suggest anything, since the fix is different for each. Walk me through what the error actually means in plain language, and ask me to check one thing at a time rather than listing five possible fixes at once. If this is a DNS issue, remind me that DNS changes can take a little while to update, and help me figure out if I've just not waited long enough.

Parent note

A parent needs to buy the domain for this lesson — domain registrars require the account holder to be an adult, and the domain will be registered in their name. Plan for about 10 minutes together: picking the domain, entering payment details, and pointing it at your deployed project.