How Do You Build a Website for Free With AI?

Question: How do you build a website for free with AI?

You keep the scope small: plan a simple site, use AI to draft the pages and copy, generate a basic static HTML/CSS version or use a free site builder, check every claim manually, then publish on free hosting. The free version is usually good enough for a first brochure site, but a serious business should plan for a custom domain and real photos later.

A free AI-built website can work if the job is small enough

A free AI-built website probably will not replace a good designer or developer, but it can absolutely get a simple local business online if you keep the job small enough.

The mistake is asking AI for “a complete business website” and expecting it to magically understand the business, write honest copy, choose useful pages, create trustworthy images, set up hosting, handle enquiries, do local SEO, and make everything look like a professional studio touched it. That is too much of a blob. The result will usually be generic, overbuilt, or quietly wrong.

The better version is smaller and more useful. Ask AI to help plan a simple site. Feed it real business details. Get it to draft copy. Ask it for a sitemap. Ask it to generate a basic static HTML and CSS version. Use free hosting to publish the first version. Then check the whole thing like a human who cares whether a real customer can understand it.

A first website does not need a complicated CMS, a paid theme, a perfect logo, a custom booking system, a membership area, or a clever animation that breaks on mobile. It needs clear pages, honest copy, useful photos, a working contact method, and a web address people can visit.

Start with the right kind of website

The easiest free AI-assisted site is a static brochure site. Static just means the pages are plain files instead of a database-backed web app. Think HTML, CSS, images, and maybe a little bit of JavaScript if you really need it.

For a first version, static is a feature, not a limitation. There is less to break, less to secure, and less to maintain. You can upload the files to GitHub Pages, Netlify, Cloudflare Pages, Neocities, or another static host and have a real page online without paying for a server.

This approach is good for:

• Local business brochure sites.
• Service pages.
• Personal portfolios.
• Simple landing pages.
• Event pages.
• Clubs and community projects.
• Early product pages.
• Temporary test sites.

It is not the right first choice for everything.

I would not use a free AI-generated static site as the first version of an ecommerce store, paid membership site, private customer portal, booking system with payments, medical or legal intake form, or anything handling sensitive data. Once you have accounts, payments, private records, file uploads, or business-critical workflows, the job changes. That is closer to web application work, and the risk profile is different.

If you are trying to build an actual app, How Do You Build a Web Application? is the more relevant path. If you are building a public brochure site for a small service business, keep reading.

The example site: Green Fern Gardens

To keep this concrete, I will use a fictional example business throughout the article.

Green Fern Gardens is a small local landscaping and gardening business in Hamilton, New Zealand. It offers lawn care, hedge trimming, garden tidy-ups, planting, small landscaping jobs, and seasonal maintenance. Its customers are homeowners, landlords, retirees, and busy families.

The first version of the website needs to do a few plain things:

• Explain what the business does.
• Show the main services.
• Make the local service area obvious.
• Build a bit of trust.
• Show photos or placeholders for the type of work.
• Give people a way to request a quote.
• Work well on mobile.

The first sitemap can be simple:

• Home.
• Services.
• Gallery.
• About.
• Contact.
• Optional FAQ.
• Optional Service Areas.

For a first version, I would rather have five clear pages than twelve thin pages that all say the same thing.

That is also a useful SEO habit. Thin pages made only to catch keywords are not a great starting point. A clear Services page with real detail is usually better than separate “lawn mowing Hamilton,” “hedge trimming Hamilton,” and “garden tidy-up Hamilton” pages if each page is just copied and lightly changed.

Choose tools, but do not start with tools

This is where people get stuck. They ask which AI website builder is best before they know what site they are building.

Do the boring intake first.

For Green Fern Gardens, I would collect:

• Business name.
• Location and service area.
• Phone number and email address.
• Main services.
• Opening hours.
• Type of customers.
• Tone.
• Proof, such as reviews, real photos, insurance, years of experience, or local knowledge.
• What makes the business different.
• Questions customers usually ask.
• Jobs the business does not do.

For the example, the notes might look like this:

Business name: Green Fern Gardens.

Location: Hamilton, New Zealand.

Services: lawn mowing, hedge trimming, garden tidy-ups, planting, small landscaping, seasonal maintenance.

Customers: homeowners, landlords, retirees, busy families.

Tone: friendly, local, reliable, practical.

Main action: request a free quote.

Contact: hello@example.com and 021 000 000.

AI works much better when you give it actual business details instead of asking it to invent a generic local business from thin air.

That also protects you from one of AI’s worst habits: inventing credibility. Do not let it claim awards, certifications, years in business, insurance, staff numbers, reviews, or local partnerships unless those things are true.

Pick the AI assistant

For planning and copy, you have plenty of free or partly free options. ChatGPT has a free plan. Gemini can be used through Google’s Gemini app, with paid plans for higher limits and extra features. Claude has a free plan with limited usage. Microsoft Copilot can also be used free. These limits change, so I would not build the whole workflow around any one free allowance.

For a simple website, any good general assistant can help with:

• Site planning.
• Page structure.
• Homepage copy.
• Service descriptions.
• FAQ ideas.
• Editing copy back toward plain language.
• Basic HTML and CSS.
• Pre-publish review.

For code testing, you can use local files, VS Code, CodePen, StackBlitz, GitHub’s web editor, or whatever feels least annoying. Bolt.new, Replit, and similar AI app builders can also help, but check their current free limits before relying on them.

The important thing is not the tool name. The important thing is the scope.

Do not ask AI to build a whole platform when you only need a five-page static site.

This is the same lesson as a lot of vibe coding: the smaller and clearer the job, the better the assistant behaves. The tool can be useful, but you still have to be the builder. That is the line I keep coming back to in pieces like What Are the Best Vibe Coding Tools for Non-Developers? and Bolt.new Review: Fast App Prototypes, With a Few Important Caveats. AI can move fast, but the output still needs review.

Give AI examples before asking for a design

Do not just tell AI, “make it modern.”

“Modern” is how you get a page that looks like every startup template ever made. For a local landscaping business, that is not the brief. You want simple, local, trustworthy, easy to read, and believable.

Before prompting, collect three to five example sites. They do not have to be competitors. They can be any sites with useful parts.

Write down what you like:

• I like the clear homepage hero.
• I like the simple service cards.
• I like the contact button at the top.
• I like the before and after gallery.
• I like the FAQ section.
• I like that the copy is plain and not too salesy.

Also write down what you do not like:

• I do not like popups.
• I do not like huge stock photos.
• I do not want a flashy startup-style site.
• I do not want animations that make the page feel slow.
• I do not want copy that sounds like a marketing agency wrote it.

Then give that to AI.

Prompt:

I am planning a simple website for a small landscaping and gardening business.

Here are the things I like from other websites:

• Site 1: I like the clear homepage hero, simple service cards, and obvious contact button.
• Site 2: I like the before and after gallery and friendly local tone.
• Site 3: I like the FAQ section and the way they explain service areas.

I do not want a flashy startup-style site. I want something simple, local, trustworthy, and easy to read on mobile.

Create a website plan with the pages, sections, calls to action, and content needed for the first version.

That is already a much better prompt than “make a website.”

Ask AI for the sitemap

Once you have the business details, ask for a sitemap.

Prompt:

Create a simple sitemap for Green Fern Gardens, a small landscaping and gardening business in Hamilton, New Zealand.

The site should be suitable for a free static website. Keep it simple and easy to maintain.

Include page names, the purpose of each page, sections for each page, the recommended call to action, and what content I need to provide manually.

For Green Fern Gardens, I would expect something like this:

• Home: summary, services, trust signals, quote call to action.
• Services: plain descriptions of each service.
• Gallery: real job photos or placeholders until real photos exist.
• About: local owner-operated business, values, service style.
• Contact: phone, email, service area, quote request.
• FAQ: quote process, green waste, weather, access, one-off jobs.

The important part is not that AI invents the perfect sitemap. The important part is that it gives you something to argue with.

You might decide the FAQ belongs on the Contact page. You might skip Gallery until real photos exist. You might add Service Areas if people often search by suburb. That judgement is yours.

Draft the homepage copy

The homepage should answer the basics quickly.

For Green Fern Gardens, the first screen should probably say something like:

“Friendly gardening and landscaping help in Hamilton.”

Then a short line:

“Lawn care, hedge trimming, garden tidy-ups, planting, and seasonal maintenance for local homes and rental properties.”

That is not fancy. It is useful.

Prompt:

Write homepage copy for Green Fern Gardens.

Business details:

• Local landscaping and gardening business in Hamilton, New Zealand.
• Services: lawn care, hedge trimming, garden tidy-ups, planting, seasonal maintenance, small landscaping.
• Customers: homeowners, landlords, retirees, busy families.
• Tone: friendly, practical, local, reliable.
• Avoid hype, cliches, and corporate wording.
• Main call to action: request a free quote.

Create a hero headline, short intro paragraph, three service highlights, why choose us section, simple process section, and short final call to action.

The first AI draft will probably be too polished or too generic. That is normal. The job is to edit it back toward how a real local business would talk.

Revision prompt:

Rewrite this homepage copy so it sounds more like a real local gardening business and less like marketing copy. Keep it clear, friendly, and practical. Use plain language. Remove hype. Do not invent facts.

I like using that last sentence a lot: do not invent facts. It will not make the model perfect, but it reminds both you and the assistant what matters.

Build the Services page without keyword sludge

For a first free site, start with one Services page.

The page can include:

• Lawn care.
• Hedge trimming.
• Garden tidy-ups.
• Planting.
• Seasonal maintenance.
• Small landscaping jobs.

For each service, explain what it includes, who it helps, when someone might need it, and how to enquire.

Prompt:

Write a Services page for Green Fern Gardens.

Include sections for lawn care, hedge trimming, garden tidy-ups, planting, seasonal maintenance, and small landscaping jobs.

For each service, include what the service includes, who it helps, when someone might need it, and a short call to action.

Keep the tone plain, local, and trustworthy.

If you want local SEO ideas, ask for them carefully:

Prompt:

Suggest five local SEO-friendly service page ideas for this business, but only if each page can be genuinely useful and not just a thin duplicate of the main Services page.

That caveat matters. Do not make a separate page for every keyword unless you have enough useful information to make each page worth reading.

This lines up with the broader SEO/GEO point in Is GEO Just SEO With AI Search Added?: clear, useful pages beat vague pages with search terms sprinkled on top.

Write the About page without fake credibility

About pages are where AI can get a little too helpful.

It may invent a founder story. It may decide the business has ten years of experience. It may claim awards, insurance, certifications, or five-star reviews. That is not harmless copy polish. It is false information on a business website.

Use a prompt that blocks that.

Prompt:

Write an About page for Green Fern Gardens.

Use this rough information:

• Small owner-operated gardening and landscaping business.
• Based in Hamilton.
• Focused on reliable, tidy, practical outdoor work.
• Works with homeowners, landlords, and busy families.
• Values clear communication, turning up when promised, and leaving the property tidy.

Make it sound human and local. Do not invent awards, qualifications, staff numbers, reviews, insurance, or years in business.

Then read it carefully. If a sentence sounds impressive but you cannot prove it, cut it.

For a real small business, plain truth is stronger than fake authority. “We are a small local gardening business focused on tidy, reliable outdoor work” is better than “our award-winning team delivers premium landscape transformations” if that second line is not real.

Add a practical FAQ

FAQs are useful because they answer the questions people are already asking before they are ready to call.

For a local gardening business, the questions are not complicated. That is the point.

Prompt:

Create a practical FAQ page for a local landscaping and gardening business.

Include questions about the quote process, service areas, one-off jobs versus regular maintenance, green waste, weather delays, access to the property, whether customers need to be home, how to send photos before a quote, and what jobs the business does not do.

Keep answers short and honest.

The “what jobs the business does not do” question is underrated. It prevents awkward enquiries and helps the site feel real. If Green Fern Gardens does not do large retaining walls, arborist work, paving, or excavation, say so.

Good websites do not only sell. They set expectations.

Use real photos before AI images

For a real business, AI images should be placeholders at best. Real job photos will usually build more trust than perfect fake lawns.

The best image order is:

1. Real photos from the business.
2. Before and after job photos.
3. Owner or staff photo, if appropriate.
4. Local outdoor photos.
5. Carefully generated placeholder images.
6. Free stock images if needed.

AI image tools and stock libraries can be useful while the site is being planned, but a local business website should not pretend a generated garden is real work. If the image is just decorative, fine. If it implies a job you completed, it needs to be real.

You can still use AI to plan images:

Prompt:

Create eight image ideas for a small local landscaping and gardening business website.

The images should feel realistic, local, and trustworthy. Avoid glossy corporate stock photo style. Include ideas for the homepage hero image, service cards, about page, gallery placeholders, and contact page visual.

That prompt gives you a shot list. The best next step is not always “generate images.” It might be “go outside and take better photos.”

Ask AI for the static HTML and CSS

Once the copy and structure are ready, ask AI for the actual static site.

Keep the requirements plain. Do not ask for a full CMS. Do not ask for a JavaScript framework. Do not ask for login, admin screens, accounts, booking flows, payments, animation libraries, or anything that turns a brochure site into a maintenance job.

The simple file structure can be:

/index.html

/services.html

/gallery.html

/about.html

/contact.html

/styles.css

/images/

Prompt:

Create a simple static HTML and CSS website for Green Fern Gardens.

Requirements:

• Five pages: Home, Services, Gallery, About, Contact.
• Shared navigation.
• Mobile-friendly layout.
• Clean, simple design.
• Warm natural colours suitable for a gardening business.
• No JavaScript required.
• No external frameworks.
• Use placeholder image paths like /images/garden-hero.jpg.
• The contact form should be shown as a visual form only unless we connect a real form service later.
• Include comments explaining where to edit business details.

Return the full file contents for index.html, services.html, gallery.html, about.html, contact.html, and styles.css.

Important: a static HTML contact form does not send emails by itself. It can look like a form and still do nothing. If you need real enquiries, use a mailto link, a phone number, Google Forms, Tally, Netlify Forms, Formspree, or another form service.

For the first version, I would not let the form delay the entire site. A clear phone number and email address are better than a beautiful form that silently fails.

Choose a free publishing option

There are several sensible free hosting paths. The right one depends on how technical you want to be.

GitHub Pages is a strong option for static HTML and CSS sites if you are willing to use GitHub. GitHub describes Pages as static site hosting that takes HTML, CSS, and JavaScript files from a repository and publishes them as a website. For a simple project site, that is a good fit.

Basic GitHub Pages flow:

1. Create a GitHub account.
2. Create a public repository.
3. Upload index.html, the other pages, styles.css, and images.
4. Go to Settings > Pages.
5. Choose the branch and folder.
6. Publish.
7. Visit the generated github.io URL.
8. Add a custom domain later if needed.

Netlify is often easier for non-Git users because it supports drag-and-drop deployment for static sites, along with Git-based deploys if you want that later. Its free plan exists, but as always, check the current limits before using it for a business site.

Cloudflare Pages is a good fit for static sites, especially if you already use Cloudflare for DNS. Cloudflare’s own Pages page lists a free plan with static site hosting features, and its docs note that static asset requests are free and unlimited on both free and paid plans.

Vercel is developer-friendly and excellent for static sites and frontend projects, but its Hobby plan is aimed at personal projects and small-scale applications. If the website is for a real business, check the current plan terms before assuming the free plan is the right long-term home.

Carrd is the easiest path if you want a one-page site and do not want to handle files. It is simple, responsive, and has a free option, though custom domains and more advanced features may require a paid plan.

Neocities is charming, old-web, and good for simple static sites. It is probably not my first choice for a polished local business site, but it is very OSJ in spirit: HTML, CSS, and a page you own enough to understand.

Free URLs might look like:

• greenferngardens.github.io.
• greenferngardens.netlify.app.
• greenferngardens.pages.dev.
• greenferngardens.vercel.app.
• greenferngardens.carrd.co.

Free hosting is fine for getting online, but a real business should probably buy the domain once the site proves useful.

Test before publishing

This is where the whole AI workflow either becomes useful or becomes a mess.

Open the site locally. Click everything. Read every page out loud if you can stand it. Shrink the browser to phone width. Send it to someone who did not build it and ask what the business does.

Check:

• Every navigation link.
• Every page title.
• The business name.
• The phone number.
• The email address.
• The service area.
• Opening hours, if included.
• Image paths.
• Image file sizes.
• Alt text.
• Contact links.
• Mobile layout.
• Spelling.
• Fake-sounding claims.
• Invented awards, reviews, or years in business.
• Repeated sections that say the same thing.
• Any form that appears to work but does not.

Then use AI as a reviewer.

Prompt:

Review this website before I publish it.

Check for unclear wording, fake-sounding claims, missing contact information, missing location or service area, weak calls to action, basic SEO issues, mobile readability issues, and anything AI may have invented.

Give me a practical fix list.

Notice the order here. You are not asking AI to rewrite the whole site. You are asking it to inspect and list problems. That is safer and easier to review.

If you are publishing anything more complex than a static brochure site, read What Security Checks Should You Run on a Vibe-Coded Website? before you put it in front of real users. Forms, logins, uploads, payments, admin pages, and private data all change the risk.

Do the basic SEO pass

A free first website still needs basic SEO. Not a giant strategy. Just enough for people and search engines to understand the business.

Check:

• The homepage says what the business does.
• The location and service area are visible.
• The page title includes the business name and main service.
• Each page has one clear main heading.
• Services are named plainly.
• Contact details are easy to find.
• Images have useful alt text.
• The site loads on mobile.
• There are no fake reviews.
• There is no copied competitor text.
• There is no AI filler.
• The contact method works.

Prompt:

Review this small business website for basic SEO.

Check whether the homepage clearly says what the business does, where it operates, who it helps, and what action visitors should take.

Suggest practical improvements without keyword stuffing.

That last part matters. Keyword stuffing makes small business websites feel fake fast. A gardening site should sound like a gardening business, not a spreadsheet of suburb names.

For a broader marketing angle after the site is live, How Do You Market Your SaaS Online Without Turning Into a Hype Machine? has the same basic lesson: clear explanation, useful proof, and steady distribution beat launch theatre. Even if the site is not SaaS, the principle holds.

What I would avoid

I would avoid building a full CMS for a five-page site unless you genuinely need one.

I would avoid login features, accounts, dashboards, payments, and bookings in the first free version. Those features can be useful later, but they turn the project into a web app with more things to secure and maintain.

I would avoid fake testimonials. AI can write them instantly. That does not mean they belong on the site.

I would avoid fake staff photos, fake job photos, and AI images that imply work the business did not do.

I would avoid 30 thin location pages. If you serve Hamilton and nearby suburbs, say that clearly. Add separate area pages only when you have useful local detail.

I would avoid delaying launch for a logo. A simple wordmark is fine for version one.

I would avoid obsessing over animations. Most small business sites need clarity more than movement.

I would avoid publishing AI copy without editing it. The danger is not just errors. It is sameness. AI copy often sounds polite, smooth, and empty. A local business site should sound like a real person who does real work in a real place.

The goal is not to make the fanciest free website. The goal is to publish a clear first version that real customers can understand.

A free AI website checklist

Before publishing, check:

• The site has a clear purpose.
• The business name is correct.
• The services are real.
• The location or service area is visible.
• The phone, email, or contact method is correct.
• The copy sounds human.
• AI has not invented reviews, awards, years in business, qualifications, or staff.
• The pages work on mobile.
• Every navigation link works.
• Images are compressed and relevant.
• Real photos are used where possible.
• The contact method works.
• The site has basic SEO titles.
• The site is published with HTTPS.
• The free hosting URL is acceptable for now.
• There is a plan to buy a domain later if the business keeps the site.

That checklist is deliberately plain. Plain is good here.

Small business websites usually fail in plain ways: nobody knows what the business does, the phone number is hard to find, the page sounds fake, the form does not work, or the photos do not match the work.

Fix those first.

The takeaway

Building a website for free with AI is possible, as long as you keep the site simple and check the output carefully.

For a small business, the first version does not need a complicated CMS, a paid theme, or a perfect brand system. It needs clear pages, honest copy, useful photos, a working contact method, and hosting that gets it online.

AI can help with all of that. It can plan the sitemap, draft the homepage, write service descriptions, suggest FAQs, produce a simple static site, and review the result before publishing. But it still needs you to supply the real details and make the final judgement.

That is the whole trick.

Do not ask AI for a miracle. Give it a small job, real facts, a clear structure, and enough review that the finished site sounds like it belongs to an actual business.