Are vibe coded websites safe for a small business?

A website built by describing it to an AI tool can suit a small business. It working on launch day tells you nothing about whether it is safe. Here is what a review checks, with the failures we have found on AI-assisted sites.

On this page

An AI-built website can be a sensible choice for a small business, and "it works" is not evidence that it is safe. Treat the output as a draft that needs a person who is accountable for it. OWASP, the group behind the standard list of web security risks, says the same in its guidance on coding with AI: keep a human owner and have a developer approve AI-generated changes.

We build sites with an AI coding assistant every week, so none of this is an argument against the tools. It is an account of what the review step catches, because the review is the part you are really paying for.

What the research says, and what it does not

Two figures get quoted about AI and code security, and both are usually stated too loosely.

Veracode's benchmark gave more than 100 AI models 80 coding tasks, each built around a known weakness such as SQL injection or cross-site scripting. In its October 2025 update, 45% of the generation tasks produced code with a known security flaw. That is a rate per task in a test, and it varied a lot between models. It does not mean 45% of AI-built websites are unsafe.

The other figure is about 40%, from a New York University study of GitHub Copilot, which found roughly 40% of programs vulnerable across 1,689 programs generated in security-sensitive scenarios. It tested a 2021 version of the tool, so it shows that plausible code can be insecure. It is not a current failure rate.

Neither study tells you the share of Australian small business sites at risk. Both support the same practical step: check generated code before it faces the public.

What a review catches on real sites

These come from our own AI-assisted builds and from sites we have been asked to look at. Details are removed and no client is named.

  • Server-only code reaching the browser. On one build, a helper that talks to the database sat in a module the page also imported. The login page rendered normally and did nothing when used, because the browser could not load the server code. Looking at the page would never have shown it. Using the form did.
  • A framework upgrade that broke every page. After a security update to a web framework, two copies of one of its core packages ended up installed side by side. The build and the type check both passed, and the live site returned an error on every page. Only requesting the live site caught it, which is why we release to a small share of visitors first.
  • A security policy that blocked the things the site depended on. A strict content security policy stopped a booking widget and the advertising and analytics tags from loading, for about three months. Automated audits during that period passed, because they read the policy but do not watch what it blocks.
  • A form that said it worked. A move between hosts left leads going to an old preview address for several days. On another site, a signup form returned a success message while the email service rejected every send. In both cases the visitor saw a thank you page and the owner saw nothing.

None of these is exotic. Each one looks fine in a demo, and each cost real enquiries or took a site down until someone tested it properly.

What to ask a reviewer to check

OWASP's current list is the Top 10:2025. It includes broken access control, security misconfiguration and software supply chain failures. It is an awareness list rather than a certificate, so use it to shape the questions below.

RiskWhat it means for your businessWhat a review checks
Keys and secrets in the browserAnything sent to a visitor's browser can be read. A private key placed there is public.Deployed JavaScript, network requests and the code repository for tokens and keys. Exposed ones are revoked and replaced.
Unprotected forms and endpointsSomeone can call the service behind a form directly, without using your page. Hiding a button does not protect what it does.Server-side permission checks on private actions, and request limits and spam handling on public forms.
Missing input checksUnexpected input can break a booking, overload the site or be treated as an instruction.Server-side checks on type, length and required fields, tested with oversized and malformed submissions.
DependenciesYour site inherits the risk of every package it includes, and AI tools can suggest packages that do not exist or old versions with known flaws.A list of what is installed, a check that each package is genuine, an audit for known vulnerabilities and a named person who updates them.
Security headersBrowser instructions can limit which scripts run and whether another site can frame your pages.The real response headers, and a content security policy tested so it does not block what the site needs.
Hosting and recoveryLosing the admin account or having no backup can stop trading even when the code is sound.Multi-factor sign-in, who holds each account, backups and a recovery plan.

A public enquiry form does not need a customer login, but its endpoint still needs validation and abuse controls. Reading customer records, changing bookings or reaching an admin area does need a permission check that does not trust a record number typed into the address bar. The Australian Cyber Security Centre's small business guidance starts with multi-factor authentication, software updates and backups, and applies to the website's accounts as much as the office computers.

The part people forget: search and speed

Security is half a review. Google does not ban AI-assisted content, and its guidance on generative AI asks for useful, accurate pages and warns against producing many pages that add nothing. A review should also check that:

  • page titles and descriptions are specific to each page;
  • the text and links are visible once the page has rendered, not only in a screenshot;
  • nothing accidentally tells search engines not to index the site;
  • the pages load acceptably on a mobile connection.

An attractive page can still be slow and thin, and a fast site can still be insecure. We cover the owner-side checks in how to tell whether your website was built badly.

Privacy and who is covered

Most businesses with an annual turnover of $3 million or less are outside the Privacy Act, but the OAIC lists exceptions, including health service providers and businesses that trade in personal information. A small practice with an AI-built booking form could be covered despite its size. Before a site collects customer details, trace where they go: which inbox, which database, who can read them and how long they are kept. Our post on whether a small business needs a privacy policy covers the policy side.

When an AI-built site is a fair choice

The risk depends on what the site does.

  • A brochure site with an enquiry form is a reasonable fit. Review the secrets, the form, the headers, the dependencies and the copy.
  • A booking system, customer portal or shop needs everything above plus server-side permission checks, workflow testing and privacy handling. Do not launch a custom login or payment flow without a review.
  • A site with a live AI feature, such as a chat box, adds the behaviour of the AI itself. Credible-looking output can still be false, so limit what the feature is allowed to do.

Before launch, ask for a short written release note covering what was reviewed, what was found, what was fixed and retested, what is still open and who maintains the site. Our launch checklist is a good starting list, why contact form emails land in spam explains one of the quieter failures, and what a maintenance plan should cover covers the ongoing work. Make sure you also hold the accounts, as explained in who actually owns your website. If you are deciding between a builder, a professional and a professional using AI, see AI website builder or a professional.

How we use AI on your site

We build with AI and review the result. Pages are written as typed code in version control, so each change can be read, tested and rolled back. Releases go to a small share of visitors before everyone, and the checks above are run on the deployed site rather than the preview. Why we moved our own and client sites off WordPress is in is WordPress still worth it in 2026. If you would like a site built and reviewed this way, see pricing or get started.

Common questions

Are vibe coded websites safe?
Not by default, and not automatically unsafe either. An AI-built brochure site with a contact form can be reasonable once someone has reviewed the deployed site for exposed keys, form handling, security headers and dependencies. A site with logins, bookings or payments needs a much deeper review before launch.
What is vibe coding?
Building software by describing what you want to an AI tool and accepting the code it produces, often without reading it closely. For a website, that usually means prompting a tool until the pages look right and then publishing them.
What are the downsides of vibe coding a business website?
The page can look finished while server-side checks, form protection and error handling are missing. Nobody may be responsible for updates, so dependencies go stale, and the owner often cannot tell whether a form still delivers enquiries.
Can I make a website with vibe coding?
Yes, and a simple site can be made quickly. Before it takes customer details, have someone check where those details go, who can read them and what happens when something breaks. Decide who looks after it after launch.
Does Google penalise AI-built websites?
No. Google says AI-assisted content is not against its guidelines when it is helpful and accurate, and that using automation mainly to manipulate rankings is spam. Check the facts, the page titles and descriptions, how the pages render for crawlers and how fast they load on a phone.
How do I check a vibe coded website before launch?
Ask for a written release note covering what was reviewed, what was found, what was fixed and retested, and who maintains the site. Test the enquiry form yourself, and ask whether any keys or tokens are visible in the code sent to the browser.

Want a website that turns readers into customers?

A custom site, hosting and upkeep for one monthly fee, with your leads and Google results in a dashboard you can check any time.