Published
8 MIN READ
ChatGPT Sites: Can It Be Your Company Website?
ChatGPT Sites is the OpenAI feature that creates, hosts and publishes a lightweight website or app from a ChatGPT conversation. It works well for prototypes, internal portals, reports and event pages. As a company's main website, it runs into beta limits, hosting rules and responsibilities the terms leave with whoever publishes.
The feature appeared in preview on June 2, 2026, inside Codex, and entered public beta on July 9. On September 11, OpenAI said users had created more than 5 million Sites in three months, according to Runtimewire's coverage of the announcement. The number is about creation: it doesn't say how many were published or how many are still live.
Most pages on the topic in Portuguese teach the step by step. This article reads the official help docs and the terms of use and translates what they say into a decision for the company. Left out is a different subject, getting cited in ChatGPT answers, which is a problem for your own website, and choosing studios that use AI to build the website.
What does ChatGPT Sites deliver?
A website hosted by OpenAI itself, created and edited through conversation. You describe what you want, attach files, data and links, review a private preview and publish. The result gets its own address, which can be a subdomain ending in chatgpt.site or a domain of yours, when the feature is available for the account.
The OpenAI help center, updated in early October 2026, lists dashboards, project tracking, launch calendars, prototypes, internal portals and reports as uses. A Site can store data and files and have a login.
Access requires a paid plan: the beta covers Plus and Pro accounts and ChatGPT workspaces, and doesn't reach Free or Go. At Wama, AI goes into code and automation, with Claude Code and Framer's agents, and every result gets a human read before it goes to the client. In Sites, the person who asks for the change is the same person who approves and publishes it.
What do the terms leave with whoever publishes?
Almost everything that happens after publishing. The ChatGPT Sites terms, updated on July 23, 2026, say the content remains yours, but that you grant OpenAI a license to host and display that content to the extent needed to operate the service.
In exchange for ready-made hosting, you take on five commitments:
Responsibility for the whole website: content, visitors, login, operation and whatever is promised to users.
Indemnification: if a third party complains about your Site, you defend and indemnify OpenAI.
Personal data: you're the controller of what the website collects, the role LGPD (Brazil's data protection law) assigns to whoever decides on the processing. Transparency, consent controls and a privacy policy, when the law requires them, are on you.
Sales only through a third-party processor: the Site can't process card data or facilitate financial transactions on its own. Orders, delivery, refunds, support and taxes stay with you.
Attribution: OpenAI may show a notice in the website's footer or bar saying it runs on ChatGPT.
This package resembles what weighs on a product you assemble alone in an AI builder: what LGPD demands when data leaks from a SaaS built with AI applies here too, if the Site has a form or a login.
Where the beta weighs on a company's day to day
In three areas a corporate website can't afford: usage limits, publishing without a safety net and editing without approval.
Usage limits. The help docs warn that, when you hit a beta limit, you may be unable to create a new Site, add storage or keep a heavily used Site available to the public. The limits apply to the total of all Sites on the account and may change during the beta. For the page receiving your paid media campaign, that means the website going down on the worst possible day.
Publishing without a safety net. Every deployment URL is production. There's no separate test environment: to review without touching what's live, you have to save a version and only then deploy. Deleting a Site is permanent, with no restore.
Editing without approval. The owner can give a colleague edit permission. After the first publish, that editor publishes new versions to the same URL with no approval step from the owner. On a company website, the path is different: separate whoever publishes content from whoever touches the design, as the CMS content editor, who publishes without touching the layout, does, and test AI-made changes before they go live, as in the roles and review of Framer AI on an already published website.
At Wama, people who only publish content get the content editor role and change the website through the CMS, without touching the design.
Domain, data and leaving the platform
The content is yours, but the account, the hosting and the keys stay with the person who created the Site in ChatGPT. Only the owner manages who has access, changes the name or URL, transfers ownership and configures secrets and the custom domain.
A custom domain is possible where the feature exists, with three conditions: you must already own the domain, Sites doesn't register a domain for you and setup goes through DNS records. In Enterprise workspaces, custom domains weren't available at launch, and public publishing comes turned off until an admin enables it.
Two points matter for a company with a data policy. Sites offers no data or inference residency at launch, which includes code, database, files, artifacts and logs. And on Plus and Pro plans, the conversations in which the website is created may train models if the improve-the-model option is on; on Business and Enterprise plans, not by default.
The help docs don't document exporting the code or migrating the Site to other hosting, nor do they cover Google indexing. That doesn't prove it's impossible, but it's what a website contract needs to answer in writing before signing. On Wama projects, when the contract ends the website, the domain and the account are in the client's name, billed to their card, and whoever switches vendors takes everything with them.
When ChatGPT Sites works and when it doesn't
The more a website depends on brand, customer data and continuity, the less the beta fits it.
Use | Does ChatGPT Sites work? | Why |
|---|---|---|
Prototype to validate an idea | Yes | Fast, disposable, no brand commitment |
Internal dashboard or portal | Yes | It's the first use OpenAI describes |
Short event page | It depends | Works if the traffic fits within the beta limit |
Company corporate website | Not a fit | Usage limits, footer attribution, no documented exit |
Page receiving paid media | Not a fit | A heavily used Site can go offline to the public |
Store or billing | Only with a third-party processor | Orders, refunds and taxes stay with you |
Health or card data | No | Prohibited by the help docs and the terms |
Reading the table matches the way Wama declines and routes projects. When the client requires owning the code, the project goes to custom development with the code in the client's name. A logged-in area or portal becomes a digital product project. A store with its own checkout is something Wama doesn't take on, and refers to another vendor.
What does a company website need that Sites doesn't cover?
Predictability on four things: who owns it, who approves, how much it costs per year and what happens if the tool changes. ChatGPT Sites handles creation and day-one hosting well.
Before choosing, ask for these in writing:
Which account does the website live in, and who can transfer it?
Who approves a change before it goes live?
Where is the data of people who fill out the form, and who is the controller?
How does the website leave the platform, if that's ever needed?
How much does it cost to keep the website running per year, adding up plan, tools and changes?
The last question is answered in detail in the cost of maintaining a website after delivery, and the upfront investment is covered in how much a professional website costs in 2026.
At Wama, a corporate website takes 4 to 6 weeks, in the US$ 2,000 to US$ 8,000 range. AI sped up building, not deciding: the total timeline didn't change, and the time saved goes into polish. That's the part a website generated in a conversation doesn't replace, as shown in what changes in a corporate website project.
Frequently asked questions
Is ChatGPT Sites free?
There's no separate price, but the feature requires a paid plan. The public beta covers Plus and Pro accounts and ChatGPT workspaces, and isn't available on Free or Go. Usage counts toward each plan's limits.
Can I use my own domain on ChatGPT Sites?
Yes, where the feature is enabled. You need to already own the domain and change the DNS records to the values Sites provides; it doesn't register a domain for you. At launch, custom domains weren't available in Enterprise workspaces.
Can I sell through ChatGPT Sites?
You can, as long as it's through a third-party payment processor that you connect and maintain. The July 23, 2026 terms prohibit the Site from processing card data or facilitating transactions on its own. Orders, delivery, refunds, customer support and taxes are the publisher's responsibility.
Who is responsible for the data collected on the website?
Whoever publishes. The terms say you're the controller of the personal data the Site collects, through forms, login or cookies. It's up to you to provide transparency, consent controls and a privacy policy when the law requires. Hosting is with OpenAI; responsibility is with you.
Can a website made with ChatGPT Sites go offline?
Yes, in three situations. A heavily used Site can stop being available to the public when the account hits a beta limit. OpenAI can remove or restrict Sites at risk of violating its policies. And in Business and Enterprise workspaces, the admin can deactivate the Sites created there.
If your company wants a website that stays in its own name, with review before every change and an annual cost known from the proposal, talk to Wama.
