Skip to the content
I Want AI To
17 builds on showA website

Can I use AI to build a website? Yes, and here is the part it can't do for you

Yes. In our recorded run Claude wrote a three-page site from five plain-English prompts in under three minutes of its time. Checking it, real content and putting it live stayed with us.

Short answer: yes, as long as “build” means “write the files”. In our run Claude wrote every page from plain-English prompts and we wrote no code. It did not publish anything, it did not host anything, and it only knew what we told it about the site. The rest of this post splits the job into Claude’s part and your part, using the numbers we recorded.

Yes, and here is what ‘build’ means

People asking this question tend to picture one of two things. Either they type “make me a website” and a finished site appears on the internet, or they picture learning to code with a very patient tutor. Our run was neither.

Claude wrote real HTML and CSS files you can download and open. That is a big part of the job, and it is still only part of getting a site online. Somebody has to put the real words and photos in, look at it on a phone, and upload the files to a host. In our run, that somebody was us.

What Claude did in our run

We ran it on 1 October 2026 with claude-sonnet-5-5, through Claude Code 2.1.287 with only its file tools switched on: no terminal and no web access. We didn’t use the claude.ai website, so your screen will look different. Nothing Claude wrote was edited by hand.

It took five prompts in one conversation:

  1. Describe the site.
  2. Answer Claude’s questions and attach a screenshot of a site we liked the look of.
  3. Ask it to check every page as someone on a phone, and as someone using a keyboard or a screen reader.
  4. Add a new walk.
  5. Ask how to put it live.

Across all five, Claude spent 158.9 seconds working. The result was four files: index.html, walks.html, about.html and style.css.

The example was Tom’s Towpath Walks. Tom is made up, and so are his walks: we asked Claude to invent four so we could see the layout, and it did. That is fine for a demo and exactly what you shouldn’t publish on a real site.

Adding a walk later was the easy part. Claude changed only index.html and walks.html and told us which files to upload again. That is what keeping the site up to date looks like.

The full run, with every prompt and reply as they came back, is on the build me a website page. We won’t repeat the prompts here.

What it got wrong or left to us

We tested the files in a browser at laptop and phone size. The first build, after prompt 2, passed 78 of 94 checks. Two pages had no main heading, there was no skip link for keyboard users, and the smallest text was 11.5 to 12.5px.

Prompt 3 asked Claude to check its own work and fix what it found. After that, 96 of 100 checks passed and the lowest text contrast was 6.79:1. The four failures were all the same thing: small labels at 13px, below the 14px we look for. So one extra prompt fixed most of it, though not all of it.

Claude was open about its limits. After prompt 2 it said it hadn’t opened the files in a browser. After prompt 3 it said it had checked by reading the code and had not tried the pages on a real phone. In prompt 5 it said its button names for GitHub and Cloudflare were from memory.

Three things were wrong or missing:

  • The build output directory. Claude said to leave Cloudflare’s build output directory empty, or type / if the box insists. Cloudflare’s Git integration page says to leave the build command blank when there is no build step, and doesn’t say what goes in the output directory.
  • A taken project name. Claude said Cloudflare adds extra letters to the address if your project name is taken. Cloudflare’s Git integration page doesn’t say that. Use whatever address your project page shows.
  • No “page not found” page. Claude didn’t make a 404.html. Cloudflare’s docs say that without a top-level 404.html, Pages treats the site as a single-page app and sends every unknown address to the home page. So a mistyped link shows the home page instead of an error.

The three jobs that stay with you: content, a phone check, putting it live

Content. Claude can write placeholder text, but it can’t know your real walks, opening hours or prices. Swap in your own words and photos, and read every line before it goes live.

A phone check. In our run, Claude never looked at the pages on a phone. Our browser tests did, and they still found small text. Once the site is live, open it on your own phone. Scroll every page, tap every menu link, and look for text that is hard to read or anything that spills off the side of the screen. If something looks wrong, describe it to Claude in plain words and ask it to fix the file.

Putting it live. Claude’s instructions for GitHub and Cloudflare were a reasonable first draft, and two details didn’t match the docs. Keep the official pages open beside its steps. The set-up page walks through the three free accounts once, and the build page has the clicks we checked against GitHub’s and Cloudflare’s documentation.

What it costs, and what to expect from the free plans

At the time of the run, 1 October 2026, the cost line on our build page was £0 a month on Cloudflare’s free plan and Claude’s Free plan, with your own domain optional.

Plans change, so we rechecked the docs on 9 October 2026:

  • Claude’s help centre says code execution and file creation, the feature that lets Claude hand you files to download, is available to all users including the Free plan. On Free, Pro and Max you switch it on in Settings, then Capabilities.
  • The Pro plan gives more usage per session than Free. Claude’s help centre lists it at $20 a month in the US, with local pricing varying by region.
  • Cloudflare’s Pages limits page, for the Free plan, allows up to 20,000 files per site, 25 MiB per file and 500 builds a month. A four-file site like ours is nowhere near those limits.

A domain of your own is the one cost you might choose to add.

We’re not lawyers and can’t give legal advice. What we can say is that the text and photos on your site are your responsibility as the owner, whoever or whatever wrote the first draft. If a question goes further than that, ask someone qualified.

When a website builder or a person is the better call

This route suits a small site you are happy to check yourself. A website builder may suit you better if you want to edit pages by dragging things around, or you would rather not deal with uploading files and connecting a host. A person may be the better call if the site is central to your income and you want someone else responsible for checking it.

If you are weighing platforms, read Wix, Squarespace, WordPress or Cloudflare. If you want to know which AI to use, the best AI to build a website for a beginner covers that, so we won’t repeat it here.

Where to start

If you don’t have the accounts yet, set them up first. Then pick the run closest to what you want: Tom’s small personal site above, a CV website or a website for your business. Describe your site in plain English, check it on your phone, and then put it live.

Questions

Questions people ask.

Can you use AI to build a website with no coding?

Yes. In our run Claude wrote every file from five plain-English prompts and we wrote no code. You still have to upload the files and connect a host to put the site online.

Can AI build an entire website automatically, with nothing for me to do?

No. Claude wrote the files. Adding the real content, checking the site on a phone and putting it live all stayed with us, and two of Claude's going-live details didn't match Cloudflare's docs.

How much does it cost to have AI build a website?

At the time of the run, 1 October 2026, our cost line was £0 a month on Cloudflare's free plan and Claude's Free plan, with your own domain optional. Claude's help centre says file creation is available on the Free plan. Check the current plan pages before you rely on that.

Is it legal to use AI to create a website?

We're not lawyers and can't give legal advice. The text and photos on your site are your responsibility as the owner, so check what you publish and ask someone qualified if you're unsure.

Will the AI site look right on a phone?

Probably close, but check. Claude said it had checked by reading the code and had not tried a real phone. The first build passed 78 of 94 of our checks. After we asked for a phone and accessibility check, 96 of 100 passed, and small 13px labels still failed.