Skip to content
SITE STRUCTURE23 / 50

How many pages should your business website have?

Website page count follows the sitemap. Give distinct services, buyer questions, proof, and genuine location needs a clear home, then count the pages rather than starting from an arbitrary package size.


Insights
A central website sitemap branching into distinct services, audiences, and proof pages.
Editorial visual / 23

Forget the number

Business owners often ask for a five page website, ten page website, or twenty page website before anyone maps what the site needs to explain.

Page count feels concrete.

The number also affects price and timeline.

The problem is simple.

A fixed number does not tell you whether the website covers the right buyer questions.

One business sells one focused service to one audience.

Another sells six services across four locations with separate buying journeys.

Both businesses do not need the same sitemap.

There is no Google rule requiring a certain number of pages.

The useful question is different.

Which topics deserve their own page because a visitor arrives with a distinct question, search intent, or decision?

Page count is a result of the sitemap, not the starting point.

Build the core

Most business websites need a clear home for a few basic jobs.

The homepage explains the business and routes visitors.

Service or product pages explain what the business sells.

Proof pages show relevant work, case studies, reviews, or customer evidence.

The About page adds context around the people, company, experience, or operating model.

The Contact page makes the next step clear.

Legal pages support privacy, terms, and required disclosures.

From there, the structure depends on the business.

A company with one service might need one focused service page.

A company with five distinct services often benefits from separate pages for the services buyers search, compare, and purchase differently.

A multi location business needs location pages only where real local information exists.

A SaaS company often needs feature, use case, pricing, proof, demo, resource, and support paths beyond the basic company pages.

A content section belongs in the sitemap when a real publishing plan exists.

Add pages with a reason

A new page earns a place when the page has a clear job.

The page answers a distinct search intent.

The page supports a different buyer decision.

The page needs different proof.

The page speaks to a different audience or location with enough unique detail.

The page supports a campaign or sales path.

The page holds a repeatable content type such as case studies or resources.

A page does not earn a place because a competitor has one.

A page does not earn a place because the navigation looks empty.

A page does not earn a place because a keyword tool produced another phrase.

Google's people first guidance asks publishers to create useful, original content for a real audience rather than producing many pages mainly for search traffic.

The same principle protects the sitemap.

Ten strong pages with clear intent are more useful than thirty thin pages repeating the same message.

The reverse also matters.

Trying to force ten distinct services onto one generic Services page creates another problem. Visitors need to scan a large page for the one service they care about. Search intent also becomes harder to map cleanly.

Start with buyer questions.

Group questions which belong together.

Split topics when the decision changes.

Then count the pages.

The number should appear at the end of planning, not at the beginning.

Discuss a Project