A website is often the first place a potential customer checks before calling, visiting or donating. For a small business or organisation, it does not need to be large or complicated. It needs to answer visitors' questions quickly, work well on a phone and be easy to keep up to date. Most of what makes that possible is decided before any design work starts.
This guide takes you through the planning stage step by step. By the end you should have a clear list of goals, a sitemap (the list of pages and how they connect), a plan for the content, and an understanding of the practical and legal points to raise with a web designer or developer.
Step 1: decide what the website is for
Start with the actions you want visitors to take. For most small organisations, there are only a few.
- Phone, email or send an enquiry.
- Book an appointment or a table.
- Buy a product online.
- Find the premises and check when they are open.
- Donate, volunteer or sign up to a newsletter.
Rank them. The top one or two should shape the whole site: they belong on the home page, in the navigation and on every relevant page. A website that tries to give equal weight to ten different actions usually ends up guiding visitors towards none of them.
Step 2: understand your visitors' questions
List the questions people ask you by phone, by email and in person. These are the questions your website should answer before visitors need to contact you. A joiner might hear “Do you work on listed buildings?” and “How far do you travel?”. A charity might hear “How do I refer someone?” and “Can I volunteer if I work full time?”. Each frequent question is a candidate for a page, a section or a short answer in a page of frequently asked questions.
Also think about where visitors come from and what device they use. A large share of visits to many small business websites comes from mobile phones, so the mobile layout deserves as much attention as the desktop one. If you already have a site with analytics, your designer can confirm the pattern for your own visitors.
Step 3: draw the sitemap
A sitemap, at the planning stage, is simply a list of the pages your website will contain and how they are grouped. Keep it short. A typical small business site might contain the following.
- Home: what you do, for whom, where, and the main action.
- Services or products: one page per main service, rather than one long page listing everything. Separate pages are easier to read and easier for search engines to understand.
- About: who is behind the business, and the experience, qualifications or memberships that matter to customers.
- Examples of work: case studies or a gallery, with a few lines explaining each project.
- Contact: phone, email, address, a map if you have premises, and a simple form.
- Legal pages: privacy notice, cookie information and, if you sell online, terms and conditions.
Draw it on paper as boxes and lines. If a page has no clear purpose or would contain only a sentence, merge it into another. If a page grows to cover several distinct topics, split it.
Step 4: plan the content before the design
A frequent cause of delay in small website projects is content that is not ready: text unwritten, photographs not taken, approvals pending. Designers can work with placeholder text, but a design built around placeholder text often has to change when the real words arrive.
For each page in your sitemap, note what it needs and who will provide it.
| Page | Text | Images | Who provides it | When |
|---|---|---|---|---|
| Home | Short introduction, main services, main action | One strong image of your work or premises | Owner | Before design starts |
| Service pages | What it is, who it suits, how it works, frequent questions | Two or three photographs per service | Owner, with a photographer | Before design starts |
| About | Background, team, memberships | Portraits | Owner | Before the build |
| Contact | Details and directions | Map or entrance photograph | Owner | Before the build |
| Privacy notice | How you handle personal data | None | Owner, with advice if needed | Before launch |
Write in plain English, for a reader in a hurry. Lead with the answer, use short paragraphs and descriptive headings, and avoid internal jargon. If writing is not your strength, budget for help with copywriting, or at least ask someone outside the business to read your drafts.
Step 5: sort out domain, hosting and accounts
Domain name
Your domain is your address on the web. Domains ending in .uk and .co.uk are run by Nominet, the registry for the United Kingdom. Since 2014, the .scot ending has also been available, intended for people and organisations with a link to Scotland. Whichever you choose, register it in the name of your organisation, with an email address you control, not in the name of the designer or an employee. Losing access to a domain is one of the most disruptive problems a small business can face online.
Hosting and the website platform
Hosting is the service that stores your website and makes it available online. The platform is the software used to build and edit the site, often called a content management system. Ask your designer to explain which platform they propose, whether you will be able to edit text and images yourself, and what happens if you later want to move to another provider. Some hosted website builders make it hard to take your site elsewhere, while open-source platforms can be moved more easily but need regular updates.
Accounts and ownership
Keep a secure list of every account connected to the site: domain registrar, hosting, platform administrator login, email, analytics and any plug-ins or paid services. The organisation should hold the main login for each, even if the designer has their own access. Agree in writing who owns the design and the code once the project is paid for.
Step 6: build in accessibility from the start
An accessible website can be used by people with a wide range of disabilities, including those who use screen readers, keyboard navigation or magnification. Under the Equality Act 2010, service providers in England, Scotland and Wales must make reasonable adjustments so that disabled people are not put at a substantial disadvantage, and that duty can extend to websites. The widely used technical standard is the Web Content Accessibility Guidelines (WCAG) published by the World Wide Web Consortium. Version 2.2 was published in October 2023, and level AA is the usual target.
Practical points to raise with your designer include sufficient colour contrast, text that can be enlarged without breaking the layout, descriptive link wording, form fields with clear labels, alternative text for meaningful images, and navigation that works with a keyboard alone. Building these in at the planning stage costs far less than adding them later.
Step 7: privacy, cookies and legal information
If your website collects personal data, for example through a contact form, a newsletter sign-up or an online shop, you need to comply with the UK General Data Protection Regulation and the Data Protection Act 2018. In practice that means a privacy notice explaining what you collect, why, how long you keep it and how people can exercise their rights. The Information Commissioner's Office (ICO) publishes guidance aimed at small organisations.
Cookies and similar technologies are covered by the Privacy and Electronic Communications Regulations 2003, often shortened to PECR. Non-essential cookies, such as many of those used for advertising, have generally required consent. The rules were amended by the Data (Use and Access) Act 2025, which relaxes the consent requirement for some low-risk uses, so check the ICO's current guidance when planning your site rather than relying on an older template.
If you trade as a limited company, the Companies (Trading Disclosures) Regulations 2008 require certain information on your website, including the company's registered name, its registration number, the part of the United Kingdom in which it is registered and its registered office address. Sole traders and partnerships have their own disclosure rules. Guidance from Companies House sets out what applies to each structure.
Step 8: plan for search and for upkeep
Being found
Search engines need clear signals about what each page covers. Give every page a distinct title and heading that uses the words your customers would type, describe your location naturally if you serve a local area such as Perth and Kinross or Dundee, and keep your business name, address and phone number consistent everywhere they appear online. Be wary of anyone who guarantees rankings: no designer or developer controls how a search engine ranks pages.
Maintenance
Websites need looking after. Software updates, security patches, backups and content updates all take time. Before the project starts, agree who will do each of these and how often. A website that was excellent at launch but has not been touched for years tends to show it, through outdated information, broken features or security warnings in the browser.
Step 9: write it up as a website brief
Bring the previous steps together in a short document: goals, audience, sitemap, content plan, functions needed (forms, booking, shop), accounts and ownership, accessibility expectations, legal pages, maintenance and your timescale. Share it with any designers you are considering. A clear brief lets them propose a sensible scope and makes their proposals easier to compare.
Frequently asked questions
Should I use a website builder or hire a designer?
Both can work. A website builder can suit a very simple site that you are comfortable editing yourself. A designer or developer brings expertise in structure, accessibility and presentation, which often matters more as the site grows. The planning steps above are useful either way.
How many pages does a small business website need?
There is no fixed number. Many small organisations are well served by somewhere between five and fifteen pages. What matters is that each page has a clear purpose and answers real questions.
Who should own my domain name?
Your organisation. Register it in the organisation's name with contact details you control, and keep the login safe. If a designer registers it for you, ask for it to be transferred to your own account.
Do I need a privacy notice if I only have a contact form?
A contact form collects personal data such as names and email addresses, so you need to explain how you use it. The ICO provides guidance on what a privacy notice should contain for small organisations.