business website needs enough pages to answer distinct visitor needs clearly, and no more. Five pages can be plenty for a focused service business; fifty can be too few for a complex catalogue or multi-location organisation. Page count is an output of information architecture, not a measure of quality and not a sensible starting package on its own.
List the important reasons people visit: understanding a service, checking fit, comparing options, seeing proof, finding a location, getting a price, reading requirements, applying, booking or contacting support. Group closely related needs where one page can satisfy them without becoming a wall of unrelated sections.
- It serves a meaningfully different audience, problem or stage of the decision.
- People search for it independently and the business has enough unique substance to answer well.
- It needs its own conversion path, proof, eligibility rules or operational information.
- It is important enough to link directly from campaigns, sales conversations or support.
- Combining it with another subject would make both harder to scan or maintain.
A separate page for every tiny service variation or nearby town is weak when the content is substantially the same. Search visibility comes from satisfying a distinct need, not swapping a place name in a template. Consolidate overlapping subjects into a strong page and create a location or service page only when the offer, proof and information are genuinely specific.
- Homepage: positioning, priority routes and credible summary evidence.
- Service or product pages: one per distinct buying decision, not one per keyword synonym.
- Work or proof: genuine case studies, examples or an honest explanation of current experience.
- About: who is responsible, how the business works and why it can be trusted.
- Contact or start: the next step, expected response and information needed.
- Policy and support pages required by the service, data use and customer relationship.
Ten case studies should usually be one reusable content type, not ten separately designed layouts. Decide who can create a page, which fields are required, how navigation changes and when old content is reviewed. A smaller site with strong ownership stays more useful than a large site whose pages slowly contradict each other.
EverypageshouldearnitsURLbyservingadistincthumanneed.