ChatGPT Sites
Publish your Site and connect your own address.
Your domain, whichever AI built the site
Give customers a clear address for links, QR codes and printed materials, and keep that address when you move hosts or change tools. Choose what you used to build the project.
Claude & Claude Code
Take your web project from an artifact or code to a public address.
Gemini & Google AI Studio
Deploy your web app, then give it a domain you own.
Grok Build & Grok Bot
Connect a domain to your published Grok site or deployed project.
Cursor & Codex
Publish the repository and connect the domain at its host.
Hermes & OpenClaw
Give the web project your agent created a lasting public address.
Lovable, Bolt, v0 & Replit
Use your builder’s publishing route and connect your own name.
Other AI tools
The domain belongs to your project, whichever tool built it.
One domain workflow, different publishing routes
Check names and compare registration and renewal here. Buy the chosen name in your own registrar account. Connect it to the service that publishes your site, using the records that service gives you.
Which service hosts the published site?
The AI builder and the host can be different. Choose the service serving the working public URL; its settings provide the final DNS values. These are setup routes, not records to paste unchanged.
| Publishing host | Subdomain such as www | Apex domain |
|---|---|---|
| Lovable | Use the A and TXT records from the project's manual setup, or its distinct advanced CDN/proxy CNAME route. | Use the root record set provided by Lovable; configure www separately if requested. |
| Bolt Hosting | Use Bolt's CNAME and any ownership TXT shown for the chosen hostname. | Use the ALIAS, ANAME or flattened CNAME record from the Bolt project's DNS instructions. |
| Vercel | CNAME from the chosen host (for example www) to the project's unique Vercel target. | A record with the value shown in this project's domain settings. |
| Netlify | CNAME from the chosen label to the site's Netlify subdomain, or the dedicated target shown for High-Performance Edge. | Use the recommended ALIAS, ANAME or flattened CNAME route when supported, or Netlify's documented A-record fallback. |
| Cloudflare Pages | After associating the hostname in Pages, use the CNAME to this project's pages.dev hostname. External DNS can serve a subdomain. | The apex domain must be a Cloudflare zone in the Pages account, with Cloudflare nameservers. Pages creates its record during setup. |
| GitHub Pages | CNAME to the site's default <owner>.github.io hostname, without a repository path. | Use GitHub's documented ALIAS, ANAME or A records; IPv6 uses the listed AAAA records. |
| Cloud Run / Google AI Studio | Use the chosen load balancer, Firebase Hosting or eligible domain-mapping route and the A, AAAA or CNAME records it returns. | Supported through the chosen route. Copy the console's exact apex record set rather than adapting a www CNAME. |
| ChatGPT Sites | Enter the hostname, then copy the DNS records and verification values the Site provides. The example helper can format owner-reported CNAME and TXT shapes. | OpenAI supports entering an apex domain or subdomain where custom domains are available. The owner's Site settings determine the required records. |
ChatGPT Sites
- Publish. Publish the Site in ChatGPT and check its public link.
- Connect your domain. Open Site settings → Add domain and copy the records and values this Site supplies for the apex or subdomain. Our example helper formats owner-reported CNAME/ALIAS and TXT shapes and checks public DNS; current Site instructions take priority.
- Check the result. Open the final address over HTTPS and test the real order, booking, enquiry or app action.
Read the step-by-step guide · Open DNS helper
Official references: ChatGPT Sites help
Claude & Claude Code
- Publish. For a web project, use its available publishing route or export the HTML/project files and deploy them on a compatible host. Check the public deployment before connecting the address.
- Connect your domain. Add your domain in the publishing host’s domain settings, then copy that host’s DNS records to your registrar. For example, a project deployed on Vercel uses Vercel’s domain settings.
- Check the result. Open the final address over HTTPS and test the real order, booking, enquiry or app action.
Official references: Claude artifacts and export · Vercel custom domains
Gemini & Google AI Studio
- Publish. In Google AI Studio, deploy the web app to Cloud Run or sync its project to GitHub and deploy on a compatible host. For code created in Gemini or Gemini CLI, use the project’s chosen hosting service.
- Connect your domain. For Cloud Run, follow Google’s custom-domain route, such as a load balancer or Firebase Hosting. If another host serves the app, use that host’s domain settings and DNS records.
- Check the result. Open the final address over HTTPS and test the real order, booking, enquiry or app action.
Official references: Build and deploy in Google AI Studio · Cloud Run custom domains
Grok Build & Grok Bot
- Publish. Grok Build Mode can publish a website to a grok.me link or a custom domain. For a project built by Grok Bot or the Grok coding tools, deploy the resulting code on its chosen host.
- Connect your domain. For a Build Mode publication, use the custom-domain option and the records it provides. For a separately deployed project, add the domain in that host’s settings and use its records.
- Check the result. Open the final address over HTTPS and test the real order, booking, enquiry or app action.
Official references: Grok Build Mode publication and domains · Vercel custom domains for a separately hosted project
Cursor & Codex
- Publish. Use the project’s existing deployment setup, or deploy its repository on a host that supports the stack, such as Vercel, Netlify or Cloudflare. Test the deployed customer action.
- Connect your domain. Add the purchased domain in the hosting project. Copy the host’s DNS records to the registrar, wait for verification, and open the address over HTTPS.
- Check the result. Open the final address over HTTPS and test the real order, booking, enquiry or app action.
Official references: Deploy a project on Vercel · Add its custom domain
Hermes & OpenClaw
- Publish. Have the agent deploy the generated web project to a host compatible with its files and runtime, using the owner’s project and account.
- Connect your domain. Use the deployment host’s custom-domain settings. Keep the same domain when changing the AI agent or moving to another host by updating its DNS records.
- Check the result. Open the final address over HTTPS and test the real order, booking, enquiry or app action.
Official references: Example deployment workflow · Example custom-domain setup
Lovable, Bolt, v0 & Replit
- Publish. Publish using the builder’s supported deployment route, or export/sync the project to a compatible host. Confirm the app works at the deployment URL.
- Connect your domain. Add the domain in the service that actually hosts the published project and follow its current domain settings, DNS values and plan requirements.
- Check the result. Open the final address over HTTPS and test the real order, booking, enquiry or app action.
Official references: Custom domains for a Vercel-hosted project
Other AI tools
- Publish. Identify whether the result is a static site, a web app with a backend, or already a hosted publication. Publish it using a host that supports that runtime.
- Connect your domain. Choose a name here, buy it in your own registrar account, then add it at the publishing host. Use the records that host supplies and verify the live address.
- Check the result. Open the final address over HTTPS and test the real order, booking, enquiry or app action.
Official references: Example custom-domain setup
For the agent building the site
Read the full website workflow. Platform routes are also available as JSON, with hosting and DNS routes. Choose the publishing host before requesting DNS values: the ChatGPT Sites TXT helper is specifically for ChatGPT Sites.