The decision of whether to put all services on one page or create separate pages for each one is one of the first questions a business owner asks when planning a new website. The answer does not depend on what is trendy or what the competition does — it depends on what questions customers actually type into the search engine. One page can answer one main question. If customers ask different things, you need different pages.
On this page you will find a practical way to make this decision: how to analyze customer questions, what criteria determine whether a page makes sense, and what mistakes to avoid. You will also learn when Google penalizes for too many pages and when it rewards a well-thought-out structure.
The key parameter for website structure
Instead of asking how many pages do I need, ask on how many different questions does my website need to answer. Each page (or section on a page) should answer one distinct question. If a customer is looking for price information about a procedure, and another customer wants to know what that procedure looks like — these are two different questions, even if they relate to the same service.
This way of thinking changes the entire approach to website structure. Instead of counting pages, you count questions that need answering. This approach is called intent-based architecture.
Sources of customer questions?
The best source of questions is phone calls and emails that already come into the business. Owners of small offices, salons, and service companies often hear the same questions repeatedly. The second source is Search Console — it shows which queries have already appeared in search results. The third is direct inquiries through the website form.
It is worth writing down at least 20 questions before designing the structure. Only after writing them down can you see which are similar (can be answered by one page) and which are completely different (require separate pages or sections).
Intent test: when two searches give the same answer
Not every query needs a separate page. Two queries lead to one page if the customer expects the same answer. Example: queries dental implant price and how much does an implant cost — both expect an answer in the form of a specific amount. One query dental implants might expect information about what an implant is, while teeth whitening — what whitening is. These are different answers, so potentially different pages.
The following example shows how to group 8 queries for a dental practice (example with illustrative numbers):
| Query | What the customer expects | Group |
|---|---|---|
| dental implant price | cost of the procedure | price |
| how much does implant cost | cost of the procedure | price |
| dental implants who can get | indications and contraindications | for whom |
| are implants safe | safety information | safety |
| teeth whitening results | what the final result looks like | results |
| teeth whitening how long | procedure duration | process |
| dental dentures types | what types of dentures exist | types |
| dentures price | cost of dentures | price |
In this example on illustrative numbers: 8 queries create 6 groups. Each group is potentially one page or section.
The criterion is simple: if the answer to two queries sounds the same — that is one page. If the answer is different — different pages or sections.
The same logic works the other way too: if two outwardly different queries in practice lead the customer to the same next step — for example, booking an appointment — you don't need separate pages for them just because the wording differs. What matters is the customer's goal, not the exact phrasing.
When a separate page makes sense
A separate page for one service is justified when it meets at least a few of the following criteria:
Its own price or terms
If a service has a separate price list, different payment terms, or schedule — it needs its own page. A customer searching for service A price cannot get an answer if the price is buried somewhere on a shared page.
Its own process
If the delivery method of the service differs from others — different stages, different tools, different requirements for the customer — a separate page is needed.
Its own photos or cases
If a service has real work photos, real customer reviews, real case studies — that is a strong argument for a separate page.
Enough facts
Google does not like thin pages (thin content). A separate page should contain at least 300 useful words that actually help the customer make a decision.
If a service does not have enough facts to write 300 useful words — it is better to make a section on a shared page rather than a separate page.
Its own audience
If a service targets a clearly different group than the rest of the offer — for example, business clients alongside individual customers — a separate page lets you match the language, examples, and call to action to that specific group, instead of writing generic text that doesn't fully land with anyone.
When a separate page hurts
According to Google's spam policies, scaled content abuse is a situation where many pages are generated primarily to manipulate rankings rather than help users — creating many pages solely to occupy more search results falls under this. You can read more in the official Google documentation Spam Policies.
Thin content
When you create 20 pages with one paragraph where you only change the heading and a few words — that is thin content. It gives the reader nothing the neighboring page doesn't already give, so there is no real reason for it to exist as a separate page.
Duplicate content
According to Google's SEO Starter Guide, the same content under different addresses is duplicate content, and it's worth reducing it. If a page for service A and a page for service B share most of their text, Google picks one of them to show rather than both — that's a missed chance for visibility, not an automatic penalty. For pages that are genuinely similar, you can point Google to a preferred address with a rel="canonical" tag — more in the official documentation Google Search Central - Consolidate duplicate URLs.
People-first page: Who, How, Why
Google helpful content document recommends that each page answer three questions: who, how, and why. These are not technical requirements — they are a way to create content that really helps the customer.
You can read more about this approach in the official guide Google Search Central - Creating helpful content.
Who
Who performs the service? What qualifications, experience, or certifications does this person have? Customers want to know who they are entrusting their money and time to.
How
What does the process look like from first contact to completion? What are the stages? How long does it take? What does the customer need to prepare?
Why
Why this price? Why choose this company over the competition? Why does the process look this way and not differently?
URL structure
According to Google SEO Starter Guide, descriptive URLs help both users and search engines. URL parts can be displayed in search results as breadcrumbs.
Scheme for small business:
- 01homepage
- →02services section
- →03service page
- →04FAQ/price
example.com/services/dental-implantsThe URL should be readable and understandable. Once chosen, treat the address as permanent: changing a slug without a 301 redirect breaks links the customer may have saved and resets that page's history in Search Console.
Decision matrix: query frequency x answer difference
| Same answer | Partially different answer | Different answer | |
|---|---|---|---|
| Frequent query | Section on one page | Separate page | Separate page |
| Medium query | Section on one page | Section or page | Separate page |
| Rare query | Do not create page | Do not create page | Section or page |
Frequent query = hundreds of impressions per month in Search Console. Medium = dozens. Rare = single digits or none.
Do it yourself: five steps
Write down 20+ queries from phone calls, emails, and Search Console. Do not invent them — real phrases.
Group by expected answer.
Determine the number of pages.
Check if there are enough facts — minimum 300 useful words.
Create a plan.
Structure with automation system
An automation system works differently than manual planning. It takes queries from Search Console and inquiries, groups them by intent, and suggests a page map. After a month, the system shows the number of impressions for each page — without promising positions, only actual data.
Check SEO and maps to see how Aura can help with page structure and local visibility.
Check also Websites and stores if you are planning a new site, and Copywriting for the text on it.
For a single campaign, check Landing page; to measure the results afterward, check Analytics and BI.
To understand what questions customers ask, read the article Why customers dont leave inquiries.
Read about automation in small business in the article Where to start automation.
Read about restaurant data in Google in the article Restaurant data in Google, on the website and on portals.
Read about reporting automation in the article Reporting automation: how to set up numbers.
Frequently asked questions
Is one page with all services worse for SEO?
No. One page with sections for each service can be great for SEO if the content is specific and answers customer questions. The problem only appears when the page is empty — without prices, processes, questions. Then Google treats it as thin content.
How many services can be on one page?
There is no specific number. It can be 5, 10, 15 — but each service must have at least 3-4 paragraphs with specifics (price, process, for whom, FAQ).
What to do when one service has 10 variants?
Ten variants of one service is too many for one page. Solution: divide into 2-3 main groups, each with its own page. Other variants — in FAQ or comparison table.
Do I need to create a separate page for each service to have an FAQ?
No. FAQ can be on one page with a list of questions about different services. But if there are many questions (15+) — it is better to spread them across separate service pages.
How to check if a page has thin content?
Read the text and ask yourself can the customer make a decision after reading. If yes — the content is sufficient.
Should I create a separate page for each service?
If your company has fewer than 5 services, keeping them on one page with sections is usually better. With 10+ services, a differentiated structure makes more sense.
Does changing page structure affect rankings?
Yes, but the impact is temporary. When changing URLs, use 301 redirects and canonical tags. After a few weeks, rankings will stabilize.