How Many Pages Does a Business Website Actually Need?

Count decisions, not menu items

A website needs enough pages to give important questions a focused answer. It does not need a separate page for every keyword variation, internal department, or paragraph somebody wants approved.

The right number follows from the business model, audiences, offers, evidence, locations, languages, and publishing programme. Page count is an output of information architecture—not a target chosen before it.

Useful planning ranges

These ranges are orientation, not standards:

A ten-page site can be bloated. A thousand-page site can be coherent. The test is whether each indexable page has a distinct job and enough value to perform it.

The minimum useful business site

A simple service business often begins with:

1. Home: position the business, route priority audiences, show evidence.
2. Offer page or pages: explain what is provided, for whom, and how it works.
3. Evidence: case studies, work, results, credentials, or process proof.
4. About: establish relevant experience, principles, and people.
5. Contact or conversion page: set expectations and make the next step clear.
6. Required policies: privacy, cookies, terms, accessibility statement where appropriate.

If three services answer different buyer questions, they probably deserve separate pages. If they are minor parts of one coherent engagement, one strong service page may be clearer.

When a topic deserves its own page

Create a separate page when at least one of these is true:

It serves a distinct intent

“Brand identity” and “design system” may be related capabilities, but a buyer evaluates them for different reasons. Each needs different explanation and evidence.

It supports a distinct decision

A pricing page, implementation guide, security page, or comparison may answer a question that blocks purchase even when it is not a primary service.

It has unique evidence

A case study, research report, location, or product family may contain enough original information to stand alone.

It needs an independent destination

Campaigns, sales teams, partners, search results, or internal links may need a stable URL that opens directly at the relevant answer.

It has a different owner or lifecycle

Structured content such as people, locations, releases, reports, and documentation often needs separate records even when the visual presentation feels connected.

When pages should be combined

Combine pages when they:

• answer the same question with slightly different wording;
• contain only a paragraph of unique value;
• compete for the same search intent;
• exist solely because of internal company structure;
• repeat the same proof and call to action;
• cannot be maintained independently;
• would be more useful as sections of one complete resource.

Two thin pages do not become authoritative because each has a focused title. They often divide links, evidence, and attention.

Troiana's article on the case against chasing every keyword explains why search demand should not be translated into one URL per phrase.

Unique pages versus page templates

Budget conversations often confuse URL count with design scope.

A site may contain 200 case studies using one case-study template. Designing and building that system is not the same as designing 200 unique pages. Conversely, a seven-page campaign site may contain seven bespoke compositions.

Ask two separate questions:

• How many content records or URLs must exist, migrate, and be maintained?
• How many unique templates and component patterns must be designed, built, and tested?

The first affects content and migration effort. The second affects design and development effort.

Build the sitemap from a content matrix

Create a table with these columns:

Then review:

1. Pages with no clear audience or task are candidates for removal.
2. Pages sharing the same intent are candidates for consolidation.
3. Important tasks with no destination reveal gaps.
4. Pages without owners will decay after launch.
5. Pages with no unique evidence may need stronger content before they deserve a URL.

This turns the sitemap from a drawing of boxes into a set of editorial commitments.

Do not hide everything on the homepage

One-page websites can work for a temporary campaign, a single event, or a very narrow offer. They become fragile when visitors need to:

• compare multiple services;
• share a specific answer;
• evaluate detailed evidence;
• enter through search on a narrow question;
• navigate a long page with accessibility and orientation needs;
• return to changing resources.

A concise homepage should route people. It does not need to contain the full site to prove the business is simple.

Do not manufacture pages for SEO

Pages aimed at near-identical phrases—“web design”, “website design”, “professional web design service”—usually compete rather than build depth.

Map one primary intent to one best page. Related questions can become sections, supporting articles, examples, or FAQs when they add real information.

Before creating a new page, search the existing site and ask whether an established URL should be improved instead. Internal competition is easier to create than authority.

Plan for what the team can maintain

Every page creates an obligation: facts, links, screenshots, people, prices, product details, and claims can become wrong.

Record an owner and review trigger for important content. Event-driven review—after a product change, policy update, rebrand, or team departure—is often more useful than an arbitrary annual refresh.

If the organisation cannot maintain 40 location pages, one accurate location directory is better than 40 abandoned promises.

Common questions