How do you publish a reliable website with ChatGPT Sites?

You want a small calculator that estimates the monthly value of time saved by an automation. A visitor enters minutes saved per task, tasks per week, and an hourly rate. The page explains the formula and shows an estimate without storing personal information.

ChatGPT Sites can turn that brief into an interactive preview and a hosted release. The generation step is only one part of the job. The complete product path includes scope, data decisions, verification, audience controls, version choice, and operations.

Confirm availability and product limits first

OpenAI announced ChatGPT Sites as a public beta on July 9, 2026. As documented on July 15, it was available on eligible paid plans, subject to rollout and workspace controls, and unavailable at launch in the European Economic Area (EEA), Switzerland, and the United Kingdom. Check current documentation before committing a delivery plan.

Sites supports hosted web experiences inside its runtime. OpenAI notes that some frameworks, private networks, databases, background services, and hosting patterns may not be supported. A small client-side calculator fits more naturally than a product that depends on private infrastructure or specialized workers.

The beta also has plan-specific usage limits that may change. Account and workspace settings can control creation and publishing. Confirm that the intended operator can create, publish, and manage the Site before building around it.

Write a calculator brief with a testable formula

A request to build a modern savings calculator leaves the formula and data behavior undefined. Write the product contract in the same structured way as a good prompt. Give Sites a bounded outcome and tell it what must remain outside scope.

Audience: Operations leads evaluating one repetitive task.
Inputs: Minutes saved per task, tasks per week, hourly rate.
Formula: minutes × tasks × 4.33 ÷ 60 × hourly rate.
Output: Monthly time saved and estimated labor value.
Rules: Reject negative, blank, and non-numeric values.
Privacy: Calculate in the browser and store no entered values.
Non-goals: Accounts, uploads, payments, analytics, or email.
Checks: Mobile layout, keyboard use, reset, and formula examples.

The constant 4.33 represents average weeks per month for this illustrative estimate. Explain it beside the result so visitors can judge the assumption. Do not label the output as guaranteed savings or financial advice.

Review the private preview as a candidate

OpenAI says ChatGPT can generate a Site, provide a private preview, and refine it through feedback. Use that preview to inspect structure and behavior before deployment. It is an editable candidate, not production evidence.

Start with one known example. Ten minutes saved across 30 weekly tasks equals five hours per week. At an hourly rate of $40, the displayed monthly estimate should be $866 when rounded to whole dollars using the stated 4.33 factor.

Check the page hierarchy, field labels, units, formula explanation, reset behavior, and result announcement. Give feedback about one observed mismatch at a time. If the calculator uses four weeks instead of 4.33, name that difference and require a regression check for the known example.

Save a version after the flow behaves as intended. OpenAI's documentation distinguishes saved versions from deployments. Review the saved candidate you intend to release rather than relying on the latest conversational state.

Test calculations and failure states

Use boundary values, not only one pleasant example. Submit zeros, decimals, large valid numbers, negative values, blank fields, spaces, copied currency symbols, and letters. The calculator should either produce a defined result or show a specific correction without losing valid fields.

Check rounding at each stage. Prefer calculating with unrounded values and rounding only the displayed result unless the brief defines another rule. Confirm that reset restores the documented initial state and that a stale estimate disappears after input becomes invalid.

Test keyboard order, visible focus, labels, error associations, and result announcements. Use narrow and wide viewports and zoom the page. Reload after entering data to confirm that the no-storage requirement holds.

Open browser developer tools and inspect storage and network activity. The calculator's formula may run locally while other scripts still send telemetry. Document the complete behavior rather than extending a local-calculation claim to the entire Site.

Review audience, access, and forms separately

A new Site begins with limited access until the operator changes its sharing settings. Available options can include owner and admins, selected members or groups, the workspace, or anyone on the internet. Public availability also depends on workspace policy and permission.

Choose the smallest audience that meets the calculator's purpose. Test the Site while signed out and, where relevant, as an invited visitor. Confirm that the selected audience and any sign-in feature inside the Site produce the intended experience.

Our calculator stores no entries and needs no account. If a later version adds email capture, uploads, or sign-in, treat that as a new data flow and release decision. Review collection, purpose, retention, deletion, access, and notices before enabling it.

OpenAI's help content says to review forms, uploaded files, links, generated content, and interactive behavior before publishing. The ChatGPT Sites Terms also leave responsibility for the Site with its operator. Generated notices do not replace an accurate review of the implementation.

Release the reviewed version deliberately

OpenAI states that every deployment URL is a production URL. Select the saved version, confirm the audience, and publish only after the release checklist passes. Visit the resulting URL as the intended audience and repeat the known calculation.

Record the release time, version, audience, formula, owner, and checks. Keep a link to the previous reviewed version where the product supports version management. Share the URL only after confirming that production matches the candidate.

If you connect a custom domain, you must already control it and update its domain name system (DNS) records. Domain availability and workspace support can differ. Verify the final hostname, transport security, redirects, and link sharing instead of assuming the default URL and custom domain behave identically.

Prepare rollback and takedown operations

A released calculator can contain a wrong formula, misleading copy, broken access, or an unexpected data path. Name the person who monitors reports and can restrict access. Define when to restore a reviewed version, unpublish, or take down the Site.

Permanent deletion is not the first response to every defect. OpenAI notes that deleting a Site permanently removes it and cannot be undone. Restrict access or roll back when a reversible action safely contains the issue, then preserve evidence needed for diagnosis.

Confirm the result after any incident action. A changed sharing setting should block the former audience, and a corrected deployment should replace the faulty behavior. Record what happened, which version was affected, and which checks prevent recurrence.

This operating responsibility resembles controlled vibe coding. AI can generate and refine the interface, but a person still owns requirements, evidence, and release decisions.

Check the calculator before sharing its URL

Use this checklist for the final candidate and production release:

• Current plan, region, workspace, runtime, and publishing limits support the intended use.
• The brief fixes inputs, units, formula, rounding, explanation, privacy, and non-goals.
• Known examples, boundaries, invalid values, reset, reload, and stale-state recovery pass.
• Keyboard, focus, result announcements, zoom, and narrow mobile layout remain usable.
• Storage, network, forms, sign-in, links, and notices match the documented data behavior.
• The selected audience works when tested as the intended visitor.
• A saved reviewed version, owner, monitoring path, rollback, restriction, and takedown process exist.
• The production URL reproduces the approved candidate after deployment.

ChatGPT Sites can compress the distance between a product brief and a hosted interface. It does not compress the responsibility for a production release. Brief, preview, verify, and release should remain distinct stages with evidence at each boundary.