AI Will Build You a Website in an Afternoon. That Was Never the Hard Part.

AI will build you a website in an afternoon. That was never the hard part. Kartia blog title graphic.

The short version: AI website builders work. They’ll produce a clean, functional, decent-looking site in an afternoon, and if your website’s main job is to exist and look legitimate, that may be all you ever need. What they’re good at is the part that was never hard, which is the building. The part that was always hard is deciding what the site is for, who it’s for, and what you want someone to do when they land on it. A site can be built perfectly and still never have been asked what job it’s supposed to do.


I’ve worked on hundreds of websites over the years. I’ve built a good number from scratch and been called in to fix plenty more. So when people ask whether an AI builder can do what I do, they usually expect me to say no.

The honest answer is that it can do a surprising amount of it. Just not the bit that decides whether the website works.

Can AI actually build a decent website?

Yes, and anyone telling you otherwise is either not paying attention or has something to sell you. Modern AI builders will take a description of your business and return a structured, responsive, reasonably tidy website faster than I can book a kick-off call.

They’re good at layout. They produce a sensible page structure, write passable starter copy, pick a colour palette that doesn’t fight itself, and make the thing work on a phone. Ten years ago that was weeks of work.

So let’s not pretend the tools are rubbish. They aren’t.

But producing the pages was never the expensive part of a website. It was always the cheapest part. The expensive part sits upstream, it’s invisible, and an AI builder will sail straight past it without mentioning that it did.

So what does an AI website builder leave out?

It leaves out the decisions. Every website that works is the result of a few uncomfortable choices: who this is for, what single thing we want them to do, and what we’re deliberately leaving off the page. An AI builder makes none of them. It can’t. You didn’t tell it, and it won’t ask.

What it does instead is cover everything. Ask it for a website for a plumbing business and you’ll get a page about emergency call-outs, and hot water systems, and bathroom renovations, and commercial contracts, and a blog, and a testimonial slider. All of it competent. None of it chosen.

The result is a site that says a great deal and asks for nothing.

Think of it like a builder who can frame a house in a day but never asks how many people are living in it. You’ll get a house. Whether it’s the right house is a question nobody raised, and you won’t find out until you’re living in it.

Why do AI-built websites all feel the same?

Because they’re all answering the same question that nobody asked. A model is trained to produce the most plausible version of a thing, and plausible is the enemy of distinctive.

That’s what the technology is built to do, so it’s less a fault than a consequence. Ask for a website for an accountant and you’ll get the average of every accountant’s website. It will be fine. It will also be interchangeable with your competitor’s, who used the same tool and described their business in roughly the same words.

For a lot of businesses, being interchangeable is the actual problem they were trying to solve.

Is an AI-built website bad for SEO?

Not inherently, and it’s worth being precise here, because there’s a lot of nonsense in circulation. Google does not penalise a website for being made with AI. Its published guidance is about whether content is helpful and made for people, not how it was produced.

What Google does act on is low-value content produced at scale to game rankings. That’s where the real risk sits, because “generate a page for every service and every suburb” is the easiest thing in the world to do with an AI builder, and it’s exactly the shape of thing that gets demoted.

The structure an AI builder produces is usually fine. It’s the substance that tends to be thin, and thin is what costs you.

What about accessibility?

This is the one people don’t think about, and automated output doesn’t reliably handle it. Accessibility is the difference between a website everyone can use and one that quietly turns people away. The usual gaps are unglamorous: alt text that describes nothing, colours without enough contrast to read comfortably, forms that can’t be navigated without a mouse.

An AI builder won’t necessarily get those wrong. It just won’t reliably get them right, and it won’t tell you which.

Put bluntly, those are customers you’re losing, and you’ll never see them in your analytics. There’s a legal dimension as well. Australia’s Disability Discrimination Act covers goods and services provided to the public, courts have applied that to websites, and the Human Rights Commission points to WCAG 2.2 AA as the benchmark, including for AI tools under its 2025 guidance.

It’s complaints-driven rather than audited. Nobody is inspecting your site, so most small businesses never hear a word about it. That isn’t quite the same thing as being in the clear.

When is an AI website builder the right call?

Often. If you need a presence so people can confirm you exist and find your phone number, a builder is a sensible use of money, and I’d rather tell you that than sell you something you don’t need.

Same if you’re testing an idea. If you don’t yet know whether the business works, spending real money on a website is premature. Build the cheap version, find out, and come back when there’s something worth investing in.

I’ve told people this. It earns me nothing and it’s still the right answer.

The moment it stops being the right answer is when the website has a job that matters.

So where’s the line?

The line isn’t complexity. Almost everyone gets that wrong, assuming AI is fine for simple sites and breaks on complicated ones.

It’s about consequence. If the site’s job is to exist, AI is fine. If its job is to win work you’d be upset to lose, it isn’t.

One thing I’ve watched go wrong, repeatedly. It wasn’t an AI build, which is rather the point, because this isn’t an AI problem. It’s a website problem that an AI builder does nothing to protect you from.

A client arrives convinced they need to start again, because the site doesn’t feel right to them any more. It’s recent. It’s styled nicely. Page speed is workable. Nothing about it looks broken, and that’s the honest reason they can’t explain what’s wrong with it.

Look underneath and there’s nothing done on the technical side at all. No hierarchy for Google to read, because every heading on the site was tagged the same way and nobody changed the default. Images sitting at megabytes each. No keyword work anywhere.

That site looked completely finished. That’s the part worth sitting with, because looking finished is precisely what an AI builder is excellent at producing, and it tells you nothing at all about whether the thing underneath was built to do a job. The client was about to spend money rebuilding the layer they could see. The layer they could see was the only part that was fine.

Which raises the question I’d want answered before committing to any builder. What happens when you need to change it? Some platforms won’t let you export your site’s code if you leave. Some meter how many AI-assisted edits you get in a month. Those terms vary by product and they change, so don’t take my word for which is which. Go and read what yours actually says before you build anything on it.

You may be perfectly happy with the answer. Just make sure you’ve read it, because that’s the difference between owning a website and renting the ability to change one.


If you’re weighing this up and you’d rather talk it through with someone who isn’t trying to sell you a platform, that’s a conversation worth having before you commit rather than after. We build websites at Kartia, so I’m plainly not neutral about any of this. I’d still rather tell you a builder will do the job and you should save your money than sell you something you don’t need.

Frequently asked questions

Can AI build a complex website?

Usually yes, at least structurally. Complexity isn’t really what limits these tools. The limit is judgement: an AI builder will happily produce a large, intricate site without ever asking which parts of it should exist. Complexity handled badly is worse than simplicity handled well.

Will Google penalise my website for being built with AI?

No. Google’s guidance targets unhelpful content produced at scale to manipulate rankings, not the use of AI itself. The practical risk isn’t the tool. It’s that AI builders make it very easy to mass-produce thin pages, and thin pages are what gets demoted.

Can I move an AI-built website to WordPress later?

Sometimes, and it depends entirely on the platform. Some let you export cleanly. Others hold your site in a proprietary format with no real way out, which means a move becomes a rebuild. Worth checking before you commit, not after.

Is it cheaper to start with an AI builder and upgrade later?

It can be, if you go in knowing that’s the plan. Where it gets expensive is drifting: running a site that was only ever meant to be temporary for years, patching it as you go, and paying for the rebuild anyway at the end.

Picture of Jarrad Nicoll

Jarrad Nicoll

Jarrad heads up web, technology and AI at Kartia, a strategy-led branding and web design studio in Brisbane. He spends his days under the bonnet of websites most people assume are fine, and explaining, without the jargon, why they aren't.