Build a website with Claude and put it live on UK hosting

If you have never touched code and want a single landing page, the chat window is the gentlest start. You see the code appear, ask for changes in ordinary sentences, and save the result as a few files. There is nothing to install.

If you want a proper site with several pages, a menu that is the same on every page, and the ability to add a page next month, Claude Code is a better fit. It keeps the whole project in view, so a change to the header is made once and appears everywhere. You do need to be comfortable running a few commands in a terminal, or willing to follow along while it explains each one.

Neither option changes what the hosting needs to do. Both end with a folder of built files that gets uploaded to your account.

The quality of what Claude builds depends mostly on what you tell it. A vague request such as "make me a website for my business" gets a generic result with invented text. A good brief names the business, the town you serve, the pages you need, the one action you want visitors to take, and the facts that must appear exactly as written, such as prices, opening hours and your phone number or email address.

Gather your real material first: a few sentences about what you do, three to five photos, your contact details and any legal details a UK business must show. If you are a limited company, that includes the registered name, number and registered office. Our guide on what to put on a UK business website lists the usual items, and it is general information rather than legal advice.

Decide the pages too. Four good pages, usually Home, Services, About and Contact, beat a dozen thin ones. You can add more once the first version is live.

Claude can produce many kinds of site, and the choice decides how easy hosting will be. The simplest is plain HTML, CSS and a little JavaScript. A step up is a static site generator such as Astro, which builds your pages into ordinary files ahead of time. Both produce a folder of files with no database and no program running on the server, which makes them quick, cheap to host and hard to break.

Heavier choices exist: a WordPress site, or an app that needs a running Node.js process. Our plans support those as well, because Node.js, Python and Redis are available on every plan, and we cover the options in which stack to ask Claude for. For a brochure site, a local business or a portfolio, static is usually the right answer, and it is where we would start.

Why static suits shared hosting so well: there is nothing to keep running. Visitors receive finished files from a LiteSpeed web server in London, so pages arrive quickly for UK visitors, and there is very little to attack compared with a site that runs code on every request.

AI-written code usually runs, but running is not the same as being right. Treat the first version as a capable draft from a fast junior colleague. Read it, test it, and keep the final say.

Start with the content. Assistants fill gaps with plausible text, which can include prices, awards, opening hours and claims that are simply wrong. Every fact on the site must be one you have checked. A made-up testimonial or an invented guarantee on a business website is a real problem, whoever wrote it.

Then look at the technical basics: does every link work, do the images have descriptive alt text, does each page have its own title and description, and is there a visible way to contact you. Ask Claude to explain anything you do not understand, and to list every file it created. If something loads from another company's server, such as a font, a script or a form service, you should know about it, because it may need a mention in your privacy notice.

Claude cannot know your business. It cannot confirm that your prices are current, that a claim is legally safe to make, or that a photo is yours to use. It also cannot see your customers' reactions. Those judgments stay with you.

It can make mistakes in code, particularly in security. Forms, logins and anything that stores visitor data deserve extra care. If your site only shows information, a static build removes most of that risk, which is another reason to start there. If you do take payments or store personal data, have an experienced developer review the work.

Finally, keep the project somewhere safe. Claude Code changes real files, so a backup, or better a Git repository, means you can undo a change that went wrong. You own what you create and publish, and you are responsible for it, so read it before it goes live. For a wider look at protecting a site, see our website security checklist.

A site is never finished. Once it is live, look at your enquiries, note what visitors ask, and add or improve a page when a pattern appears. With Claude Code you can describe the change, review it, rebuild and upload again in minutes, which is one of the real strengths of this way of working.

Keep your own backup of the project folder, update any tools the site depends on from time to time, and set a reminder to re-read every page for facts that have gone out of date. If you hit a problem, our live chat is open 24/7 and our guides cover common faults. When you are ready to put the site online, choose a plan, register your domain and follow the deployment guide.