How to Build a Free Website with AI (No Code Required)
Who this is for
You run a small business or you’re a solopreneur just getting off the ground. You need a real website, a fast one that shows up on Google, and you don’t have a developer or a budget for a $300/month (or even $20/month) website builder. This guide gets you there for free, using an AI coding agent to do the actual building.
It’s not an online store. If you’re selling hundreds of products with a cart and checkout, you want Shopify, and that’s a different post. This is for a site that earns trust and brings in leads: your services, your story, your work, a contact form, a blog. The kind of site most businesses actually need.
It looks long because I’ve spelled out every action. The real work is short: you install two things once, you tell an AI what you want, and it builds the site while you watch. By the end you’ll have a live, professional site with a web address, running on tools that cost nothing to start.
The short version (TL;DR)
In a hurry? Here’s the whole thing in six moves. Everything after this is just each move, click by click, with commands you can copy.
- Install Node.js. One download, one time.
- Create a free GitHub account and organization, and add an SSH key.
- Open a desktop AI coding agent on the project folder you cloned.
- Paste the big build prompt and answer its questions.
- Preview the site, then push it to GitHub.
- Connect the repo to Netlify. It builds, hosts, and secures the site for free.
That’s a real, fast, SEO-ready website, live, for $0. Keep reading for the details.
Why Astro (and why not plain HTML)
When you ask an AI to “build me a website” with no direction, it tends to spit out a pile of standalone HTML files, one per page. That works for about a day. Then you want to change your phone number in the header, and now you’re editing it in twelve separate files and praying you didn’t miss one. Your menu, your footer, your brand colors, all copy-pasted into every page. It rots fast.
Astro fixes that. It’s a modern website framework that’s genuinely friendly to beginners and to AI agents. The big idea: you write the shared parts once, in one place. One header, one footer, one layout, one set of brand colors. Every page pulls from those. Change the header once and it updates across the whole site. Your blog posts become simple text files you (or your AI) can add without touching the design. It’s the difference between a real, maintainable website and a shoebox of HTML.
It’s still just as free, and it still deploys as a plain fast website. You get the easy maintenance without giving up anything.
Here’s the full stack you’ll end up with, all on free tiers:
| Tool | What it does | Cost to start |
|---|---|---|
| Node.js | Runs the website software on your computer | Free |
| GitHub | Stores your code safely online | Free |
| AI coding agent | Actually builds and edits the site for you | Free tier / your existing plan |
| Astro | The website framework the AI builds with | Free |
| Netlify | Hosts the live site and gives it an address | Free |
And yes: the Full Count site you're reading this on is built exactly this way, with an AI coding agent on Astro, pushed to GitHub, and deployed free on Netlify. We practice what we preach.
Prefer a different framework?
Astro is my pick for this kind of site, and it’s what the rest of this guide uses. But here’s the thing: the stack around the framework (GitHub, your AI agent, Netlify, the free SSL) is the part that actually matters, and it’s identical no matter what you build with. If you’d rather use something else, swap the framework’s name in the Step 4 prompt and every other step still applies.
These are the alternatives worth a look, all free and all things an AI agent builds well:
| Framework | Reach for it when | Trade-off vs Astro |
|---|---|---|
| Astro | Marketing sites, blogs, lead-gen, the sweet spot for this guide | None worth noting here; it's the default for a reason |
| Eleventy (11ty) | You want the simplest possible setup, nothing extra | Fewer modern niceties out of the box |
| Hugo | Content- or blog-heavy sites, and it skips the Node install entirely | Templating is quirkier (your AI handles it fine) |
| Next.js | You expect to grow into app features: logins, dashboards, tools | Heavier and more complex than a brochure site needs |
| SvelteKit | You want something lighter than Next but still app-capable | Smaller ecosystem, a bit less AI training data |
Two more you’ll hear about, but file them as a different path, not a swap. WordPress is the classic small-business CMS, but you’re renting hosting every month and babysitting plugins instead of owning clean code. Framer and Carrd are genuinely free drag-and-drop builders, fine for a quick one-pager, but you’re locked inside their tools rather than building something portable that’s yours.
The honest bottom line: any of the frameworks above is a fine choice. Pick one, name it in the prompt, and let the AI run. The decision matters far less than just getting started.
Step 1: Install Node.js
Node.js is the engine that runs Astro on your computer. Installing it also gives you npm, the tool that downloads the website’s building blocks. You install this once and forget about it.
On a Mac
Two easy ways. Use Homebrew if you’d like one reusable command (and a handy tool for installing other things later), or grab the manual installer if you’d rather just click through it.
Homebrew is a free "package manager" for Mac that installs developer tools from a single command. If you don't already have it, paste this into Terminal and press Enter (it may ask for your Mac password, and take a few minutes):
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
When it finishes it may print one or two Next steps lines to run. Copy and run them so your Mac can find Homebrew. Then install Node:
brew install node
Go to nodejs.org, download the LTS version (the big green button), open the .pkg file, and click through the installer. That's it.
On Windows
Go to nodejs.org, download the LTS version, open the .msi file, and click through the installer. Leave every option at its default and let it finish.
Then check it worked (both)
Open your terminal. On Mac that’s Terminal (press Cmd + Space, type “Terminal”); on Windows that’s PowerShell (press the Start key, type “PowerShell”). Paste this and press Enter:
node -v
npm -v
If you see two version numbers (like v22.9.0), you’re done. If it says “command not found,” close the terminal, open a fresh one, and try again.
Step 2: Set up GitHub
GitHub is where your website’s code lives online. Think of it as the master copy: safe, backed up, and the thing Netlify watches so it knows when to update your live site.
Create the account
Go to github.com and sign up. Use your business email. When it asks, the free plan is all you need.
Create an organization too. An organization is just a container for your business’s projects, separate from your personal account. It’s cleaner, and easier to hand off or add a teammate to later. In the top-right menu go to Your organizations → New organization, and pick the Free plan. Name it after your business. You’ll put your website repository inside it.
Set up an SSH key so you can push code
An SSH key is a secure handshake between your computer and GitHub, so you never type a password when saving your work. You might already have one (plenty of people do), so check before making a new one.
First, check whether you already have a key
In your terminal (Terminal on Mac, PowerShell on Windows), run:
ls ~/.ssh
If you see a file ending in .pub (most often id_ed25519.pub or id_rsa.pub), you already have a key. Skip ahead to Copy your public key and use whichever .pub file you have. If it says the folder doesn’t exist, you don’t have one yet, so make it below.
Create one (only if you don’t have it)
Paste this, with the email you used for GitHub:
ssh-keygen -t ed25519 -C "you@yourbusiness.com"
Press Enter three times to accept the defaults, no passphrase needed. You get a private key that stays on your computer and a public key (id_ed25519.pub) to hand GitHub.
Why ed25519? It’s simply the modern key type, and the one GitHub recommends, shorter and more secure than the older RSA style. You may have seen id_rsa in older guides; that still works too, so if that’s the .pub you already have, just use it.
Copy your public key
Use whichever file you have: id_ed25519.pub (shown here), or swap in id_rsa.pub if that’s yours.
On a Mac:
pbcopy < ~/.ssh/id_ed25519.pub
On Windows (PowerShell):
Get-Content $HOME\.ssh\id_ed25519.pub | Set-Clipboard
Either way, the key is now on your clipboard, ready to paste.
Give it to GitHub
In GitHub, click your profile picture → Settings → SSH and GPG keys → New SSH key. Give it a title like “My laptop,” paste into the Key box, and click Add SSH key.
Test the connection
ssh -T git@github.com
Type yes if it asks about authenticity. When you see “Hi yourname! You’ve successfully authenticated,” you’re connected.
Tell Git who you are
One more one-time setup so your saves are stamped with your name. Paste both lines, with your details:
git config --global user.name "Your Name"
git config --global user.email "you@yourbusiness.com"
Create the repository
Back on GitHub, inside your organization, click New (or the + in the top-right → New repository). A repository, or “repo,” is the home for one project’s code.
- Owner: your organization.
- Name: here’s a tip: if you think you might ever use GitHub’s own free hosting, name it after your domain, like
yourbusiness.com. Otherwise any short name is fine, likewebsite. - Set it to Private (you can make it public later), and don’t check any of the “add a README / .gitignore” boxes, since you want it empty.
- Click Create repository.
Clone the repo to your computer
Cloning makes a folder on your computer that’s already linked to this GitHub repo, so later you just save and push with nothing to wire up. Pick where it should live (your Documents folder is fine), then run these two lines, swapping in your org and repo name:
cd ~/Documents
git clone git@github.com:yourorg/website.git
That creates a website folder (named after your repo). It’ll say something like “You appear to have cloned an empty repository.” That’s expected, since there’s nothing in it yet. This is the folder you’ll point your AI at next.
Step 3: Open your AI coding agent
This is the part that does the heavy lifting. You need a desktop AI coding tool, one that can create and edit files in a folder on your computer. The web/chat versions in a browser can’t do that; they can only talk. You want the desktop app.
Good options, any one works:
- Claude Code (in the Claude desktop app)
- ChatGPT (desktop app with its coding/agent mode)
- Cursor, Windsurf, or VS Code with an AI agent extension
Open your tool and start a new project pointed at the folder you just cloned (the one named after your repo, like Documents/website). That folder is where your site gets built, and because you cloned it, it’s already linked to GitHub, so saving your work later takes one step.
Quick sanity check: the AI should be able to see and create files in that folder. If it's asking you to copy-paste code back and forth instead of doing it itself, you're in the web version, not the desktop app.
Step 4: Tell the AI to build your site
Here’s the prompt that does the work. It tells the AI to use Astro, set up all the SEO and technical plumbing correctly, and, importantly, write down the rules so it stays consistent every time you come back. Copy the whole thing, paste it into your AI, and fill in the blanks in the brackets.
Don’t worry about getting every answer perfect. The AI will ask follow-up questions, and you can change anything later just by asking.
Chose a different framework in the section above? Change “Astro” in the first line (and the @astrojs/sitemap line, which is Astro-specific) to your pick. Everything else in the prompt applies unchanged.
Build me a website using Astro. I'm a non-technical small business owner,
so set everything up for me and keep the code clean and well-organized.
First, create an AGENTS.md file in the project root that documents all of
the standing rules below, so you and any future AI session follow them
every time. Treat AGENTS.md as the source of truth for how this site is built.
Before you start building, ask me for:
- My current website, if I have one (so you can match or improve on it)
- My logo file, or offer to make a simple one if I don't have it
- My business name and a one-line description of what I do
- My brand colors (or pick a tasteful palette and show me)
- 2-3 websites I like, for inspiration on look and feel
- My social media handles (for links and icons)
- My Google Tag Manager or Google Analytics ID, so you can install it
(I may not have one yet; if so, tell me how to get it)
Technical setup, do all of this:
- Use Astro with a shared layout: one header, one footer, one set of brand
colors and fonts that every page uses. Never copy the header into each page.
- Add robots.txt allowing search engines and pointing to the sitemap.
- Add an llms.txt file describing the site for AI assistants.
- Install and configure @astrojs/sitemap so a sitemap is generated
automatically on every build.
- Generate a favicon in the sizes modern browsers and phones need.
- Add a custom 404 page that matches the site's design and links back home.
- Add basic security headers in a Netlify _headers file (for example
X-Content-Type-Options: nosniff and X-Frame-Options: SAMEORIGIN).
SEO rules, bake these in and write them into AGENTS.md:
- Every page has a unique <title> with the keywords that page should rank for.
- Every URL ends with a trailing slash, consistently.
- Every page sets a self-referencing canonical URL (the trailing-slash version),
so search engines know the single correct address for each page.
- Let me decide the URL structure; keep paths clean, lowercase, and consistent.
- If I give you URLs from an old version of my site, add 301 redirects from each
old path to its new path in a Netlify _redirects file, so old links and search
rankings carry over instead of hitting a 404.
- Every page has a meta description, Open Graph tags, and an OG share image.
Use a default OG image I provide; if a page has its own first image, use that
instead; and let me override the OG image per page when I want.
- Every page outputs valid JSON-LD (ld+json) structured data appropriate to its
content (Organization on the home page, Article on blog posts, and so on).
- Every page has exactly one H1 and a sensible H2 structure.
- Every image has descriptive alt text.
- Every image is optimized (right format and size) so pages load fast.
- Every page works and looks right on both desktop and mobile.
- Meet basic accessibility: semantic landmarks (header, nav, main, footer),
sufficient color contrast, visible keyboard focus, and a label on every
form field.
Workflow rules, write these into AGENTS.md too:
- Work only on the main branch in Git. I'm solo, so don't create new branches.
- Set up all contact and lead forms as Netlify forms (add data-netlify="true"
and a hidden "form-name" input, and make sure the form is in the static HTML
so Netlify can detect it at build time). Add a honeypot field
(data-netlify-honeypot) to cut down on spam.
- Add a simple privacy policy page (the site collects form submissions and runs
analytics) and link it in the footer.
- Never put API keys, passwords, tokens, or any other secret in the code, and
never commit them to Git. This is a public static site, so anything in the
repo can be read by anyone who finds it. Add a .gitignore that excludes .env
files. If a feature I ask for needs a secret, a login, or a live database,
stop and tell me instead of building it — that's a web app, not a static site.
- When I ask for changes, make them, then show me the result in the dev server.
Once the plumbing is in place, build out my pages based on what I tell you,
then run the dev server so I can see it.
A few notes on what you just asked for, so you know why it matters:
- The AGENTS.md file is the key to not starting from scratch every time. It’s a plain checklist the AI reads at the start of each session, so your SEO rules, your brand, and your workflow stay consistent months from now. If the AI ever drifts, you just say “check AGENTS.md.”
- The analytics ID (Google Tag Manager or GA4) is how you’ll see how many people visit and where they come from. If you don’t have one, the AI can walk you through creating a free Google account for it. Not sure you’re measuring the right things? That’s literally what we do, see the end of this post.
- Netlify forms means your contact form just works once the site is live, and submissions land in a dashboard (and your inbox). More on that in Step 6.
- Redirects (if you’re replacing an old site). You get to decide what your new URLs look like. But if you already have a site, its pages probably live at different paths, so hand the AI your old URLs and it’ll set up redirects (old path → new path) in a Netlify
_redirectsfile. Netlify applies them automatically on every deploy, so old links and your Google rankings land on the right new page instead of a dead end.
Step 5: Preview it, and push it to GitHub
See it locally
Ask your AI to “run the dev server” (or run npm run dev yourself in the terminal). It’ll give you a local web address to open in your browser, usually:
http://localhost:4321
If something else is already using that port, Astro bumps to the next one (4322, then 4323, and so on), so use whatever address it prints. This preview updates live as the AI makes changes. It’s only visible on your computer; nobody else can see it yet.
Want to show it to someone before it’s live? You can open a temporary public tunnel to your local preview with a free tool called ngrok.
Share your local preview with ngrok (optional)
Make a free account at ngrok.com, then install it:
On a Mac:
brew install ngrok/ngrok/ngrok
(No Homebrew? Download the Mac version straight from ngrok.com/download instead.)
On Windows: download the installer from ngrok.com/download and run it.
Connect your account (copy the exact line with your token from the ngrok dashboard):
ngrok config add-authtoken YOUR_TOKEN_HERE
Then point it at your running preview (use your real port if it isn’t 4321):
ngrok http 4321
ngrok prints a public https:// link right there in the terminal. Copy it and send it to anyone you want. Close the terminal and the link stops working; it’s just for a quick look.
Each run gives you a fresh random address, which is the easiest way to go. If you’d rather have a link that stays the same every time, reserve a free permanent one in the ngrok dashboard under Domains, then run ngrok http 4321 --url=your-name.ngrok-free.app instead.
Push it to GitHub
Because you cloned the repo in Step 2, the folder is already linked to GitHub, so saving your work is simple. Just tell your AI:
"Commit everything and push it to the main branch on GitHub."
The AI handles the Git commands. If you’d rather do it by hand, here are the exact lines (run them in the project folder):
git add -A
git commit -m "Initial website"
git push
Refresh your GitHub repo page and you’ll see all your files. That’s your master copy, safe online.
Step 6: Deploy it live on Netlify
Netlify takes your code from GitHub, builds it, and serves it to the world for free, with a secure https:// address included. Every time you push a change to GitHub from now on, Netlify rebuilds and redeploys automatically. You do nothing.
- Create a free account at netlify.com. Sign up with GitHub, which makes the next step one click.
- Add a new site: click Add new site → Import an existing project → GitHub, authorize it, and pick your website repo.
- Let it auto-detect the build. Netlify recognizes Astro and fills in the build command (
npm run build) and publish directory (dist) for you. Click Deploy. In a minute or two your site is live at ayourbusiness.netlify.appaddress.
From here, changes are hands-off: push to GitHub (or have your AI push), and Netlify redeploys on its own.
A few things worth knowing about the free plan
- It’s genuinely free to run a site like this. The free plan gives you a monthly pool of build credits, plenty for a normal small-business site that changes now and then. If you’re redeploying constantly, you could run it down, and the site pauses until the next month. If you ever need more, paid plans start at $9/month (the Personal plan, with more build credits), and Pro is $20/month with unlimited team members, but most people never need to upgrade.
- SSL is free and automatic. That padlock and the
https://: Netlify sets up the security certificate for you, no cost, no configuration. (Pricing and plan details change; check netlify.com/pricing for the current numbers.) - Point your own domain at it whenever you’re ready: in Netlify go to Domain management, add your domain (from Namecheap, GoDaddy, Google Domains, wherever), and follow the steps. SSL extends to your custom domain automatically.
Where your form submissions go
Because you set your forms up as Netlify forms in Step 4, Netlify catches every submission automatically, with no separate service and no server to run. After your first deploy:
- Go to your site’s Forms tab in the Netlify dashboard to see submissions.
- Under Forms → form notifications, add an email notification so you get a message the moment someone fills it out. You can also send submissions to Slack or a webhook.
- One catch: Netlify only “sees” a form if it’s in the finished HTML when the site builds. Your AI handled that with the hidden
form-nameinput, but if a form ever stops recording, that detection is the first thing to check. Just tell your AI “this form isn’t being detected by Netlify” and it’ll sort it.
A few ground rules worth knowing
A couple of things about how a site like this works day to day, so there are no surprises.
There’s no login or dashboard to edit it. Unlike Squarespace or WordPress, there’s no admin panel someone signs into to change the words. Your site is a set of files in your GitHub repo. To edit it, you (or anyone you trust) open the repo on a computer that has the AI coding agent and make changes there, then push them. More than one person can work on it — that’s exactly what GitHub is for — each person just needs access to the repo on their own machine.
You’re never locked out of your own site. Because it’s plain code, you or any developer can open it and edit it by hand. Astro is approachable enough that changing text, swapping an image, or nudging a color is doable even if you’re not a developer. The AI just gives you a clean, consistent, well-organized starting point, so the site stays stable and good-looking as it grows instead of turning into a tangle.
A static site is a secure site. There’s no database, no login, and no server running your code for someone to break into — it’s just fast files served to visitors. That removes almost the entire category of things that get small-business sites hacked. It’s one of the quiet reasons this approach is worth the small effort.
One hard rule: never let an API key, password, or any secret end up in your code. Everything in the repo is readable by anyone who finds it, and the live site is public files. If your AI ever offers to paste a key into the code, stop. Secrets belong on a server, never in a static site.
When it’s more than a website, call someone. Astro is built for a fast, static marketing site: pages, a blog, a contact form, no logins. The moment you want real user accounts, logins, payments, a customer portal, or anything that stores and serves data live, you’ve crossed from “website” into “web application” — a different setup that needs real attention to security. That’s not a reason to avoid it; it’s a reason to get help before bolting it onto a static site. If you’re not sure which side of the line you’re on, reach out — a quick conversation saves a lot of rework.
That’s it, now the fun part
Step back and look at what you have: a fast, professional, search-ready website, live on the internet with a secure address, backed up on GitHub, and it cost you nothing. The plumbing (the part that used to need a developer) is done, and it’s done right.
From here it’s all upside, and it’s the easy part. Want a new page? Ask. A photo gallery, a testimonials section, a booking link, a FAQ, a whole new blog post? Ask. Because the AI set it up on Astro with a shared layout and a written set of rules, every new thing you add matches the rest and keeps your SEO intact. You describe what you want in plain English; the AI builds it; you push it; Netlify ships it.
And here’s the real difference: you’re not boxed in the way a site builder boxes you in. With Squarespace, Wix, or any drag-and-drop tool, you get their themes and the exact features they decided to offer, and that’s your ceiling. Here there isn’t one. You’re not picking from a template gallery or a feature list; if you can describe it, the AI can build it. A custom quote calculator, an interactive service-area map, an animated timeline, a layout no template has ever done. Dream it up and ask for it.
You don’t need to become a developer. You just need to keep asking for what your business needs.
Want someone to build it for you?
We can take it from here
Not your thing, or you'd just rather someone owned this for you? Reach out. We'll build you a beautiful, fast website for an affordable price, and keep it running so you never have to think about it.
Get in touch