webshunya icon logo

Found

How Many Service Pages Does Your Website Actually Need?

Decide which services need separate pages and which belong together, without creating repetitive content.

Milan Gohil

·

10 min read

A single central paper website card branches into three distinct service cards carrying only simple object icons: a gear, a pencil and a wrench.
A single central paper website card branches into three distinct service cards carrying only simple object icons: a gear, a pencil and a wrench.

OVERVIEW

Here is a short version of what I write

There is no fixed number of service pages a business needs. Create a separate page when a service serves a distinct customer problem and needs its own explanation, evidence or buying journey.

  • Group services that answer essentially the same need.

  • Separate services when the audience, questions or proof differ.

  • Make every page useful on its own and easy to find.

There is no useful number like:

“A small business needs 8 service pages.”

A company offering bookkeeping, payroll and tax advisory has a different website problem from an industrial manufacturer offering 30 different engineering services. The better question is: Which services genuinely need their own page, and which ones are better explained together? A service usually deserves its own page when the person looking for it has a different problem, needs different information, expects different proof or goes through a different buying decision.

If two “services” are only different names for essentially the same thing, creating another page may add more content without adding more value. Google does not prescribe a target number of service pages. Its current guidance instead emphasizes useful, people-first content and warns against creating substantially similar pages primarily to capture similar searches. (Google Search spam policies; Google people-first content guidance)

Want the quick answer? Let AI map your services first

If your AI tool can access your website, paste this:

I am deciding how many individual service pages this website should have:

WEBSITE:
[PASTE WEBSITE URL]

Review the business, existing services, navigation and service-related pages.

Do NOT assume every named service needs its own page.

For every service or sub-service you find, evaluate:

1. What customer problem does it solve?
2. Who is the likely buyer?
3. Does someone specifically look for this service?
4. Does it require substantially different information from the parent service?
5. Does it have a different process, deliverable, pricing consideration or buying decision?
6. Would it require different examples, case studies, proof or FAQs?
7. Could another existing page fully satisfy someone looking for this service?
8. Does it substantially overlap another service page?

Classify each service as:

SEPARATE PAGE
The service has a distinct enough intent and information need.

KEEP UNDER PARENT SERVICE
Useful service, but does not currently justify a complete separate page.

MERGE
Two or more existing pages appear to satisfy essentially the same intent.

NEEDS MORE RESEARCH
Public website information is not enough to decide.

Then propose a simple service-page hierarchy.

Clearly separate:
- what you observed
- what you inferred
- what would require keyword/search data or customer research to confirm

Do not invent search volume or SEO performance.
Do not create separate pages simply for keyword variations.

Use the answer to create your first service map. Then run the decisions through the checks below.

The easiest test: would the customer need a different page?

Imagine an HVAC company provides: Air-conditioning installation and Air-conditioning repair. Technically, both are about air conditioning. But the person looking for installation is probably asking:

What system should I buy?

What does installation involve?

How much capacity do I need?

Which brands do you install?

Someone needing repair has a completely different situation:

My system isn't cooling.

Can someone come today?

What faults do you repair?

Is my system worth fixing?

Those are different problems, different decisions and different information. Separate pages make sense. Now compare: Emergency AC repair and 24-hour AC repair. If the company is describing exactly the same service to exactly the same person with exactly the same process, two pages may simply be duplicating the same answer.


Left-to-right service-page planning: check the customer need, required information, and whether a parent page can explain the service clearly before considering a separate page.

This is not an algorithm. It is a way to stop page planning from becoming:

“We have 14 things in our service list, so we need 14 pages.”

Test 1: Is the problem different?

Start with the customer situation. An accounting firm might offer:

Service

Customer situation

Bookkeeping

We need our financial records managed every month.

Payroll

We need employees paid correctly and on time.

VAT returns

We need to file and manage VAT correctly.

Management accounts

We need better financial information for decisions.

These services are related. But the reason someone needs each one is different. That gives you a strong reason to investigate separate pages. Compare that with an accountant listing:

  • Monthly Bookkeeping

  • Professional Bookkeeping

  • Business Bookkeeping

  • Small Business Bookkeeping

Those labels alone do not prove four different pages are needed. The question is whether they represent four genuinely different customer needs.

Test 2: Does the service need different information?

A separate page should give you room to say something useful that does not belong on every other service page. Consider a commercial construction company. It offers: Preconstruction planning and Construction management. A preconstruction page may need to explain feasibility, budgeting, scheduling, site considerations and early planning. A construction-management page may need to explain coordination, contractors, site management, reporting and delivery. Even if the same company provides both, the information needed before buying them is different.

That strengthens the case for separate pages. Now imagine the company lists: Commercial construction consultation as a minor first step inside every project. If the entire service can be adequately explained in one section of the main construction page, forcing it into a standalone page may produce a very weak page. The question is not:

Can we write 800 words about this?

It is:

Does somebody need a dedicated destination to understand or choose this service?

Test 3: Would you show different proof?

Proof is a surprisingly useful page-splitting test. Take a healthcare clinic offering: Sports physiotherapy and Post-surgical rehabilitation. Both fall under physiotherapy. But the useful proof may differ. Sports physiotherapy may need athlete recovery examples, common injuries and return-to-sport processes. Post-surgical rehabilitation may need experience with particular procedures, recovery stages and coordination with medical treatment. If the best evidence for Service A is not the best evidence for Service B, that often indicates that the buying decision is different enough to deserve focused content.

Test 4: Does the process or outcome change?

Consider an industrial maintenance company offering: Preventive maintenance and Emergency repair. Preventive maintenance may involve scheduled inspection, planned downtime and ongoing maintenance contracts. Emergency repair may involve fault diagnosis, availability, response time and rapid parts replacement. Someone comparing preventive-maintenance providers should not have to dig through emergency-repair information to understand the offer. Separate pages make sense because the service journey changes.

Test 5: Could one strong page answer both needs properly?

This is the best merge test. Suppose a landscaping company has:

  • /lawn-care

  • /lawn-maintenance

  • /residential-lawn-maintenance

Open all three. If they serve the same audience, explain essentially the same work and lead to the same enquiry, ask:

If we combined the strongest information from all three into one excellent page, would the customer lose anything important?

If the answer is no, you probably have a consolidation opportunity. If combining them would force different customer problems, processes or buying decisions into one confusing page, keep investigating separate pages.


Compare keeping services on one page with creating separate pages, based on customer problems, audience, process, proof, questions and next steps.

Keep together when…

Separate when…

Same customer problem

Different customer problem

Same audience

Different buyer or audience

Same process

Different process

Same proof

Different proof

Same FAQs

Different questions

Same next step

Different conversion path

One page can explain both clearly

Combining them makes the page confusing

Difference is mainly wording

Difference is meaningful to the customer

This table is more useful than trying to calculate an “ideal” service-page count.

Your Services page can still exist

Separate service pages do not mean removing the main Services page. A useful structure can be:

Services

  • Bookkeeping

  • Payroll

  • VAT Services

  • Management Accounts

The main /services page becomes an overview. It helps someone understand:

What does this company offer?

The individual pages answer:

Tell me everything I need to know about this particular service.

This hub-and-detail pattern is also useful for internal linking: Google recommends linking important pages from other relevant pages so both people and Google can discover and understand them. (Google link best practices)

What if you offer 30 services?

Don't put 30 unrelated links into one giant menu just because 30 pages exist. Group services where the grouping makes sense. An engineering company could have:

Engineering services

Design & Planning

  • Mechanical Design

  • Electrical Design

  • Process Engineering

Installation

  • Equipment Installation

  • Commissioning

  • System Integration

Maintenance

  • Preventive Maintenance

  • Condition Monitoring

  • Emergency Repair

Now the website can have depth without turning the navigation into a flat list. This is where your service-page planning connects directly with the sitemap and findability work from the previous article.

Be careful with service × location pages

Suppose you offer five services in ten cities. That does not automatically mean you should create 50 pages. A page such as:

  • /payroll-services-manchester

should have a real reason to exist beyond replacing one city name with another. If the location materially changes availability, office information, team, local regulations, customer proof, service area or buying information, a dedicated page may be genuinely useful. If you create dozens of substantially similar city/service pages whose main purpose is capturing similar searches and funneling everyone to the same destination, that moves toward the kind of doorway behaviour Google explicitly warns against. (Google Search spam policies)

So treat service pages and location pages as separate decisions. Don't multiply them automatically.

More pages do not automatically mean more SEO

This is where website planning can go wrong. A keyword tool shows:

  • commercial cleaning

  • office cleaning

  • professional office cleaning

  • business cleaning

  • corporate cleaning

That does not mean you should immediately create five pages. Google recommends using the language people search with, but it also emphasizes useful, people-first content rather than creating large amounts of search-first material. (Google Search Essentials; Google people-first content guidance) Its spam policies specifically call out substantially similar pages created to rank for specific similar queries as doorway abuse, and large volumes of low-value generated pages can fall under scaled content abuse. (Google Search spam policies)

The practical rule is: Use search language to understand demand. Use customer intent to decide page boundaries.

Don't create thin service pages just because the sitemap has space

Imagine a furniture-restoration company offers: Antique chair restoration but all it can currently say is:

We restore antique chairs. Contact us for more information.

That probably does not justify an entire page yet. The service may still be mentioned under a broader:

Antique Furniture Restoration

page until you have enough useful information to explain:

  • what work is involved

  • what furniture is suitable

  • examples

  • materials/process

  • limitations

  • typical customer questions

  • what happens next

Google's people-first guidance asks whether a page provides substantial, useful and complete information that helps someone achieve their goal. (Google people-first content guidance) A separate URL by itself does not create value.

Use this worksheet before adding a service page


Service-page decision worksheet comparing two services across intent, information, evidence and the customer journey.

Question

Service A

Service B

Different customer problem?

Yes / No

Yes / No

Different search or buyer intent?

Yes / No

Yes / No

Needs its own explanation?

Yes / No

Yes / No

Different process or deliverables?

Yes / No

Yes / No

Different proof or examples?

Yes / No

Yes / No

Different FAQs?

Yes / No

Yes / No

Different CTA or next step?

Yes / No

Yes / No

Can the parent page cover it properly?

Yes / No

Yes / No

You do not need a magic score. Look at the pattern. If nearly everything is different, a dedicated page is probably justified. If almost everything is the same, splitting the page may only be creating duplication. If the result is mixed, research the customer/search intent before deciding.

A practical example: one company, three different decisions

Imagine a security company offers:

CCTV Installation

Different buyer problem, equipment considerations, installation process, proof and questions. → Separate page makes sense.

CCTV System Installation

Same service, same buyer, same process. → Probably not another page.

CCTV Maintenance

Existing system, different problem, different process and potentially a different commercial relationship. → Separate page may make sense. This is how page planning should work. Not:

We found three keywords, therefore three pages.

What should every separate service page actually earn?

Before approving a new service URL, you should be able to explain why that page exists in one sentence. For example:

This page exists because companies looking for payroll support have different questions, requirements and next steps from companies looking for bookkeeping.

Good. Compare:

This page exists because “professional bookkeeping service” is another keyword.

Not enough.

How many service pages should you have, then?

Enough to cover the meaningful services customers need to understand and choose. No more than that. A company with three simple services may need three focused pages. Another company may genuinely need forty because it serves different industries, technical requirements and buying journeys. The total number is the output of the planning process. It should not be the input. Start with every service the business offers.

Then ask:

  • Is the customer problem different?

  • Does the page need different information?

  • Are the process, proof or questions different?

  • Would one combined page become confusing?

Yes: Investigate a separate service page.

No: Keep it within the parent service or merge overlapping pages.

If every page you create has a clear reason to exist, your website may end up with 6 service pages or 60. Both can be right. The problem starts when the page count is decided before the customer need is.

ARTICLE WRITTEN BY

Milan Gohil

I like looking beyond the obvious problem to understand what is really holding a business back. I write about the patterns, questions and practical lessons I discover while working through real challenges

ARTICLE WRITTEN BY

Milan Gohil

I like looking beyond the obvious problem to understand what is really holding a business back. I write about the patterns, questions and practical lessons I discover while working through real challenges

Book your strategy call

Book your call now

On this page
AI Summary

Book your strategy call

Book your call now

All Blogs

All Blogs & Articles

Two small paper browser windows connected by a sturdy orange bridge; a continuous thin black route crosses intact from old to new, with a small magnifying glass beside the destination..

Found

How to Redesign or Migrate a Website Without Losing SEO

Two understated cut-paper hands pass a single orange key above an open ivory folder holding a miniature website card and neatly arranged small tools.

Chosen

Website Handover Checklist: What Your Developer Should Give You

A single central paper website card branches into three distinct service cards carrying only simple object icons: a gear, a pencil and a wrench.

Found

How Many Service Pages Does Your Website Actually Need?

A small paper analytics panel with an unlabeled black line that dips; a large orange-rimmed magnifying glass examines a disconnected paper link below the chart.

Found

Why Your Website Traffic Dropped After a Redesign and What to Check First

A tactile paper branching pathway with a tiny dark human figure at its entrance.

Seen

How to Test Your Sitemap and Navigation Before a Website Redesign

A miniature paper shopping trolley carrying three simple product boxes crosses a broad orange bridge between two spare storefront cards.

Found

Ecommerce Migration Without Losing Product URLs, Feeds or Customer Journeys

Two small paper browser windows connected by a sturdy orange bridge; a continuous thin black route crosses intact from old to new, with a small magnifying glass beside the destination..

Found

How to Redesign or Migrate a Website Without Losing SEO

A single central paper website card branches into three distinct service cards carrying only simple object icons: a gear, a pencil and a wrench.

Found

How Many Service Pages Does Your Website Actually Need?

A tactile paper branching pathway with a tiny dark human figure at its entrance.

Seen

How to Test Your Sitemap and Navigation Before a Website Redesign

Two understated cut-paper hands pass a single orange key above an open ivory folder holding a miniature website card and neatly arranged small tools.

Chosen

Website Handover Checklist: What Your Developer Should Give You

A small paper analytics panel with an unlabeled black line that dips; a large orange-rimmed magnifying glass examines a disconnected paper link below the chart.

Found

Why Your Website Traffic Dropped After a Redesign and What to Check First

A miniature paper shopping trolley carrying three simple product boxes crosses a broad orange bridge between two spare storefront cards.

Found

Ecommerce Migration Without Losing Product URLs, Feeds or Customer Journeys

Before you invest in another fix, make sure it is the right one.

Your website may not need more pages, more content or another redesign. It may need clarity on what is actually holding it back.

Before you invest in another fix, make sure it is the right one.

Your website may not need more pages, more content or another redesign. It may need clarity on what is actually holding it back.

Something isn’t working as well as it should?

Your website may not need more pages, more content or another redesign. It may need clarity on what is actually holding it back.

© 2026 Webshunya Studio®. All rights reserved.