Paper Lantern Studio has three offers, but each visitor needs a different answer. A beginner wants to understand a lighting workshop. A returning viewer wants a shot-list pack. A brand wants to judge a collaboration. Putting all three pitches in the same opening can make the next step harder to find.
ChatGPT Sites now gives Plus and Pro users more room to separate those experiences. OpenAI's October 15, 2026 release notes removed the fixed limit on the number of Sites those accounts can create. Usage and storage limits still apply. The useful response is a clear brief for each offer, followed by a deliberate decision about which pages deserve to exist.
| Fictional offer page | Visitor decision | Approved next action |
|---|---|---|
| Desk Light Lab | Is this practical workshop suitable for my desk-video setup? | Open Nina's existing interest form |
| Shot List Starter | Does this pack contain the planning sheets I need? | Review the pack on Nina's existing store page |
| Paper Lantern Collaborations | Does this creator's work suit our campaign? | Open Nina's existing business-contact page |
This is a fictional planning example. Nina, the studio, and the offers are invented; the table does not report working destinations, sales, or conversion results. Each destination would need to be supplied and checked before a real page was shared.
Understand what changed in the Sites limit
The October change concerns how many Sites Plus and Pro users can create. It does not remove the cost of building, editing, running, or storing a site. Do not turn “no fixed site-count limit” into an unlimited-usage claim.
OpenAI's current Creating and using ChatGPT Sites guide says Sites is available to Plus, Pro, and supported Business and Enterprise workspaces. Workspace settings and roles affect access. Building and editing count toward Codex usage, while running and hosting have separate usage.
Check the actual account before planning a portfolio of pages. A shared usage or storage limit can still prevent another Site from being created. The editorial question comes first: does this offer need a different visitor experience?
Separate pages by the decision they serve
Nina's workshop visitor needs the audience, agenda, requirements, and next session details. The pack visitor needs a clear contents preview and an accurate explanation of the files. The brand visitor needs relevant work samples and a direct business-contact route.
These are three distinct decisions. That is a stronger reason for separate pages than having three thumbnail colors or three social captions. A new page should reduce the effort required to understand a specific offer.
Write one sentence above each brief: “This visitor needs to decide whether…” If two briefs produce essentially the same answer, combine them or use a section on an existing page. More pages also mean more places for dates, links, and claims to become stale.
Give every offer its own evidence packet
Before generating a preview, collect the material that supports the page. For Desk Light Lab, Nina supplies an owned desk photograph, a short demonstration, and a three-part agenda: frame the shot, move one lamp, and record the comparison.
For Shot List Starter, she supplies screenshots of the actual sheets, a list of included files, and the existing store description. The page should show what the buyer receives rather than substitute a decorative mockup for the contents.
For collaborations, Nina selects relevant owned work and approved descriptions of her contribution. She leaves out invented clients, audience numbers, testimonials, and campaign outcomes. Missing evidence is a reason to narrow the copy or pause the page, not a prompt for plausible filler.
Build one reviewable preview at a time
Start with the offer that has the clearest materials. Nina could ask: “Build a private preview of a single-page website for the fictional Desk Light Lab workshop. Use only the supplied content and existing interest-form URL. Include the audience, agenda, requirements, and next action. Ask about missing details. Save a version for review before publishing.”
That prompt gives the review a defined object. It does not ask the builder to invent a business, collect payments, or connect an unspecified service. Dates and pricing stay unset until the creator supplies them.
Review the first preview before copying its structure to another offer. A useful workshop page may need a visible agenda; a useful resource-pack page may need a contents comparison. Reuse the studio's visual identity while adapting the information to the visitor's decision.
Test the action behind the page
Read each page on a phone, starting from the same context a visitor will have after a video or profile link. Can someone tell what the offer is without opening three sections? Does the first image support the actual promise? Is the main action easy to distinguish?
Then open the destination. The workshop button should reach the intended interest form. The pack button should reach the correct product and version. The business-contact button should reach the creator's approved contact route.
Record the destination and the person who checked it. If the destination is unfinished, keep the preview private. A polished page cannot fix a broken form, unclear store listing, or contact route nobody monitors.
Budget for maintenance as well as creation
Keep a simple page inventory: offer, owner, destination, last review date, and next review trigger. A workshop page needs attention when session details change. A pack page needs review when files or pricing change. A collaboration page needs review when selected work is replaced.
Also check usage and storage notices before making copies. The absence of a fixed site-count cap does not mean every idea deserves a deployment. Create another page when the visitor's decision changes enough to justify its upkeep.
Avoid inventing a former numerical cap or a new traffic allowance. Use the current account notices and official documentation for limits. Keep the operating plan small enough that one person can check every public offer after a material change.
Approve a version and leave a useful handoff
OpenAI says every deployment URL is a production URL. Save a version when reviewing changes without updating a live Site, and treat deployment as a separate decision. Verify the intended audience and sharing settings before putting a URL in a profile, video description, or campaign.
Nina's next artifact is an offer-page inventory containing the approved copy version, working destination, review owner, and next check date. It gives each page a reason to exist and someone responsible for keeping its promise accurate.
Growit o1 is a physical device in development. Consult the o1 guides, current product boundaries, and o1 AI direction before planning a device role. This brief does not establish Sites creation, deployment, or account access through o1. Keep the approved page inventory with the creator's existing production and campaign records.
