How to Build a Website for a Small Business

A useful small-business website does not begin with colours, templates or software. It begins with a commercial purpose: who the site is for, what those people need to know and what you want them to do next. Once those decisions are clear, the technical build becomes much easier to control.

This guide sets out a practical route from the first idea to a working website. It is written for UK sole traders and small-business owners who may be building the site themselves or commissioning someone else to do it.

1. Define the job the website must do

Write one sentence describing the website's primary job. Keep it specific enough to guide decisions. For example:

The website should help homeowners within 15 miles understand our heating services, trust the business and request a quotation by phone or form.

That sentence tells you more than a vague objective such as “improve our online presence”. It identifies the audience, the service, the geographical area and the main conversion.

Choose one primary action and no more than two supporting actions. Typical primary actions include:

• calling the business;
• sending an enquiry;
• booking an appointment;
• buying a product;
• visiting a physical location;
• requesting a quotation.

A website can support several actions, but every page should have a clear priority. When everything is presented as equally important, visitors often do nothing.

2. Understand the people who will use it

You do not need a complicated set of fictional personas. You do need to understand the real questions a prospective customer asks before making contact.

For each important customer group, note:

• the problem they are trying to solve;
• what they already know about the service;
• what may make them hesitate;
• what evidence would help them trust you;
• whether they are likely to visit on a phone, at work or at home;
• the action they should be able to complete without assistance.

A local tradesperson may need prominent service areas, availability and proof of completed work. A consultant may need a clear explanation of the process, expertise and expected outcomes. An online shop needs product information, delivery terms, returns information and a reliable checkout.

3. Decide what the first version actually needs

Start with the smallest complete website that can do its job properly. “Small” should not mean unfinished. It means avoiding features that are not yet justified.

A practical first-version page set

Page	What it must achieve
Home	Explain who you help, what you provide, why the visitor should trust you and what to do next.
Services or products	Give enough detail for a customer to decide whether the offer fits their needs.
About	Provide relevant facts about the business, people, experience and working approach without invented claims.
Contact	Make the real contact routes, opening hours, service area and expected response time clear.
Privacy and other required notices	Explain how personal information, cookies, sales or bookings are handled where applicable.

Add separate location, service, booking, case-study, delivery or returns pages only when they solve a genuine user need. Do not launch an empty blog, a redundant “welcome” page or a members' area simply because another site has one.

4. Set a first-year budget, not only a build budget

Separate one-off project costs from recurring ownership costs. A low initial quote can become expensive if essential functions, support or renewals are excluded.

Typical one-off items

• planning and project management;
• design and development;
• copywriting, photography and graphics;
• data or content migration;
• payment, booking or other specialist configuration;
• testing and launch work.

Typical recurring items

• domain renewal;
• hosting or a website-builder subscription;
• business email;
• premium themes, plugins or apps;
• maintenance, monitoring and backups;
• transaction charges and payment-service fees;
• ongoing content and promotion.

Ask every supplier for a written list of what is included, what renews, who bills you and what happens if you stop paying. Compare the expected cost over at least three years, not just the introductory price.

5. Choose the build route

Common ways to build a small-business website

Approach	Usually suits	Main trade-off
Hosted website builder	Simple service, portfolio and small retail sites where ease of use matters more than technical control.	You depend on the platform's pricing, features and migration options.
Self-hosted WordPress	Content-led and expandable sites where ownership, hosting choice and a large extension ecosystem are important.	Someone must manage updates, backups, security and compatibility.
Freelancer or agency	Businesses that need professional planning, design, integrations or simply cannot spare the time to build well.	Quality and ownership depend on the brief, contract and supplier.
Custom development	Cases with genuinely unusual workflows that cannot be met sensibly by established software.	Higher cost, longer delivery and greater dependence on specialist maintenance.

Do not choose software before writing down the required pages, functions, integrations, budget and maintenance capability. A platform should fit the project; the project should not be distorted to justify a platform already chosen.

6. Keep ownership and access under business control

The business should be the registrant or account owner for its domain, hosting, website platform, analytics, email and payment services. A developer may administer these systems, but should not be the only person able to access them.

For every important account:

• use an email address controlled by the business;
• store recovery details securely;
• enable multi-factor authentication where available;
• record who has administrator access;
• keep invoices, licence details and renewal dates;
• agree how access and files will be handed over when work ends.

Before replacing an existing website, confirm that changing the site will not accidentally interrupt the domain or business email. Domain, DNS, hosting and email are connected, but they are not the same service.

7. Prepare the content before the build stalls

Gather complete drafts rather than leaving every page filled with placeholder text. The design cannot be judged properly until real headings, paragraphs, lists, photographs and calls to action are present.

Create one folder or shared workspace containing:

• approved page copy;
• the logo in usable formats;
• original photographs and proof that stock images are licensed;
• contact details, opening hours and service areas;
• pricing or quotation rules that may be published;
• legal and privacy information relevant to the site;
• existing analytics, domain and hosting access;
• a list of old URLs if an existing site is being replaced.

Use real evidence. Do not invent testimonials, qualifications, client logos, awards, case studies or performance figures to make an incomplete website appear established.

8. Build and test one complete user journey

Test the website as a customer would use it, not only as a collection of pages. For example: search or land on a service page, understand the offer, check trust information, open the contact page, submit the form and receive a useful confirmation.

Before launch, verify at least the following:

• the site works on current mobile and desktop browsers;
• navigation, buttons and forms work with a keyboard as well as a pointer;
• every important link opens the intended page;
• forms reach the correct monitored inbox;
• payments and bookings have been tested safely;
• the site uses HTTPS without mixed-content warnings;
• there is no accidental “noindex” setting or password protection;
• the old site's important URLs have appropriate redirects where needed;
• analytics and Google Search Console are connected to accounts owned by the business;
• a restorable backup exists before launch.

9. Launch, measure and improve

Launching is the start of ownership, not the end of the project. Record the launch date and check the website during the first few days for failed forms, broken redirects, unexpected mobile problems and indexing issues.

Measure outcomes that matter to the business: qualified enquiries, bookings, sales, calls or visits. Impressions, clicks and page views are useful diagnostic information, but they are not substitutes for commercial results.

Review the site using real evidence. Improve pages that attract relevant visitors but do not answer their questions. Add new content when customers repeatedly need information that the existing site does not provide. Remove or merge pages that serve no distinct purpose.

A sensible next step

Before choosing a platform or supplier, write a one-page brief containing the website objective, primary audience, required pages, required functions, available content, first-year budget, deadline and ownership requirements. That single document will prevent many of the most expensive mistakes later.

Sources and further guidance

• Google Search Central: Get started with Search Console (checked 21 July 2026).
• Information Commissioner's Office: privacy notices and cookies for small organisations (checked 21 July 2026).
• National Cyber Security Centre: small organisations guide to cyber security (checked 21 July 2026).