We get asked some version of this every few weeks now, and it deserves a straight answer
rather than a defensive one: can you just have ChatGPT build your website?
Yes. You genuinely can. You can describe a business, ask for a site, and have working HTML
in front of you in about ninety seconds. It will look fine. For a single-page brochure site
for a side project, it might be all you ever need, and anyone telling you otherwise is
protecting their invoice rather than giving you advice.
But “it produced a website” and “you have a working web presence” are different
achievements, and the distance between them is where almost everyone gets caught out. Here is
what actually happens when a business tries it.
The first draft is the easy 20%
Generated code is genuinely good at the part that feels hardest to a non-developer: layout,
colour, copy scaffolding, a responsive grid that doesn’t collapse on a phone. That used to be
days of work. It isn’t anymore, and pretending otherwise is silly.
What it doesn’t produce is everything that happens after the file exists. A website isn’t a
document. It’s a system with a hosting bill, a security surface, a legal exposure, and a
maintenance schedule. The generated file is step one of roughly forty.
Where it breaks, in the order it usually breaks
1. It has nowhere to live
You have an index.html. Now you need a domain, DNS records, a host, an SSL
certificate, and a deployment method. Each of those is a place to get stuck, and the failure
modes are unhelpful — a misconfigured DNS record doesn’t say “your DNS is wrong,” it just
silently serves nothing for 48 hours while you wonder whether you bought the wrong thing.
2. The contact form doesn’t work
This is the single most common thing we’re called about. Generated sites produce a
beautiful contact form that posts to nowhere. HTML can’t send email. You need a form handler,
spam filtering, and deliverability setup — SPF and DKIM records so your enquiries don’t land
in a junk folder you never check.
We’ve picked up sites that had been quietly dropping every enquiry for months. The owner
assumed business was slow.
3. Nobody is patching it
Static HTML is relatively safe. The moment you add anything dynamic — a form handler, a
booking widget, a CMS so you can edit your own text — you’ve got dependencies, and
dependencies get vulnerabilities. Someone has to be watching for them and applying patches.
If that someone is you, it’s a standing commitment, not a one-off.
4. You can’t edit it
Hand-generated HTML has no admin screen. Changing your phone number means editing code and
re-uploading. Six months in, most owners stop updating their site at all, which is how you end
up with last year’s hours and a staff member who left in March still on the team page.
5. It’s invisible to search and to AI
This is the expensive one, and it’s invisible until you go looking.
Generated sites routinely ship with no meta descriptions, no structured data, no
LocalBusiness schema, a single H1 or none at all, and no XML sitemap. Google can
crawl it but has little to work with. Worse, AI assistants deciding which local business to
recommend lean heavily on structured data and corroborating signals. A site with none is
unlikely to be the one named.
You can have a beautiful website that is, functionally, not findable. That’s the most
common outcome we see.
6. Accessibility is an actual legal exposure
Colour contrast, keyboard navigation, focus states, alt text, form labels. Generated output
is inconsistent here. For a US business this isn’t only an ethical matter — ADA web
accessibility claims are a real and growing category of demand letter, and “an AI wrote it”
is not a defence.
What this actually costs
The honest arithmetic looks something like this. The build is free and takes an afternoon.
Then you spend a weekend on DNS and hosting, discover the form doesn’t work, spend another
evening on that, launch, wait three months, notice no one is finding you, and start reading
about schema markup.
At that point you’ve spent considerably more of your own time than you expected, on work
that isn’t your business, and the site still isn’t doing the one job you built it for. The
cost was never the build. It was everything attached to the build.
So when is it the right call?
We’d genuinely tell you to do it yourself if:
- It’s a personal project, a portfolio, or a landing page for something you’re testing.
- You don’t need enquiries to arrive reliably.
- Nobody finding you through search would be an inconvenience, not a problem.
- You enjoy this kind of thing and want to learn.
Those are real situations and we’re not going to pretend they aren’t.
Where it stops making sense is when the website is a channel your business depends on —
when enquiries arriving matters, when being found matters, when a day of downtime or a
security warning in front of your domain name costs you actual money. At that point you’re
not buying HTML. You’re buying the assurance that it works, stays working, and gets found.
What we actually do differently
We use AI tooling ourselves, daily. It would be strange not to — it’s genuinely good at the
parts it’s good at. The difference isn’t that we avoid it. It’s what sits around it:
- Custom design, not template output. We research your market and
competitors first. We’re not interested in building sites that look like everyone else’s,
and AI-generated design has a strong house style you start recognising everywhere. - A site you can actually run. A CMS, so you can change your own hours
without calling anyone. - Hosting that’s managed. Patching, backups, staging environments,
uptime — handled, not hoped for. - Findable by construction. Schema, semantic structure, performance and
accessibility built in from the start rather than retrofitted after you notice the silence. - Someone to call. Standard updates inside 24 hours.
Building it is half the job
The other half is being found — and that’s genuinely a different discipline from building,
which is why we don’t pretend to do both under one roof. Our sister studio
PG&J handles search, AI
visibility and social. If you’re already a Webjed client, your site and hosting stay exactly
where they are; PG&J simply picks up the marketing side.
If you’ve already built something with AI and it isn’t getting traction, that’s a
completely reasonable place to start from — bring it to us and we’ll tell you honestly whether
it’s worth building on or starting over. Sometimes it’s the former.