Why not just ask ChatGPT to write your website?
You can, and the page will look good. Here is what you still need once the HTML exists: hosting, a domain, a working form, and a way to change it later.
The SiteShip team · 5 min read
It's a fair question, and the honest answer starts with "you can."
Ask ChatGPT or Claude for a website for your bakery and you'll get one. It will have a header, a nice photo area, your opening hours and a contact section. It often looks better than a template. For a lot of people that moment is a surprise: the hard part seems to be over.
It isn't quite. What you have is a file. A website is a file plus everything around it. Here is the rest of the list.
1. Somewhere to put it
A web page has to live on a computer that is always on and that the public can reach. That's hosting. There are good free hosts, and they work well. But each one asks you to open an account, upload or connect your files, and learn its way of publishing a change.
The most common question we see from people who built a site with AI is exactly this one: it made my site, now where does it go?
2. Your own address
You'll want the site at yourbusiness.com, with the padlock that tells visitors it's secure. That means buying a domain and adding a few records at the company you bought it from, so the address points at your host. It is a small job, and it is easy to get wrong the first time.
3. A contact form that sends something
This one catches people out. An AI can draw a perfect contact form. Name, email, message, a Send button. But a form on a plain web page has nowhere to send what people type. Something has to receive the message, check it isn't spam, keep a copy and email you.
Without that, the form looks finished and does nothing. You won't see an error. You just won't hear from customers.
4. The files search engines look for
To be found, a site needs more than visible words. Each page needs a title and a description. The site needs a sitemap, and a file that tells search engines what they may read. A local business also benefits from having its name, address and hours written in the structured form that Google reads.
An AI will write these if you ask, and may remember them if you don't. The trouble is keeping them right on every page, every time something changes.
5. Changing it next month
This is the big one. Your hours change. You add a service. You spot a typo.
With a file on your computer, each change means finding the file, giving it back to the AI, getting a new version, and putting it online again. If your site has several pages, the phone number in the footer now lives in several files. Change it in three and miss the fourth, and your site quietly disagrees with itself.
And when a change goes wrong, there is no undo unless you kept the old copies.
When doing it yourself is the right choice
None of this is hard for someone who has done it before. If you, or someone you know, are comfortable with hosting accounts and domain settings, doing it yourself is a good route. It costs your AI plan and a domain, the files are yours to keep, and you can use any tools you like.
We mean that. Our comparison page says plainly that this route is cheaper than SiteShip, and lists who it suits.
What SiteShip does instead
SiteShip is for the owner who wants the result and not the list above. You add it to ChatGPT or Claude as a connector, and your AI builds on our engine. That changes each item:
- Hosting is included. There's no account to open elsewhere.
- Your domain is connected with a padlock. You still add the records at your registrar, and your AI tells you which ones.
- Forms work: spam is filtered, every lead is saved, and it's emailed to you.
- Search files are written by the engine on every page, from details you give once.
- Changes are a sentence in the chat. They wait in a draft until you click Publish, and earlier versions are kept.
The engine also checks every change the AI makes and refuses ones that would break a page. The engine page shows what that looks like.
What it costs, and what it doesn't do
Building and previewing is free. Putting a site live is $29 a month or $290 a year, on top of the ChatGPT or Claude account you need to do the building (one that supports connectors).
SiteShip won't give you a download of your site's files, a built-in store, or a booking system. For selling and bookings, your AI adds a Shopify shop, Stripe buttons, or a Calendly or Cal.com calendar. If holding the files yourself matters most, do it yourself.
The takeaway: the HTML is the easy part now. Before you choose, ask how the site gets online, where the form's messages go, and how you'll change the phone number in six months. If you have good answers, you don't need us. If you'd rather not think about it, see how the engine works.
Free to build. Pay only to go live.