ChatGPT Sites puts a publish button on five paid ChatGPT plans

Four of the five pages the Wonder Tools writer lists as his own are documents ^[3]. The music theory games for his daughters are the only build in that list that had to be interactive at all ^[3]. He says he has no coding skills ^[3], and his own summary is that the process now feels like making a Google Doc ^[2]. That comparison is more exact than it reads as praise, because those are Google Doc jobs, delivered with a better typeface and a link you can send.

The showcase around them behaves the same way. The builds he credits to other people include a Jenga-like physics game and a playable collection of eight classic video games ^[9]. Good work, but a one-off, with no second release on the calendar.

The bundling claim and the market claim rest on different evidence. Bundling is mechanical and real: the tool sits inside a subscription, and the last step in the described flow is a button that publishes the page or keeps it private ^[11]. The market claim needs figures this account does not carry, and there is no pricing and no count of how many published pages stay live ^[5]. What the evidence shows being displaced is a shared doc and a PDF attachment. The parts a client keeps after a small studio finishes, the domain and the files, are not in the flow at all ^[4].

The strongest comparative signal in the piece is a preference: the writer likes his Sites version of a book group landing page better than the one he built earlier with Claude Artifacts ^[6]. One person, two attempts, and nothing on whether either page is still being read. This account measures time to first draft, not retention of the artifact, which nobody tracked here ^[5].

Two axes sort the candidate pages. First, whether the page has to live at your own domain. Second, whether a named person owns it six weeks from now. Pages needing neither are the honest fit, and an unfinished beta ^[1] costs you very little there. Pages needing the domain but no owner still belong on static hosting, because you will want the URL long after you stop caring about the words on it. Pages with an owner but no domain work internally, provided everyone accepts that the chat thread is now where edits happen ^[4]. Pages that need both belong wherever your team already edits things, because the files do not come back to you ^[4].

What this forces is a rule about who may publish a page under the company's name, and a habit of checking whether the ones already published are still true a quarter later.