ChatGPT Sites vs a Custom Website (2026)
What ChatGPT Sites can and can't do as of October 2026: payments, databases, domains, SEO and ownership, and when a business site needs a custom build.
As of October 2026, ChatGPT Sites is a good fit for dashboards, internal portals, prototypes and event pages, and a weak fit for a company website that has to take payments through a local gateway, run a content management system, rank in search and stay under your control for years. OpenAI opened Sites as a public beta on July 9, 2026 and has shipped updates almost every month since: sharing with outside viewers on September 3 and editing from the live site, scheduled automations and a profile showcase on September 29. This guide sets out what Sites can and can't do today, according to OpenAI's own documentation, and where a custom build still earns its cost.
What is ChatGPT Sites, and what can it build today?
ChatGPT Sites is OpenAI's in-chat builder that creates, hosts and shares interactive websites and lightweight apps from a conversation in ChatGPT. It has been in public beta since July 9, 2026.
You describe what you want, ChatGPT generates the site, shows you a private preview, and refines it until you publish. OpenAI's own examples are dashboards, project trackers, launch calendars, prototypes, internal portals and reports. In Business and Enterprise workspaces, a Site can also read from connected apps, so a team can build an issue dashboard where each visitor sees data through their own account.
Under the hood, according to OpenAI's developer guide, Sites runs on Cloudflare Workers, with a D1 relational database (up to 10 GB per site) and R2 object storage. HTTP, HTTPS and WebSockets are supported; raw TCP connections are not.
Availability as of October 2026:
- Sites is available in public beta for ChatGPT workspaces, Plus and Pro accounts. It is not available on the Free or Go plans.
- Public publishing and the expanded beta were not available in the European Economic Area, Switzerland or the United Kingdom at launch.
- In Enterprise workspaces, public publishing is off by default and an admin has to turn it on.
- Usage is included up to plan-specific beta limits, which OpenAI says may change during the beta.
The pace of change matters. Between July and the end of September, OpenAI added custom URLs (August 20), named external viewers (September 3), and editing from the published site plus scheduled updates (September 29). Anything in this article, including the table below, is a snapshot.
What can't ChatGPT Sites do yet?
Most early write-ups of Sites were based on the July launch notes, and some of those limits have already moved. Here is what OpenAI's help centre and developer guide say as of early October 2026.
| Question | ChatGPT Sites (October 2026) | Typical custom build |
|---|---|---|
| Where does it run? | OpenAI-hosted, on Cloudflare Workers | Hosting you choose and contract for |
| Database | D1 relational database, 10 GB per site; R2 file storage | Any database, sized to the project |
| Payments | Allowed only through a third-party payment processor you connect and maintain; no handling of card data | Any gateway, including Korean PGs, with server-side confirmation |
| Staging | Every deployment URL is a production URL; save a version and review before deploying | Separate staging and production environments |
| Custom domain | Where available, using a domain you already own; not in Enterprise at launch | Yes |
| Data residency | Not supported at launch | Chosen per project |
| Regions | Public publishing not available in the EEA, Switzerland or UK at launch | No platform restriction |
| Search controls | Not covered in OpenAI's Sites documentation | Meta tags, sitemaps, structured data, hreflang |
| Deleting | Permanent, with no restore | Depends on your backups |
Two points are easy to get wrong:
- Payments are no longer simply "not allowed." The current help article says you can sell goods or services through a third-party payment processor, but you are responsible for connecting, configuring and maintaining it, and for fulfilment, refunds, support and taxes. Sites must not process payment-card data themselves.
- "Some frameworks may not be supported." OpenAI's wording is that frameworks, private networks, databases, background services and hosting patterns that don't fit the Sites runtime may not work. If your project depends on a specific stack or a long-running job, test it before you commit.
Is a ChatGPT Site good for SEO and AI search?
Nobody can answer that with confidence yet, and that is the honest position. OpenAI's Sites documentation, as of October 2026, does not describe controls for page titles, meta descriptions, sitemaps, robots rules or structured data. That doesn't mean a Site can't be indexed. It means you have to check it yourself rather than assume.
If search matters for the site you're planning, check these before you launch:
- Is the content in the HTML? Open the page source (not the browser inspector) and look for your headings and body text. Content that only appears after JavaScript runs is harder for some crawlers to read.
- Can you set a unique title and description per page? Ask ChatGPT to add them, then confirm they appear in the source.
- Can Google fetch it? Connect the custom domain to Google Search Console and run URL Inspection on a few pages.
- Is there a sitemap? If not, ask for one and check that it lists every public page.
- Will the URL last? A site on a ChatGPT-hosted address builds its search history on a domain you don't own. If you move later, plan redirects.
None of this says a builder site can't rank. Plenty of builder sites do well. The question is whether you can see and control the parts that search engines and AI assistants read. On a custom build, those parts are written into the code and can be checked line by line.
Who owns the site, and what happens if you leave?
This is the question to settle before any business site goes on a hosted builder.
- The code. Sites can link a local project and record which Git commit each version was built from, which helps. OpenAI's guide doesn't describe a one-click export of a finished Site as a standalone project. If portability matters, keep the source in your own repository from day one.
- The data. Form entries and records live in the Site's D1 database and R2 storage on OpenAI's platform. Plan how you would get them out before you collect anything important.
- The account. Only the owner can manage access, change the URL, set secrets and connect domains. If that owner is one employee's personal Plus account, the company's site is tied to that person.
- Privacy duties. If a Site collects personal information or uses Sign in with ChatGPT, OpenAI's help article states that you are responsible for complying with privacy and data-protection laws.
Several commenters on Hacker News's "Sites in ChatGPT" thread (350 points, October 1, 2026) raised the same lock-in worry, and others pointed out that a maintained website is an ongoing job, whoever builds it.
When is ChatGPT Sites enough, and when do you need a custom site?
A practical way to decide is to look at what the site has to do in its second year, not on launch day.
| You need… | ChatGPT Sites | Custom build |
|---|---|---|
| An internal dashboard or tracker for your team | Strong fit | Usually more than you need |
| A prototype to test an idea with users | Strong fit | Later, once the idea holds |
| A one-off event or campaign page | Good fit | Optional |
| A company website people find through search | Possible, but you have to check search controls yourself | Search structure is part of the build |
| Online sales with a local payment gateway | Only through a processor you connect and maintain | Gateway integration is part of the build |
| Member accounts, admin screens, staff roles | Limited to what the runtime and sharing model support | Designed around your roles |
| Non-technical staff editing pages for years | Edits go through ChatGPT | A content management system built in |
| Several languages with proper hreflang | Not documented | Standard |
If most of your answers sit in the first three rows, start with Sites and save the money. If they sit in the last five, a custom build is not about taste; it's about owning the parts the business depends on.
What does a custom site add for a company entering Korea?
A foreign company's Korean site usually needs things a general-purpose builder wasn't designed around:
- Korean checkout. Local cards and easy-pay wallets run through a Korean payment gateway, with a merchant contract and server-side payment confirmation. See our guide to Korean payment gateway integration.
- Naver as well as Google. Korea's leading search engine has its own webmaster tool and its own crawler. The steps are in Naver SEO for foreign websites.
- Korean login and messaging. Kakao and Naver login, KakaoTalk notifications and Korean address search are integrations, not templates.
- A decision about scope. Not every company needs a full Korean site on day one. Do you need a Korean website? walks through the options.
What we do on client projects
We are a two-person studio in Korea: the CEO and a director design and build every project ourselves. Our standard way of building is direct code development, mostly in Next.js, with other technologies where a project needs them.
- We build with AI too. We develop and review code every day with Claude Code, an AI coding agent, and a person reviews each change before it ships. So this isn't a case against AI-built sites; it's about who controls the result.
- Search and AI readability are part of the build. This website is our own evidence: page text is rendered on the server so it sits in the HTML, the site publishes structured data (JSON-LD) for the organisation, services and FAQs, it has an llms.txt file describing the company for AI assistants, and Korean and English pages are linked with hreflang. We build that structure; we don't promise rankings or AI citations.
- Editing can stay with you. Where a project needs it, we build an admin area so your team can update page content without going back to a chat or a developer. The pages on this site are edited that way.
- Korean set-up support. We support the Korean-side applications for payment gateways, KakaoTalk channels and Naver Search Advisor. Our English-speaking founder handles consultations and documents directly.
Frequently asked questions
Is ChatGPT Sites free?
No. As of October 2026, Sites is not available on the Free or Go plans. It is available in public beta for Plus, Pro and ChatGPT workspace accounts, with usage included up to plan-specific beta limits.
Can I use my own domain with ChatGPT Sites?
Yes, where custom domains are available. You must already own the domain and add the DNS records Sites gives you. OpenAI says custom domains are not available in Enterprise workspaces at launch.
Can I sell products or take payments on a ChatGPT Site?
Only through a third-party payment processor that you connect, configure and maintain yourself. Sites must not process payment-card data, and you remain responsible for fulfilment, refunds, customer support and taxes.
Will Google index a ChatGPT Site?
OpenAI's documentation doesn't address search indexing as of October 2026. Check the page source for your content, connect the domain to Google Search Console and run URL Inspection before relying on search traffic.
ChatGPT Sites vs Wix: which is better for a small business?
They solve different problems. Sites is fastest when you want something built from a conversation, such as a tracker or prototype. An established website builder offers more mature controls for a marketing site. If you need local payments, an admin area or several languages, compare both with a custom build.
Sources
All checked October 2026.
- OpenAI, ChatGPT release notes: Sites public beta (July 9, 2026), custom URLs (August 20, 2026), external viewers (September 3, 2026), Edit site, automations and profile showcase (September 29, 2026)
- OpenAI Help Center, Creating and using ChatGPT Sites: availability, custom domains, production URLs, payments, data residency and deletion
- OpenAI, ChatGPT Sites developer guide: Cloudflare Workers runtime, D1 and R2 storage, supported protocols, secrets
- Hacker News, "Sites in ChatGPT" discussion, October 1, 2026
Need payments, an admin area or Korean integrations on your site? See how we build on our web services page, then send us your project details or email dwkim@nqsolution.kr. We'll tell you whether a builder is enough or a custom build makes sense.