How many pages does a small-business website actually need?

Most sites need enough pages to give each distinct customer question or search intent a useful home. That may be one well-organized page for a solo business with one offer, five to fifteen pages for a typical marketing site, or hundreds for a retailer with real categories and products.

The important word is useful. A page earns its place by helping someone understand, compare, trust, visit, enquire, book or buy. Page count should follow those jobs—not a package a designer wants to sell.

These ranges are planning heuristics, not rules:

Business type	Sensible planning range	What usually creates the pages
Solo professional	1–5	One offer, biography, proof and contact
Local service business	5–12	Distinct services, service area, reviews and enquiries
Restaurant	3–7	Menu, story, hours/location, reservations and private events
Contractor	6–20	Trades or project types, portfolio, process, service area and bid request
Multi-location business	10–50+	Shared services plus a useful page for each staffed location
Law firm	8–40+	Practice areas, attorney profiles, FAQs, proof and required disclaimers
Ecommerce business	10–1,000+	Categories, products, shipping, returns, support and account flows
Custom platform	8–30+ public pages/screens	Marketing, onboarding, accounts, dashboards, help and application states

The same business can sit at either end of its range. A restaurant with one dining room and a stable menu has a different sitemap from a restaurant group with four venues, online ordering, events and gift cards.

Start with what a visitor needs to decide. Do they need to choose between services? Check whether you work in their city? Compare project types? Understand a sensitive process before calling? Reserve a table, request a bid or buy a product?

Each materially different decision may deserve a page. Minor variations usually do not. “Residential window cleaning” and “commercial high-rise window cleaning” involve different buyers, proof, safety questions and conversion paths; separate pages can clarify both. Three finishes of the same cabinet door probably belong on one product or service page.

This is also the sounder SEO model. Google recommends organizing a site logically, publishing helpful and original content, and linking relevant pages so people and crawlers can understand and discover them (Google SEO Starter Guide). It does not prescribe a minimum page count.

The core pages and what each must accomplish

Home

The home page should quickly answer: What do you do? Who is it for? Where do you work? Why should someone trust you? What should they do next? It is an orientation page, not a compressed version of every other page.

Services or products

A small operation can begin with one services page. It should make the offer concrete: problems solved, what is included, who it suits, how the work happens, proof, common questions and the next step. Split it only when individual services need meaningfully different explanations or target different searches.

About

An About page should reduce the risk of hiring you. Relevant experience, people, operating principles, credentials and an honest company story matter more than a long mission statement. For a personal practice, this may be a section on the home page. For a firm where individual professionals influence the choice, each person may need a profile.

Work, case studies or reviews

Proof deserves a clear home when buyers need to see outcomes, taste or workmanship. A gallery may be enough for a nail studio; a custom builder may need a page per project; a consultant may need short case studies that explain the problem, work and result. Do not invent numbers you cannot support.

CMT’s own work shows how different shapes follow different jobs: a one-page lawn-service site routes seven services toward a call; a four-screen restaurant site separates its menu, story and private dining; and a legal site uses dedicated practice and FAQ content to answer anxious questions before contact.

Contact or the primary conversion page

Give visitors the practical details and a next step: phone, email, location or service area, hours, form, booking or quote request. Ask only for information needed to respond. If “request a bid” has a different workflow from a general enquiry, it can justify its own page.

FAQs and support

Put short objections on the page where they arise. Create a separate FAQ or help library when the questions are numerous, recurring or useful across several services. A searchable support center is appropriate for software; it is usually excessive for a five-page brochure site.

Policy and legal pages

Privacy, cookie, terms, returns, shipping, accessibility, professional disclaimers and licensing notices are not decorative extras. Which ones you need depends on what the site collects or sells, your industry and the jurisdictions you serve. Treat that as a legal and operational question, not an SEO checkbox, and have the relevant professional confirm the requirements.

Three sample small-business sitemaps

These are starting points. The names should change to match the language customers use.

Solo professional with one clear offer

Home
- Services
- About
- Contact
Privacy policy

This could also be one page with anchored sections plus a separate privacy policy. Add a Work page only when examples materially help the sale.

Local contractor with distinct services

Home
Services
- Kitchen remodeling
- Bathroom remodeling
- Home additions
Projects
- Selected project pages
Process
Service area
About
Request an estimate
Privacy policy

Project pages can grow as real work becomes available. The three service pages earn their place because the scope, questions, imagery and buying intent differ.

Multi-location professional business

Home
Services
- Service A
- Service B
- Service C
Locations
- Downtown
- Northside
- Lakeside
Professionals
- Individual profiles
Resources
- Guides and FAQs
About
Contact
Privacy, terms and required notices

Each location page should contain facts that help someone use that location: address, hours, contact details, directions, accessibility information, staff, services available there and location-specific proof.

When does a service deserve its own page?

Create a service page when most of these are true:

Customers ask for it by name.
It solves a distinct problem or serves a distinct audience.
Its process, pricing factors, proof or FAQs differ.
Someone searching for it would be disappointed by a generic services page.
You can write a complete, accurate page without padding.

Keep related services together when the distinctions are internal jargon, the content would repeat almost word for word, or none has enough substance to help a buyer. If one services page is already clear and converting, more URLs are not automatically an improvement.

For businesses that need organic search to generate leads, structure matters. One general page cannot always be the best answer for several unrelated needs. The practical checklist in why your website is not showing up on Google explains why a distinct service may need a page worth ranking, while still rejecting empty keyword pages.

When does a location deserve its own page?

A staffed office, store, clinic or restaurant normally deserves a page because customers need unique hours, directions, contact details, services and local context. A service-area page may also be useful when it explains where crews travel, scheduling limits, travel fees or local examples.

Do not manufacture 75 city pages by swapping place names in the same copy. Google classifies substantially similar city or regional pages that merely funnel visitors onward as doorway abuse (Google’s spam policies). If you cannot make a location page specific and useful, use one honest service-area page instead.

When is a blog useful?

A blog is useful when customers repeatedly research questions before buying and you can publish durable answers. It can support complex services, demonstrate judgment and give service pages relevant internal links. “How long does ceramic coating last?” has a job. “Company picnic recap” probably does not, unless culture is central to recruitment.

Do not add a blog because a website checklist says every business needs one. An empty “Coming soon” page and three abandoned posts make the business look unattended. Start with the questions sales calls, estimates and support conversations already reveal. If ongoing content is part of the plan, a content-driven site may need templates for services, locations, people and articles; that is a structural requirement, not just extra pages.

One page or several?

A one-page website is a fair choice when the business has one audience, one main offer, one location or compact service area, a short trust case and one conversion action. It can be fast to understand and easier to maintain. Use clear headings, in-page navigation where helpful, and a call to action that remains easy to find.

Choose several pages when visitors arrive with different goals, services need independent explanations, locations have distinct facts, proof needs room, or search is an important acquisition channel. Separate pages also give people direct URLs to share and let you measure which topics lead to enquiries.

Page count alone does not make either option accessible. W3C guidance emphasizes well-structured content, logical headings and marked-up page regions (Page Structure Tutorial). Across a multi-page site, repeated navigation should remain in a consistent relative order, and users should have more than one practical way to locate pages when the site grows (Consistent Navigation; Multiple Ways). For a very small site, links from the home page may already provide a useful overview.

The test is simple: does separating this content make the customer’s path clearer? If yes, use another page. If it merely makes the sitemap look larger, do not.

The risks at both extremes

Forcing everything onto one page can bury important answers, produce an unwieldy mobile scroll, make navigation vague and ask one URL to serve unrelated search intents. A visitor who wants commercial services should not have to pass residential testimonials, the company history and six other offers to reach relevant details.

Inflating the sitemap creates the opposite problem. Thin service pages weaken trust. Cloned location pages are hard to maintain. Repeated copy makes it unclear which URL is authoritative. Every page also creates an obligation: accurate content, working links, accessibility checks, analytics, updates and redirect planning if it later disappears.

Website scope and cost therefore rise with content, integrations, migration and functionality—not with a magic page threshold. CMT’s services process starts with the business, then defines the sitemap and content model before layout.

Pages you probably do not need yet

A separate page for every minor variation of one service.
A thin page for every suburb you are willing to drive to.
A blog with no owner, editorial plan or customer questions to answer.
Individual testimonial and FAQ pages when a relevant section would be clearer.
Careers, press or investor pages when there is nothing current to publish.
A portal, dashboard or account area when email and a form already handle the workflow.
Legal boilerplate copied from another business without checking whether it fits yours.

“Not yet” is deliberate. A good structure can grow. Start with the smallest site that answers the real questions well, then add pages when the business gains a service, location, audience, body of proof or repeatable content need.

A five-question worksheet to estimate your scope

How many distinct services, product categories or practice areas do customers request by name? Count only those you can explain with unique problems, process, proof and FAQs.
How many physical locations need their own hours, directions, staff or service details? Add one useful page per genuine location; use one service-area page for geography that does not justify separate content.
How many audiences follow different paths? Homeowners and general contractors, patients and referring clinicians, or diners and private-event planners may need separate routes.
What proof and decisions must happen before contact or purchase? Add the pages needed for projects, menus, pricing context, team profiles, booking, shipping, returns or support.
Which pages can you keep accurate for the next year? Remove speculative pages nobody owns. Keep policy pages, service details, hours and calls to action on a review schedule.

Your first estimate is the total of those justified pages, plus a home page, contact path and applicable policy pages. Then combine anything that would repeat. The result is your planning sitemap—not a quota.

If you want a second set of eyes, send CMT Web the draft sitemap. You will get a scoped recommendation, including when a smaller site is the honest answer.