A service business website should help visitors understand what you do, who it suits, how the work happens, what conditions apply and how to start a conversation. Consider a homepage, service information, a business profile and a contact page first. Add separate pages when services need different explanations, rather than choosing a fixed page count before understanding the work.

Start with customer questions, then name the pages

Collect questions your team actually receives in conversations, emails and quotation requests. Separate confirmed answers from matters assessed case by case. Those questions help you decide both which pages to create and which information belongs together.

What problem can you help with? Introduce it on the homepage and explain it on a service page.
Does this service fit my situation? State suitable work, scope and exclusions.
What can I verify about the business? Provide accurate team information, a working method or real work you have permission to show.
What must I prepare, and how long might it take? Explain the process and factors used to assess timing.
How is the price assessed? Explain the pricing method and information needed. Be clear when a fixed price is unavailable.
How do I begin? Give a clear contact or briefing route, with the next step explained.

This is a content planning framework, not a guarantee of enquiries or sales. If visitors still need to ask every basic question, improve the answers on existing pages before adding more pages.

Four foundational pages to consider

1. Homepage: introduce the work and help people choose a route

Describe the main services, problems addressed and suitable customers in everyday language. Keep the introduction focused and link to relevant service information. The homepage does not need every detail. Use an action label such as “Send a brief for assessment” when that is the actual next step, rather than making people guess what a button does.

2. Service information: help visitors judge whether the scope fits

Explain deliverables, included and excluded work, process, customer inputs and factors affecting time and price. Services with similar answers can start on one overview page. Services with substantially different terms, such as a new design project and ongoing maintenance, may need separate detail pages so their conditions remain clear.

3. Business profile: provide information people can verify

Give accurate business details, working methods, responsibilities and experience supported by evidence. Team photographs and profiles need permission. Do not invent client counts, awards or endorsements. If you do not yet have publishable case studies, describe the real process and acceptance criteria instead of presenting fictional work as customer evidence.

4. Contact or briefing page: make the first step understandable

Show channels that someone actually monitors. A form should request information needed for the initial conversation, such as the problem, a contact method and availability. Explain what happens after submission and state a response window only if the team can support it. Before launch, check both the confirmation and delivery to the recipient. A form in a design image is not a tested enquiry system.

Additional pages need a clear purpose and usable information

How we work: Useful when the process or the customer's responsibilities affect the decision. A short explanation can remain on the service page.
Projects or case studies: Use real work with publication permission. Explain the brief, scope and deliverables without inventing measured outcomes.
Pricing and scope: Useful when packages or assessment criteria can be explained. For individual estimates, state the inputs needed and costs that may be separate.
Frequently asked questions: Answer useful questions people actually have. Important service conditions should also appear near that service.
Articles: Useful when the team has knowledge that helps visitors decide and someone can maintain it. An empty archive does not need to be added just to fill the navigation.

Privacy information and conditions relating to data collection should reflect the actual use and be checked by the responsible person. This article is not legal advice or a universal list of mandatory documents.

Example sitemap: a fictional building services company

This planning example is not an Exploera customer case study. The fictional company offers site inspections and ongoing building care. It receives a brief before assessing a price and does not offer online booking or payment in the first phase.

Homepage: Introduce building services and direct visitors to two service types.
Building inspection: Explain coverage, inspection scope, report deliverables, exclusions and information needed before arranging a visit.
Ongoing care: Explain service rounds, responsibilities and how a contract is assessed.
About the team: Provide only accurate, verifiable team details and qualifications.
Send information for assessment: Explain the contact route and initial inputs without requesting unnecessary personal information.

Five pages are a reasonable starting point in this example because the two services have different conditions. Add project pages when suitable evidence and permission exist. A new page should answer a new question, rather than split an existing paragraph merely to create another URL.

When should information be separated or combined?

Separate pages when visitors have different needs, the service has distinct conditions and there is enough information for each page to support a decision. Combine information when the answers largely repeat or each proposed page contains only one sentence. Multiple location pages that change only the place name add little useful detail. If service conditions genuinely differ by area, explain those actual differences.

Link related information deliberately: a service page can lead to the process and briefing route, while an article can lead to a relevant service. Google recommends understandable site organisation and descriptive link text. More pages or links do not guarantee search rankings.

Plan a sitemap the team can maintain

Before agreeing the work, identify the source owner for each page, what the team can edit and what requires provider help. Services, articles and information repeated in several places need clear ownership. Test editing, saving, previewing and reopening so the information remains consistent.

Exploera's native Articles and Media, locale data and draft previews are used to prepare this article. Other pages, brand-specific layouts, forms and integrations must match actual capabilities, entitlements and project scope. Do not assume every website automatically includes booking or payment.

If you have an existing site, read what to prepare before a website revamp, then bring your customer questions and page list to the discussion. Explore Exploera's managed website service or send a brief for scope assessment.

Questions to answer before handing over the sitemap

What main question does each page answer, and where should it lead?
Which information is confirmed, and what still needs business approval?
Do usable images and publishable work already exist?
Who maintains the content, and how will both languages be checked?
Which pages or systems are necessary at launch, and which can wait?

Clear answers let the page count follow the actual work and help the team assess design, content and system requirements more accurately.

Sources and scope

Content organisation and linking guidance were checked against Google Search Central's SEO Starter Guide, and reader-focused content against Creating helpful, reliable, people-first content on 13 October 2026. The sitemap is a planning proposal, not a page list prescribed by Google. AI assisted writing and source comparison. The AI-generated illustration is conceptual artwork, not a system screenshot or a customer project.

Articles

Which pages a service business needs