ChatGPT Sites can take a website from a written description to a public page without requiring HTML, CSS or JavaScript. The important distinction is between generating a page that looks complete and launching one that works: the design needs review, a contact form needs an explicit request to save messages, and the finished site needs the right sharing settings.
Start with the pages and a brand asset
In ChatGPT, open the sidebar’s More menu, select Sites, and choose Create Site. This opens Work mode with @Sites already in the prompt box. That command tells ChatGPT to use its website builder; you can also select Sites after typing @. In the example build, the active model was GPT-5.6 Sol Light.
A useful first prompt states the kind of site, its main sections, and the desired look. A sample bakery request called for a homepage, a cookie menu, an about section, a way to make contact, and a warm visual style. A PNG logo was attached before generation. ChatGPT Sites used it to inform the site’s gold, cream, and brown palette.
There is no need to specify every visual detail in the first request. The initial version of this site took about 3 minutes and 57 seconds to generate, after which it could be inspected and revised through further prompts. That timing describes this build, not a guaranteed turnaround for other sites.
Review the first draft before asking for changes
The generated page appeared in a preview beside the chat. A draggable divider gave either the conversation or the site more room, while full-screen mode made it easier to judge the layout. The first draft included a logo and navigation in the header, a prominent opening section, three cookie product cards, an about section, and a contact form. Each displayed cookie price was $4.
▲ Chat and website preview
At this stage, look at what the page actually communicates, not just whether every requested section exists. Check the balance of the opening section, spacing between sections, navigation labels, and whether images help explain what the business offers. Full-screen inspection revealed that the bakery logo appeared too often, including outside the header. It also revealed that the contact form, though visible, was not yet connected to submission storage.
Use follow-up prompts for focused design edits
The next request kept the logo in the top navigation but removed repeated copies elsewhere. It also asked for realistic photos of freshly baked cookies that matched the products. ChatGPT Sites then replaced a logo badge in the opening section with a cookie photo, added distinct images to the product cards, and placed another baking photo in the story section. The images were sourced and positioned through the request rather than manually searched for, resized, and placed.
For a product-focused page, that change may make the offer clearer than repeating a brand mark. The practical lesson is to give specific feedback: identify what should stay, what should go, and what should take its place. Then inspect the new version rather than assuming the revision solved every layout problem.
Make the contact form work, then verify it
A form’s appearance does not establish that it can receive messages. In this build, a separate prompt asked ChatGPT Sites to make the contact form functional and store submissions for later review. The update took about 37 seconds and added form validation, error handling, success alerts, and persistent storage. Persistent storage means submitted information remains available for the site owner to view later.
The form was then checked from the website preview in a separate browser window. A sample inquiry produced a success confirmation. Back in the administrative interface, View saved submissions opened a list containing the entry, its timestamp, sender details, and message. That end-to-end check matters more than seeing a send button on the page: it confirms that a message reaches the place where the owner expects to find it.
Set access and choose an address
Once the design and form are ready, the Share control is available in the chat interface or through the site’s menu on the Sites dashboard. The sharing setting initially says Only those invited. To let other people open the site through its public link, change it to Anyone with the link. Open that link in a regular browser tab to check the published page outside the editing interface.
Site settings also provide a name and URL path. The assigned address ends in .chatgpt.site, and its subdomain can be changed. Alternatively, Add Custom Domain lets an owner connect a registered domain. The service supplies DNS records—settings that direct the domain to the site—and connection steps. The exact changes needed at a domain registrar may vary, so that part still requires the owner to follow the instructions for their registrar.
Check traffic after launch
The Sites dashboard includes an Analytics option in a site’s menu. It shows unique visitors, total page views, traffic trends, and top pages, with time ranges such as 7 or 30 days. The example dashboard displayed 1 unique visitor and 51 page views. These are figures from that site, not a prediction of traffic for a new one. The analytics appear basic, but they offer a quick way to check activity without setting up an external tracking script.
▲ Contact submissions and traffic metrics
What to do next
For a personal project or small business page, begin with a concise description and any available logo. Treat the generated site as a draft: inspect it, request precise changes, explicitly enable and test any form, and only then make it accessible through a public link or connected domain. After launch, use the built-in analytics to see whether people are reaching it.