A three-person cleaning company is reviewing its proposed website menu: Home, About Us, Who We Are, Our Story, Our Team, Services, Why Choose Us, FAQs, Gallery, Blog, and Contact. None of those labels is inherently wrong. Together, though, they can turn a straightforward business into a maze of nearly identical pages.

The company doesn't need to look bigger online than it is. It needs to help a visitor answer a few questions: Do you provide the service I need? Do you work where I live? Who am I dealing with? How do I get in touch?

Plan the pages around those decisions, not around how many menu items a website template can hold.

Start With Four Core Destinations

For many small cleaning, lawn-care, and handyman businesses, four destinations make a useful starting structure. This is a planning recommendation, not a legal requirement or a Google ranking formula:

  • Home: Introduce the business, its main services, the area it serves, and the next step. Send visitors toward details rather than trying to explain everything on the homepage.
  • Services: Give people a clear view of the work offered, important exclusions, and where to learn more or request an estimate.
  • About: Explain who operates the business, its relevant experience, and what customers can reasonably expect. Include the team here if a separate team page would add little.
  • Contact: Provide a working phone number, form, or other appropriate contact method, along with useful service-area and response information.

These are destinations, not necessarily four separate URLs. A very small business might communicate the same information through clearly labeled sections of one carefully designed page. Another may need several service pages because customers arrive with genuinely different needs. The test is whether people can find distinct answers without searching through repeated copy.

Combine About Us, Who We Are, and Our Team Unless They Do Different Jobs

An owner-operated handyman service usually doesn't need an About page, a Who We Are page, an Our Story page, and a Team page. If they all introduce the same owner and repeat the same background, one well-organized About page is clearer.

That page can introduce the owner, explain the kind of work the business accepts, describe relevant qualifications accurately, and show a real team photo if the people have agreed to appear. There is no need to invent a leadership structure or imply the company has a larger staff than it does.

A separate Team page may earn its place when customers choose among different professionals, roles or specialties materially affect the service, or staff profiles require information that would overwhelm the About page. Otherwise, introduce the people where the customer already expects to learn about the business.

The same logic applies to a standalone Why Choose Us page. Substantiated strengths usually fit more naturally beside the services, process, and people they explain. A separate page filled with generic claims is another click without another answer.

Use Services as a Hub, Then Split Only When Needed

A Services overview gives visitors a quick way to recognize the work they want. It can link to individual services where those topics warrant their own explanation.

For example, a cleaning company might need distinct pages for recurring house cleaning and move-out cleaning if the scope, preparation, estimate questions, and customer expectations differ. A handyman who offers only a narrow set of closely related small repairs may be better served by one detailed page with clear sections.

Before creating a service URL, ask whether it will explain something customers can't already understand on the overview. If the new page only swaps a heading and city name while repeating the same paragraphs, it probably hasn't earned its own place.

Google's SEO Starter Guide recommends organizing a site logically to help visitors and search engines understand how pages relate. Its sitelinks guidance also recommends informative headings, useful internal links, and avoiding repetitive content. Neither source prescribes a minimum number of service pages.

Give Common Questions a Clear Place Before Creating Another Page

Several familiar website labels describe information that can often live inside a core page:

  • Service area: A concise list or explanation on Home, Services, or Contact may be enough. Create a dedicated coverage page if the geography or availability rules genuinely need more explanation; don't create near-identical pages for every neighboring town.
  • Pricing and estimates: Explain how quotes work on the relevant service page. A separate pricing page may help if the business offers several clearly defined packages or a shared pricing process that needs its own explanation.
  • FAQs: Answer a question where it comes up. A dedicated FAQ page is useful when customers repeatedly need answers that cut across several services, not simply because the website template includes one.
  • Work examples and reviews: Place genuine, permission-cleared examples beside the work they help explain. A portfolio may deserve its own page when there are enough distinct projects to browse. A gallery of generic stock images does not.

A Blog or Insights section is optional. It makes sense when the business can publish useful, accurate information that deserves a separate article. It isn't part of a compulsory small-business page count, and an empty blog can be left out at launch.

Keep Privacy and Other Utility Information Accessible, but Don't Treat It as Sales Navigation

A Privacy page serves a different purpose from a Services page. It should accurately describe relevant data practices if the business collects inquiry details, uses analytics, or relies on outside form and scheduling providers. The FTC's data-security guide urges companies to understand what personal information they hold and keep only what they need.

The exact legal notices required depend on the business, its activities, and applicable laws. For example, California's privacy regulator explains obligations for businesses covered by the CCPA; those duties should not be presented as universal requirements for every small company in the United States.

Terms of use, booking policies, cancellation rules, or other notices may also be appropriate depending on the business and how customers transact with it. Don't publish generic legal language just to fill a footer. Have the actual terms and applicable requirements reviewed, and make important booking or payment conditions visible when customers need them—not buried in a legal page.

These utility pages can be easy to find in the footer without competing with Services or Contact in the main menu. An accessibility contact route should also be practical and discoverable; adding an unsupported compliance badge or generic statement is not a substitute for an accessible website.

Keep the Main Menu Small Enough to Explain at a Glance

For a compact multi-page service site, a header that reads Home · Services · About · Contact is a reasonable starting example. If several major service types need distinct pages, they can appear under Services rather than each becoming a top-level item. Put privacy notices and other supporting links in an organized footer.

That isn't a fixed menu rule. The point is clear naming, consistent placement, and a short route to the customer's task. The W3C Web Accessibility Initiative's menu guidance explains how semantic, well-labeled menus support navigation with assistive technologies. Its design guidance recommends consistent navigation across pages and screen sizes.

Before launch, try three simple visits on a phone: a customer looking for a specific service, someone checking whether you cover their address, and a person ready to request an estimate. If they can't find what they need, adjust labels and links before adding another page.

Add a Page Only When It Answers a Different Question

When a designer proposes one more page, ask: What question will this page answer that the existing pages cannot answer clearly? Then ask who will keep that answer accurate when services, staff, or policies change.

If the proposed page serves a distinct customer need, is substantial enough to stand on its own, and has a natural place in the navigation, it may be worth creating. If it repeats another page's purpose, merge the material and improve the original.

The goal isn't the smallest site at any cost. It's the smallest clear structure that fully explains the real business. Visitors don't need separate pages for every label in a marketing presentation. They need answers they can find, understand, and act on.

Sources and Further Reading