What pages does a local service website actually need?

A local service website needs enough information for someone to decide whether you can help and what to do next. That can be one well-organised page. It can also be several pages when your services, locations or customer questions are genuinely different.

Page count is not a quality target. Give each page a clear job, then remove anything that duplicates another page without helping the visitor.

Choose one page or several

You do not automatically need a services hub, separate testimonials page or blog. A short service list can live on the homepage; a review can sit beside the service it describes.

Gather these fields before designing

Business and contact details

• The business name customers recognise, a short description and a real contact route.
• Where you operate, whether customers visit you or you visit them, and any relevant access instructions.
• Opening or contact hours, including how out-of-hours messages are handled.
• The main action: call, request a quote, send an enquiry or book an appointment.

Service information

• The service name in language customers use.
• What is included, what is excluded and who it is suitable for.
• A clear price where appropriate, or the information needed to prepare a quote.
• Likely next steps, including whether an enquiry is only a request rather than a confirmed booking.
• Answers to the questions you repeatedly receive before a customer commits.

Evidence and reassurance

• Real work photos that you have permission to publish.
• Accurate qualifications, memberships or insurance statements that you can substantiate.
• Genuine customer feedback used with appropriate permission and attribution.
• A short explanation of who does the work and how customers can raise a problem.

Do not fill empty space with invented reviews, stock photos presented as your own work or promises you cannot support. A specific explanation of your process is better than an unsupported claim to be the best.

A fictional garage example

Imagine a fictional independent garage offering routine servicing and fault diagnosis. Its homepage explains the business, vehicles it works on, location and contact options. A servicing page sets out what the service includes and how to request a quote. A diagnosis page explains the initial assessment and how further work is agreed.

Both pages offer a request-an-appointment route. The confirmation says the garage will contact the customer to agree a time; it does not pretend the diary is booked automatically. Opening hours and arrival instructions appear wherever customers need them.

That is a useful small site. It does not need dozens of pages named after nearby towns. Add a location page only if it supplies genuinely different information. Google's spam policies identify doorway abuse, including similar regional pages that funnel people to the same destination.

Test the contact route, not just the homepage

1. Open the site on a phone. Find a service, the area covered and the next step without guessing.
2. Check that the telephone and email links point to the right destination.
3. Submit an agreed test enquiry using non-sensitive test details. Check receipt in the actual monitored inbox, including spam handling.
4. Try a missing required field and an invalid email address. Check that the error explains how to fix it without erasing everything.
5. Follow the booking link. Check the service, location, price information and confirmation on the external system too.
6. Navigate using a keyboard. Check visible focus, useful link labels and labelled form fields. Check readable text and contrast.

These checks are a starting point, not an accessibility certification. GOV.UK's testing guidance explains why manual and automated checks both matter. For a fuller assessment, involve someone competent in accessibility and people who use assistive technology.

Agree who keeps it working

Record who controls the domain, hosting, editor and booking account. Keep recovery details under the business's control. Ask what backups or exports exist, how a failed site is restored and what happens when you leave a supplier.

Assign a person to update prices, hours and service changes. As a practical routine, check contact routes monthly and after changes. Include privacy, cookies and any business-specific disclosures in the project brief, with appropriate specialist advice where needed. This checklist is not legal advice.

If you are starting from nothing, take this brief to More Hands by Foundry Works and check the current free-website scope. If a site already works, a bounded improvement may be more useful than a rebuild.