Building a website traditionally means choosing a hosting service, registering a domain, installing software and either writing code or learning a website builder.
ChatGPT Sites aims to simplify much of that work.
The feature lets ChatGPT create, host, edit and share websites directly from a prompt. You can use it to make a landing page, online guide, interactive dashboard, internal business tool or simple web app without arranging a separate deployment process.
You describe what you need, review the result, request changes and choose who can access it.
ChatGPT Sites is currently in public beta, so availability, features and usage limits may depend on your plan, region and workplace settings. Here’s how to get started and what to check before publishing anything.
What Is ChatGPT Sites?
ChatGPT Sites is a website creation and hosting feature built into ChatGPT.
It can create:
- Informational websites
- Landing pages
- Interactive guides
- Business dashboards
- Project trackers
- Internal workplace tools
- Portfolios
- Simple games
- Web apps that save information
- Sites that accept uploaded files
The important difference between Sites and an ordinary ChatGPT response is that the result isn’t just a block of code or a mock-up.
ChatGPT can turn the project into a working hosted website with its own shareable address. You can then return to Sites later to edit it, review its visitor numbers, update its sharing settings or connect a custom domain where that option is available.
Who Can Use ChatGPT Sites?
Sites is in public beta.
Access can depend on:
- Your ChatGPT plan
- Your country or region
- Your workspace settings
- Limits applied during the beta
- Whether an organisation administrator has enabled it
ChatGPT should display your current Sites limits and warn you as you approach them.
Reaching a limit may prevent you from creating another Site, adding more storage or keeping a high-traffic Site publicly available. You may still be able to edit and manage Sites you’ve already created.
Where to Find ChatGPT Sites
On the ChatGPT Website
Open ChatGPT and select:
More > Sites
You can also open the Sites section directly from ChatGPT’s Sites page.
This area displays the Sites you’ve created and lets you reopen, manage, analyse or delete them.
In the ChatGPT Desktop App
Open the ChatGPT desktop app and go to the Sites section.
From there, you can begin a new Site from a prompt or work with a compatible project stored on your computer.
The exact interface may change while the feature remains in beta, so look for Sites in the main ChatGPT navigation if the menu has moved.
What You Need Before You Start
You don’t need to know how to code, but you should have a reasonably clear idea of what you want the Site to do.
Before writing your first prompt, decide:
- Who the website is for
- What visitors should be able to do
- What information it needs
- Whether it should save data
- Whether visitors need to sign in
- Who should be allowed to access it
- Whether you have images, documents or branding to provide
- What the finished design should feel like
A vague prompt can still produce a website, but a detailed prompt is more likely to create something useful.
Step 1: Start the Sites Workflow
Begin a new ChatGPT request and include the word website in your prompt.
You can also mention @Sites.
This tells ChatGPT explicitly that you want to use the Sites workflow rather than receive general website advice or a code sample.
Example prompt:
Build a website for a local gardening service. Include a home page, services section, photo gallery, customer testimonials, contact form and service area covering western Sydney.
For a more interactive project:
Example prompt:
@Sites Build a household budget dashboard that lets users add income and expenses, organise transactions into categories and view monthly totals in a simple chart.
Step 2: Describe the Audience and Purpose
Tell ChatGPT who will use the Site and what problem it should solve.
Compare these two prompts.
Basic prompt:
Build me a website about photography.
Improved prompt:
Build a beginner-friendly photography website for Australian parents who want to take better family photos with their phones. Include simple tutorials, example settings, indoor and outdoor tips, and a checklist they can use before taking a photo.
The second prompt gives ChatGPT far more useful direction.
Try to explain:
- The intended audience
- The main purpose
- The most important pages or sections
- The action visitors should take
- The overall tone
- Any accessibility requirements
Example prompt:
The audience is older Australians who may not be confident with technology. Use large text, simple navigation, strong contrast and plain English.
Step 3: Explain What the Site Must Do
A Site can be a simple page containing information, or it can behave more like an application.
List the important functions directly in your prompt.
Example prompt:
Create a project request dashboard for a small marketing team. Team members should be able to submit a request, choose its priority, assign an owner, update its status and filter requests by team member or due date.
Other functions could include:
- Search
- Forms
- Filters
- Calculators
- Checklists
- File uploads
- Saved progress
- User accounts
- Interactive charts
- Downloadable reports
- Scores or leaderboards
- Personalised views
Don’t assume ChatGPT will know which information needs to be saved.
If users should be able to return later and find their previous entries, say so clearly.
Example prompt:
Save each user’s tasks and progress so they remain available when the user returns.
Step 4: Add Your Content and Files
You can give ChatGPT source material to use while building the Site.
This may include:
- Logos
- Brand guidelines
- Product information
- Documents
- Spreadsheets
- Images
- Existing website copy
- Screenshots
- Examples of layouts you like
Example prompt:
Use the attached logo and brand guide. Follow the supplied colours and typography, but keep the layout clean and easy to read on mobile devices.
Another example:
Example prompt:
Use the attached spreadsheet as the source for the product names, descriptions and categories. Don’t invent products or prices that aren’t in the file.
Files can provide useful context, but review the finished Site carefully. Check that ChatGPT hasn’t misunderstood a spreadsheet, omitted information or exposed something that shouldn’t be public.
Step 5: Give ChatGPT Design Direction
You don’t need to provide precise technical design instructions, but some visual guidance can help.
You could request:
- Clean and minimal
- Bright and playful
- Professional and corporate
- Warm and welcoming
- Magazine-style
- Dark mode
- Mobile-first
- Large text and accessible contrast
- Image-led layout
- Simple card-based design
Example prompt:
Use a clean editorial layout with a white background, large readable headings, generous spacing and blue accent colours. Avoid unnecessary animations and make the Site easy to use on phones.
You can also reference an existing style without asking ChatGPT to copy it exactly.
Example prompt:
Use the general feel of a modern technology news website, with strong headlines, clear categories and a simple article grid.
Step 6: Let ChatGPT Build the First Version
Once ChatGPT has enough information, it can create the initial Site.
Depending on the complexity of your request, it may:
- Plan the Site’s pages and features.
- Create the layout.
- Add your supplied content.
- Build interactive controls.
- Configure storage if information must be saved.
- Generate a preview.
- Ask questions or request approval where necessary.
A complex dashboard will usually take more work than a basic landing page.
When the preview appears, don’t publish it immediately. Treat the first version as a draft.
Step 7: Review the Preview Carefully
Check the Site as though you were a real visitor.
Look at:
- Headings
- Navigation
- Buttons
- Forms
- Images
- Links
- Mobile layout
- Spelling
- Calculations
- Saved information
- Sign-in behaviour
- Privacy wording
- Download functions
Test every interactive feature.
For example, if the Site includes a form, submit a test entry. If it includes a calculator, check the result manually. If it saves progress, close and reopen the Site to see whether the information remains.
Also check whether ChatGPT has added content you didn’t provide, such as invented testimonials, fake statistics, unsupported claims or placeholder contact details.
Step 8: Ask ChatGPT to Make Changes
In the Site preview, select Edit.
Under Describe website edits, explain what you want changed.
You can also provide a screenshot or attach additional files when visual context would help.
Useful editing requests include:
- Layout: Make the main heading shorter and move the call-to-action button above the first image.
- Mobile design: Replace the three-column layout with a single column on mobile screens.
- Forms: The contact form is asking for too much information. Keep only name, email address and message.
- Filters: Add a filter that lets visitors view results by location.
- Writing: Rewrite the introductory text in plain English for readers with no technical knowledge.
- Branding: Keep the current layout, but change the colours to match the attached brand guide.
Try to give one clear group of related changes at a time. That makes it easier to check whether each request was completed correctly.
Step 9: Save a Version Before Publishing
ChatGPT Sites separates saving a version from deploying it.
Save a Version
Saving creates a deployable version of the Site that you can inspect before making it available to visitors.
Use this when the Site still needs testing or approval.
Example prompt:
Save this as a new version, but don’t deploy it yet.
Deploy a Version
Deploying publishes the saved version and produces a live address.
Every deployed Sites address is treated as a production deployment. That means you should only deploy when you’re ready for the selected audience to access it.
Ask ChatGPT to save rather than deploy if you want a private review first.
Step 10: Choose Who Can Access the Site
New Sites begin with restricted access for their owner and workspace administrators.
Depending on your plan and workplace settings, sharing options may include:
- Only you and workspace administrators
- Selected users or groups
- Anyone in your organisation
- Anyone on the internet
Public publishing may be disabled in managed workspaces. Enterprise administrators must enable it before a Site can be shared openly.
Sharing access lets people visit the Site. It doesn’t automatically give them permission to edit it.
Choose the narrowest audience that fits the project. An internal staff dashboard generally shouldn’t be public, while a promotional landing page may need to be available to everyone.
Step 11: Add Sign in With ChatGPT When Needed
Public Sites can optionally include Sign in with ChatGPT.
This can support features such as:
- Saved progress
- Personalised information
- Records belonging to individual users
- Member-specific views
- User accounts without building a separate sign-in system
A Site can remain available to the public while offering extra features to people who sign in.
Example prompt:
Add Sign in with ChatGPT. Keep the public information available to signed-out visitors, but require sign-in before someone can save a checklist or view their previous entries.
Don’t request sign-in unless the Site genuinely needs to identify visitors. A simple informational landing page probably doesn’t require it.
Step 12: Ask for Storage When Information Must Be Saved
Some Sites only need to display content. Others need to remember information between visits.
Tell ChatGPT when data must be permanent.
Example prompt:
Save project requests so they remain available after the browser is closed.
Example prompt:
Store player names and scores between visits.
Example prompt:
Let users upload profile images and keep those images linked to their account.
Behind the scenes, Sites may use different types of storage:
- A structured database for records, scores and saved progress
- File storage for images, documents, audio or video
- A combination of both for uploaded files that also need searchable information
You don’t need to understand the technical names to request these features. Explain what the visitor expects the Site to remember.
Temporary choices, such as dismissing a notice or switching between light and dark mode, may not require permanent storage.
Step 13: Review Your Site Analytics
Sites automatically records basic traffic information for supported accounts.
The analytics area can show:
- Unique visitors
- Page views
- Changes over time
- Different date ranges
- Different reporting intervals
To find it:
- Open Sites.
- Locate the Site.
- Select More actions.
- Choose Analytics.
Analytics is currently unavailable for Sites owned by Enterprise workspaces.
The built-in figures are useful for a quick overview, but they may not replace a more advanced analytics platform if you need detailed marketing attribution or visitor behaviour reports.
Step 14: Connect a Custom Domain
Where the feature is available, you can connect a domain or subdomain you already own.
For example:
- example.com
- tools.example.com
- guide.example.com
Sites doesn’t register the domain for you. You need to own it and have permission to change its DNS settings.
To connect one:
- Open the Site’s settings.
- Select Add domain.
- Enter the domain or subdomain.
- Copy the DNS records provided by Sites.
- Add those records through your domain provider.
- Return to the Site settings and refresh the domain status.
Custom domains aren’t available for Enterprise workspaces at launch, and access may vary for other accounts.
Only change DNS records when you understand which existing services may be affected. Incorrect changes can interrupt a website or email service already using the domain.
A Simple ChatGPT Sites Prompt Formula
A strong prompt can follow this structure:
- Site type: What you want to build
- Audience: Who will use it
- Purpose: What problem it solves
- Pages: Which sections it needs
- Functions: What visitors can do
- Content: Which files or information to use
- Design: How it should look and feel
- Storage: What it should remember
- Access: Who should be able to visit
- Restrictions: What must not be invented or exposed
Here’s a complete example.
Complete example prompt:
@Sites Build a mobile-friendly website for an Australian community sports club. Include a home page, upcoming events, training timetable, team contacts, registration information and a form for volunteer enquiries. Use the attached logo and club colours. Make the text easy for parents to read on phones. Don’t invent player names, sponsors or event dates. Keep the Site private while I review it, and save a version without deploying it.
More Example Prompts
Small-Business Website
Example prompt:
Build a professional website for a mobile dog-grooming business serving Brisbane. Include services, service areas, a price guide, frequently asked questions and an enquiry form. Use a friendly tone and make the phone number easy to find on mobile devices.
Event Planner
Example prompt:
Create an interactive event-planning Site for a family birthday. Include a guest list, task checklist, budget tracker and timetable. Save all changes between visits and limit access to invited family members.
Educational Guide
Example prompt:
Build a beginner-friendly website explaining common AI terms. Include a searchable glossary, short examples and a quiz. Use plain English and avoid technical jargon unless it’s explained immediately.
Internal Business Dashboard
Example prompt:
Create an internal dashboard for tracking customer support issues. Staff should be able to add a case, assign an owner, set a priority, update its status and filter by department. Require workspace sign-in and keep all records private.
Simple Game
Example prompt:
Build a mobile-friendly trivia game with 20 Australian geography questions. Show one question at a time, calculate the score and let signed-in players save their best result.
Privacy and Security Checks
A website can collect more information than users realise, particularly when it includes forms, accounts, saved records or file uploads.
Before sharing a Site:
- Remove confidential information
- Test its sharing settings
- Check who can access uploaded files
- Review every form field
- Avoid collecting information you don’t need
- Check whether personal data is stored
- Explain how sign-in information is used
- Keep passwords, API keys and secret values out of prompts and files
- Review third-party images and content for copyright issues
- Test the Site while signed out
Sites shouldn’t be used to process payment-card information or protected health information. It also shouldn’t be used to enable financial transactions, distribute malware, impersonate people or organisations, or create phishing experiences.
Sites doesn’t support data residency or inference residency at launch. Businesses with strict requirements about where their code, files, databases or logs are stored should review this limitation before using the service.
Australian businesses also need to consider their responsibilities under local privacy and consumer laws when collecting personal information.
Current Limitations
ChatGPT Sites is promising, but it isn’t a complete replacement for every website platform.
Current limitations include:
- It remains in public beta
- Availability varies by plan, region and workspace
- Usage limits apply
- Some frameworks and hosting patterns aren’t supported
- Private networks and some external databases may not work
- Background services may be limited
- Custom domains aren’t available to every account
- Analytics is limited compared with specialist platforms
- Generated text, images and functionality still require human review
- Public Sites may need additional privacy, accessibility and legal checks
- Deleted Sites can’t be restored
More complex commercial websites may still be better suited to an established content management system, ecommerce platform or professional development workflow.
Who Will Benefit Most?
ChatGPT Sites is likely to be most useful for:
- Small businesses needing a simple website
- Teams building internal dashboards
- Teachers creating interactive resources
- Community organisations
- Creators testing an idea
- Students building project presentations
- People creating a temporary event Site
- Developers producing quick prototypes
- Non-technical users who need a working web tool
It may be less suitable for a large online store, heavily regulated service or complex application that requires specialised infrastructure.
Is ChatGPT Sites Worth Using?
ChatGPT Sites makes it much easier to move from an idea to a working online experience.
Its biggest advantage isn’t simply that AI can generate a page. It’s that ChatGPT can create the Site, host it, refine it through conversation and give you controls for sharing, storage and visitor access.
That could make it particularly useful for prototypes, internal tools, educational resources and straightforward public websites.
The trade-off is that creating something quickly doesn’t remove the need for testing. You still need to check the wording, links, calculations, accessibility, privacy settings and interactive features.
Start with a small, low-risk project. Learn how editing, saving and deployment work before building anything that handles important business or personal information.
Why This Matters for Australia
Australian small businesses, schools and community groups often need online tools but may not have the budget to hire a developer or subscribe to several website services. ChatGPT Sites could help them produce a simple information page, interactive guide or internal dashboard much faster.
It may also give Australian workers a practical way to turn spreadsheets, documents and ideas into small web tools without learning programming first. A local club could build an event page, a teacher could create a revision quiz, or a sole trader could test a new service before investing in a larger website.
Privacy and consumer obligations still apply. Anyone collecting names, email addresses, uploaded files or other personal information should carefully review what’s stored, who can access it and whether the Site is suitable for that data.
The sensible approach is to begin with a straightforward project, keep it private while testing and only publish after checking the Site from a visitor’s point of view.
