Can ChatGPT Build a Website? What ChatGPT Sites Does and Doesn't Do
Yes, even for free: ChatGPT writes the code on any plan and GitHub Pages or Cloudflare Pages hosts it free. Plus and above add ChatGPT Sites. Steps and limits.
Can ChatGPT build a website? Yes, and you can do it for free. On any plan, including Free, ChatGPT can write a site's code and copy, and a free static host such as GitHub Pages or Cloudflare Pages can publish those files on its own subdomain. On paid plans, ChatGPT Sites can also build, publish and host the site at a chatgpt.site address. It doesn't register domains, run every framework or take payments natively, and it won't do the content work a business site needs after launch.
Updated November 20, 2026: added what Netlify's free plan covers and what happens when a site hits its limit, read from Netlify's pricing page, as a third free host for a site ChatGPT wrote.
We checked OpenAI's help center and release notes on November 6, 2026. Our tools couldn't open those pages, so we worked from search-result excerpts of them plus news coverage, and we say where sources disagree. We didn't build a Site for this article. We make PolyDraft, a different kind of tool, and explain it near the end.
Key takeaways
- Free route: ChatGPT's Free plan can write the HTML, CSS and copy, and GitHub Pages or Cloudflare Pages can host a static site free on their own subdomain. A custom domain costs a registrar's fee, and every later change means editing and uploading files again.
- Plans: as of November 6, 2026, ChatGPT Sites is on Plus, Pro, Business, Enterprise and Edu plans. Free and Go don't include it.
- Timeline: Sites was previewed in Codex for Business, Enterprise and Edu workspaces on June 2, 2026, and opened as a public beta in ChatGPT on July 9, 2026. Co-editing, and view-only sharing with people outside a workspace, followed in September.
- Cost: hosting is included with Plus and Pro, within plan-specific usage limits that OpenAI says may change during the beta. Building and editing count toward your Codex usage.
- Not included: domain registration, frameworks and hosting patterns outside the Sites runtime, native payments, and health or card data.
- Fit: Sites suits a small interactive site, a prototype or an internal tool. A marketing site whose content keeps changing needs more than that.
Can ChatGPT build a website for free?
Yes. ChatGPT's Free plan can write the files for a small static website, meaning the HTML, CSS, small scripts and the copy, and you can publish it at no cost on a free static host such as GitHub Pages or Cloudflare Pages. The free route has three conditions: the site lives on the host's subdomain unless you pay for a domain, a plain static site has no database or server code, and every change means editing the files and uploading them again. ChatGPT Sites, which builds and hosts a site inside ChatGPT, isn't included on the Free or Go plans as of November 6, 2026.
Free hosts for a site ChatGPT wrote (limits as documented on November 16, 2026)
| Free host | Free address | What it serves | Free-plan limits | Good for |
|---|---|---|---|---|
| GitHub Pages | username.github.io | Static files from a GitHub repository; free for public repositories on GitHub Free | Published site up to 1 GB; soft limits of 100 GB bandwidth a month and 10 builds an hour. GitHub's terms say Pages isn't intended as free hosting for online businesses, ecommerce or commercial SaaS. | A personal, portfolio or project site |
| Cloudflare Pages | project.pages.dev | Static files uploaded as a folder or zip in the dashboard, or built from a Git repository | Free plan: 20,000 files per site (1,000 when you drag and drop in the dashboard), 25 MiB per file, 500 Git builds a month, 100 custom domains per project. Cloudflare now suggests Workers for new projects; Pages still works for a simple static upload. | A small business or brochure site you want to upload without using Git |
Netlify also has a free plan. As of November 20, 2026, its pricing page lists Free at $0 with a 300-credit monthly limit covering production deploys, compute, form submissions, bandwidth and web requests, and says the free plan's monthly limits are hard limits that can't be exceeded or cost anything. When a site reaches them, it pauses until the next billing cycle, and if one project goes over, every project on the account pauses. Form submissions count against those credits, so Netlify can receive a simple contact form itself, and its page offers deploying by dropping a file, folder or zip. New projects start private until you publish them.
How to build and publish a free website with ChatGPT
- Ask for plain files. Describe the pages, what each must say and who the site is for, and ask for plain HTML and CSS with no build step, as separate files named
index.html,styles.cssand so on. Any static host can serve that. - Save the files in one folder. Copy each code block into a file with the name ChatGPT gave it, and keep images in the same folder.
- Check it on your computer. Open
index.htmlin a browser, click every link, and check every fact ChatGPT wrote. A contact form needs a third-party form service, because a static host has nowhere to store submissions. - Upload it. On Cloudflare Pages, create a project and upload the folder or a zip of it. On GitHub Pages, create a public repository, upload the files, and turn on Pages in the repository settings.
- Connect a domain (optional, paid). Buy one at a registrar and add it in the host's settings. On Cloudflare Pages, a root domain such as example.com must use Cloudflare's nameservers; a subdomain such as www.example.com only needs a CNAME record.
- Set up search basics. Give each page its own title and description, add a sitemap and robots.txt, and verify the site in Google Search Console. Our robots.txt generator writes the crawler file.
What's free and what isn't. Writing the code on ChatGPT's Free plan, within its usage limits, and hosting a static site on GitHub Pages or Cloudflare Pages cost nothing. A custom domain, ChatGPT Sites (Plus and above), a database or server code, and paid form or email services cost money. The biggest cost is time: a free hand-built site has no editor, so whoever changes the content later has to edit code.
What it can genuinely do
Given a clear description, a general assistant will produce a working single page: semantic HTML, a responsive stylesheet, small interactive behaviours, and copy that reads like a person wrote it. It will write meta titles and descriptions, produce valid JSON-LD, draft a robots.txt and a sitemap, and explain any of it when you ask. In a chat, the Preview option on supported code blocks shows an HTML page or React component without leaving ChatGPT. For a one-page site with fixed content, that genuinely covers the creative work.
It is also a good editor. Pasting an existing page and asking what is unclear, what is unsubstantiated, or which heading does not match its section produces useful answers. None of this is in dispute, and the point of this article is not to talk you out of it.
Four ways to build a website with ChatGPT, compared with a website builder
There are four ChatGPT routes to a website, and they differ mainly in who hosts the result and who can edit it later. A chat gives you code to paste elsewhere. ChatGPT Sites builds and hosts the site for you. Codex, OpenAI's coding agent, writes a full project you deploy to a host of your choice. A conventional website builder such as Squarespace, Wix, Webflow or Framer gives you an editor and hosting, and you write the content. If that route suits you, our guide to beginner website builders compares how easy each is to start and what it costs later.
| ChatGPT chat (code blocks) | ChatGPT Sites | Codex plus your own host | Website builder | |
|---|---|---|---|---|
| Writes code and copy | Yes | Yes | Yes, across a whole project | Varies; most now add AI writing or page generation |
| Hosts the site | No; preview only | Yes, on OpenAI's runtime | No; you choose and pay for a host | Yes, on the vendor's hosting |
| Your own domain | Wherever you host it | Connect one you already own; Enterprise depends on admin settings | Yes, through your host | Yes, on paid plans |
| Database | No | Yes, up to 10 GB per Site | Whatever you set up | Usually a CMS or forms, not a general database |
| Several editors | No | Yes: the owner adds editors; OpenAI's help describes them as members of the owner's workspace | Through your code repository | Yes, seats vary by plan |
| Editing without code | No | By asking ChatGPT; no separate content editor documented | No | Yes, a visual editor and CMS |
| Leaving with your work | You already have the code | Not described in the documentation we could read | You own the repository | Varies; often limited |
| What you pay | Nothing on the Free plan (or your paid plan); free static hosts such as GitHub Pages or Cloudflare Pages cost nothing | Your paid plan, within usage limits | Your plan plus hosting | A monthly subscription |
The table reflects OpenAI's documentation as of November 6, 2026 and describes website builders in general. Check the specific builder you're considering.
What ChatGPT Sites does, and what it still doesn't
ChatGPT Sites creates, previews, publishes and hosts interactive websites and lightweight apps from a conversation, and its limits are those of a hosted product. It has been available longer than many guides suggest:
| Date (2026) | What happened |
|---|---|
| June 2 | Sites previewed in Codex for ChatGPT Business, Enterprise and Edu workspaces, for internal tools shared inside the workspace. |
| July 9 | Public beta in ChatGPT. Pro, Pro Lite and Edu got it first, then Plus over the following days. Business and Enterprise workspaces could publish publicly. Not offered in the UK, the EEA or Switzerland at launch. |
| August 20 | Plus and Pro owners can change a Site's chatgpt.site address; the old address redirects. |
| September | Build Together: invited people can edit and publish the same Site. Business and Enterprise owners can also share a Site with named people outside their workspace as view-only guests, without publishing it publicly. |
As of November 6, 2026, according to OpenAI's help center:
- Storage. Each Site's database holds up to 10 GB. Files have no fixed per-Site limit.
- Usage. Plus and Pro have no fixed limit on the number of Sites, but usage and storage limits still apply, and a shared limit can stop you creating new Sites. Building and editing count toward Codex usage, while hosting usage (traffic and storage) is tracked separately. Builders that bill this way differ in the details; our Lovable pricing breakdown shows how one of them meters credits and hosting. Enterprise hosting charges are currently waived, within the same kind of limits.
- Sharing. New Sites are private. You invite specific people, or publish publicly. In Enterprise workspaces, public publishing stays off until an admin enables it, and roles decide who can create and publish.
- Ownership of settings. Editors can change and publish a Site after the owner's first publish. Only the owner manages access, the name and address, secrets and custom domains, and OpenAI advises giving edit access only to people you trust.
What it still doesn't do:
- It doesn't register a domain. You must already own one and be able to change its DNS records. Sites connects it; the purchase happens at a registrar. OpenAI's older help text said custom domains weren't available in Enterprise workspaces at launch, while its current workspace guide describes them where an admin has enabled them, so Enterprise users should check with their admin.
- It doesn't run arbitrary stacks. Sites hosts what its supported runtime can serve. OpenAI says some frameworks, private networks, databases, background services and hosting patterns aren't supported.
- It doesn't take payments natively. Payments go through a third-party provider that you set up and maintain, and card data must be handled by that provider, not the Site.
- It isn't for health data. Sites must not handle protected health information.
- Regional availability isn't settled in the sources. At launch, Sites wasn't offered in the UK, the EEA or Switzerland. Several reports say Plus and Pro users there got access on July 20, 2026, but we couldn't confirm that in OpenAI's own documentation.
None of these are shortcomings of the model. They are the boundaries of a hosted product, the same kind of limit every platform has, drawn in a different place.
How to publish a site with ChatGPT Sites, step by step
Publishing with ChatGPT Sites takes five steps, and only the custom domain happens outside ChatGPT. This is the sequence OpenAI's help center describes as of November 6, 2026; button names may differ as the beta changes.
- Describe the site. On a paid plan, ask ChatGPT to build it: the pages, what each must say, any form, and who it's for. Building and every later edit count toward your Codex usage.
- Preview and revise. Review the deployed preview and ask for changes until it's right. Check every fact it wrote.
- Publish. Publishing gives the Site a chatgpt.site address. Plus and Pro owners can rename that address later.
- Choose who can see it. In Share, keep it private, invite specific people, or make it public. In a workspace, your admin's settings decide whether public publishing is allowed.
- Connect your domain (optional). Buy the domain at a registrar if you don't own one, add it in the Site's settings, and copy the DNS records Sites gives you into your registrar. Only the owner can do this.
The work that remains after the site is live
Publishing is the short part; search setup and ongoing operations still sit with you. Search Console verification and sitemap submission happen outside the chat; our SEO checklist for a new website covers both. The site runs on OpenAI's runtime, within its supported capabilities and your plan's usage limits.
The manual path still exists when you need something Sites cannot host: a framework it does not support, a backend pattern outside its runtime, or full control of the serving stack. That's where Codex, or code from a chat, goes to a host you choose. Then the sequence is the old one: choose a host, create an account, upload the build, register a domain, point DNS, provision HTTPS, verify in a search console, submit a sitemap, and set up monitoring. Our robots.txt generator and llms.txt generator produce the crawler files; both are among our free website tools. For one static page this is an afternoon. It stops being an afternoon the moment a second person needs to change the content, because now the workflow requires them to edit code, and that is the real limit, rather than anything about the quality of the generated output.
Is a ChatGPT Site good for SEO?
It can be, but OpenAI's documentation doesn't say how Sites handles the basics search engines need, so check them yourself before you rely on one for search traffic. We haven't tested this. On a published Site, check:
- The text is in the HTML. View the page source, not the rendered page. If the main text only appears after JavaScript runs, search engines and AI crawlers may see less of it.
- Each page has its own title and description, and a single H1 that matches what the page is about.
- robots.txt and a sitemap exist at the root of the address you publish on, and the robots.txt doesn't block crawlers you want.
- One address is the main one. If you connect a custom domain or rename the Site, confirm the old address redirects or names the new one as canonical, so the same page isn't indexed twice.
- You can verify ownership in Search Console. With your own domain you can add a DNS record; on a chatgpt.site address you can't, so check whether a URL-prefix method works.
Our guide to whether AI assistants can read your website covers the same checks for AI crawlers, and our measurements of 46 live sites on website builders show how hosted builders handle them.
Where this path works well
ChatGPT is a good route when the content won't change much or the infrastructure already exists. That covers a single landing page with fixed content (our landing page vs website guide helps you decide when one page is enough), a prototype you need in front of someone today, a component or section for a site that is already deployed, and a rewrite of copy you will paste into an existing CMS. With Sites, the list extends to small interactive tools and internal apps a hosted runtime can serve, such as dashboards, document finders and resource hubs, which is what OpenAI itself positions Sites for. If you're weighing it against paying for a site, our website cost calculator compares the build routes on cost. If a hosted one-page builder would do the job without pasted code, see our Carrd alternatives for one-page sites.
Where it stops working
A chat-driven build stops being the whole answer once the site has to carry a business: content that changes on a schedule, a marketing structure with a page per intent, ecommerce, or an exit where you take the work with you. Sites' runtime supports what it supports. A marketing site with a blog, editors who are not developers, and pages that must stay internally consistent is a content-operations problem, not a prompting problem. Our guide on how to evaluate an AI website builder lists what to test before you commit to any tool.
What to check before you trust generated markup
Two checks are worth running on anything a general assistant produces. First, verify the facts: a model will produce plausible-sounding specifics, and an invented statistic on your own site is your problem, not the model's. Second, verify the technical claims against primary documentation rather than the model's summary of it. Google's structured data guidance requires that markup describe what is actually visible on the page, and generated JSON-LD frequently describes a page that does not exist yet.
What the output is still worth
None of this makes the generated output worthless — it makes it an input rather than a deliverable. A conversation with a general assistant is an unusually good way to get a first draft of the thing most projects actually stall on: what the site should say. Argue your positioning with it, have it draft page copy, ask it to list the objections a buyer would raise, and you finish with a brief that is far more specific than the one you would have written from a blank page. Our guide to the best AI tools for small business compares ChatGPT, Claude, Gemini and Copilot for this kind of everyday work.
The same applies to structure. Asking for a sensible page inventory for your kind of business, or for the questions a service page should answer, produces a plan worth keeping even when none of the generated code survives. Treated that way the exercise costs an hour and sharpens everything downstream, whether the site is then built by a developer, a builder, or you.
The alternative, stated as a position
We make PolyDraft, so treat this as our position rather than a neutral finding. ChatGPT Sites closed most of the gap between generating a site and having one live. What it leaves to you is the marketing work after launch: deciding what to publish from search and AI-search demand, writing it, linking it, and refreshing what stops performing. PolyDraft is an AI-native website marketing system built around that work. As of November 6, 2026:
- It researches the business, writes the copy, and builds a multi-page, server-rendered Astro site that deploys to your own Cloudflare account. Titles, descriptions, structured data, canonicals, a sitemap, robots.txt and llms.txt come with every plan, along with a blog admin and an inquiry inbox a non-developer can use.
- Sites built since November 2026 get a content calendar in their admin, planned from keyword and question data. The GEO sub-queries in it are AI-predicted, not real assistant query data.
- Once the site's Search Console property gives PolyDraft access, its SEO and GEO autopilot uses that data every week to write new articles and refresh the ones that slip.
Every week, the autopilot uses that evidence to decide what to publish or refresh next, and reports what moved.
PolyDraft is the wrong choice for a hosted mini-app or internal tool, where ChatGPT Sites is quicker, and for a store, pixel-level canvas design, or built-in redirects. The full sequence is on how it works, and if you are comparing tools more broadly, our comparison of ten Lovable alternatives covers the category, and our guide to the best AI app builders groups app builders and coding agents by who edits the result.
Frequently asked questions
Can ChatGPT create a website for free?
Yes, for a small static site. ChatGPT's Free plan writes the HTML, CSS and copy, and GitHub Pages or Cloudflare Pages will host the files at no cost on their own subdomain. A custom domain costs a registrar's fee. ChatGPT Sites, which builds and hosts the site inside ChatGPT, needs Plus or a higher plan as of November 6, 2026.
Where can I host a website ChatGPT made for free?
GitHub Pages and Cloudflare Pages both host static sites free. GitHub Pages serves files from a public GitHub repository, with a 1 GB site limit and a 100 GB monthly bandwidth soft limit, and isn't meant for running an online business, store or commercial SaaS. Cloudflare Pages lets you drag and drop a folder or zip of up to 1,000 files. A plain static site on either host has no database or server code. Netlify's free plan also works, within a hard limit of 300 credits a month; a site that reaches it pauses until the next billing cycle.
Do I need to know how to code to build a website with ChatGPT?
Not for a first version: ChatGPT writes the code, and you save the files and upload them. You do need to be comfortable with files and folders, and every later change means asking ChatGPT again and re-uploading. On Plus and higher plans, ChatGPT Sites removes the upload step, because you edit the site by asking ChatGPT.
Can ChatGPT build and publish a website by itself?
On a paid plan, yes, within what the Sites runtime supports. As of November 6, 2026, ChatGPT Sites on Plus, Pro, Business, Enterprise and Edu plans builds, publishes and hosts the site, with its own database and a chatgpt.site address. It doesn't register a domain; you connect one you already own. Free and Go plans don't include Sites, and Enterprise workspaces keep public publishing off until an admin enables it.
Can ChatGPT host my website?
A ChatGPT Site, yes. Hosting is included with Plus and Pro within plan-specific usage limits that may change during the beta, and building and editing count toward Codex usage. It isn't a general-purpose host: only what the Sites runtime can serve will run. Code you generated outside Sites still needs a host that serves it publicly.
When did ChatGPT Sites launch?
OpenAI previewed Sites in Codex for Business, Enterprise and Edu workspaces on June 2, 2026, and opened a public beta in ChatGPT on July 9, 2026, starting with Pro, Pro Lite and Edu, then Plus. Co-editing, and view-only sharing with named people outside a workspace, were added in September 2026.
Is ChatGPT Sites available in the UK and EU?
It wasn't at launch: OpenAI excluded the UK, the EEA and Switzerland from the July 9, 2026 public beta. Several reports say Plus and Pro users there gained access on July 20, 2026, but we couldn't confirm it in OpenAI's documentation as of November 6, 2026. Check OpenAI's help center for your country and plan.
Is a ChatGPT-built website good for SEO?
The markup can be sound, with correct titles, headings and structured data, and a published Site is served rather than sitting in a file. OpenAI doesn't document how Sites handles rendering, robots.txt, sitemaps or canonical addresses, so check those on your own Site. A chat-driven build also doesn't give you a content plan or the ongoing work after launch.
Can it handle a contact form?
In a ChatGPT Site, it should: each Site has its own database (up to 10 GB), so a form can store submissions. We haven't tested one. Check how you get notified of new entries and whether the data handling suits what visitors send. A form in a plain generated file, with no site behind it, has nowhere to put an enquiry.
When is this the right approach?
For a single interactive site or lightweight app the hosted runtime can serve, a quick prototype, or a section added to a site that already exists and is already deployed. It stops being the right approach once the site is a business asset: content changes regularly, non-developers edit it, or the work has to be portable.
Written by Vincent Chen, who is accountable for the claims on this page.
About this article. Drafted by an AI agent following PolyDraft's blog workflow, checked by an automated QA script, fact-checked by a separate AI agent, and approved by Vincent Chen. OpenAI's help center and release notes were checked on November 6, 2026 through search-result excerpts, because our tools couldn't open those pages; news coverage fills in dates the excerpts didn't show. We didn't build a ChatGPT Site for this article. On November 16, 2026 we read Cloudflare's Pages documentation directly and GitHub's Pages documentation through search excerpts, because our tools couldn't open docs.github.com. On November 20, 2026 we read GitHub's Pages limits page and Netlify's pricing page in full through a page-rendering service; GitHub's limits were unchanged. The illustrations are original.
Revision history: November 6, 2026: corrected the publication date to October 8, 2026, when it first went live, and removed an incorrect statement that this article predated the Sites launch.
Sources
New and re-checked sources were checked on November 6, 2026. OpenAI pages were read through search-result excerpts.
- OpenAI Help Center — Creating and using ChatGPT Sites
- OpenAI Help Center — Managing ChatGPT Sites for your workspace
- OpenAI Help Center — Understanding responsibilities for your ChatGPT Sites
- OpenAI Help Center — ChatGPT release notes
- OpenAI Help Center — ChatGPT Enterprise and Edu release notes
- OpenAI Help Center — Working with writing blocks and code blocks in ChatGPT
- OpenAI — ChatGPT Sites Terms
- OpenAI — ChatGPT is now a partner for your most ambitious work (July 9, 2026)
- VentureBeat — Codex update adds Sites for enterprise workspaces (June 2026)
- Android Authority — ChatGPT Sites gets faster and more collaborative (September 2026)
- AlternativeTo — ChatGPT Sites now lets teams co-edit and share privately (September 2026)
- Cloudflare Docs — Pages limits (checked November 16, 2026)
- Cloudflare Docs — Pages Direct Upload
- Cloudflare Docs — Pages custom domains
- Cloudflare Docs — Cloudflare Pages overview
- GitHub Docs — GitHub Pages limits (checked November 20, 2026)
- Netlify — Pricing (checked November 20, 2026)
- GitHub Docs — What is GitHub Pages?
- GitHub Docs — Terms for Additional Products and Features
- Google Search Central — SEO Starter Guide
- Google Search Central — Structured data markup
- Google Search Central — Build and submit a sitemap


