ChatGPT Sites on a Custom Domain: How to Connect Yours

ChatGPT built you a website, and now you want it at yourname.com instead of a preview link or a platform subdomain. Good instinct: the domain is the part of a website people remember, type, and trust. It is also the part ChatGPT cannot do for you, because connecting a domain happens outside the chat, in the small gap between your domain registrar and your hosting. This guide walks that gap end to end, assuming no prior DNS knowledge.

Why the preview link was never going to be enough

A ChatGPT preview link points at your conversation, not at a place on the internet. Even after you put the site on real hosting, the free address you get is typically a subdomain, your site's name attached to the platform's domain. Subdomains are honest and functional, and for a hobby project they are fine.

A custom domain changes three things that matter the moment the site represents you or a business. First, memory: people can hold maria-bakes.com in their head; nobody retains a platform subdomain. Second, ownership: the domain is registered to you, so you can move hosting later and the address survives, along with any reputation it earned in search engines. Third, signals: an email address at your own domain, a clean link on a business card, a name that looks intentional in search results. None of this makes the site better; it makes the site yours.

Step 1: get the site hosted first

A domain is an address, not a location. Before pointing it anywhere, the site needs to live somewhere permanent, which a chat preview is not. If your site is still inside the conversation, do the hosting step first: the short version is that you either download the files and upload them to a host, or paste an instruction file into ChatGPT and let it publish the site for you. The full walkthrough is in host a website made with ChatGPT, and the mechanics behind it are covered in how AI-hosted websites work.

Once the site answers at its platform subdomain, you have something for the domain to point at, and everything below takes about ten minutes.

Step 2: buy the domain, from anyone

Domains are sold by registrars: Namecheap, OVH, Gandi, GoDaddy, your local providers, hundreds of others. They all sell the same product, since domain names are managed by central registries; the differences are price, interface, and upsells. A .com or a European country extension typically runs 10 to 20 euro a year. Two buying tips: turn on the free WHOIS privacy option if offered, and ignore bundled hosting offers, since your hosting decision is already made.

There is no need to buy the domain where you host. The registrar holds the name; your host serves the site; DNS connects them. Keeping those roles separate is normal and slightly healthier, because it means no single company holds everything.

Step 3: point the domain at your hosting

In your hosting dashboard, add the custom domain to your site. The platform will show you one or two DNS records to create, usually a CNAME record, which is a line in your domain's settings that says "this name points at that hosting". You copy the record into your registrar's DNS panel, which every registrar exposes as a simple form: type, name, value, save.

Then you wait, briefly. DNS changes propagate across the internet in anywhere from a minute to a few hours. There is nothing to do during this window and nothing you did wrong; it is simply how the system distributes updates.

If typing DNS records feels risky, remember you have an unusual assistant here: paste the record your host gave you into ChatGPT along with the name of your registrar, and ask it to walk you through that registrar's specific panel. Explaining exactly this is something it does well.

Step 4: SSL happens for you

The padlock in the browser bar, and the https:// that browsers now demand, comes from an SSL certificate issued for your domain. On modern hosting you do not buy, configure, or renew this: once the DNS record is in place, the platform requests a certificate automatically, usually within a minute or two, and renews it forever after. If your hosting quotes you a price for SSL, that is a sign you are looking at the wrong decade of hosting product.

When the certificate is live, both the platform subdomain and your custom domain serve the same site, and the padlock shows on both.

What it costs, all in

The honest total for a ChatGPT-built site on its own domain: the domain at 10 to 20 euro per year to the registrar, plus hosting. On AI-Hosted, custom domains and SSL are included in every plan, flat 15, 39 or 129 euro per month including VAT, detailed on the pricing page, with a 14-day free trial that needs no card. There is no per-domain fee and no certificate fee, which means trying this end to end costs you exactly the price of the domain.

Afterwards: the domain stays, everything else can change

The quiet payoff of doing this properly arrives later. Rebuild the site in ChatGPT next month, redeploy it, and the domain keeps pointing at the new version. Outgrow the design, switch templates, even switch hosting providers someday: the address on your business cards never changes, because you own it. That permanence is the whole point, and it is why the custom domain step, small as it is, is the moment a chat experiment becomes a real website.