Chat your way to a first draft, then get it onto the actual internet.
Ten minutes of describing what you want, and Claude hands back a genuinely good-looking website in the preview pane. Then comes the part the demo clips skip: getting it live and keeping it there. The homepage that looked perfect in the chat can ship with every image broken, a contact form that submits into nothing, and a phone number you can only change by starting a fresh conversation and re-uploading a file by hand. Yes, you can build a real website by chatting with Claude, and non-developers do it every day. Building the draft is the easy 10 percent. This covers the whole thing: the prompt that gets a strong first draft, the three honest ways to publish it, what it costs, and where the plain approach turns into a chore versus where the conversation edits your real, live site in place. That last route runs through Devani, a fully managed CMS you talk to with the same Claude account you already have.
Start to finish, the way it actually goes.
Every route shares the same first two moves. They split at publishing, which is where most of the friction lives.
- Describe the site in plain language. Open a conversation at claude.ai and tell it what you're making, who it's for, and the sections you want. Claude writes the HTML and CSS and renders a working preview right in the chat through Artifacts, so you see the real page, not a mockup.
- Iterate by talking. "Make the header darker," "move testimonials above the pricing," "warmer tone on the about copy." Each request redraws the preview in seconds. Keep going until it matches what's in your head. This is the part that genuinely feels like magic, and it's the part every approach gets right.
- Get it out of the chat. A preview inside Claude isn't a website anyone else can visit. You export the HTML (the download arrow in the Artifacts pane), rename the file to index.html so a web server knows where to start, and drop it in a folder.
- Publish to a host. Static hosts take that folder and give you a live URL. Static.app, GitHub Pages, Cloudflare Pages, and Netlify all have free tiers. Static.app is the least technical: sign up, drag a zipped folder in, get a something.static.domains address in about ten seconds.
- Point a domain, if you want one. The free tiers hand you a subdomain. A real yourname.com is a separate $10 to $20 a year from any registrar, plus a few DNS records the host tells you to add.
- Edit it later. This is the step nobody plans for and everybody hits. On the plain route, a change means reopening the old conversation, asking for the edit, re-downloading the file, and re-uploading it to replace the old one. Small change, whole round trip, every time.
What to tell Claude so the first draft isn't generic.
"Make me a website" gets you a website nobody asked for. Four things in the first message do most of the work.
What it's for, who it's for
"A one-page site for a mobile dog groomer serving retirees in a small town" gives Claude a tone, a color instinct, and a rough content shape in one sentence. Purpose and audience up front save you a dozen correction rounds later.
Name the sections
Spell out the blocks: hero with a headline and a call to action, services, a short about, testimonials, a contact form. Claude will invent a reasonable set if you don't, but naming them yourself is how you get the page you meant instead of the page it guessed.
Give it the look
"Warm off-white background, near-black text, one soft blue accent, generous whitespace, no stock-photo clutter." A short style brief anchors the whole draft. Vague on style and you'll get the same rounded-card, purple-gradient default everyone else gets.
Hand it your real content
Paste the actual services, prices, and about text if you have them. Claude fills gaps with placeholder copy, and placeholder copy is exactly the stuff people forget to replace before publishing. Real words in means less rewriting out.
The draft is the easy part. Publishing it, and then editing it forever, is where you actually live.
Three traps between the preview and a site that works.
The chat-to-preview loop is polished enough that it hides how much is left to do. Three things bite almost everyone the first time, and none of them are Claude's fault so much as they're the nature of a single HTML file living outside a real content system.
First, the images break. The pictures in your Artifacts preview are often temporary links tied to the chat session, and they die the moment the page leaves Claude. Publish and you get a wall of broken-image icons. The fix is to host every image yourself with public URLs, or to point at files sitting in the same folder as your index.html, which is more file wrangling than the smooth preview led you to expect.
Second, the interactive bits are decorative. A contact form in exported HTML is a nice-looking form that goes nowhere, because a static file has nothing on the other end to catch a submission. Making it real means bolting on a third-party form service, and a store or a booking calendar means bolting on more. What you've built is a digital brochure, which is genuinely enough for a landing page or a portfolio, and genuinely not enough for a site that does anything.
Third, every edit is a manual round trip. Change your hours, add a service, swap a headline, and the plain route sends you back to the conversation to regenerate, re-download, and re-upload the file. That's fine once. By the fifth time you're maintaining a website by copying files around, which is the exact chore a website was supposed to spare you.
Same conversation, very different aftermath.
"Build a website by chatting with Claude" covers three different methods, and they diverge entirely at the point where you have to live with the result.
Artifacts + a static host
The simplest path. Chat, export, drop the file on a free host.
- ✓ Nothing to install, free to start, live in minutes
- ✓ Perfect for a one-page landing site or portfolio you'll rarely touch
- × Chat images break on publish; forms and stores need bolted-on services
- × Every future edit is a download-and-reupload loop by hand
Claude Code + Git
The most control, if you're comfortable near a terminal.
- ✓ Full version history; Claude commits and pushes, your host redeploys
- ✓ Genuine best pick for a developer who wants a real build pipeline
- × GitHub and Cloudflare setup is a real learning curve for a non-coder
- × You still own hosting, forms, media, and SEO plumbing yourself
Claude + Devani
The conversation edits your live site, not a copy of it.
- ✓ Connect your own Claude account over MCP, no API keys, no copy-paste
- ✓ It edits live content and layout inside the builder; every change snapshots with one-click rollback
- ✓ Fully managed with a genuinely free tier, database-free, near 100/100 Lighthouse and a 0.7-second desktop LCP out of the box, with forms, blog, and media built in
- × It's a full CMS to stand up, so for one throwaway HTML page you'll never edit again, the Artifacts route is genuinely simpler
The difference that matters is where the words land. With Artifacts or Claude Code, you chat in one place and the website lives in another, and a person or a Git push has to carry changes across the gap. Devani is MCP-native, so the assistant works hand in hand with the visual builder: you connect the same ChatGPT or Claude account you already pay for, and "change the hours on the contact page" edits the published contact page. There's nothing to export and nothing to redeploy, because the thing you're chatting about is the live site itself. A site can be built this way in ten to fifteen minutes and go live in under a minute on the managed free tier, with hosting, SSL, and backups all handled for you.
Cheaper than it sounds, billed in a few separate places.
No single price tag covers this, because "chatting with Claude to build a site" spans an AI plan, a host, and maybe a domain. Here's the honest breakdown in USD.
| What you need | Typical cost (USD) | Note |
|---|---|---|
| A Claude plan | Free to start; Pro around $20 / mo | A free account runs Artifacts; heavier or longer building wants a paid plan |
| Static hosting | $0 | GitHub Pages, Cloudflare Pages, or Static.app free tier, on a subdomain |
| Custom domain | $10 to $20 / yr | Optional, from any registrar; the host gives you the DNS records |
| Forms and custom domain on a static host | around $5 / mo | If you go the Static.app route and need working forms |
| Devani | Free tier, then flat plans | Fully managed: hosting, SSL, forms, and media included; live in under a minute |
For a one-page brochure you'll leave alone, the plain route is close to free and hard to beat on effort. Once the site needs to grow, get edited often, or actually do something, the math shifts toward a real system rather than a hand-published file. If you're pricing a proper build out, what a small business website really costs lays out where the money goes.
Can you really build a website just by chatting with Claude?
Yes. From a plain-English description, Claude writes complete HTML and CSS and shows a working preview in the chat through Artifacts. You never touch code. What trips people up is the publishing rather than the building: that preview has to be exported and put on a host before anyone else can see it, and that step is where a chat-only tool stops and a real platform keeps going.
Do you need to know how to code?
No. Describing what you want in normal sentences is the whole skill for the building part. Some publishing routes ask more of you (GitHub and Cloudflare have a learning curve), but the least technical paths, dragging a file onto a static host or connecting Claude to a CMS over MCP, need no code at all.
Why are my images broken after I publish?
The images in a Claude preview are usually temporary links tied to your chat session, so they stop working once the page leaves Claude. Fix it by hosting each image yourself with a public URL, or by keeping the image files in the same folder as your index.html. A platform with a real media library sidesteps this entirely: Devani, for instance, auto-compresses uploads to WebP and serves them from a CDN, so nothing points back at a dead chat link.
How do I edit the site after it's live?
It depends on how you published. With an exported HTML file, you reopen the original conversation, ask for the change, re-download the file, and re-upload it to replace the old one. Every edit is that round trip. If Claude is connected to a CMS like Devani over MCP instead, you just tell the assistant what to change and it edits the live page directly, then snapshots it so you can roll back if you don't like the result.
How long does it take?
The draft is fast: a solid first version in ten to fifteen minutes of back-and-forth. Publishing a static file adds a few more minutes for exporting, hosting signup, and a domain if you want one. Connecting Claude to Devani gets a site live in under a minute on the managed free tier, and edits after that are as quick as sending a message.
Is a website built this way fast and good for SEO?
A single exported HTML file can load quickly because there's not much to it, but you're on the hook for the meta tags, structured data, sitemap, and redirects yourself, and a hand-published file has none of that by default. A CMS handles the SEO plumbing for you. Devani serves plain static files from a CDN with per-page SEO built in, which is how it lands near 100/100 Lighthouse without you tuning anything.
Chatting with Claude to get a website is real, and for a simple page it's the fastest first draft you'll find anywhere. The honest gap is everything after the preview: publishing, media, forms, and the endless small edits a live site actually needs. The plain export-and-host route serves a brochure page well and stops there. For a site you'll keep editing, connecting Claude to a CMS built for it means the conversation never leaves the live site. For the wider view of how these tools differ, and why "generate a draft" and "run a real site" are two different jobs, this look at AI website builders is the companion piece.
Talk to your site, not a copy of it.
Connect the Claude account you already have and edit the live page by chatting. Free to start, fully managed, and live in under a minute with nothing to run.