Topic hub

Starting a Website

Starting a business website is not mainly a design exercise. It is a sequence of decisions about purpose, audience, content, ownership, technology, budget and responsibility. Making those decisions in the right order…

15 published guides5 subtopicsUpdated 21 July 2026

A small-business owner planning the structure and content of a new website

Start here

The main guide for this topic

Complete guide

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 d…

Open the complete guide →

Explore the topic

Subtopics

3 guides

Budget and Costs

A website budget should cover more than the invoice for the initial build. A small-business website also needs a domain, host…

Explore →3 guides

Choosing How to Build a Website

A small business can build a website with a hosted website builder, self-hosted WordPress, an e-commerce platform, a freelanc…

Explore →4 guides

Common Website Mistakes and Troubleshooting

Website problems are easier to solve when they are separated into planning, content, technical, search and operational causes…

Explore →1 guides

Planning and Strategy

Website planning turns a broad intention such as “we need a better website” into a project that can be priced, built and eval…

Explore →4 guides

Website Structure and Content

A business website is easier to use and maintain when every page has a clear purpose, a defined audience and a logical place …

Explore →

Published guides

Articles in this section

The first article in this subtopic is scheduled for publication. The category is not shown publicly before that date.

About this section

This section is for UK small-business owners, sole traders and independent professionals who are planning a first website, replacing an outdated one or trying to regain control of a project that has become confusing. Use it as a route through the main decisions rather than trying to solve everything at once.

Choose your starting point

Where to begin with a website project
Your situation	Start with	The first result you need
You do not yet know what the website should achieve	Planning and Strategy	A written objective, audience and measure of success
You need to understand the likely cost	Budget and Costs	A first-year and ongoing budget, including maintenance
You are comparing builders, WordPress or professional help	Choosing How to Build a Website	A shortlist based on requirements, control and support
You need to decide which pages and materials are required	Website Structure and Content	A page list, navigation plan and content inventory
You are hiring a designer, developer, writer or agency	Working with Website Professionals	A clear brief, deliverables and ownership terms
You are preparing to publish or diagnosing a problem	Common Website Mistakes and Troubleshooting	A tested launch or a prioritised repair plan
You collect personal data or sell online	Legal and Compliance for UK Websites	A list of obligations that apply to the actual business model

A practical route from idea to launch

Define the job of the website. Decide what a useful visit should lead to: an enquiry, booking, sale, application, visit, phone call or another specific outcome.
Identify the audience and evidence. Record who the priority customers are, what they need to know and what proof the business can genuinely provide.
Set the scope. List the pages, functions, content and integrations needed for the first release. Separate essentials from later improvements.
Choose a build route. Compare platforms and suppliers against the same requirements. Do not begin with a favourite brand or a sales demonstration.
Protect ownership. Keep the domain, hosting or platform account, email, analytics, payment and advertising accounts under business-controlled access wherever practical.
Prepare content before the final build. Collect accurate service information, prices or pricing logic, policies, photographs, testimonials with permission and clear calls to action.
Build and test on a non-public version. Check mobile use, forms, payments, navigation, accessibility, privacy controls, speed and recovery before launch.
Launch with measurement and maintenance. Confirm backups, Search Console, analytics where appropriate, renewal dates and a named person responsible for updates.

What a sensible first version includes

A small first release can still be professional. It normally needs:

a clear home page that explains the business and the next step;
service or product pages that answer real buying questions;
about and contact information that can be verified;
working enquiry, booking or purchase routes;
privacy and legal information relevant to the site;
mobile-friendly navigation and readable content;
basic search visibility, measurement and maintenance arrangements.

It does not need every future feature. Features that are not ready, tested or maintainable should be left out rather than published as unreliable promises.

Decisions that should remain with the business

A supplier can advise and implement, but the business should understand and approve:

the website objective and priority audience;
the domain owner and account holder;
what personal data is collected and why;
the final page list and customer journey;
the total recurring cost;
who can make changes after launch;
which results will be measured;
how the website will be recovered if something fails.

Common ways projects go wrong

Design begins before the content and page purpose are known.
The cheapest quotation is selected without comparing exclusions.
The domain or important accounts are registered in a supplier's name.
The site is launched with placeholder text, untested forms or missing policies.
Every possible function is added before the core customer journey works.
No one is responsible for backups, updates or enquiries after launch.
Success is judged by appearance or visits alone rather than useful business actions.

What to prepare before you spend money

Create a short project note containing:

the main objective;
the priority audience;
the desired customer action;
the essential pages and functions;
the available content and missing materials;
the budget for the first year and later years;
the people who will approve and maintain the site;
the required launch window and any genuine deadline.

The next practical step is to complete that note before selecting software or asking suppliers for prices. It will make every later decision more consistent.