Move a ChatGPT-built website to YaDominios Cloud (ChatGPT Sites)
Updated: 2026-08-22 · YaDominios
Two things have to be true before your domain shows the site, not one: the DNS records in place (we handle that), and — inside ChatGPT — the site shared with «anyone on the internet». A new ChatGPT Sites page starts out PRIVATE, visible only to its owner, which is why the most common error is a domain that answers with a valid padlock and still says «Not Found». To move it to YaDominios Cloud: ChatGPT has no export button, so ask it in the same chat to hand over the site's files, push them to GitHub, and connect them in the dashboard.
Just want your domain to show that site, without moving it? Then the guide you want is How to connect a domain to a ChatGPT Sites website: it's a few DNS records and you're done. This guide covers the other thing — bringing the site onto hosting of your own.
Where your ChatGPT site lives today
ChatGPT Sites is in public beta and comes with the Plus, Pro, Business, Enterprise, and Edu plans. You ask for a website, it builds one, and it hosts it: it doesn't just write the code, it puts it online.
You open it from More → Sites, or directly at chatgpt.com/sites. Every address it hands you is a real, live deployment.
One thing is worth knowing up front: while the site lives there, it depends on that plan. OpenAI's own documentation says it plainly — hitting a usage limit can stop you from «keeping a high-usage Site public». Moving it to hosting you control is what makes it genuinely yours.
Problem number one: valid padlock, but it says «Not Found»
This is the one that catches everybody, because everything looks right: the domain answers, the security padlock closes, and visitors still get a «Not Found». And it's almost never the DNS.
The cause is nearly always the same: the site is private. A new ChatGPT Sites page starts out visible only to its owner (and workspace admins). Connecting a domain does not make it public — those are two separate settings. Until you switch it to «anyone on the internet», the whole world gets a «Not Found», including you if you open the domain in another browser.
Here are the three symptoms and what each one means:
| What you see in the browser | What's missing | Who does it |
|---|---|---|
| «Server not found», or nothing responds | The DNS records aren't in place yet, or haven't propagated | Us. Takes minutes to a couple of hours. |
| Red security warning / invalid certificate | Go back to the site's settings and refresh the domain status | The site owner |
| The padlock works, but it says «Not Found» | Change who can see the site to «anyone on the internet», and refresh the domain status while you're there | The site owner |
Watch out for one trap in reasoning: the padlock doesn't prove there's a site behind it. The certificate is issued as soon as the DNS records validate, and that can happen before the site is actually bound to the domain. Padlock plus «Not Found» means your DNS is perfect and whatever's missing is inside ChatGPT.
And if the site lives in an Enterprise workspace, two more warnings apply: public publishing is off by default and only an admin can turn it on, and custom domains aren't available on that kind of account at all.
Connecting your domain, step by step
This is the official procedure. Steps 1, 2, and 4 are done by the site owner; step 3 is ours.
- Open the site's settings and select Add domain.
- Enter the apex domain or subdomain you want to use.
- Copy the list of DNS records it shows you and send it to us. We'll have it in place the same day, without touching your email. You won't have to paste anything by hand.
- Wait a few minutes, go back to the settings, and refresh the domain status. Without that step, validation never finishes.
- And the one that isn't on their list but decides everything: in the sharing options, set the site to visible to anyone on the internet. Without this, none of the rest matters.
ChatGPT doesn't register domains: you have to own yours and be able to change its DNS records. If the domain is with us, that part is already handled.
⚠️ What you CAN and CANNOT do today
Status as of August 22, 2026. We're putting it this plainly because a lot of wrong information is circulating, and because we'd rather tell you what exists than promise something that doesn't.
| ✅ YES | Version control, but inside ChatGPT Sites. It saves versions of your site and you can ask it to list earlier ones or roll back to one. |
| ✅ YES | Publishing the site and having it live at the address ChatGPT gives you. |
| ✅ YES | Using your own domain, via the DNS records ChatGPT provides. That's what this guide covers. |
| ❌ NO | Exporting the site directly to a GitHub repository. We found no official confirmation that this feature exists: OpenAI's public documentation doesn't describe it. |
| ❌ NO | So we won't promise you that you can download your site and take it to GitHub. If someone assures you otherwise, ask them to show you where OpenAI says so. |
How we checked. On August 22, 2026 we went through these eighteen questions one by one against both of OpenAI's official sources: their help center and their developer documentation. Anything not confirmed in either one is marked here as unconfirmed. And yes, the two sources differ in depth: if an answer really matters to you, both are worth reading.
What does exist inside Sites: saving versions of your site, reviewing them, and rolling back to an earlier one, plus — on workspace accounts — inviting colleagues as editors who can save and publish changes. That's real version control and real collaboration, but all of it happens inside ChatGPT.
This can change, and we hope it does. The day OpenAI documents an official way to export a site or connect it to your own repository, we'll update this section. Until then, you'll only read what's confirmed here.
Our opinion, stated plainly: your site being unable to leave is not a minor technical detail. It means the only copy of your website lives in a subscription account. We think anyone should be able to take their work into version control of their own — it's standard professional practice everywhere else in the industry — and we'll keep asking for it through the channel OpenAI keeps open for exactly this, the support chat at help.openai.com. If you also think you should be able to take your own work with you, ask for it there too: a thousand customers asking counts for more than us asking alone.
Official sources for this section: Creating and managing ChatGPT Sites (help center) and Sites (developer documentation).
Moving it to YaDominios Cloud
First, plainly: ChatGPT has no «export» or «download my site» button. It isn't in their documentation. So the route depends on how your site was built.
If you built it on the ChatGPT website (the normal case)
There's no folder on your computer — the documentation is explicit: starting a site on the web requires no local project at all. Everything lives on OpenAI's servers.
The only thing you can try today is asking ChatGPT itself, in the same chat where it built the site. And we'll call it what it is: a workaround, not an official feature. It isn't an export, it's a manual copy — undocumented, unguaranteed, and it may not hand you everything:
Give me every file for this site in one copyable block:
the HTML, the CSS, the JavaScript, and the list of images it uses.
I want them complete, so I can publish them on another host.If what it hands you is complete, that's your website: push it to a public GitHub repository, connect it at yapanel.yadominios.com/panel/cloud, and it goes live at yourname.sitios.dev with free HTTPS. If you'd rather not deal with that, send us the files and we'll do it.
And if it doesn't come out complete, don't blame anyone: that's where things stand today. For a brochure site it usually works fine. For one with a database, user accounts, or forms that store things, the honest assumption is that it gets rebuilt: send us your current site's address, we use it as the model, and we build it here from scratch — yours and versioned from day one.
If you built it from a project on your computer
Then you do have the folder, with a hidden .openai folder inside containing a hosting.json file. That folder is your website: push it to GitHub and connect it in the dashboard. If it's an app that needs building (Next.js and similar), add the build action and connect the yapanel-build branch — full steps in the technical guide.
What moves and what doesn't
| Part | Moves? | Details |
|---|---|---|
| Design and all copy | Yes, completely | It's ordinary code. It arrives exactly as it was. |
| Images and files | Yes | They move into your site's storage. |
| The database | Yes, with one extra step | The data has to be pulled out and loaded into your site's database. |
| Sign in with ChatGPT | No | That button only exists inside ChatGPT. If your site uses it, it has to be replaced with your own login. |
| Editing from the chat | No | After moving, you edit the files and push them. In exchange, nobody can switch your site off. |
Limits worth knowing first
While the site lives on ChatGPT: the database goes up to 10 GB, file storage has no fixed cap, and there are plan-specific usage limits — hitting one can stop you from creating new sites, adding storage, or keeping a high-traffic site public. Their documentation also warns that some frameworks, databases, and background services aren't supported, and that it can't be used to process health or payment-card data, or to enable financial transactions.
None of those limits follow the site once it moves here.
Frequently asked questions
The padlock works but the page says «Not Found». Is my DNS wrong?
Almost certainly not. The most common cause is that the site is still private: a new ChatGPT Sites page is visible only to its owner until you change the permission to «anyone on the internet». Connecting a domain doesn't make it public — those are two separate settings. Also check that you refreshed the domain status in the settings.
Can I download my site from ChatGPT?
There's no export or download button; it doesn't exist in their documentation. What does work is asking ChatGPT itself, in the chat where it built the site, to hand over the HTML, CSS, JavaScript, and images. With those you can publish it anywhere.
Will you add the DNS records for me?
Yes. If the domain is with us, send us the list ChatGPT gave you and we'll have it in place the same day, without touching your email. You won't have to paste anything by hand.
Will connecting the domain break my email?
Not if it's done properly. Email records are separate from website records and are left untouched. We never delete an email record when connecting a website.
Why move it if it works where it is?
Dependency and limits. While it lives on ChatGPT, your site depends on you keeping that plan, and hitting a usage limit can leave you unable to keep it public. Here, the site is yours, on your domain, with no third-party subscription in the middle.
I have an Enterprise account and I can't find the connect-domain option. Why?
Because custom domains aren't available in Enterprise workspaces, and public publishing is off by default there — an admin has to turn it on. That's a ChatGPT restriction, not a problem with your domain.