What does ChatGPT Sites actually cost?
ChatGPT Sites has no separate price tag. It is bundled into paid ChatGPT plans, so the real cost is your subscription plus the beta usage limits attached to it. There is no per-site fee, no hosting invoice, and no free tier access.
Sites is OpenAI's built-in website and web app builder. You describe a site in chat, ChatGPT generates and hosts it, and you get a shareable production URL, with no separate deployment workflow to set up.
The pricing question that matters is therefore not "how much is Sites" but "which plan do I need, and what stops working when I hit a limit". Those are the two things that decide whether this replaces a real hosting setup or just supplements it.
The extractable facts, as published by OpenAI:
--- Plan required: a paid ChatGPT plan. Sites is not available on the Free or Go tiers.
--- Rollout order: Pro, Pro Lite, Enterprise and Edu first, then Plus and Business.
--- Reference plan prices: ChatGPT Plus is US$20 per month and ChatGPT Pro is US$200 per month.
--- Usage limits: plan-specific limits apply across all Sites during the beta. ChatGPT displays the current limits and warns you as you approach one.
--- Region: availability depends on plan, region and workspace settings. As of July 2026 it was not available in the EEA, the UK or Switzerland.
--- Hosting and domain: hosting is included. Custom domains are supported where available, but you must already own the domain and be able to edit its DNS records. Sites does not register domains.
--- Analytics: unique visitors and page views are recorded automatically, with no analytics SDK to install.
What happens when you hit the beta usage limit?
Hitting a Sites usage limit does not just slow you down, it changes what you are allowed to do. According to OpenAI's Sites documentation, reaching a limit can prevent you from creating a new Site, adding storage, or keeping a high-usage Site public.
Read that last clause carefully, because it is the single most important line in the pricing story. A popular page can lose its public status because it became popular.
You can still edit and manage existing Sites when you are over a limit. So the failure mode is not data loss, it is availability. Your page stops being visible to the audience you built it for.
For a practitioner running a campaign, that is a real risk to price in. A landing page that goes quiet mid-campaign costs more than the US$20 you saved on hosting.
Is ChatGPT Sites cheaper than Framer, Webflow or Carrd?
If you already pay for ChatGPT, Sites is cheaper, because the marginal cost of one more page is zero. If you do not, a dedicated builder is usually cheaper for pure landing pages, because you are not buying a whole AI subscription to get a hosting feature.
The honest comparison is not about money, though. It is about what each tool is built to guarantee.
Where ChatGPT Sites wins: speed from idea to live URL, no deployment setup, built-in traffic analytics without an SDK, and optional Sign in with ChatGPT for identity-aware pages. It also handles internal tools and dashboards, not just marketing pages, which most page builders do not.
Where the dedicated builders win: Framer ships its AI tools on every plan and is the faster path to a polished, design-led marketing page. Webflow is the stronger choice when the site is content-heavy, needs to scale to many pages, or has to compete on technical search and AI-citation visibility. Carrd remains the cheapest way for one person to get a functional single page online.
So the verdict splits by buyer:
--- You already pay for ChatGPT Pro or Plus and need an internal tool or a fast throwaway page: use Sites. Nothing else is faster.
--- You need a designed marketing site that is the front door of your brand: use Framer or Webflow. Design control and SEO structure matter more than build speed.
--- You need to take payments or run a store: neither Sites nor a chat tool. See the next section, this is a hard policy limit.
--- You are in the EEA, the UK or Switzerland: as of July 2026 Sites was not an option at all.
What can ChatGPT Sites not be used for?
Sites carries explicit policy and technical limits, and several of them will disqualify it outright for commercial work. These are published restrictions, not opinions, so check them before you plan around the tool.
No payments and no commerce. OpenAI's documentation states that Sites must not be used to process payment-card data or to enable financial transactions. That rules out checkout flows, paid bookings and any store front. If your interest is in AI-mediated buying, that is a different architecture entirely, which we covered in what agentic commerce actually is.
No Protected Health Information. Also explicitly prohibited, which removes clinic and medical use cases.
No data residency at launch. The documentation states Sites does not support data residency or inference residency at launch, and that this covers deployed Sites, site code, D1 and R2 storage, generated artifacts and logs. For a Hong Kong business with client data-handling commitments, that is a compliance conversation, not a footnote.
Every deployment URL is production. There is no staging environment by default. If you want to review a build before it is live, you have to explicitly ask ChatGPT to save a version without deploying it.
Custom domains are not available in Enterprise workspaces at launch, and analytics are not available for Sites owned by an Enterprise workspace. The plan that costs the most has the fewest of these two features.
Framework support is partial. Some frameworks, private networks, databases, background services and hosting patterns are not supported. An existing project may simply not be deployable.
Will AI assistants and Google cite a page you built this way?
Hosting your page is not the same as being findable. A Sites page is served from an OpenAI-managed hosted domain unless you attach a custom domain, and it inherits none of the search authority or structured-data discipline that gets a page quoted in an AI answer.
This is the cost line nobody puts in the comparison table. Publishing is now nearly free; being retrievable is not.
AI-generated pages commonly fail on the same mechanical points: heavy client-side rendering that leaves crawlers with a near-empty page, missing XML sitemaps and indexing settings, thin internal linking, and no structured data for an answer engine to lift. None of those are fixed by the page looking good.
If the page exists to win customers who ask an AI assistant rather than type a query, the page has to be readable, quotable and structurally sound. That is a separate job from generating it, and it is the job that decides whether the page earns anything.
How do you check whether your page is actually visible to AI?
Check it before you spend on traffic. UD's UDomain AEO Auditor runs a free Answer Engine Optimization scan of a live URL and returns an AI visibility score with a prioritised fix list.
What the free scan includes, verified on the product page:
--- Price: HK$0. Completely free.
--- Card required: no credit card, no account, no sign-up. Enter a URL.
--- Speed: results in under 30 seconds for most sites, up to about 60 seconds for complex ones.
--- Coverage: ChatGPT, Google AI Overview, Perplexity, Claude and Gemini.
--- Depth: 170+ AEO structure checks, scored out of 172, plus JSON-LD coverage, internal linking, citation signals and peer comparison.
--- Output: an AI visibility score, brand-mention monitoring across major AI engines, and a prioritised action plan.
--- Email: used only to open the full dashboard and optional follow-up analysis. No charges, no auto-billing.
--- Timeline expectation: UD states structural changes are typically re-crawled within 2 to 4 weeks, while citation and authority signals accumulate over 1 to 3 months.
Run it on whatever you publish, whether that is a Sites page, a Framer page or your existing site. The score tells you whether the page is a real asset or a URL nobody will ever be pointed to.
Where does UD's own tool fall short?
The AEO Auditor is a diagnostic, not a fix, and being honest about that matters more than the pitch. Here is what it does not do.
It scores structure, it does not rewrite your site. You get a prioritised action plan. Implementing it is still your work, or a paid engagement.
It cannot promise a citation. The published figures on the product page, roughly 80% average visibility lift after AEO work and up to 3× conversion on AI-cited traffic, are UD's own aggregate numbers, not audited third-party benchmarks. Treat them as directional.
It needs a public URL. A Site restricted to your workspace, or one that has lost public status because of a usage limit, cannot be scanned meaningfully.
It does not price the deep work. UD publishes no fixed rate for consultant-led AEO and SEO implementation. You have to ask.
Who should skip it: if your page is a private internal dashboard, or a temporary campaign URL you will delete in three weeks, AI visibility is irrelevant and the scan tells you nothing useful. Spend the twenty minutes elsewhere.
For the neighbouring decisions, we have separately compared what the main AI writing tools really cost, which is the other half of most content budgets.
The next step, in one line
If you already pay for ChatGPT and need a page live today, use Sites, and treat the beta usage limit as your real availability risk. If the page has to be found, scan it before you promote it.
The build is the cheap part now. Being the answer is the part worth paying attention to.
We know AI's cold edges. We know your real challenges. 28 years with UD, turning technology into a partnership with warmth.
Reviewed by the UD AI team.
See Whether AI Can Find Your Page
Run a free 30-second scan, no card and no sign-up, and see how your page scores across ChatGPT, Gemini, Perplexity and Google AI Overview.
If the report shows work to do, we'll walk you through every step, from structured data to internal linking to a citation strategy that holds up.
