How to plan a small-business website that earns its place

Plan your website around real customer decisions, with a page-planning framework, platform questions, launch checks, and a downloadable worksheet.

In this guide

A useful small-business website helps a person make a decision. It explains the offer, supplies enough evidence to evaluate it, and makes the next step work. The difficult part is deciding which information and functions belong in that first version—and which can wait.

This guide takes you from an uncertain brief to a website you can evaluate before launch. It is for founders planning a first site and owners replacing one that no longer fits. You’ll leave with a page plan, a completed example to adapt, a way to evaluate platforms, and concrete launch criteria. If your main concern is preserving existing search traffic, use the companion website migration guide alongside it.

First, identify the decision your website needs to support#

“Get more customers” describes a business ambition. It doesn’t tell a designer what the website must do. Narrow it to a visitor, a situation, and a next step.

Consider these hypothetical briefs:

Business situationVisitor’s decisionWebsite’s primary job
A contractor offers repair and replacementIs my problem something they handle?Explain the options and collect enough context for an inquiry
A consultant launches a new serviceDoes this person understand our situation?Describe the work, show relevant experience, and invite a conversation
A product company begins selling directlyIs this the right product, and can I buy it?Explain the product and provide a dependable purchase path

Complete this sentence before choosing a layout: “When someone arrives because of ___, they should be able to decide ___ and then ___.”

For a service business, the next step may be an inquiry rather than an immediate sale. That changes how much explanation the page needs. A visitor deciding whether to request a conversation needs confidence about the fit, the process, and what will happen after submitting a form. They don’t necessarily need every detail of a future proposal.

Choose one primary action for each page. Secondary actions can help people who aren’t ready, such as reading a case study. Make the distinction visible instead of giving five buttons equal emphasis.

Build a page plan from questions, not a template menu#

Start a document with the questions people ask before working with you. Add the questions you wish they asked, especially where misunderstanding leads to a poor fit. If you haven’t launched, write down assumptions and test them in conversations; don’t label guesses as customer research.

Group the questions by the decision they support. The groups become candidates for pages.

PageQuestion to answerEvidence or detail to gatherNext step
HomeWhat is this business, and is it relevant to me?A clear offer and a small amount of meaningful proofExplore the appropriate service or product
ServiceWhat does this work involve?Scope, fit, process, limits, examplesDescribe the project or request a conversation
ProductWhat am I buying?Specifications, price, options, use, delivery informationPurchase or ask a product question
AboutWho is behind this, and how do they work?Accurate background, perspective, real peopleExplore relevant work or get in touch
Case studyWhat did they actually do?Role, challenge, deliverables, supported outcomesSee the related service
ContactWhat happens if I reach out?Requested information, working submission pathSend the inquiry

This is a planning tool, not a required six-page package. One service may need one substantial page. Several genuinely different services may need separate explanations. A product catalog has different structural needs from a consultancy.

When does a topic deserve its own page?#

Give it a separate page when a visitor has a distinct question, you have enough useful information to answer it, and there is a meaningful next step. Keep it within an existing page when the separate version would mostly repeat the same explanation.

For example, floor installation and refinishing involve different situations and decisions. Those may warrant separate service pages. Five location pages with identical copy and swapped city names offer much less to a reader. See the local SEO guide for a way to evaluate location content.

Record the intended purpose, audience, source material, and owner of every page. An owner is the person who can confirm its accuracy, not necessarily the person writing it.

A completed first-version plan#

Imagine a founder launching an operations consultancy for small service businesses. This is a fictional planning example, not an Antilo client or a tested conversion formula. The founder has relevant employment experience but no independent client case studies yet.

The broad brief is “a professional website that brings in leads.” A more useful brief is: “When an owner arrives because work keeps getting lost between inquiry and delivery, they should be able to decide whether our operations review suits their problem and then describe their situation.”

Here is how that decision changes the scope:

Planning decisionFirst-version choiceReason
Main offerA defined operations review, with implementation scoped separatelyVisitors can understand what the first engagement covers
Core pagesHome, operations review, About, and ContactEach answers a different question; no empty resource library
EvidenceA clearly labeled example of a handoff map, plus relevant experience with accurate role attributionShows how the founder thinks without implying a client result
Inquiry fieldsName, email, business, and “Where does work currently get stuck?”Gives the founder context for the first reply
Pricing explanationExplain what changes the scope and how a quote is preparedGives useful context while the offer is still being established
Initial follow-upA human reply describing whether a conversation makes senseMatches what a solo founder can actually deliver
Deferred workAutomated booking, a newsletter, and a library of industry pagesNone is necessary to evaluate or inquire about the first offer

A visitor could move from a referral directly to the operations review page, read the example, check the founder’s background, and inquire. That is the path to design and test. The homepage introduces it; it is not the only entrance.

If early inquiries repeatedly ask whether implementation is available, the next improvement may be a clearer explanation on the service page. If inquiries come from businesses with the wrong kind of problem, revisit the offer and examples. Neither observation automatically calls for a redesign.

Write the first service page before polishing the homepage#

A homepage often becomes vague because the underlying offer is still vague. Work through one important service in detail first. Then use what you learn to write a clearer introduction to the business.

A useful service-page draft follows the customer’s reasoning:

  1. Situation: describe a problem or goal the reader recognizes.
  2. Offer: explain the work you do and who it suits.
  3. Scope: identify what can be included and what needs separate discussion.
  4. Evidence: show relevant work, experience, or a useful explanation of your method.
  5. Process: explain what happens when the reader takes the next step.
  6. Action: invite a specific, manageable response.

Here is an invented example, not a client result. “Premium flooring solutions” tells a homeowner little. “We repair damaged hardwood and help you work out whether the surrounding floor needs refinishing” identifies a problem, an offer, and a decision. The second version creates something the rest of the page can explain.

You don’t have to use those headings literally. The structure is a check on whether the page answers the questions, not a formula for making every business sound the same.

Keep claims close to their evidence#

If a testimonial supports the ease of working with you, use it to illustrate that experience. Don’t treat it as proof of a financial result. If you completed a website, describe the website and the role you played. If a project is still developing, label its stage.

Choose the platform around the work after launch#

The platform decision is partly about what you need to build and partly about what you can maintain. Compare a realistic task on each option: adding a service, changing a product, publishing an article, or handling an inquiry.

Before making the choice, answer:

  • Who will edit the site, and how comfortable are they with the tools?
  • Does the business need payments, inventory, bookings, accounts, or integrations?
  • Which tasks must work without developer help?
  • What recurring costs and outside services are involved?
  • What can be exported or transferred if the arrangement changes?
  • Who owns the domain, content, accounts, and finished assets?

For Colorado Sauce Company , the project included moving from Wix to Shopify and building around cases, offers, discounts, and customer accounts. That was a specific ecommerce scope. It does not mean every service business needs a store platform or every redesign requires a migration.

Compare operating tradeoffs, not just design options#

These are questions to investigate, not fixed claims about every product in a category. The particular plan, implementation, and support agreement matter.

Approach under considerationWhat makes it worth consideringTradeoff to investigate before choosing
Hosted visual site builderAn owner wants direct control of a relatively straightforward siteCan you export what matters, and do essential integrations add recurring costs?
Hosted commerce platformCatalog management and selling are central to the workWhat will the complete selling workflow require beyond the base subscription?
Content management systemSeveral people need to maintain substantial or structured contentWho owns updates, backups, permissions, and troubleshooting?
Static site with an editing workflowThe site is mostly published information, with deliberately chosen outside servicesCan the actual editor publish confidently, and who repairs a failed build or integration?

Ask the person proposing a platform to demonstrate the work you will do after handoff. Give them a realistic change: “Add a service, update its navigation link, replace a photograph, and correct the change if we make a mistake.” Then have the intended editor try it. Note every step that requires another person, another subscription, or a support request.

Before approving the build, record who controls the domain registration, website account or repository, form service, and recovery email. Have the builder explain what happens if you change providers. Account ownership and a usable handoff belong in the scope from the beginning.

Treat search basics as part of the page plan#

A page should have a descriptive title, a clear main heading, a stable URL, and links from relevant parts of the site. Use the language people need to understand the subject; avoid forcing the same phrase into every heading.

Write a distinct description that accurately summarizes the page. Keep navigation labels understandable. Link to related work at the point where it helps a reader evaluate a claim, rather than collecting every link at the bottom.

Google’s link guidance recommends crawlable links and descriptive link text. In practical terms, “see our flooring research” helps explain a destination better than an isolated “click here.” This also makes the page easier to scan.

If you are replacing an existing site, preserve useful URLs or plan appropriate redirects. Check the migration checklist before changing published addresses. A new design can still leave old business cards, search results, and customer bookmarks pointing at the previous structure.

Design the reading experience before adding effects#

Review a long paragraph, a service comparison, a form, and a navigation menu on a narrow phone screen. Can you read the text without zooming? Can you distinguish a heading from body copy? Does the page still make sense when a photo is absent?

Choose images that answer a question: what the product looks like, what the work involved, or who someone will meet. Write alt text according to the image’s purpose. W3C distinguishes informative images, which need a meaningful text alternative, from purely decorative images, which generally use an empty alternative. A complex chart needs its information explained in text as well. See the W3C images tutorial .

Avoid putting essential instructions only inside an image. A screenshot of a process may illustrate it, but the steps should remain readable as text. That makes them usable on small screens and available to people who cannot access the image.

Make the inquiry form a complete experience#

A submit button is only one state. Test a missing required field, an invalid email, a successful submission, and a server failure. On failure, the person should understand what happened and retain what they typed. On success, the page should confirm the submission rather than merely clearing the fields.

Use visible labels and distinguish optional fields. Don’t ask for information you do not need to begin the conversation. W3C’s forms tutorial explains labels, instructions, validation, and feedback in more detail.

Someone should also own the receiving end. Confirm who receives inquiries, where they are stored, and how follow-up works. A technically successful submission that nobody reads is still a business problem.

For the fictional consultancy above, the form should ask about the work getting stuck, not require a detailed project brief before a conversation is possible. If the founder can only check inquiries on working days, the confirmation should reflect that. A promised response time is an operational commitment; only publish one the business can support.

Review performance without turning a score into the goal#

Large images, unnecessary scripts, and unstable layouts can get between a visitor and the task. Test representative pages rather than only the homepage, including the page with the most images and the form or checkout path.

Google’s Core Web Vitals documentation describes loading performance, responsiveness, and visual stability through LCP, INP, and CLS. Use those measurements to diagnose a visitor problem. A lab test of one page is not a substitute for real-user experience, and a perfect score does not make an unclear offer persuasive.

Ask what a proposed optimization changes for the visitor. “The product image now loads sooner without shifting the purchase button” is an understandable improvement. Keep the work connected to a task someone is trying to complete.

A practical launch review#

Set aside a review session before launch. Work through the site as an unfamiliar customer, not as its author. If possible, have someone outside the project try the primary task and describe where they hesitate.

CheckHow to verify itWho should confirm it
Offer and claimsRead the page against the actual service and available evidenceBusiness owner
Links and imagesFollow internal links; check old URLs and image loadingBuilder
Inquiry or purchaseTest required fields, failures, confirmation, and receiptBuilder and recipient
Phone and keyboard useComplete the main task at a narrow width and without a mouseReviewer
Search settingsCheck titles, canonical URLs, indexability, sitemap, and redirectsBuilder
Ownership and maintenanceConfirm account access, update responsibility, and handoff notesOwner and builder

Turn “looks good” into observable acceptance criteria#

A checklist becomes more useful when you record the actual result. For the consultancy example, a short acceptance record might contain:

  • Comprehension: a person outside the project can explain what the operations review includes, what needs a separate quote, and what happens after an inquiry. Record misunderstandings instead of prompting the person toward the answer.
  • Navigation: starting on the service page, the reviewer can find the founder’s background and return to the inquiry without using a search engine or the browser’s back button.
  • Submission: a labeled test inquiry arrives with the expected fields, its confirmation appears, and the recipient can reply. Check both the form service’s record and the receiving inbox if the setup provides both.
  • Recovery: with the developer deliberately simulating a failed submission in a test environment, the visitor sees an understandable error and retains their message. Do not interrupt a live service to run this check.
  • Editing: the owner changes a paragraph and image in the agreed workflow and can restore the previous version without guessing.

Those observations do not constitute a complete accessibility or security audit. They do give the owner and builder a shared definition of whether the main journey works. Agree separately on any specialist testing the project requires.

Decide what prevents launch and what can follow. A broken contact path blocks the business purpose. Another decorative animation rarely does. Keep a short record of known issues, who owns them, and when they will be revisited.

Download the website planning worksheet to record the decisions in this guide.

Make the first review about a decision#

Before launch, decide what you need to learn from the site. For an inquiry-led service, a manageable record might track inquiries received, whether each fit the offer, the question that remained unanswered, and whether a conversation followed. Keep that business record private; an analytics dashboard does not need copies of people’s messages.

Separate three different situations:

ObservationWhat to investigate before changing the design
Few relevant people reach the service pageHow the intended audience discovers the business and which links they follow
People inquire, but repeatedly misunderstand the offerThe wording, examples, scope, and expectations on the page
Suitable inquiries arrive, but conversations stallResponse handling, availability, and the next step after contact

These are starting points for investigation, not diagnoses from traffic alone. A quiet week is not enough to decide that a page has failed. Record the number of observations and the context, including changes in promotion or availability. For a new site with little traffic, direct conversations and observed task attempts can reveal questions that percentages conceal.

Choose the next change because you can explain the problem it addresses. The companion guide to marketing measures develops that review process further.

Questions that come up before a first launch#

Can I launch before I have case studies?#

Yes, if the offer and experience are described honestly. Use relevant professional work with clear role attribution, show a process you can explain, and identify work in progress as such. Empty testimonial slots and invented results do not help someone decide.

Should I publish a blog immediately?#

Only if there is something useful to publish and someone who can maintain it. Service and product information usually deserves attention before a schedule of general articles. One substantial answer to a real customer question can be a better starting point than a grid of interchangeable posts.

How do I know the first version is enough?#

Ask whether the intended visitor can understand the offer, evaluate the fit, and complete the next step. Then ask whether the business can maintain the site and respond to what it receives. Missing either side gives you a more useful priority than simply adding pages.

If you want help turning those decisions into a working site, Antilo’s website design work connects planning, writing, design, and implementation. You can also use the marketing budget guide to decide what belongs in the first scope.

Next step

What needs attention in your business?

We can start with the decision you are facing, the project you need to finish, or the marketing you cannot keep up with. We’ll discuss the work involved and whether we can help.