ChatGPT Sites as Your Business Website? Read This First

You can now type "build me a website for my plumbing company" into ChatGPT and get a live URL a few minutes later. That is ChatGPT Sites, and it is genuinely impressive. It is also a public beta with a fine-print page that reads like a list

You can now type "build me a website for my plumbing company" into ChatGPT and get a live URL a few minutes later. That is ChatGPT Sites, and it is genuinely impressive.

It is also a public beta with a fine-print page that reads like a list of reasons not to run your business on it. So here is the fine print, read for you.

OpenAI built a website tool and then listed what it is for

ChatGPT Sites lets you create, preview, publish and share interactive websites and lightweight apps from inside ChatGPT Work. It is in public beta. It is not available on Free or Go, and workspace admins can switch it off.

Per runtimewire's report of an OpenAI thread on X from September 11, users have created more than 5 million Sites in roughly three months. Read that as a creation count. It does not say how many were published, how many are still alive, or whether a single visitor ever came back.

Now look at what OpenAI itself says to build. The help article's examples are dashboards, project trackers, launch calendars, prototypes, internal portals and reports. There is not one example of a plumber, a dentist or a bakery.

That is not an accident. It is a product aimed at the thing a team needs for Thursday's meeting, not the thing a stranger finds on Google at 9pm with a burst pipe.

Where it earns its keep

We are a web agency, so let us be fair to the tool. It is excellent at three jobs.

• A throwaway page. A one-off landing page for a trade show, a menu for a pop-up, an event schedule.
• An internal tool. A request tracker for your crew or a document finder for your office, behind a login and shared only with your workspace.
• A prototype you show a designer. "Make it look like this" beats a three-page brief.

For all three, speed beats polish. And all three have an audience you control, which matters in a moment.

If you are weighing the bigger question of doing it yourself or hiring, we covered the full cost picture in build your website yourself or hire someone. This post is narrower: what does this one new tool actually promise?

The address, the domain and the DNS homework

A published Site gets a chatgpt.site address. OpenAI's developer guide shows one: goblin-tales.openai.chatgpt.site. You will not put that on a van.

A custom domain is possible where available. But Sites does not register one for you. You must already own the domain, copy the DNS records it gives you and paste them into your registrar.

Custom domains are not available in Enterprise workspaces at launch. For a one-person shop that is a non-issue. For a franchise with a corporate ChatGPT plan, it is the end of the conversation.

Your domain is the one asset on a website you actually own. Keep it at your registrar, in your name, whatever you build on top of it.

The beta limits sit on the exact thing a marketing site needs

Here is the sentence that matters most. OpenAI says that if you reach a beta limit, you may be unable to create a new Site, add storage, or keep a high-usage Site publicly available. You can still edit and manage existing Sites.

Read the last part of that again. "Keep a high-usage Site publicly available."

A marketing website has one job: be public, all the time, especially when it works and traffic climbs. A tool that may restrict public access exactly when a site becomes popular is built for experiments, not for the page that carries your phone number.

The limits are plan-specific, they apply across every Site on your account, and OpenAI says they may change during the beta. The docs name no numbers. ChatGPT shows them in the product.

Every deployment URL is a production URL.

— OpenAI Help Center, Creating and managing ChatGPT Sites

That line is from the same help article, and it deserves a second look. There is no staging by default. Unless you save a version without deploying it, an edit you approve is an edit your customers see.

Editors can publish later versions without a separate owner-approval step. So if your nephew has "Can edit" access, he can push to the live site at midnight.

Payments, forms and patient data are three separate problems

This is where small businesses get hurt, so slow down.

Payments. The help article says you can sell goods or services through a third-party payment processor, and that you are responsible for connecting it, plus fulfillment, refunds, support and taxes. The developer guide, in its list of uses not to attempt, says not to use Sites to "enable financial transactions."

Personal data. OpenAI says Sites must not process Protected Health Information or payment-card data. For anything else, it puts the privacy-law duty on you. If your Site has a contact form, a booking form or an open-text field, you are the one deciding what is collected, who sees it and where it goes.

A dental practice, a physio clinic or a law firm with a "tell us what happened" box is on the wrong side of that line before the first visitor arrives.

Residency. Sites does not support data residency or inference residency at launch. That covers the deployed Site, its code, its database and file storage, and its logs. If you serve EU or UK customers and your contracts or your own policies care where data lives, "none yet" is a complete answer.

A site that can be taken down, and a chat that can train a model

Two more lines from the help article, both easy to miss.

First, OpenAI may remove or restrict a Site if there is a risk it violates OpenAI policies or platform safety requirements. There is an appeal route, by email link or a form. Appeal is not the same as a guarantee. Your lead source now has a landlord who can pause it.

Second, training. For Free, Go, Plus and Pro users, OpenAI says it may use your conversations to train its models if "Improve the model for everyone" is on. That explicitly includes conversations where you create, design or edit a Site. For Business and Enterprise customers, it does not by default.

So if you paste your price list, your client names and your supplier terms into a personal Plus account to "build the site," that conversation falls under the consumer rule unless you changed the setting. We wrote about the wider version of this problem in shadow AI and client data in ChatGPT. A website build is a very efficient way to feed it.

What the docs never mention is how anyone finds you

Neither OpenAI page I read says a word about search engines, sitemaps, page metadata or SEO. I searched both for the terms. That is not proof Sites cannot rank. It is proof nobody at OpenAI is promising it.

The built-in analytics count unique visitors and page views, and they are not available for Sites owned by an Enterprise workspace. That tells you how many people arrived. It does not tell you where they came from, which page converted, or whether a search engine has indexed you at all.

A website that wins local searches needs real work: service pages that match what people type, a clean structure, fast load, schema, a Google Business Profile that agrees with it. We lay that out in local SEO for small business. And a growing share of your visitors are now AI agents rather than people, which is the subject of is your website ready for AI agents.

None of that is a prompt. It is a build, then a habit.

How we would split the work

Disclosure: Bunny Honey Club builds websites for a living. We have an obvious interest here, so judge this section accordingly.

Our honest view is that ChatGPT Sites is a good tool and a poor home. Use it for the first draft, the internal dashboard and the Friday event page. Do not make it the one place your phone number lives.

Here is the split we would give a client today.

1. Prototype in ChatGPT Sites if you like. It costs an afternoon on a plan you may already have, and it gives us a clear picture of what you want.
2. Build the real site on hosting you control, on your own domain, registered in your name.
3. Put forms and payments on providers whose terms are not in doubt, with the data going where your policies say it goes.
4. Treat SEO as part of the build, not a plugin you add after launch.

We have built 100+ websites. Our first prototype lands within 24 hours of the brief and delivery inside five days, with Lighthouse performance at 95 or better. Once, a client who had been quoted eight weeks by a traditional agency got a full five-page site from us in under 48 hours.

We bring that up for one reason. The hard part of a website was never getting something on a screen. ChatGPT Sites has solved that, inside a chat window you may already pay for. The hard part is everything after the screen.

If you want the lead-generating version of a website, we will build it for you.