How Many Pages Does a Small Business Website Actually Need?

"How many pages should our website have?" comes up early in almost every website project, usually because the client assumes more pages means more professional, or more SEO value. Neither is automatically true. This guide explains what actually decides the right number, how search engines treat pages, typical counts by type of business, what each core page needs, which pages you can skip, and how to scope the first version without guessing.

The short answer: enough pages to cover what you actually offer, no more

A small business site needs a home page, an about or company page, at least one services or products page, and a contact page — that's the floor, and it's often enough on its own for a simple, single-service business. Past that floor, each additional page should exist because a specific service, audience or piece of content genuinely needs its own space, not because round numbers like "ten pages" feel more substantial.

How visitors and search engines treat a page

To a visitor, a page is an answer to one question: what do you do, who are you, how much, how do I reach you. To a search engine, a page is an entry point: each one can rank for the searches it is about, and a page about one clear topic ranks far better than a page about six. That is the whole logic behind page count. You add a page when there is a distinct question or search it should answer, and you fold content into an existing page when it would otherwise be a thin paragraph with a heading. A site with eight focused pages outperforms one with twenty vague ones, and both outperform a single long home page that tries to do everything.

What decides the number for your business

• How many distinct services or product lines you offer. A business with one core service can often explain it fully on a single services page. A business with five distinct offerings, each with different pricing or process, usually needs five separate pages so each one can rank and convert on its own.
• Whether a page would have enough real content. A page with two sentences and a stock photo doesn't help visitors or search engines — it's better folded into a stronger page than left thin.
• Whether customers ask distinct questions about each offering. If enquiries about Service A and Service B are genuinely different conversations, separate pages let each one address its specific questions.
• How many locations and languages you serve. Each real branch and each language version multiplies the count, which matters for scoping and budget.

Typical page counts by type of business

These are starting points drawn from how small business sites in each category tend to be used, not rules. The right number for you comes from the list of services, locations and questions, not from the category.

What each core page needs to do

Our guides to writing a homepage that converts and whether you need a blog or just good service pages cover the two pages that cause the most debate.

Pages you probably do not need

• A "welcome" or splash page before the home page. It only adds a click.
• Separate mission, vision and values pages. One paragraph on the about page says the same thing.
• A news page with no news. An empty or year-old news page signals neglect; leave it out until there is a plan.
• A gallery with three photos. Put them on the relevant service page instead.
• One page per suburb with the same text and a swapped place name. Search engines treat these as duplicates and visitors see through them; one areas-served page with real detail does better.
• A separate page for every minor variation of a service. If two offerings share a process and a customer, one page explains both.

Does more pages help SEO?

Only conditionally. A page helps SEO when it targets a genuinely different search term with enough unique, useful content to earn its own ranking — a dedicated page for one service can outrank a generic services page for searches specific to that service. A thin page created purely to increase the page count usually ranks worse than folding that same content into a stronger existing page, and can dilute the site's overall quality signal. Internal links matter here too: a service page that links to the related pages a visitor might need next (areas served, pricing, a relevant case study) spreads authority through the site in a way that an isolated page sitting with no inbound links from anywhere else does not.

Should every service get its own page?

If a service has its own pricing, process, or a distinct target customer, a dedicated page usually helps — someone searching for that specific service lands somewhere directly relevant, rather than scrolling a long combined page. If two services are close variations of the same offering, one shared page that explains both is usually stronger than splitting thinly across two.

Locations and languages multiply the count

A business with three real branches needs a page for each, with that branch's address, hours, phone number and map, because people search for the branch nearest them and because each one can have its own Google Business Profile pointing to it. A business serving a wide area from one office needs one areas-served page, not one page per town. Languages work the same way: a Bahasa Malaysia or Chinese version of the site is a second copy of each page you translate, so a ten-page site in three languages is thirty pages to write and maintain. Translate the pages that matter to the customers who need them, usually home, the main services and contact, rather than everything at once.

A worked example

Take an aircon company in the Klang Valley offering installation, servicing, repair and chemical cleaning, with one office and customers across the valley. Installation and repair are different conversations with different prices, so each gets a page. Servicing and chemical cleaning are closely related and often bought together, so one page covers both. That gives home, about, three service pages, an areas-served page listing the districts covered, a gallery of real installations, and contact: eight pages. Add a short FAQ if the same questions come up on every call, and a blog only if someone will write the "how often should I service my aircon" posts customers search for. Ten pages at most, each with a reason to exist.

A second worked example: a business with more than one branch

Now take a tuition centre with two physical branches, offering primary, secondary and SPM-level classes. Each branch needs its own page with its address, hours, and the classes actually taught there, because a parent searching for tuition near a specific area wants that branch's details, not a shared page that forces them to scroll past the other one. Each level of class — primary, secondary, SPM — has a different syllabus, fee and target parent, so each gets its own page rather than one long page covering all three. That already totals home, about, two branch pages, three class-level pages, fees, enrolment and contact: ten pages, before any FAQ or blog. The lesson is the same as the aircon example: count the real distinctions first — branches, levels, services — and let the page total follow from that, rather than picking a number and trying to fill it.

Can you start small and add pages later?

Yes, and it's often the more sensible approach than guessing at full scope upfront. Launch with the pages you can confidently fill with real, specific content, then add a page when a new service, location or genuine content need appears — see our guide on what to prepare before a website project starts for how to scope the first version realistically.

Common mistakes

• Choosing a page count before listing the services. The list comes first; the number falls out of it.
• One services page for everything. It ranks for nothing in particular and makes every visitor scroll.
• Padding to reach a package tier. Thin pages cost money to build and help nobody.
• Duplicate location pages. Copied text with a swapped town name is a known search-quality problem.
• Launching with a blog and no plan. An abandoned blog hurts more than none.
• Forgetting that each language multiplies the work. Scope translations page by page.
• Never revisiting the structure. A new service deserves a new page; a discontinued one should lose its page.

Where Gotka Technologies fits

Gotka's web design packages are built around page count for exactly this reason: Starter covers up to 5 pages from RM5,300, Business up to 10 pages from RM9,800, and Growth up to 20 pages from RM14,300, with additional individual pages at RM900 each if you need to go beyond a tier later, and Bahasa Malaysia or Chinese versions at RM400 per page. During scoping, Gotka helps map out which pages your specific business actually needs before quoting, rather than defaulting to a round number.

Key terms used in this guide

• Core pages: the home, about, service and contact pages every business site needs.
• Service page: a page dedicated to one offering, with its own description, pricing and proof.
• Thin page: a page with too little unique content to be useful to a visitor or to rank.
• Areas-served page: a single page listing the towns or districts a business covers from one location.
• Location page: a page for one real branch, with its own address, hours and map.
• Duplicate content: near-identical text on several pages, which search engines discount.
• Scope: the agreed list of pages and features a website project will include.
• Package tier: a web design package defined by a maximum page count.