Build and Launch a Website with AI
Connect your own domain to an AI website (2026): choosing a platform URL or custom domain
Start with a published AI website. Using v0 and Netlify, choose its address, add a domain, enter DNS records and check HTTPS, redirects and public access.
Once an AI website is published, you can use your own domain by adding it to the hosting platform and entering its supplied records at your DNS provider. After verification and working HTTPS, put the new address on your résumé, business card or social profile.
The steps below start from a published site and use v0 and Netlify as examples. If the page is still an editor preview, publish it first. Publishing an AI-generated webpage as a link
| Purpose | Starting option | What to manage |
|---|---|---|
| Friends testing or internal review | The project's production platform URL | Permissions and whether recipients can open it |
| Long-term portfolio or brand | A domain you control | Renewal, DNS, primary address and redirects |
| Adding a portfolio beside an existing site | An unused subdomain such as work.example.com | Confirm it is not used by another service |
A platform address works for initial feedback. A domain lets you retain your public address when a portfolio is on a long-term résumé or you later move hosting. Migration still needs domain setup and checks that page paths and links remain accessible.
Domain and hosting may have separate bills. Check renewal prices, custom-domain support and the hosting plan's permitted uses before buying. Personal website budget guide
Using the documentation domain example.com, example.com is the root domain, while www.example.com and work.example.com are subdomains. Each can point to a different service.
If the root already hosts your company site, choose an unused work.example.com for the portfolio. Check existing DNS names before adding it to the project, keeping changes focused on the portfolio address. Replace documentation examples with your own domain.
Prepare the hosting project's panel and the actual DNS provider's console. Registration and DNS may be on different platforms. If unsure, check current nameservers in the registrar panel and find the corresponding DNS service. Save existing records before editing for verification or recovery.
For a v0 project, open Customize Domain from Publish, or use Settings → Domains in the project menu. Enter the public domain and follow the prompt to the Vercel project's Domains page to check DNS. For a portfolio subdomain, select only that address. v0 custom-domain documentation
For Netlify, add a custom domain under Domain management → Production domains. Open Pending DNS verification to see project-specific records. Netlify handles the root and www together and may list both when you add one. If either already serves another purpose, check the intended address first. Netlify external DNS documentation
Match type, name and value individually in the DNS console. Targets can differ between projects, so copy your own project's instructions.
| Field or type | Meaning |
|---|---|
| Name / Host | To connect work.example.com, a panel managing example.com often takes work. Some accept a full address; inspect the saved final name. The root commonly uses @ or an empty field. |
| A | The platform-specified IPv4 address. |
| CNAME | The supplied target hostname, including any project-specific target. Omit protocol and webpage path. |
| TXT | A supplied ownership-verification record. Website access still requires the appropriate pointing record. |
With external DNS, Vercel usually requests A for an ordinary root and CNAME for subdomains. Netlify roots may also use ALIAS, ANAME or CNAME flattening if supported. Follow project instructions and DNS capabilities. Vercel domain configuration · Netlify root-domain configuration
For conflicting A, AAAA or CNAME records pointing to an old service, establish whether that service must remain available first. Email MX, email verification and unrelated business records usually do not concern this change. With the existing DNS provider, change only required records. For a nameserver change, copy existing records to the new provider first and verify websites and email afterward.
Return to the platform's domain page after saving. If verification remains pending, compare type, name and value, then allow time for DNS caches. Networks can temporarily see different results.
When the domain and certificate are ready, open the new HTTPS address in a logged-out browser and over mobile data. Follow a visitor's actual path:
- Open the homepage and at least one project detail and confirm the correct site version.
- If the root and
wwware both configured, test both HTTPS URLs and confirm intended redirects reach the chosen primary address. - Check images, downloads and contact buttons. For existing login or forms, use test data and ensure redirects or submissions do not remain on the old domain.
- Only after validation, update the résumé and social profiles to the primary address.
| Symptom | First checks |
|---|---|
| Invalid records in the panel | Active DNS provider, duplicated domain in the name and target belonging to this project |
Only the address with www works | Both root and www added to the project, records completed and HTTPS enabled |
| Old website opens | Current DNS and old records, caching and the project associated with the domain |
| Certificate warning | Domain verification, certificate status, target records and proxy requirements |
| Domain opens but visitors see login | Production deployment access protection and visitor permissions |
With Cloudflare DNS, proxy status changes the request path. If hosting requires direct DNS verification, follow its guidance on temporarily setting the relevant record to DNS only; limit changes to that record. Cloudflare proxy status
After launching, record the primary address beside the domain renewal date. Keep updating the same hosting project and validate mobile pages and public access through the primary address. Portfolio launch and update checklist