Vibe coding websites: what it is, and the checks it skips for a first site
Vibe coding a website means describing it in plain English and judging what the AI makes by looking at it. It suits a simple first site if you add three checks and publish with care.
Short answer: yes, you can build a first website this way with no coding experience, as long as the site is simple and you check the result yourself before anyone else sees it. Those checks matter more than which tool you pick.
What vibe coding a website actually means
The computer scientist Andrej Karpathy coined the term in February 2025. Wikipedia describes it as giving an AI model a plain-language description of a project and letting it write the code, and notes that it “may involve accepting AI-generated code without thorough review of the output, instead relying on results and follow-up prompts to guide changes.” That is how most people use the phrase. It is a nickname with no formal standard behind it, though it caught on fast: Collins made it its Word of the Year for 2025.
For a website, it looks like this. You type something like “a single page for my dog-walking business, friendly, with a contact section” (a made-up example). A few moments later you have files. You open them in a browser and look. Does it look right? That is the test.
The appeal is obvious. There is no tutorial on tags and selectors to get through first; you start with the thing you want. The weakness is just as obvious once you say it out loud. Looking only catches what you can see, on the screen in front of you, at the moment you look.
The loop: describe, look, correct
The loop is short. You describe, you look, you correct.
Your first prompt gets you a page. It is usually decent, and sometimes sure of itself about things you never asked for. You notice the heading is too big, the colours feel off, or there is a section you didn’t want. So you say so in plain English: “Make the heading smaller. Use a calmer green. Remove the reviews section.” Look again. Correct again.
I like this loop because you stay in charge of the taste while the AI does the typing. You never need to know what a stylesheet is to say “that button looks cramped”.
The loop has a blind spot, though. You only correct what you notice. If you never open the page on a phone, nobody tells the AI about the phone. If you never read the words slowly, nobody tells it about the typo. That is why the checks further down exist.
Why a static first site suits it
A static site is just files: a page, some styling, maybe a few pictures. It has no database, no logins and no payment form to go wrong where you can’t see it. There is very little to break.
That matters, because vibe coding means accepting output you haven’t read. If the thing you are building can’t do much, not reading the code costs you very little. For a brochure page, a one-page landing page or a CV site, the worst likely outcome is “it looks a bit rubbish and I try again”. Once a site stores people’s details, not reading the code becomes a real gamble. So keep your first site static, and save the bigger ideas until you have a feel for where the AI cuts corners.
Our recorded runs show what slips past a quick look. On the landing page build, the form’s messages never appeared until a later prompt asked Claude to try to break the form. On the CV website build, the small labels came out at 12.8px, which is fine on a laptop and small on a phone. Each build page has the prompts and Claude’s unedited replies.
Three checks the vibe does not do for you
This is the bit worth pinning to the wall. You will be using the same three checks whichever tool you end up with.
The phone check. Open the page on your actual phone. A narrowed browser window on your laptop is a start, but the real device in your hand is the test. A page that looks lovely on a big screen can fall apart on a small one: text running off the edge, buttons too small to tap, a picture filling the whole screen. If something is wrong, go back to the loop and say exactly what you saw: “On my phone the menu overlaps the heading.” That is a perfectly good prompt.
The text check. Read every word, out loud if you can stand it. AI will happily write smooth, confident copy that is slightly wrong: a claim you never made, a service you don’t offer, a name spelt two ways on one page. It may also leave sample text in place. On the CV build, Claude marked its sample jobs and degree with yellow PLACEHOLDER tags, which was helpful, but they are still yours to replace. You are the only person who knows what is true about your business, so you are the only one who can do this check.
The links check. Click every link and every button. Does the email link open an email? Does the contact button go somewhere? Does the link to your other page land on that page? Broken links don’t announce themselves. On the website build, Claude didn’t make a “page not found” page, so a mistyped address showed the home page once the site was live. Nothing looked broken, which is exactly why you have to try it.
Where vibe coding stops: publishing and keeping it safe
Up to now you have been working on your own computer, and your mistakes are private. Publish, and they are public. This is the stage to slow down.
The route on our start page keeps your site in a GitHub repository and has Cloudflare publish whatever is in it, with no terminal involved. At the time of writing (21 October 2026), Cloudflare’s documentation says that once a Pages project is connected to a GitHub repository, Cloudflare “will automatically deploy your code every time you push a change”. In practice, every change you upload to GitHub goes live by itself, so run the three checks before you upload, and leave the uploading until you are done.
A few facts from the docs, also at the time of writing:
- GitHub lets you upload up to 100 files at a time through the browser, up to 25 MiB each.
- Cloudflare’s free plan allows 500 builds a month and up to 20,000 files per site, far more than a first site needs.
- GitHub may block an upload that contains a secret such as a token. Passwords and keys don’t belong in a website’s files anyway.
To keep your work safe, keep a copy of the folder that works on your own computer before you ask for changes. Then one bad edit can’t wipe out the good version. Screens on both services change often, so follow the current steps on the start page and in the linked docs instead of something you half-remember from a video.
When you upload, you are choosing what the world can see. Give it one last look on your phone, read the words and click the links. Then upload.
When to use a site builder instead
Sometimes vibe coding is the wrong call. If you need to take bookings, sell things or keep people’s details, a site builder takes much of that worry off you, because someone else has already dealt with the fiddly, risky parts. If you would rather not think about hosting at all, that is a fair reason too.
We compare the main builders with the build-it-yourself route in website on Wix, Squarespace, WordPress or Cloudflare. Read it before you commit either way. The honest answer depends on what the site has to do.
Where to start
Start small: one page, something you can describe in a couple of sentences. If you are still not sure this is realistic for you, can I use AI to build a website answers that directly. When you are ready, set up the free accounts on the start page, pick a build, and run the three checks every time. That habit is the part of vibe coding worth taking seriously.
Questions
Questions people ask.
What is vibe coding in plain English?
You tell an AI what you want in everyday language, it writes the code, and you judge the result by using it instead of reading the code. You describe, it builds, you look and ask for changes. Andrej Karpathy coined the term in February 2025.
Can I vibe code a website with no coding experience?
Yes, for a simple first site. You don't need to understand the code to say what looks wrong. You do need to check the result properly: on a real phone, word by word, and link by link.
Is a vibe coded website safe to publish?
A simple static site has very little in it that can go wrong. The safety comes from the checks you do before you upload, from keeping a copy of the version that works, and from never putting passwords or keys in the site's files.
Do I need to read the code AI writes for me?
Not for a first static page. You do need to read every word your visitors will see, because that is the part where AI is most likely to be quietly wrong or to leave placeholder text behind.
Is vibe coding better than a site builder for a first website?
It depends what the site has to do. For a simple page you want full control over, vibe coding fits well. For bookings, payments or storing people's details, a site builder is usually the calmer choice.