Vibe coding a business website with AI builders: what works and what breaks

AI builders such as Bolt, Lovable, v0 and Replit, plus AI coding tools like Cursor and Claude Code, can produce a good-looking, working website in an afternoon. For prototypes, landing pages and simple brochure sites, that is genuinely useful. The trouble starts when the site has to do business work: deliver every lead, rank in search, protect customer data and keep working after the hundredth prompt. Here is an honest view of where these tools shine and where they usually need help.

What "vibe coding" means

The phrase describes building software by describing it. You type "a website for a family-owned roofing company with a quote form and a gallery," the tool writes the code, and you keep asking for changes until it looks right. Many people never open the code at all.

Two broad styles have emerged:

• Browser-based AI builders (Bolt, Lovable, v0, Replit) that handle the code, preview and often hosting in one place. They are aimed at people who want a result, not a codebase.
• AI-assisted coding workflows (Cursor, Claude Code and similar tools) where an AI works inside a real project on your machine or repository. These suit people comfortable with files, Git and a terminal, and they produce code a developer can keep working on.

The main tools, briefly

These products change quickly, often month to month, so treat any feature list (including ours) as a snapshot and check current capabilities and pricing directly.

What AI builders do well

• Speed to a first version. A founder can test an idea, show investors a clickable product, or validate a landing page before spending real money.
• Clear communication. A working prototype explains what you want to a designer or developer better than a long brief.
• Simple sites. A few pages, a contact form, a menu or a portfolio can be perfectly serviceable.
• Internal tools. Small dashboards and calculators used by a handful of staff are a sweet spot.
• Modern stacks. Most builders output React, often with Tailwind and a hosted database, which is a reasonable foundation if it is cleaned up later.

We use these tools ourselves for early concepts. The question is not whether they are useful, it is what has to happen before a business depends on the output.

What commonly breaks

These are the issues we see most often when owners bring us an AI-built site.

Forms that quietly fail

The form looks fine and shows a thank-you message, but submissions go nowhere, land in a database nobody checks, or send from an unauthenticated address straight to spam. Test every form end to end, confirm where submissions are stored, and make sure notification emails come from a domain with proper SPF, DKIM and DMARC. Add spam protection too, or a public form will fill with junk.

SEO basics

Many builders produce a single-page app where content is rendered in the browser by JavaScript. Search engines can render JavaScript, but these sites often also miss the basics:

• Unique page titles and meta descriptions per page
• Real, crawlable URLs instead of one route doing everything
• An XML sitemap and a sensible robots.txt
• Proper heading structure and image alt text
• Redirects from an old site's URLs, so existing rankings are not lost
• Open Graph tags so links preview properly when shared

None of this is exotic, but a prompt rarely produces it unprompted. Server rendering or static generation, as we describe in React and Next.js for business websites, solves much of it at the foundation.

Authentication and security

This is the most serious category. AI-generated apps can ship with database rules that let anyone read or edit other users' data, secret API keys exposed in front-end code, admin pages without real access checks, or no rate limiting on logins. If your site has accounts, payments or any customer data, have someone review it before launch. Our website security checklist is a good starting point, and it helps to understand where your API keys live and who can reach your database.

Hosting and domains

Builder hosting is convenient until you need to connect your own domain correctly, set up redirects from www, keep email working when DNS changes, or move to another host. Before launch, confirm you can export the code, know where the database lives, and understand who controls DNS. Our domains and hosting guide for GoDaddy walks through keeping those jobs separate.

Analytics and tracking

It is common to find no analytics at all, analytics firing twice, or tracking scripts loading without the consent handling your market requires. Set up Google Analytics 4 or a privacy-friendly alternative deliberately, define the conversions that matter (form submits, calls, bookings), and test them.

Performance

Large JavaScript bundles, unoptimized images and heavy animation libraries can make an AI-built site feel fast on a laptop and slow on a phone. Check Core Web Vitals on real mobile devices.

Maintainability

The biggest long-term issue. Each prompt patches the code without a plan, so after many rounds you get duplicated components, dead code and fixes that break other features. Without version control, there is no easy way back to the last good version. If the tool supports GitHub sync, turn it on early.

A pre-launch checklist for an AI-built site

When to hand it to a studio

Keep building yourself while the site is a prototype or a simple brochure and nothing breaks when you change it. Bring in professionals when:

• The site starts carrying meaningful revenue or lead flow.
• You are adding logins, payments, customer data or integrations with a CRM.
• Every new prompt breaks something that used to work.
• You need it to rank and get cited in search, not just exist.
• You want a content team to edit pages without prompting an AI.

At that point there are two sensible paths. If the site is basically sound and just needs ongoing care, our sister company AftUp runs monthly care plans for sites built in tools like Bolt and Lovable, covering uptime, fixes, SEO and analytics. If the project has outgrown its foundation, we use the prototype as the brief and rebuild it properly, typically in Next.js with a headless CMS or in WordPress or Webflow depending on who edits it. Our web development and web apps services cover that work.

How we'd decide

Use AI builders to move fast on prototypes, campaigns and simple sites, and enjoy how quickly you can test ideas. Before the site becomes a business system, check forms, SEO, security, hosting, analytics and code ownership. When it carries real revenue or customer data, get a second pair of experienced eyes on it. If you have an AI-built site and want an honest review, tell us what you've built.