How to Build a Website for Your Small Business
The same process, applied to a site that actually has to bring in customers.
Read the guide →
Most "build a website" tutorials are really platform tutorials — they show you which buttons to click in one specific tool, and the knowledge doesn't transfer anywhere else. This guide teaches the decisions that matter regardless of platform: picking a domain and a tool that fits you, structuring pages so visitors find what they need, writing content people actually read, basic design that doesn't look homemade, and launching with a real check instead of just hitting publish.
What you'll be able to do: Go from no website at all to a live, working site of your own — built step by step, with decisions you can explain, not copied from a template you don't understand.
Outcome: "I have a domain name shortlisted and a platform decision I can actually defend, instead of picking whatever a YouTube video happened to use."
Write down three possible domain names right now, each under 15 characters, with no hyphens and no numbers — then say each one out loud. If you stumble saying it, cross it off.
A domain name is the address people type or click to reach your site; a platform is the tool you use to actually build and host it — these are two separate decisions, and conflating them is the single most common beginner mistake. For the domain: stick to `.com` unless you have a specific reason not to (it's still what people assume by default), keep it short and easy to say over the phone, and avoid anything that's ambiguous when spoken aloud (hyphens and unusual spellings cause this). For the platform, there are really three categories: a visual website builder (Wix, Squarespace and similar — drag-and-drop, hosting included, fastest to a working site, least flexible later), a CMS like WordPress (more setup, far more flexibility and plugins, a small learning curve), or hand-coded HTML (full control, requires knowing or learning to code — not the default choice for a first site). Choose based on one honest question: do you want this live this week, or are you building a skill you'll reuse? The first answer points to a builder; the second points to WordPress or code.
Someone with no coding background, wanting a site live this week for a side project, shortlists "lentilandthyme.com" (short, easy to say, no hyphen) and picks a visual builder over WordPress — accepting less long-term flexibility in exchange for not needing to learn hosting, updates, or plugin security, which WordPress would require managing.
Outcome: "I have a simple page plan — what pages exist, what's on each one, and how they connect — before I've designed a single pixel."
On a blank sheet of paper, draw one box per page you think you need, and connect them with lines showing which ones link to which. Don't open your website builder yet.
Almost every small site needs the same handful of pages: a Home page (what this is and what to do next), an About page (who's behind it, why it exists), a page for the actual offer (Services, Products, Portfolio — whatever applies), and a Contact page. Everything else — a blog, an FAQ, testimonials, a store — is an addition, not a foundation, and adding them before the core four exist is how sites end up half-finished. Navigation should mirror this: a top menu with four to six items maximum, in the order visitors actually think (Home, then About or Services depending on what matters more to your visitor, then Contact last since it's the destination, not the start). Every page should have one clear next action — a link or button telling the visitor what to do once they've read it — pages that just end are dead ends.
Home → one sentence on what this is, a photo, and a button to Services. Services → three offerings listed plainly, each linking to Contact. About → two paragraphs and a real photo, linking to Contact. Contact → a form or a clear email address, nothing else competing for attention on that page.
Outcome: "I can write a homepage and page copy that a visitor actually reads in the first ten seconds, instead of a wall of text they skip past."
Write one sentence, in plain language, answering: "what is this, and who is it for?" That sentence becomes your homepage headline.
Visitors scan before they read — most decide whether to stay within the first ten seconds, based on the headline and whatever's immediately visible, not the paragraph below it. A working headline states what the thing is and who it's for, in plain words, with no clever wordplay that requires decoding ("Smarter spaces for smaller homes" beats a pun that needs a second read). Below the headline, a one-sentence subhead adds the detail the headline couldn't fit, then a single clear call-to-action button — one, not three competing ones. Body copy should be broken into short paragraphs (two to three sentences), with the most important information first, not saved for a reveal at the end — nobody scrolls to the bottom of a page they haven't been convinced to read yet.
Before: "Welcome to our world of possibilities." (says nothing). After: "Custom dog leashes, handmade in small batches." (says exactly what this is). The second version lets a visitor decide in two seconds whether to keep reading — the first forces them to keep scrolling just to find out.
Outcome: "I can apply a small, consistent set of design rules that make my site look deliberately built, not thrown together from a template."
Pick exactly two fonts (one for headings, one for body text) and one accent color, and write them down before changing anything else on the site.
Most DIY sites look amateur for the same three reasons, all fixable without any design training: too many fonts (stick to two, max three), too many colors competing for attention (one neutral background, one text color, one accent color used sparingly for buttons and links — not five different colors), and not enough whitespace (cramming content edge-to-edge instead of giving it room to breathe makes a page feel cluttered even when the content itself is fine). Images matter too: use consistent sizing and cropping across a page rather than mixing wildly different aspect ratios, and never stretch a low-resolution image to fill a space — a smaller, sharp image beats a larger blurry one every time.
Before: five fonts, a background image behind every section, text touching the edges of the screen. After: two fonts, a plain background with one accent color used only on buttons, and consistent padding around every block of text. Nothing else changed — the content is identical — but the second version reads as intentional.
Outcome: "I've actually tested the site before telling anyone about it, and I know what to check in the first week it's live."
Open your site on your phone right now, even if you built it on a computer — most first visitors will be on mobile, and this is the fastest way to catch an obvious problem.
Before launch, click every single link and button on every page — broken links are the single most common last-minute embarrassment, and they're invisible unless you actually click through rather than just look. Check the site on both a phone and a computer, since layouts that look fine on one can break on the other. Confirm every form (contact forms especially) actually sends and that you receive the result — a form that silently fails is worse than no form at all, because visitors think they've reached you. Once live, set up basic analytics (most platforms have a built-in option) so you're not flying blind, and in the first week, check daily for broken links, misspellings someone else spotted, and whether the one clear call-to-action is actually getting clicked — if it isn't, that's a sign to revisit Chapter 3's headline work, not to add more pages.
Clicking through all four pages reveals one dead link in the footer and a contact form that submits but never arrives in the inbox (a setup error, caught only by sending a real test message). Both get fixed before the first visitor ever sees the site — exactly the kind of problem invisible from just reading the page, only found by clicking.
The complete guide — all 5 chapters, every checklist and exercise — as a clean, printable PDF. No email required.
Every guide on this site is produced with the Self-Directed Learning Framework: instead of an article that explains a topic at you, the framework turns it into a structure you work through — each chapter with one outcome, a starting action under twelve minutes, the minimum you actually need to know, a worked example, a checklist, and exercises. It starts from three questions:
Topic: Building a website from scratch, with no prior experience.
Outcome wanted: Have a live, working website of my own, built with decisions I understand — within five days.
Starting point: Complete beginner — has never built or managed a website before.
The prompt framework behind it is public: see the C.R.A.F.T. prompt framework, including the exact prompt that generated this library.
The same process, applied to a site that actually has to bring in customers.
Read the guide →Free, self-paced guides across everyday, professional and academic topics.
See all guides