There is no compulsory page count that makes every business website complete. Choose pages according to the decisions customers need to make and the information the business must maintain. A smaller site with clear service explanations can be more useful than a large collection of overlapping pages.

This guide covers page inventory, distinct service journeys, evidence and manageable content ownership. Discuss the relevant requirements through ITZ’s Website Design service.

Core business information

Provide a homepage, service information, an About page and accessible contact details. Privacy information should explain the actual handling of website enquiries and any relevant tracking or third-party services.

Start by answering who the business is, what it provides, where it operates and how a customer can take the next step. These facts may appear across the homepage, About and contact pages, but each page should have a clear role. Avoid repeating the same promotional introduction everywhere while leaving practical questions unanswered.

Individual service pages

Create separate pages where services address distinct customer requirements. Explain the scope, relevant technical details and practical inputs needed for an enquiry rather than duplicating a general company introduction.

Give a service its own page when it has a distinct audience, scope or buying discussion. Explain what is included, relevant constraints and what information helps assess a request. Do not create a page merely to target another spelling of the same keyword. A guide can explore a supporting question while linking to the primary service page.

Plan Your Website Page Structure to discuss page inventory, distinct service journeys, evidence and manageable content ownership.

Supporting evidence

Use approved portfolio examples, case studies or product information where they help customers evaluate the offering. Clearly identify the business’s contribution and avoid unsupported performance claims.

Add evidence that helps people assess suitability: approved project examples, factual credentials, useful answers and source-backed guidance. A portfolio page should state the business's actual role. A privacy page should reflect the forms and providers in use rather than a copied template. Assign an owner to each content type and its review cycle.

Page planning

The required page count follows from the audience, service catalogue and content available. Maintain a clear navigation hierarchy and avoid adding pages solely to meet an arbitrary volume target.

Turn the page inventory into a simple structure with meaningful internal links. Google's SEO Starter Guide supports making content understandable and easy to navigate. Search considerations should reinforce the customer journey, not produce unnecessary categories. Before approving a new page, write its purpose in one sentence and identify the unique material it will contain.

A practical example

Illustrative example: a maintenance company may need separate pages for ongoing contracts and emergency assessment because the scope and enquiry questions differ. It may not need separate copies of each for every nearby neighbourhood. Useful distinctions come from the service and customer need, not an arbitrary target number of pages.

Your review checklist

  • Give every proposed page one clear customer purpose.
  • Separate genuinely different services from supporting guides.
  • Check evidence and privacy information against actual operations.
  • Name the owner and next review date for important content.

Frequently asked questions

Does a small business need a fixed number of website pages?

No. Include the pages needed to explain the offering and support customer tasks, with enough distinct information to justify each page.

References and further reading

Related services and guides

Discuss the next step

Plan Your Website Page Structure. Use the form below to discuss page inventory, distinct service journeys, evidence and manageable content ownership. Share the relevant goals and existing arrangements; do not include passwords, private records or access tokens.

Plan Your Website Page Structure ↗

Reviewed and expanded on 15 October 2026. Examples are illustrative; the appropriate approach depends on your business requirements and existing systems.