Can AI build your business website?

The short answer

An AI tool can give you a website that looks finished. Most of what makes a business site work sits behind the look, and that is where AI drafts tend to break:

• Facts. The text sounds right and may still be wrong: hours you do not keep, services you do not offer, a qualification nobody holds.
• Forms. The page has a contact form, but it may send messages nowhere, or to an inbox nobody reads.
• Search. Some sites built by AI tools show search engines and link previews a nearly empty page.
• Ownership. The site, the domain and the code may sit in an account you do not control.
• Access. Missing labels, faint text and images without descriptions shut some visitors out.

None of this means you should avoid AI. It means you treat what it produces as a draft from a fast junior who has never met your customers, and you check it before it goes live.

Three kinds of AI help

The tools people mean by AI website builders work in different ways, and each one leaves different gaps.

• A chat assistant such as ChatGPT. It writes text and code from your description. Code from a chat is only a file: to become a website it needs hosting, a domain and somewhere for the form to send its messages.
• The AI builder inside a website platform. Wix, for example, builds a first version of the site from a chat, with pages, text, images and features such as booking for your trade, and you then edit it like any other Wix site. Squarespace offers its own. The result lives on that platform, with that platform's limits.
• An app builder such as Lovable. It builds a site or a small web app from a description, hosts it and can sync the code to a GitHub repository you control. It can do more than a website platform, and it leaves more decisions to you, such as how forms send email.

For a plain business site, the AI builder inside a website platform is usually the safest of the three, because hosting, forms and the search basics come with the platform. A chat assistant suits someone comfortable with code. An app builder suits a site that is closer to an application.

What AI does well

Used as a helper, AI saves real time on the parts most owners find slow:

• A first draft of each page from your rough notes, which you then correct.
• A page plan: which pages a dog groomer or a bookkeeper needs, and what goes on each.
• Shorter, plainer versions of text you already wrote.
• Draft answers to the questions customers really ask, if you paste the questions in.
• Draft descriptions for your photos, for people who use screen readers.
• The code for a simple page, if someone checks it.

The common thread is that AI is good at turning material you supply into a first version. It is bad at knowing anything about your business that you did not tell it, and it will fill the gaps with something plausible.

So give it the facts and the limits up front. A request such as this gets a far better first draft than "make me a website for my dog grooming business":

• Write the home page for a dog grooming business in Leith, Edinburgh. Services: full groom, bath and tidy, puppy introduction. Open Tuesday to Saturday, 8am to 4pm. Customers book online or by phone. Most questions are about prices by size and coat, and whether we take nervous dogs. Use only these facts, and do not add reviews, numbers or claims I have not given you.

Check every fact

Ask an AI tool for a home page for a dog grooming business and it may promise certified groomers, same-day appointments, free parking and fifteen years of experience. It writes what similar businesses often say. If any of it is untrue for you, it is now a false claim on your website.

Read the draft line by line against reality, with a pen:

• Opening hours, including holidays, and how soon you can really see someone.
• Every service listed, and every one missing.
• Prices, or what the price depends on.
• Areas covered, and any you do not cover.
• Qualifications, memberships, insurance and years in business.
• Any review, testimonial, client name or number. Delete anything you cannot point to.

Then cut the generic lines. "We pride ourselves on quality" could sit on any site in any trade. Google's guidance on AI-generated content says it looks at whether a page helps people rather than at how it was written, and generic text helps nobody. Replace it with what only you can say: the area you cover, what happens at a first visit, the questions customers ask you on the phone.

The contact form that emails nobody

A form is the part most likely to look finished and not work. What goes wrong depends on the tool:

• Code from a chat: the form has nowhere to send its messages unless someone connects it to a form service or writes the code that sends them.
• A website platform's AI builder: the form works, but it may send to the email address of whoever made the account, which may not be the inbox your team reads.
• An app builder: sending email needs a connected email service, and enquiries may be saved in a database nobody looks at.

Test it the way a customer would. On your phone, send three enquiries: a normal one, one with a long message and one with an apostrophe in the name. Check that each one arrives in the right inbox and not in spam, that replying goes to the customer and not to a no-reply address, and that the page tells the visitor what happens next.

A broken form shows nobody an error. The enquiries just stop arriving. Test it again after every change to the site, and once a month anyway.

Pages that search engines can read

Many AI app builders produce sites where the browser builds each page with JavaScript after it loads. People see the page. A program that does not run JavaScript sees a nearly empty one.

Google can run JavaScript, but its documentation describes rendering as a separate step that can be queued, and it still recommends rendering on the server or in advance, because not all bots can run JavaScript. Most social apps that build link previews do not run it either.

The tools are catching up. Lovable's documentation says apps created from May 2026 render on the server, and older ones are pre-rendered for verified crawlers when hosted with Lovable. If you move the code to another host, or use a tool that does neither, check it yourself:

• Open a page, view its source, and look for your headline and main text in it.
• Use the URL Inspection tool in Google Search Console to see the page as Google rendered it.
• Check that every page has its own address, title and description, and that menu links are real links rather than buttons.
• Paste a page link into a messaging app and see whether the preview shows the right title and image.

Put the domain, hosting and code in your name

An AI tool makes it easy to have a site live before anyone has asked who owns it. Settle it before launch:

• The domain, registered to the business on an account you control. Lovable's documentation says domains bought through it belong to the workspace, so make sure the workspace is the business's and not a freelancer's.
• The hosting or platform account, in the business's name, paid by the business.
• The code, if there is code, in a repository the business owns.
• The logins, held by at least two people in the business.

Know what you can take with you. A site made with Wix's AI builder is a Wix site, and Wix says a Wix site cannot move to another host. Wix, Squarespace or WordPress covers what each platform lets you take.

Make it usable by everyone

AI drafts often look clean and still fail the basics for people who use a screen reader, a keyboard or large text. Check these yourself:

• Every form field has a visible label. Grey example text inside a field disappears as soon as someone types.
• Every photo that carries information has a short description.
• Text is dark enough on its background to read in sunlight.
• You can reach every link, button and form field with the Tab key, and see where you are.
• Headings run in order and describe what follows.
• The page still works when you zoom the text on a phone.

PageSpeed Insights from Google runs an accessibility check alongside its speed test, and it flags many of these. It cannot catch everything, so try the form with the keyboard alone as well. For what the law expects of a business site in the US, see ADA website accessibility.

A checklist before it goes live

Copy this list and tick each line on a phone, not on the computer you built it on:

• Every fact checked against reality, and every generic line rewritten or cut.
• The phone number starts a call when tapped.
• Three test enquiries arrived in the right inbox, and replies reach the customer.
• The domain, hosting and code are in the business's name.
• Each page has its own title and description, and the sitemap is in Search Console.
• The headline and main text appear in the page source, or the tool renders pages on the server.
• Photos are resized, and the pages load quickly over mobile data.
• The accessibility check passes, and the form works with a keyboard.
• The privacy notice describes what the site really collects, and tracking waits for consent where the law requires it.
• A missing page shows a helpful message with a link home.
• Two people know how to log in and make a change.

If you are sending paid ad clicks to the site, check the page against landing pages for ads before you spend anything. The full order of checks before, during and after launch is in the website launch checklist.

Common mistakes in AI-built sites

• Publishing the first draft because it looks finished.
• Keeping invented reviews, numbers or claims because they sound good.
• Ten near-identical pages for ten towns, written to catch searches. Google treats those as doorway pages.
• A contact form that was never tested, or that sends to a personal inbox.
• A privacy notice generated for a different kind of business.
• No one in the business able to change the opening hours without asking the tool or the person who used it.

Every one of these is quick to fix before launch and costs enquiries for as long as it stays.

When to get help

An AI draft plus an owner's careful checking can be enough for a simple site: a few pages, a phone number, a form that works. Get help when the site has to do more than that:

• Bookings that should land in your booking software, or enquiries that should reach your customer records.
• A store, payments or anything behind a login.
• Rules that apply to your trade, such as health information at a clinic.
• Ads you are about to pay for, where a slow page or a broken form wastes the budget.
• No time to do the checks in this guide.

Whoever builds it, ask what they check before launch. Ours: every page on phones and desktops, its speed and its search setup, every form tested from a phone, and the domain, hosting and accounts set up in your name or handed over at launch. See websites for how a build runs, and enquiry follow-up for what happens to each enquiry after the form. Our starting prices are on the prices page.