How to Plan a Local Business Website: Pages, Proof and Enquiry Paths
Plan your website around the questions customers need answered before they contact you. Give your important services enough room, make location and contact details easy to reach, and use evidence that backs up the real work.
The right number of pages follows from those needs. A small specialist may need a compact site, and a multi-branch operation a larger one. Buying a fixed bundle of pages before you know what each is for can leave important questions unanswered and optional pages empty.
This guide helps you create a content map and a practical brief before design or development begins.
Start with three customer journeys
Write down how three plausible visitors would arrive and what they need next.
A person who knows the business name may be checking the phone, hours or entrance. They should not need to read a long sales page to find that information.
A person searching for a specific service may arrive directly on a service page. That page needs enough context to explain the provider, coverage, scope and next step without requiring a trip through the homepage.
A person comparing providers may need evidence, qualifications, process or an answer to a concern. Make that information reachable from the relevant service.
These journeys show what the site has to do. They also show why the homepage cannot carry every job.
Make a page earn its place
For each proposed page, answer four questions:
- What decision or task does this page serve?
- What information is unique to that decision?
- Which evidence can the business provide?
- Where should the reader go next?
If you cannot answer the second question, the material probably belongs in an existing page or section. If you cannot answer the third, add a task to gather evidence instead of inventing proof.
Google's SEO guidance recommends a clear site organisation and links that help visitors and search engines understand the content. That supports a useful hierarchy; it does not establish a universal page count. Google's SEO Starter Guide
A practical content map
| Page or section | Customer question | Required substance |
|---|---|---|
| Home | Is this the right kind of business? | Main activity, relevant customers/coverage and routes into services/contact |
| Services overview | Which offering fits my need? | Distinct services with concise scope and links |
| Important service page | Can this business do my particular job? | Scope, conditions, process, evidence and enquiry context |
| Location/coverage | Can I visit or receive service here? | Real premises or coverage, access, hours and relevant limits |
| About/team | Who is responsible for the work? | Actual people/organisation, experience and current supported credentials |
| Work examples | Can I assess comparable work? | Real permitted projects or evidence explained in context |
| Contact/enquiry | How do I take the next step? | Working contact routes, proportionate form and response expectations |
| Required legal/privacy information | How is the business identified and information handled? | Operator- and jurisdiction-appropriate disclosures |
Some of these can be sections rather than separate URLs. A single-location service business may place useful coverage information on its main service page. A large branch operation may need a proper location index and branch pages.
A separate page should make the reader's task easier. It should not exist just to make the sitemap longer.
Give the homepage an organising role
The homepage should identify the business quickly and help visitors choose a route. A useful first view usually explains the main activity, genuine operating area and the most relevant next action.
Then provide a clear route to priority services, important evidence and contact information. A person arriving with a specific question should be able to identify the next click from ordinary language.
Do not make visitors decode internal departments or vague navigation labels. If customers ask for equipment repairs, a menu item called "technical ecosystems" makes them do extra work.
Do not hide the phone number and contact link inside a slideshow. The page has to make sense on a phone, with a keyboard, and when decorative media fails to load.
Choose which services deserve their own pages
Create a separate service page when the customer's decision needs distinct scope, process, conditions or evidence. Several related tasks can remain together if the decision is essentially the same.
For example, a fictional building-maintenance team might need separate pages for planned commercial maintenance and emergency attendance if the customers, scheduling, scope and response arrangements differ. Three pages called "reliable maintenance", "quality maintenance" and "professional maintenance" would not create any useful distinction.
Use a service brief before writing. The service-page article includes one you can complete with the delivery team.
Handle locations without inventing branches
A branch page should describe a real operation. Useful differences include services available at that branch, opening hours, entrance, staff arrangements and customer instructions.
A service-area page should explain coverage as coverage. A team working in several towns does not automatically operate an office in each one.
Use a location page when there is enough genuine information to support the customer's local decision. Where the information is thin, a clear coverage section can be more useful than a long sequence of near-identical pages. The location-page guide gives a publish/combine decision table.
Keep addresses, public pins and private operating information under deliberate control.
Build evidence into the service path
A standalone gallery can be attractive but difficult to interpret. A reader needs to know what a picture demonstrates and whether it is relevant to the service under consideration.
Connect evidence to the claim. A permitted project example might explain the customer's requirement, the scope delivered and a meaningful constraint. Photographs should show the actual work, with privacy and image rights addressed.
If the business is new, explain its real process and supported capability. Do not fill an empty portfolio with another company's projects or synthetic images presented as completed customer work.
The photo planning guide helps choose evidence for specific customer questions.
Write the contact journey before designing the form
Decide who receives requests, what they need to assess them and what a customer sees after sending one. A polished form can still fail if no one is responsible for the inbox.
Ask for the smallest information set that supports the first useful response. Further job, billing or access details can be collected privately at the appropriate stage.
State the response expectation honestly. A submission should not imply a confirmed booking unless the business has actually confirmed it.
Use the enquiry-form guide for labels, errors, mobile completion and receipt behaviour. Ask the developer to demonstrate that a submitted request can be retrieved, not just that a success message appears.
Worked content brief: a commercial maintenance firm
The following structure is illustrative, not a recommended template for every trade.
The firm serves small commercial premises and wants recurring planned work. It also handles selected urgent repairs but cannot provide a general 24-hour emergency service.
Its site plan could be:
- A homepage that identifies the commercial customer and routes visitors to the relevant work.
- A service overview distinguishing planned maintenance from selected repair assessment.
- A planned-maintenance page explaining inspection, agreement, scheduling and exclusions.
- A repairs page explaining the types of request accepted and the actual response arrangement.
- A coverage/contact section identifying real service areas and asking for premises type, area and the immediate problem.
- An about/evidence page showing the actual responsible team and permitted comparable work.
The plan deliberately avoids promising emergency attendance everywhere, and does not make up a branch page for every nearby town.
The owner can now brief a writer and designer using specific questions. The developer can test navigation and enquiries against those questions. The team can also identify which evidence is missing before production begins.
Give the supplier a content inventory
For each page, record its proposed URL, reader task, owner, source material, required media, related pages and state. Useful states include awaiting facts, draft, review, approved and published.
Record dependencies explicitly. A branch page awaiting a verified address should not be filled with a placeholder location and forgotten. A claim about a qualification needs confirmation before publication.
Agree who maintains the website after handover. Keep the domain, hosting and important accounts under business control, with appropriate supplier access.
Review the structure on a small screen
Ask an unfamiliar person to find one service, assess its suitability and make an authorised test enquiry. Observe the navigation, labels and points where the person has to guess.
Check headings and reading order as well as visual design. W3C's accessibility guidance explains how headings communicate page organisation, including to people using assistive technology. W3C heading guidance
Test direct arrivals on service pages. Customers and search engines do not always enter through the homepage.
Add content when a real gap appears
Customer questions, service changes and evidence of different needs can justify new pages. A new keyword phrase alone is a weak content brief.
Measure whether the site helps people reach appropriate information and whether received enquiries fit the business. Keep the distinction between search visibility, website activity and actual work.
A good website plan gives every important page a purpose, a source of evidence and someone responsible for keeping it current. That is a stronger base for design and search than a pile of interchangeable pages.