← All blog posts

Should I Build My Website With AI?

Diagram on a blue-to-tan gradient headed "AI can write the code. Someone still has to check it.", under a kicker reading SHOULD I BUILD MY WEBSITE WITH AI? A white panel below splits into two columns. A red one headed AI on its own, each line marked with a cross, lists: new code, never run anywhere else; nobody checking it against the law; each page built fresh, nothing quite matches; nobody looking after it after launch. A blue one headed AI with a developer, each line ticked, lists: every line checked before it goes live; built to accessibility and privacy rules; one plan, carried through every page; kept up to date after launch. A white strip along the bottom reads: The tool isn't the risk. Using it with no developer is.

You can describe your business to an AI and have a website by the end of the afternoon. Some website builders will do it for you with a single button. It will have a homepage, a services page and a contact form, and it will look like a website.

That last part is the problem. Looking like one was never the hard part.

Should I build my website with AI?

Not without a developer. In a developer's hands AI is a genuinely useful tool, and this site was built with AI assistance. On its own, AI is a page builder with no track record: you still can't see what is happening behind the scenes, and the code it writes has never run anywhere but your site.

If you have no development background, building with AI is no different from building with a page builder. You give it instructions, something appears, and what is underneath it is a mystery. The difference is what that mystery is made of.

Isn't an AI-built website just a page builder with extra steps?

It's worse in one specific way. A page builder's code runs on millions of other sites, so its problems get found and fixed. The code an AI writes for you is brand new, and your site is the first place it has ever run.

I have plenty to say about page builders like Elementor and Divi (and I said a lot of it in Should I Move Off WordPress?), but I will give them this: their code has been tested on an enormous number of sites. When something in it breaks, it breaks for thousands of people at once, somebody reports it, and it gets fixed. When someone builds something illegal, their compliance officer sighs and sends an email ordering it fixed.

AI doesn't hand you tested or vetted code. It writes new code every time you ask, shaped to your request. Nobody else has ever run it. If there is a hole in it, nobody else has found it, and the first person to find it will be you, someone trying to get in, or someone ready for an ADA lawsuit. AI poses more risks than just bad code, too: attackers use it to find holes faster than ever, which is a whole other topic and what happened with PHP2Shell this month.

The issues resulting from building with AI as your lead developer all boil down to the same cause. AI has a goal; a developer has a background.

What does a developer do that AI doesn't?

Writing the code was never the whole job. A developer knows the rules a website has to follow, checks every line before it goes live, and is the one who answers for it when something breaks.

The difference most people won't notice

Before websites, I built high-end wine cabinets and cigar humidors for private clients, country clubs and yachts. It is the best reference I have for the kind of quality difference I mean.

On a cabinet with pairs of doors, a craftsman cuts the stiles and rails that meet from one piece of wood, so the grain carries straight across the seam. It's called grain matching, and a kit manufacturer doesn't bother with it. The gaps around each door are even, not "as close as we could get." Put that cabinet next to the same one without those details and people pick it every time, usually without being able to say why. (This one is sapele, by the way. If you have ever bought something sold as mahogany, there is a good chance it was sapele.)

Close-up of two finished sapele door stiles lying side by side, each drilled for a knob, with the stripes of the grain continuing from one stile into the next across a narrow, even gap.
Two door stiles cut from one piece of wood. The grain runs straight across the seam.
A tall finished sapele cabinet on a dolly in a woodshop: two glass upper doors over two panelled lower doors, with brass knobs where each pair of doors meets and matching grain running down the centre stiles.
The finished cabinet before dialing in the door alignment. Nobody writes "grain matched" on a spec sheet.

Websites are the same. Most visitors will never put a name to what is different about a site where every page was built to one plan and every detail was checked. They will just like it better, every time.

How can you tell a website was made by AI?

Look for inconsistency and lack of uniqueness. Nothing is exactly wrong, but nothing was decided either: pages and sections built separately that don't quite match, and each decision lacks creativity.

AI tends to build each page, and often each section, fresh. Ask it for a services page one day and an About page the next and the two are made separately. The buttons are a slightly different shape, the headings drift, and the space between sections is "as close as it could get." It is the same drift I described in Should I Move Off Squarespace?, just faster.

None of the checks below need any code. They are things you click and look at, on your own site or on one you are about to pay for.

What goes wrong on an AI-built website that you can't see?

The failures that cost the most are the quiet ones: a form that never delivers, a site a screen reader can't use, a privacy policy that describes some other website, and code that nobody is keeping up to date.

Is it ever OK to build a website with AI?

Yes, in a developer's hands, and this site is the proof. AI does the boring-but-easy parts here, and I make every call that matters and check every line it writes.

On your own, it is fine for a placeholder, a hobby project, or testing an idea before you spend money on it. Just know what you have: something that might look finished but nobody has checked.

I wrote about how AI fits into my own work, and why I stopped worrying about it, in The AI Revolution, Revisited.

How I do it

AI does a lot of the typing on the sites I build. I decide what gets built, read what it writes, and end up rewriting most of it, keeping just the good stuff I hadn't thought of. Every page follows one plan, so the site is consistent from the homepage to the privacy policy. I test with a keyboard, send the form to myself, make sure the privacy policy describes what the site actually does, and keep it all up to date after launch.

The honest answer

An AI can build you something that looks like a website. Whether it holds up (whether it follows the law, works for every visitor and matches from one page to the next) depends on whether someone who knows what to look for has checked it.

If you have a site an AI built (or you're thinking about building one) and you would like a second opinion, send me a message. I'm happy to take a look, even if the answer is that it's fine for what you need.

The Better Website Guy

Designer/developer behind The Better Website. Hand-codes every build himself: no templates and no page builders.

Let's chat

← Back to the blog