How many pages does a business website need?

A common question: how many pages does a business website need? Short answer: enough, but not too many. The real goal is clear structure. You want visitors to reach the information that leads to conversion quickly. That can be achieved with 5 pages or with 50. It depends on your business.

This guide is practical. I show examples per business type, sample sitemaps, and a checklist to decide how many pages you need. Along the way I touch on SEO, mobile and performance. Useful references: the SEO Starter Guide and Google Search Essentials.

Why one-size-fits-all doesn't work

Pages are tools. Each page should have a purpose: inform, persuade, or transact. A local hairdresser needs different pages than a SaaS vendor with extensive docs.

Factors that determine page count:

• Search intent: landing pages for key queries help traffic and conversion. See the guidance in the SEO Starter Guide.
• Product complexity: many SKUs or configurations usually need separate product pages.
• Support and documentation: technical products often require a knowledge base.
• Local presence: multiple locations need separate location pages.

Note: more pages don't automatically improve SEO. Thin or overlapping content can hurt. Often consolidation wins.

Practical page structures by business type

Examples below include indicative ranges. These are guidelines; every project is different.

Indicative engineering cost for a unique page template (design + implementation): €150–€1.500 per template. This varies a lot by CMS and features (indicative, per project different).

Sitemap examples

Small B2B example:

• /
• /services/
• /services/consulting/ (one per service)
• /case/client-name/
• /about/
• /team/
• /blog/ (with categories)
• /contact/

Small webshop with ~50 SKUs:

• /
• /category/ (5–10 categories)
• /product/sku-name/ (one per product)
• /account/
• /checkout/
• /faq/
• /legal/ (privacy, shipping, returns)

How to choose which pages you actually need (checklist)

• Define primary goals: leads, sales, support.
• Map search intent and assign pages to intents.
• Group content that competes for the same keywords.
• Decide which pages are dynamic templates vs static.
• Prioritize pages by expected impact: traffic, conversion, cost.
• Plan templates: how many unique designs and features are required?
• Add analytics and Search Console from day one and measure behavior.

SEO, performance and mobile — practical notes

A clear structure helps both users and search engines. Use logical URLs and internal linking. The Google Search Essentials docs are a good checklist for crawlability.

Mobile rendering is essential. Google uses mobile-first indexing; test responsive behavior and rendering on actual devices. Use guidance from responsive design best practices such as Responsive design — MDN. Complex desktop-only interfaces require extra design work.

Keep pages fast. Core Web Vitals affect user experience and search performance. Load only what you need and consider caching and a CDN for many product pages.

A caveat: sometimes a single comprehensive page is better than several thin pages. Look at engagement metrics; users often skim content, so structure pages into clear blocks and use direct CTAs. Nielsen Norman Group has useful research on how long users stay on pages (short attention spans), see their analysis at How Long Do Users Stay on Web Pages?.

Technical choices that affect page volume

• CMS and templates: pick a CMS that supports dynamic lists and templating. For many products, one flexible template is cheaper than hundreds of handcrafted pages.
• Taxonomy: clear categories and tags prevent duplicate content issues.
• Documentation: use a knowledge base with categories rather than dozens of tiny pages.

Measure, iterate, refine

Start with a minimal, focused set of pages and expand in phases. Use Analytics and Search Console to monitor which pages attract traffic and convert. Publish the 8–12 pages with highest expected impact first. Then add categories or product pages step-by-step and measure.

When to bring in help?

If your site needs more than ~50 unique templates or your catalog exceeds ~200 SKUs, get a technical design and hosting plan from an experienced team. A senior-led agency can help with architecture, performance and maintenance. If you want help building the structure or a price estimate, see our website development offerings or explore our services.

Closing checklist

• Define goals and priorities
• Draft an initial sitemap of ~8–12 pages
• Identify templates vs static pages
• Optimize for mobile and speed
• Hook up analytics and Search Console
• Scale iteratively and measure results

Want a short inventory or a practical plan? Request an estimate at /quote.