Topic hub

Business Website Types and Features

A useful business website is defined by the customer task it completes, not by the number of features installed. Start with the simplest website type that supports the business model, then add functions only when…

4 published guides3 subtopicsUpdated 21 July 2026

Start here

The main guide for this topic

Step-by-step

How to Add Online Payments Safely

For most small businesses, the safest payment design keeps card data on a hosted or provider-controlled payment page. The website still has responsibilities for account security, scripts, order record…

Open the complete guide →

Explore the topic

Subtopics

1 guides

Local Business Website Essentials

A local business website should remove uncertainty about identity, location or service area, opening times and the next actio…

Explore →1 guides

Membership and Client Areas

A member or client area turns a public website into an access-controlled service. It introduces identity, permissions, accoun…

Explore →2 guides

Website Features

Website features should reduce work or help a customer complete a task. Every extra integration also introduces data, supplie…

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

Information checked: 21 July 2026.

In brief: Build the smallest website that completes the customer task reliably, then add features with a named owner and an exit route.

Choose the operating model

Common website types
Type	Primary task	Operational dependency
Service website	Explain services and generate enquiries	Forms, phone tracking and content updates
Local business website	Support visits, calls and bookings	Opening hours, maps and local information
Online shop	Take and fulfil orders	Payments, stock, shipping and customer support
Booking website	Sell or reserve time	Availability, reminders, cancellation and calendar sync
Membership or client area	Provide controlled access	Identity, permissions, billing and support
Publishing site	Build an audience through content	Editorial workflow, search and internal linking

Add features in dependency order

A booking system needs reliable email and calendar ownership. Payments need reconciliation and refund procedures. Membership needs account recovery and access control. Do not install the visible feature before the business can operate the underlying process.

Use a feature register

Business owner and technical owner.
Personal data collected and retention period.
Supplier, plan and renewal date.
Failure alert and manual fallback.
Backup or export method.
Acceptance test and review date.

Avoid feature accumulation

A feature that is never maintained adds privacy, performance and security risk. Remove abandoned chat widgets, duplicate forms and unused integrations rather than leaving them connected indefinitely.

Where to go next

Use the supporting guides in this section to plan forms, booking, payments, newsletters, search and member areas. Each guide includes a practical acceptance test rather than assuming that installation equals completion.

Example: start with the customer task

A consultant may need clear service pages, evidence, a contact route and calendar booking. Adding a shop, member dashboard and chatbot at launch increases support without improving the main enquiry task. Define the minimum journey first, measure it and add another feature only when the business can explain the problem it solves.

What the business should retain

Primary customer journeys
Feature register and owner
Data-flow diagram
Manual fallback for critical functions
Quarterly feature review

Sources and date checked

Technical and product information was checked against the following primary sources on 21 July 2026. Plans, interfaces and provider terms can change, so recheck them before purchase or migration.