One page can suit a small business with a tightly defined offer, where most visitors need the same information and next step. Separate pages earn their place when services, audiences or locations need different explanations. Choose the smallest structure that covers those needs and that your team can keep current.
A five-page package does not tell you whether your business needs five pages. Before comparing website proposals, write down what someone must understand before contacting you. That gives you a practical way to discuss scope without filling pages simply because they are included.
Start with the questions customers bring
List a few real tasks: checking whether you assemble a particular kind of furniture, comparing two workshop services, or finding the entrance to a studio. For each task, note the answer, the evidence you can show and the action someone should take next.
Then group tasks that belong together. A short explanation of your service area can sit beside your offer. A detailed custom-build process may need more room, particularly if it has different requirements from your everyday repair work.
CIRA's one-page website guide identifies the type of offer and amount of content as considerations in choosing a one-page site. That is a useful starting point. The decision still depends on the information your own customers need.
When one focused page is enough
One page is worth considering when the offer is narrow and its supporting information forms a clear sequence. A visitor can understand the work, check the relevant conditions, see examples and find out how to contact you without sorting through unrelated services.
You can give that page distinct sections and links that jump to them. Someone returning for your coverage details should not have to read the introduction again. Plan those sections around recognisable questions, with labels such as “What we assemble” and “Service area”.
Keep the meaning of “one page” practical. You are deciding how to present the main business information. Separate supporting pages may still be appropriate, including any privacy information relevant to the site. This content decision also does not specify which software or development approach to use.
When information deserves its own destination
A separate page becomes useful when you would regularly want to send someone directly to it. Perhaps a customer needs to review a specialist service before a call, or someone visiting a second location needs its particular hours and access details.
Ask whether that destination has enough distinct information to be useful on its own. Can you explain its purpose without repeating the general overview? Does it have relevant evidence and a sensible next step? If the answers are still vague, keep the information together while you work out what is genuinely different.
There is a maintenance decision here too. If opening hours appear in several places, somebody must keep them consistent. Give shared information a clear home and identify who will maintain details that differ between pages.
Three fictional businesses, three task maps
The examples below are invented planning exercises, not ZXP client projects or measured results. Each recommendation depends on the stated scope; the final column shows what would change it.
| Fictional business and visitor question | Evidence or detail needed | Proposed page or section | Why it fits; what would change it |
|---|---|---|---|
| Furniture assembler: “Can you assemble my flat-pack desk at my home?” | Accepted furniture, service area, example work and enquiry requirements | One main page with offer, coverage, work examples and enquiry sections | Customers need the same service details before making an enquiry. Reconsider if a distinct installation service needs different conditions and evidence. |
| Bicycle workshop: “Do you repair bicycles as well as build custom frames?” | Repair scope and drop-off process; separately, frame options, fit and build process | Shared overview plus repair and custom-frame pages | The two decisions need different explanations and next steps. Use a combined overview until distinct approved content is ready. |
| Two pottery studios: “Which studio has my class, and how do I get inside?” | Location-specific class schedule, hours, entrance and access details | Shared class information with a destination for each actual studio | Arrival and scheduling details differ. Two service areas alone would not establish a need for two studio pages. |
A furniture assembler with one focused offer
For the fictional assembler, the important boundaries concern the same job: which furniture is accepted, where the business works and what a customer should send with an enquiry. Those answers can sit together on one main page, supported by relevant work photographs.
Splitting “chairs”, “tables” and “bookcases” into separate pages would need a reason beyond filling a menu. If the process and evidence are largely shared, clear sections may do the job. A new installation service with different conditions would prompt a fresh look at the structure.
A workshop with two different buying decisions
The fictional bicycle workshop has a stronger case for separate service pages. Someone arranging a repair needs to understand what the workshop handles and how to bring a bicycle in. Someone commissioning a frame needs information about fit, materials, consultation and the build process.
A shared overview can introduce both, while each service page carries its own explanation and next step. If the custom-frame offer is not yet defined, publish an accurate combined overview rather than an almost-empty destination. Add the separate page when there is useful, approved information to put on it.
Two studios people can actually visit
The fictional pottery business has two customer-facing studios. Location pages can be useful if classes, hours or access differ. A visitor should be able to confirm where a class takes place and find that studio's arrival information together.
Keep information common to both studios in a shared place where that makes sense. A general description of a beginner class need not be rewritten twice. Serving customers from two cities, however, would be a different situation from operating two studios. Do not imply that a business has premises it does not have.
Make the structure easy to follow
On a one-page site, use clear section headings and useful jump links. On a multi-page site, give visitors a straightforward route from the overview to the detail they need. Avoid making the menu carry every minor question.
Google's link guidance recommends descriptive link text and links between relevant pages to help people and Google understand and discover content. “Bicycle repair services” sets a clearer expectation than a standalone “Learn more”. Important pages should be linked from another page on the site.
That guidance is not a reason to pursue a particular page count. A structure decision should leave you with useful destinations, clear connections and content you can maintain; it cannot promise a ranking or enquiry result.
Take a task map to the scope discussion
Before approving a proposed structure, write one sentence for each main visitor task. Beside it, name the information needed, its proposed page or section and the person responsible for keeping it accurate. Mark missing information so the scope discussion can deal with it openly.
Use that map to compare proposals. Ask why each page exists and what a visitor should be able to do there. If you are exploring ZXP's website services, bring the map and the information you already have. They give the conversation a concrete starting point, even if the final page count changes.
Sources & references
- 01
- 02Link best practices for Google
Google Search Central
A perspective from the ZXP team.
Designed to help you ask better questions and take a clearer next step.
