TL;DR:
- Yes, AI can build a website – but not by itself, and not without technical knowledge to back it up
- The real question is whether you’re equipped to own, host, secure, and maintain what it builds
- A recent Facebook thread proved the point better than any blog post could
- Non-technical business owners asking AI to build their site are walking into a minefield they can’t see
- Technical users have real, legitimate tools – but there’s still a learning curve
- If the thread below made your head spin, that’s your answer
Someone posted in “Claude AI Community” Facebook group asking for help. The exact post by the Anonymous Participant was “I’m lost!! I am on Claude.. I want to make a website for my business idea and I’m struggling with web flow.. I’m obviously not a tech person.. should it be this difficult.. when I asked Claude to do it for me it said it can’t build the website for me.. what am I doing wrong? Please help!!”.
They’d asked Claude to build it and Claude said it couldn’t. The question: “what am I doing wrong?”
The comments exploded!
Over 280 commenters echoing similar sentiments. Learn UI/UX first. Use Squarespace. Use Claude to generate an HTML file, then transfer your hosting to Netlify. Use Claude Code, push to GitHub, host on Railway. Ask Claude to set up SSH access to your web host, then switch to Claude Code to build and manage the site. Use a prompt that doesn’t refuse requests. Just pay someone.
One comment stood out from the rest by a user “MoltCult”: “Sounds like if you got Claude to build it you wouldn’t know what to do next anyways.”
That’s the whole post right there. But let’s back up.
AI Can Build a Website. That’s Not the Issue.
Let’s be accurate about this, because a lot of content out there gets it wrong and I’m not here to blow smoke your way.
AI – specifically tools like Claude Code – can absolutely build a website. Given the right access, it can create a file structure, write HTML, CSS, and JavaScript, install WordPress, configure a database, set file permissions, and push a site live. This is not theoretical because people are actually doing it.
What it requires is shell access to a server, working knowledge of hosting environments, understanding of DNS and domain configuration, and enough technical fluency to know when something it generates is wrong. Don’t be fooled, it will generate things that are wrong – confidently and without warning.
The anonymous poster wasn’t using Claude Code. They were using the chat interface – Claude.ai. Whether accessed via desktop or browser, Claude has no connection to your hosting account, your domain registrar, or your file system. It can write your website content or even write your code. It cannot deploy the website. That distinction matters enormously.
What the Thread Actually Revealed
Going back and reading a couple of those comments as a checklist.
Someone told the poster to transfer hosting to Netlify. Does the poster know what Netlify is? Do they know what transferring hosting means, or what breaks when you do it? Someone told them to push files to GitHub. Do they have a GitHub account? Do they know what a repository is, what a commit is, what “pushing” means in a development context?
Someone told them to ask Claude to set up SSH access to their web host. SSH (Secure Shell) is a protocol for accessing a server remotely using command-line tools. It is how developers get into the guts of a server. Handing that access to an AI agent – or to anyone – without understanding what they can do with it is a significant security decision.
The poster didn’t know to ask any of those questions. That’s the point.
That original question – “what am I doing wrong?” – is a clear indicator there’s a lot of ground to cover first. Not knowing the difference between building a website and hosting one, between a chat interface and an agentic coding tool, between generating files and deploying them – those gaps are not small. They are the entire job.
One commenter named Rafał Gąsiorowski said it quite plainly: “Oh boy, security engineers, pentesters [those are penetration testers – hired to legally hack systems and find vulnerabilities before the bad guys do], and data recovery specialists will get tons of money in the incoming years.” That’s not hyperbole. It’s a prediction based on what happens when people deploy infrastructure they don’t understand.
I know this territory firsthand. In 1996, a company saw my enthusiasm for learning and building websites. They let me build their first one (basic by any standard). When I got to the contact form, I built out every field and when I tested it – it didn’t work. Their corporate IT person – to their credit – didn’t laugh. What I was missing was the action mechanism: the script that actually handles sending the form. I didn’t know it existed. I stopped the project and said I’d hit my limit. I’d later learn CGI-Perl scripts for form sends, eventually PHP. But that moment taught me something I’ve never forgotten: the wall you don’t know about is the most dangerous one.
That was 1996. The tools are different now. The wall is the same. Know your limits.
The Minefield Nobody Mentions
Here’s what an AI-built site can leave behind if nobody with technical knowledge is involved:
Security misconfigurations. File permissions set too broadly. Admin paths left at defaults. No firewall rules. No brute-force protection. AI generates functional code. It does not automatically generate hardened code. If you don’t know the difference, you won’t know what to fix.
No update strategy. WordPress, plugins, themes – they all need updates. Some updates break things. Knowing which ones, and why, and how to test before pushing to a live site – that’s not something you prompt your way into. It’s experience.
No documentation. A site built through a series of AI prompts, with no human who understands the architecture, has no paper trail. When something breaks – and something always breaks – you’re starting from scratch trying to figure out what’s running, what version it is, and what changed.
Hosting basics aren’t obvious. What’s an SSH? What’s a nameserver? What does it mean when your SSL certificate expires and your browser throws a warning? What’s the difference between shared hosting and a VPS? These aren’t questions AI reminds you to ask. They’re questions you don’t know to ask until something is already on fire.
If You Are Technical: These Tools Are Real
If you have a development background – or you’re genuinely committed to building one – the tools are legitimate and worth knowing.
Claude Code (Anthropic) is an agentic coding tool that can operate in your terminal, read and write files, run commands, and build projects. It is the tool people in that thread were gesturing toward, often without naming it correctly. It works. It requires you to understand what it’s doing. At minimum, include a CLAUDE.md file to brief it on your project and a version control file to track what changed and when.
ChatGPT with code interpreter and similar AI coding assistants are strong at writing and debugging code when you already understand the stack you’re working in. They accelerate skilled developers. They do not replace the skill.
Cursor is a code editor with AI built in. It’s designed for developers who want AI assistance inside their workflow – writing, reviewing, and refactoring code in real time. It’s genuinely useful. The learning curve is real.
Framer and Webflow have incorporated AI features for layout generation and copy. They’re legitimate website builders with real hosting infrastructure. Framer in particular has a following among designers who can code. If that’s not your background, the AI features won’t close the gap.
The through-line across all of these: they make skilled people faster. They do not make unskilled people skilled. The knowledge floor hasn’t moved. The ceiling has just gotten higher for the people who were already above it. You should commit to learning the basics before you commit to building to keep your digital environment secure.
The Questions You Should Actually Be Asking
The question shouldn’t be “can AI build my website.” The question is “should I be building my website with AI?”
Can I set up and configure hosting? Do I understand DNS? Can I recognize a security misconfiguration? Do I know what to do when an update breaks something? Can I read error logs? Do I have a backup strategy?
If those questions feel foreign, that’s useful information. It means the build is the least of it. Anyone can generate a website with AI right now. The hard part – the part that protects your business, keeps the site running, and keeps it secure – has always required someone who knows what they’re doing. AI hasn’t changed that. It’s just made it easier to skip past it without realizing you did.
The poster wasn’t doing anything wrong. It was a reasonable question in a world where AI is being sold as “just ask and it will do it for you.” The problem is that promise is only half true – the half nobody talks about is everything that comes after the build.
Ready to Skip the Minefield?
If you read this post and felt the ground shift under you a little, that’s the right reaction. A website is a business asset. It should be built, documented, and maintained by someone who understands what’s running under the hood.
I’ve been building websites since 1996. I use AI in my daily stack and think you should too – with the right foundation under you. The difference is I know what to do with what it gives me – and what to throw out.
Ready to have your website built or redesigned? Let’s talk.
