SITE ARCHITECTURE / SMALL BUSINESS
How Many Pages Does a Small Business Website Actually Need?
There is no magic five-page or ten-page answer. Your website needs enough pages to explain distinct services, prove the right things, answer important buying questions and give search engines a clear structure — without creating thin pages just to make the sitemap look bigger.
THE SHORT ANSWER
Most small businesses need more than a brochure, but fewer pages than a keyword list would suggest.
A focused business may launch with five to seven core pages. A service-led company often needs eight to fifteen once distinct services, proof and FAQs are separated properly. Businesses with many services, locations, industries or resources may need considerably more. The right number follows the decisions customers make.
Page count is the result of planning, not the starting brief.
If a proposal begins with “you need ten pages” before anyone understands your services, customers or search demand, the number is mostly arbitrary. A website with six carefully planned pages can outperform a twenty-page site full of repeated copy. The reverse is also true: forcing ten genuinely different services onto one page can make the site harder to use and harder to rank.
A useful sitemap starts by mapping what a customer needs to understand before they contact you. It then separates the topics that deserve their own search, proof and conversion path. Navigation comes afterwards.
This guide gives you a practical way to decide which pages belong in the first launch, which pages should be separate, which pages can stay combined and when location or blog content is genuinely justified.
01 / THE CORE FOUNDATION
These are the pages most small business websites need to cover the basic buying journey
The exact labels can change, but the customer still needs orientation, proof, detail and a clear next step.
Home
Summarise who you help, what you do, why the visitor should trust you and which service or next action matters most.
Orient the visitorServices
Give customers a clear way to discover your offers. If the services are materially different, use the hub to lead into dedicated service pages.
Explain the offerAbout
Answer the trust questions that service pages should not carry alone: who is behind the work, how you operate and what kind of client relationship to expect.
Reduce provider riskProof
Portfolio, case studies, reviews or project examples show that the claims on the service pages have evidence behind them.
Make credibility visibleFAQ
Resolve recurring objections around cost, timing, ownership, process, support and the practical details that often block an enquiry.
Remove hesitationContact
Give the visitor one low-friction path to call, message, submit a project brief or request a quote without hunting through the site.
Convert interest03 / WHEN A SERVICE DESERVES ITS OWN PAGE
Separate a service when the customer needs a different answer, proof or conversion path
You do not need one page for every phrase in a keyword tool. You do need separate pages when the commercial intent changes.
The problem is different
If the customer arrives with a distinct problem, the page should speak directly to that problem rather than making them extract the answer from a broad services list.
The decision criteria are different
A WooCommerce buyer evaluates payments, products, shipping and store operations. A redesign buyer worries about migration, SEO preservation and improving an existing site. Those are different buying journeys.
The proof is different
A dedicated page earns its place when it can show relevant projects, outcomes, FAQs or expertise that would be diluted on a general page.
The search intent is different
If people search for the service as its own solution and expect a focused answer, a dedicated URL can support that intent more clearly than a single paragraph inside another page.
The next action is different
Some services need a quote, some need a consultation, some need an audit and some need a booking. Separate pages let the conversion path match the decision.
04 / WHEN TO KEEP CONTENT TOGETHER
Not every variation deserves another URL
More pages only help when the new page contains enough unique value to justify the click and the indexation.
Minor service variations
If two services use the same process, proof, objections and outcome, keep them together and explain the variation inside one strong page.
Avoid artificial separationKeyword synonyms
You do not need separate pages for every wording of the same intent. One authoritative page can naturally answer multiple closely related searches.
One topic, one destinationTiny location differences
A suburb name by itself is not enough reason for a new page. Location pages need genuine service-area context, local proof or a meaningfully different market need.
No doorway pagesThin industry pages
An industry page should contain workflows, objections, integrations and proof specific to that industry. If all you can change is the industry name, keep the content on a stronger central page.
Unique value first05 / A PRACTICAL SMALL-BUSINESS SITEMAP
A service-led website often grows from six core pages into a useful 10–15 page structure
This is what that growth usually looks like when the pages have distinct jobs.
Home
The commercial overview: positioning, main services, proof and the primary route into the website.
Services hub
A clear overview of all service categories with links to the dedicated services that deserve deeper treatment.
3–6 service pages
Separate pages for the offers customers evaluate differently, each with its own proof, FAQs and conversion path.
About
Provider trust, specialisation, team, process expectations and why the business is a credible fit.
Portfolio or case studies
Project evidence that can support the claims made on service and industry pages.
Reviews
A dedicated reputation layer when you have enough genuine client feedback to help buyers validate the provider.
FAQ
Central answers to repeated commercial objections, with shorter contextual FAQs still used on relevant service pages.
Contact
The conversion destination with enough project detail to route and respond to the enquiry properly.
06 / LOCATION PAGES
How many location pages should a local Perth business create?
Only create a location page when the market deserves its own useful answer.
A plumber serving twenty suburbs does not automatically need twenty indexed pages. If the service, proof and local context are identical, mass-producing suburb swaps creates a large sitemap without creating a better website.
A location page becomes useful when it can explain real coverage, nearby areas, local projects, local market needs, travel or service conditions, relevant services and proof that matters to customers in that area. It should also link back to the strongest service pages instead of competing with them.
For a Perth-wide business, a smaller set of high-value location pages can be stronger than hundreds of thin suburb URLs. Joondalup, Fremantle, Subiaco, Osborne Park, Wanneroo, Midland, Cannington and Rockingham may each justify unique treatment when the business genuinely serves those markets and has something useful to say about them.
- Publish locations that have real commercial relevance
- Use nearby suburbs as service-area context rather than automatic new URLs
- Add local proof where it genuinely exists
- Connect location pages to the service the visitor actually needs
- Do not duplicate the same copy with only the suburb name changed
07 / BLOG AND RESOURCE CONTENT
Blog pages are not filler pages — each one should help a customer make a decision or solve a real problem
A useful resource library can grow far beyond the main sitemap without making the navigation complicated.
Pricing questions
Articles can explain cost drivers, quote comparisons and what sits inside a service price without turning a service page into a 4,000-word guide.
Commercial researchPlatform comparisons
Guides such as WordPress versus Wix or WooCommerce versus Shopify help visitors understand a decision before they are ready to request a quote.
Provider evaluationTechnical problems
Speed, security, maintenance and migration guides capture problem-solving intent and support the expertise behind the related service pages.
Problem awarenessIndustry questions
A detailed guide can address the workflow, trust signals and conversion requirements of an industry without creating a thin landing page for every niche.
Topical depth08 / PERTH WEBSITE CONTEXT
The right page count changes with the business model, not the Perth postcode
A local site should become deeper only when the customer journey becomes deeper.
A Subiaco professional firm may need separate expertise pages, people profiles and case studies. An Osborne Park B2B supplier may need product or capability pages. A Fremantle hospitality business may need menus, events and bookings. A Cannington retailer may need categories, products and ecommerce support.
Those differences change page count because the content and buying journey change. They are not reasons to charge more simply because the business sits in a particular suburb.
Perth CBDSubiacoFremantleJoondalupOsborne ParkWannerooMidlandCanningtonRockingham
09 / BUILD THE SITEMAP IN THE RIGHT ORDER
Plan the pages from customer decisions first, then turn them into navigation
This keeps the site focused while still leaving room for SEO, proof and future growth.
List the offers customers can buy
Separate genuine services from minor variations so you can see where the commercial decisions actually differ.
Map the questions behind each offer
Note the problems, objections, proof, pricing questions and next actions that a buyer needs before contacting you.
Check search intent
Look for topics that deserve their own landing page because people search for them as distinct solutions rather than as wording variations.
Add trust and support pages
About, reviews, portfolio, FAQ and contact pages complete the decision journey without forcing every service page to repeat the same company information.
Add locations only where useful
Publish local pages for markets with real relevance, unique context and genuine service coverage.
Keep future content outside the launch bottleneck
A blog or resource library can grow after launch. The initial site only needs the articles that materially support important services and buyer questions.
10 / PAGE COUNT AND PRICE
Does a website cost more every time you add a page?
Sometimes — but the relationship is not one page equals one fixed amount.
SCOPE, NOT SIMPLE MULTIPLICATIONA repeatable content page takes less work than a new page type with unique research, design, copy, functionality and integrations.
Adding a straightforward service page inside an established design system may be efficient. Adding the first case-study template, a booking flow, a location architecture or a custom comparison tool changes the scope much more. Good pricing reflects the work required to create and implement the page, not simply the number beside it in the sitemap.
SMALL BUSINESS WEBSITE PAGE-COUNT FAQS
Questions to answer before you lock the sitemap
The right number of pages becomes clearer when you know which topics deserve their own destination and which ones belong together.
06 QUESTIONS
Clear answers to the decisions that usually affect cost, scope and ownership.
ANSWER
It can be. If you have one main offer, a small number of closely related services and a simple enquiry path, five to seven well-built pages may cover the job. It becomes too small when important services, proof or search intents are forced together only to preserve the package size.
ANSWER
Only when the service creates a distinct customer decision. If the problem, proof, process, FAQs and next action are materially different, a dedicated page usually makes sense. If two services are minor variations of the same offer, one stronger page is often better.
ANSWER
No. Create location pages for markets that have genuine commercial value and enough unique context to justify the page. Nearby suburbs can often be mentioned as service coverage without becoming separate URLs. Thin suburb pages add volume to the sitemap without adding much value to the customer.
ANSWER
Technically they are pages on the site, but they should not be treated like extra brochure pages in the main navigation. A resource library can grow to dozens or hundreds of useful articles while the core commercial sitemap remains concise.
ANSWER
No. More useful pages can expand the number of problems and searches your site can answer, but thin or repetitive pages do not create authority by themselves. Search growth comes from relevant content, strong architecture, internal links, technical quality, proof and authority — not from hitting a page-count target.
ANSWER
Yes, as long as the launch version still explains the core offer properly. We often separate must-have commercial pages from future resources, additional locations or secondary services. The important part is planning the architecture early so new pages can be added without forcing a complete navigation or URL restructure.
NOT SURE WHAT BELONGS IN YOUR SITEMAP?
Tell us what you sell, who buys it and where the website needs to generate enquiries — we will map the pages around those decisions.
A second local perspective can be useful when you are deciding how much website you actually need. Creative Agency X provides another Perth-focused reference for comparing structure, design direction and the level of build behind a business website.