What you’ll be able to do

By the end of this you’ll have taken an idea sitting in your head and turned it into an actual website, live on the internet, without knowing how to code. Not a mock-up. Not a plan for a website. An actual one, with a proper domain, that works on someone’s phone when you send them the link.

I’m not going to pretend this is instant. There’s a bit of setup, a bit of trial and error, and you’ll probably swear at your laptop once. But the route from “I have an idea” to “here’s my site” is genuinely shorter than it used to be, and AI does most of the heavy lifting now, the writing, the code, even a fair bit of the thinking.

Before you start

Right, before you open any tool at all, sit with a few questions. This bit gets skipped constantly and it’s the bit that actually matters.

What does your site do? Not vaguely, specifically. Is it a portfolio to show off your photography? A single page for your dog-walking business with a phone number and some photos? A shop? The more specific you are here, the better everything downstream goes, because AI tools are only as good as what you tell them.

If what you’ve pictured is a shop, you’re in luck, because there’s a whole guide on that. It covers setting up a Shopify store with AI, writing the product pages, and getting the boring parts done without losing a weekend to them. Read that one first, then come back here if you still need a site that isn’t a shop.

Who’s actually going to visit it? A friend browsing on their phone in bed is a different design job to a client checking prices on a laptop at work. You don’t need a marketing degree for this, just a rough sense of who’s on the other end.

And the ownership question, which people genuinely don’t think about until it bites them: when you use a free AI website builder, what do you actually own at the end? Usually you own your content and your domain, but the platform owns the code and the hosting unless you export it. Worth knowing before you fall in love with a tool that locks you in.

Get set up

You need a few things before you touch a prompt box.

First, an AI assistant. ChatGPT, Claude, or Gemini all work fine for planning your site and writing copy. Any of them will do; I’d just pick whichever one you already have an account with, there’s no need to overthink it at this stage.

Second, decide how hands-on you want to be with code. If you don’t want to see a line of it, you’re looking at AI app builders like Lovable, Bolt, or v0, tools where you describe the site in a chat and it builds the whole thing for you, front end and back end. If you fancy actually reading and tweaking code, Claude Code or Cursor let you work more directly, still with heavy AI help, but you’ll be looking at files and folders.

Third, a domain name. This is the bit people find oddly stressful. A domain is just the address, yourname.com or whatever you land on, and you buy it from a registrar, plenty of the hosting platforms below sell them too. Check it’s actually available before you get attached to it.

If you haven’t got a name yet, the address is going to feel like guesswork, and that’s usually where the stress comes from. Picking something that fits, that you can say out loud without spelling it three times, and that nobody else already owns is a fiddly job. I’d get AI to name my business first, then come back here with a shortlist ready to check.

Fourth, somewhere to host the finished site. Cloudflare Pages, Netlify, and Vercel all offer free tiers that are genuinely usable for small sites, and they all connect nicely to the AI builder tools mentioned above. I won’t quote you numbers on what’s included free because it changes and I’d rather send you to check yourself than guess.

One quick thing on repos, because it comes up constantly and nobody explains it properly. A repo, short for repository, is just a folder that stores all your website’s code and tracks changes to it over time. Most AI coding tools create one automatically for you now. You don’t need to understand git properly to get going, just know that it’s the box your code lives in.

Try it yourself

Here are three prompts. Different jobs, different outcomes. Copy them, tweak the bracketed bits, paste into ChatGPT or Claude.

First one, planning the site before you build anything:

I want to build a website for [describe your business or project in one sentence]. 
My main audience is [who visits and why]. 
Suggest a simple site structure: what pages I need, what should be on the homepage, 
and what the main goal of the site is (booking, selling, showing my work, etc). 
Keep it to what's essential, don't over-complicate it.

Second, writing the actual copy for a page once you know the structure:

Write the homepage copy for a website about [your business/project]. 
Tone should be [friendly and simple / professional / warm, pick one]. 
Include a short headline, a two-sentence intro, and three short paragraphs 
covering what I do, why someone should choose me, and how to get in touch. 
Keep sentences short. No exaggerated claims.

Third, if you’re using a code-capable tool like Claude Code, Cursor, or an app builder like Lovable, this is the kind of build prompt that gets you moving:

Build a simple one-page website with a navigation bar, a hero section with a headline 
and a button, a section describing [your service], and a contact section with an 
email address and a form. Use a clean, minimal design. Make sure it looks good on 
mobile screens as well as desktop.

Three different jobs there: thinking, writing, building. You can run all three in the same afternoon.

On the copy prompt specifically, a quick honest note. AI-written copy tends to land somewhere fairly generic, competent but a bit flavourless, because it’s writing in nobody’s voice in particular. If that bothers you and you want the words to actually sound like you rather than like every other small business site out there, that’s what ScriptGrain is built for. It’s ours, so take that as you will, but it’s specifically for getting your own voice into the copy instead of the default AI tone, and the free tier gives you one profile and one draft, enough to see if it helps before you commit to anything.

Check the result

Once you’ve got something built, don’t just look at it on your own laptop and call it done. Check it properly.

Open it on your actual phone, not just by shrinking your browser window, on the real device. Does the text overflow anywhere? Are the buttons big enough to tap without missing? Does anything overlap?

Click every link. Every single one. Broken links are the fastest way to make a site look unfinished, and they’re depressingly easy to miss when you built the thing yourself and know where everything “should” be.

Fill in any form you’ve added, even if it’s just a contact form, and check what happens when you submit it. Does it actually go anywhere? Does it tell you it worked?

Show it to one other person before anyone important sees it. Genuinely, just one. Ask them what the site is for, without telling them first. If they can’t answer that in a few seconds, something in your structure or your headline isn’t doing its job.

And check the loading speed isn’t painful, particularly if you’ve added a lot of images. If it feels sluggish on your own phone on wifi, it’ll feel worse for someone on mobile data.

If it doesn’t work

Two separate issues tend to come up here: privacy, and things breaking.

On privacy first, because it matters more. Never paste passwords, API keys, payment details, or real customer data into an AI chat, ever, even the paid tools. If your site handles bookings or sales, keep that logic and any sensitive data handling well away from what you’re pasting into a prompt box. If you’re building something with real names or personal information involved and privacy genuinely matters, use placeholder data (“Jane Smith”, “test@example.com”) while you’re working things out with the AI, then swap in real data once the structure’s built and tested.

On things breaking, which will happen at some point: describe the problem specifically rather than just saying “it’s broken”. Tell the AI what you expected to happen, what actually happened, and paste the exact error message if there is one. “The button doesn’t work” gets you a worse answer than “when I click the contact button on mobile, nothing happens and no error shows”.

If a whole page looks wrong, check first whether it’s a real bug or just how narrow your browser window is. A surprising number of “broken” sites are just fine, being viewed on an oddly sized window.

And if you’re properly stuck with code you don’t understand, that’s normal. Paste the error and the relevant bit of code back into the AI and ask it to explain what’s going wrong before it fixes it. Understanding the fix, even loosely, means you’ll spot the same problem faster next time.

Questions people ask

Which AI assistant should I use to build a website?

ChatGPT, Claude, or Gemini all work fine for planning your site and writing copy. Pick whichever one you already have an account with, there's no need to overthink it at this stage.

Can I build a website with AI without knowing how to code?

Yes. If you don't want to see a line of code, use AI app builders like Lovable, Bolt, or v0, where you describe the site in a chat and it builds the whole thing, front end and back end.

Is it free to host a site built with AI?

Cloudflare Pages, Netlify, and Vercel all offer free tiers that are genuinely usable for small sites, and they connect nicely to the AI builder tools. Check what's included yourself, as it changes. You'll still need to buy a domain from a registrar.

What should I never paste into an AI chat when building a site?

Never paste passwords, API keys, payment details, or real customer data into an AI chat, ever, even the paid tools. Use placeholder data like "Jane Smith" or "test@example.com" while you work things out, then swap in real data once the structure's tested.

How do I check my new website actually works?

Open it on your actual phone, not a shrunken browser window, click every single link, and submit any form to see whether it goes anywhere. Then show it to one other person and ask what the site is for without telling them first.

Keep exploring

If all of this sounds like more setup than you fancied and you’d rather skip straight to a chat interface that builds the whole site for you, have a look at our guide “How to get AI to build me a website with Lovable”, it covers one specific tool in more depth than we’ve gone into here.

And if you get your site built but the words on it feel a bit flat, a bit like every other AI-written homepage, the guide “How to get AI to sound like my brand” is worth reading next.

Sources and review notes

Review date: 15 September 2026 — every source above was opened and checked against the text on that date.

Disclosure: ScriptGrain is one of our products — this site is made by the same studio, Adapt Progress Evolve. We have tried to compare fairly, and the alternatives named are real and worth a look.