← Panderr Blog
Website migration

A Custom Domain Is Not the Same as a Portable Website

A custom domain changes your website’s address — not who hosts it, or whether you can take it with you. Domain, hosting, and portability are three different things. Here’s the difference, what ChatGPT Sites documents, and what to check before you build.

Published October 3, 2026

**

A Custom Domain Is Not the Same as a Portable Website**##

A custom domain changes the address. It doesn’t change who hosts the site, or whether you can take it with you.

That sentence anchored a long Hacker News discussion this week about ChatGPT Sites, OpenAI’s prompt-to-published website builder. Underneath the thread’s arguments about prototypes and pricing sat a quieter confusion — one that shows up with almost every website platform, AI-powered or not. Three different things keep getting treated as one:

Domain ownership → hosting → website portability. They are not the same thing, and the differences decide what you actually own.

Three things that are not the same thing

Your domain is an address. It’s a name, registered through a registrar, that you point at things using DNS records. If you bought the domain yourself, you can repoint it — today, tomorrow, whenever. The address is genuinely yours.

Your hosting is where the website actually runs: the runtime, the storage, the servers that answer when someone visits. Hosting is a service, provided by whoever operates that runtime. You don’t own hosting; you use it, for as long as the arrangement lasts.

Your website’s portability is whether the website itself — the pages, the code, the assembled thing your visitors see — exists in a form you can download, keep, and run somewhere else.

A custom domain only touches the first item on that list. Connecting one says nothing, by itself, about the second or the third.

What the ChatGPT Sites documentation actually says

Sites is a useful test case precisely because OpenAI documents it well. Per the official Sites guide and Help Center, ChatGPT can create, host, refine, and share websites and lightweight apps; hosting is managed through Sites, in what OpenAI calls the supported Sites runtime, and every deployment URL is a production URL. The default address is an OpenAI-owned subdomain ending in chatgpt.site.

On custom domains, the documentation is specific: where the feature is available, you connect a domain you already own by copying DNS records from Sites into your domain provider’s settings. Sites doesn’t register domains, and custom domains aren’t available in Enterprise workspaces at launch. That is exactly the address layer working as designed — your name, pointed at their runtime.

On ownership of content, OpenAI’s Sites Terms are equally specific, and fair’s fair: “Website Content is your Content. You retain any ownership rights you have in Website Content.” Your words, images, and material are yours.

Here is the part worth reading twice. As of October 3, 2026, OpenAI’s current ChatGPT Sites documentation does not describe a workflow for exporting a complete Site and moving it to another hosting provider. One documented nuance: a Site can start from a compatible local project on your own machine, in which case the source began life on your computer. For a Site created from a prompt inside ChatGPT — the product’s main path — the documentation describes creating, hosting, sharing, and editing it. Moving it somewhere else isn’t part of the documented picture.

None of this is an accusation; hosted platforms are a legitimate design, and Sites is in public beta, so its documentation will keep moving. It is simply the current, documented state: address — yours. Content — yours. The website as a movable artifact — not addressed.

Why portability matters

Websites accumulate. Pages, posts, search rankings, backlinks, customer bookmarks — over time, a website becomes part of how a business is found and trusted. The address can move whenever you want; DNS sees to that. The question is whether the website itself can come along.

Portability matters whenever someone wants to change platforms, change hosts, or simply have more control over where their website lives. You don’t need a dramatic reason — wanting the option is reason enough.

The other half: websites that already exist

What if you already have a website?

AI has made it remarkably easy to start something new. But many businesses aren’t starting from zero. They already have a website, and it holds years of pages, content, images, links, and search history. For them, the question isn’t how to create a website — it’s what happens to the one they have.

Panderr starts with that existing website. And you can begin inside ChatGPT: Panderr for ChatGPT lets you start a website migration in a ChatGPT conversation — to preserve your website, improve it, or redesign it — then continue in Panderr to preview, edit, and manage the site.

Already have a website? Use @Panderr in ChatGPT to start with the website you already have.

There’s also a separate Panderr WordPress plugin, which starts the same journey from inside a WordPress dashboard — two starting points for the same workflow.

The questions to ask any AI website tool

Before a website becomes load-bearing, five questions, in writing:

  1. Can I download the complete website — files, not screenshots?
  2. Can I run it on a host of my choosing?
  3. Can I move the website to a different host or platform later, without rebuilding it?
  4. Is my domain registered in my own account, under my control?
  5. Is “export” a feature the documentation describes, or a hope?

A platform that answers these well has nothing to fear from the list.

How Panderr is built

Panderr starts from the other end of the problem: the website that already exists. Panderr replicates your website as is.

One transparency note, because this article is asking other platforms for exactly that: Panderr produces a downloadable website you can keep and take to the host of your choice. That’s the portability capability we’ve verified and stand behind today.

The broader publish-anywhere experience — publishing and DNS setup across outside hosts — is still being validated host by host, and we won’t claim it’s finished before it is. The portability promise doesn’t depend on it: the files are the exit. And the files work now.

Websites should be portable. An address you control, content you own, and a website you can carry out the door — all three, not just the first one that gets marketed.

Start with the website you already have.

Enter your URL at panderr.com to see a free preview — no signup required.

Or, in [ChatGPT](ChatGPT.com), use @Panderr to begin a website migration.

FAQ

Is connecting a custom domain the same as owning my website?

No. A custom domain is an address you point at a host using DNS. It doesn’t change where the website runs or whether the website can be downloaded and moved. OpenAI’s own Sites documentation describes custom domains as a DNS connection to a Site that remains hosted by OpenAI.

Can I export or download a website I built with ChatGPT Sites?

As of October 3, 2026, OpenAI’s current ChatGPT Sites documentation does not describe a workflow for exporting a complete Site and moving it to another hosting provider. If you started the Site from a local project on your own machine, that source exists locally because it started there — which is different from an export feature for Sites created from a prompt.

Does OpenAI own the content of my ChatGPT Site?

No. The ChatGPT Sites Terms state that Website Content is your content and you retain your ownership rights in it. Content ownership and website portability are separate questions: owning your text and images is not the same as being able to take the assembled website elsewhere.

What makes a website “portable”?

Three things together: you control the domain, the complete website exists as files you can download and keep, and those files can run on a host you choose. If any one of the three is missing, some part of your web presence stays behind when you leave.

Can I start a website migration from inside ChatGPT?

Yes — that is what Panderr for ChatGPT is for. Add Panderr in ChatGPT and use @Panderr to start with the website you already have — for example, “@Panderr Move my existing website without changing its design,” or ask it to improve or redesign what you have. You then continue in Panderr to preview, edit, and manage the site.

Is Panderr’s ChatGPT plugin the same as its WordPress plugin?

No — they are separate products and separate starting points for the same workflow. The WordPress plugin starts a migration from inside your WordPress dashboard; the ChatGPT plugin starts one from a ChatGPT conversation. Both continue in Panderr.

⸻