One Services Page or Separate Pages per Service? The Evidence

The honest answer to one page vs separate service pages is: it depends on whether each service has its own search intent, and whether your domain has the authority to rank multiple pages at once. Most articles pick a side. The evidence doesn't.

In Whitespark's 2026 Local SEO Ranking Factors survey, experts ranked Dedicated Page for Each Service as the #1 local organic ranking factor and #2 AI-visibility factor. That's a strong signal to split. But Google's John Mueller has publicly cautioned that one stronger page often beats several smaller ones covering the same topic. That's a strong signal to consolidate.

Both statements are true. They describe different situations. This piece resolves the contradiction with intent logic, a worked example, and the low-authority caveat that nobody writing on this topic seems to mention.

TL;DR

• Split into separate pages when each service has a genuinely distinct search intent and buyer journey

• Consolidate into one page when services are variations of the same job-to-be-done

• Whitespark's 2026 survey ranks dedicated service pages the #1 local organic factor — for sites with authority to support them

• Mueller's warning about one stronger page applies hardest to new and low-authority domains

• Use hub-and-spoke linking so split pages reinforce each other instead of competing

1. The apparent contradiction: survey data vs John Mueller

The Whitespark panel surveyed local SEO practitioners in early 2026 and asked which on-page factors moved rankings the most. Dedicated Page for Each Service came out on top for local organic and #2 for AI visibility (the slice covering AI Overviews and chatbot citations). The implication: if you offer plumbing, drain cleaning, and water heater installation, each one wants its own URL.

Mueller's position, archived at Search Engine Roundtable, points the other way. His framing — paraphrased from several Office Hours sessions — is that splitting thin content across many URLs often produces several weak pages competing for the same query, where one consolidated page would have ranked.

Neither is wrong. They're answering different questions.

Whitespark's question: given that you have the resources to build substantive pages for each service, does splitting help? Yes.

Mueller's question: given that you're tempted to slice one topic into five thin pages to chase keywords, will that help? No.

The operator's job is to figure out which question applies to your site.

2. When separate pages win: genuinely distinct search intents

The test isn't whether you offer different services. The test is whether buyers search for them differently and decide on them differently.

A commercial roofing contractor offering flat roof installation, flat roof repair, and emergency leak response has three distinct intents. The keyword maps are different. The price ranges are different. The decision timelines are different — emergency leak is a today problem, installation is a six-week procurement. One page trying to serve all three will lose to a competitor with three focused pages, because the page can't structure proof, pricing context, and CTAs for three different buyer states at once.

When this test passes cleanly, separate pages for each service SEO works because each page can be ruthlessly specific — the hero, the proof, the FAQ, the schema, the internal links all align to one intent. That alignment is what the Whitespark panel was rewarding.

The diagnostic questions, in order of stakes:

1. Do these services have meaningfully different keyword clusters in your tracker?

2. Do buyers compare different competitor sets for each?

3. Would the proof you'd cite (case studies, certifications, pricing logic) be different per service?

Three yeses means split. One or zero means stay consolidated.

3. When one stronger page wins: one topic sliced too thin

The failure mode Mueller is describing happens when an agency or in-house team reads a keyword list, sees variations like website design, web design services, custom website design, and small business web design, and builds a separate page for each. These aren't different intents. They're different phrasings of the same intent. The result is four pages competing for the same query, none of which has the depth to outrank a single well-built page from a competitor.

Fair enough — keyword tools encourage this. The fix is asking, before you split: would a buyer who landed on Page A feel that Page B is a different offer, or would they feel I'm running them in circles?

If the answer is circles, consolidate. Build one page that's twice as deep, with sections handling each phrasing's nuance internally. We cover the anatomy of that consolidated page in service page structure that converts.

The other case for consolidation: when separate pages would each be under ~400 words because you don't have enough to say. A 300-word service page in 2026 reads as a stub to both Google and buyers. One 1,200-word page with real proof beats four 300-word stubs every time.

4. Hub-and-spoke linking so pages aren't orphaned islands

If you split, the next failure mode is shipping five service pages that don't link to each other or to a parent. Google can crawl them, but the architecture sends no signal about how they relate or which is canonical for the broader topic.

The established pattern, documented across the topic-cluster literature, is hub-and-spoke. One hub page covers the category at a high level. Each spoke is a dedicated service page linked from the hub and back to it. Supporting content (case studies, pricing explainers, comparison posts) links up to the relevant spoke.

This is the architecture we use for our own website design service, and it's what we build for clients who have enough services to warrant the structure.

Hub-and-spoke: one category page distributes equity to four spokes, each reinforced by supporting content below.

The hub does three jobs at once: it ranks for the broad category term, it distributes link equity to the spokes, and it gives a buyer who's not sure which service they need a place to orient before clicking through. The spokes do the conversion work for buyers who already know.

5. What changes when your domain has no authority yet

Here's the caveat the rank-the-factors articles tend to skip. The Whitespark finding assumes a site that can support multiple ranking pages. If your domain is under ~6 months old, has fewer than 20 referring domains, or has no track record of ranking anything, splitting into five service pages will likely produce five pages that rank nowhere.

In that situation, Mueller's advice wins on operational grounds. Build one strong services page. Get it ranking for the broadest term you can plausibly win. Earn links and citations against that one URL. Then, six to twelve months later — once the domain has demonstrated it can rank — split into spokes and convert the original page into a hub.

This sequencing is what most should each service have its own page advice misses. The right answer for a 5-year-old domain with 200 referring domains is genuinely different from the right answer for a 4-month-old site. Both can end up at the same architecture; they just shouldn't start there.

The related risk worth flagging: building dozens of near-identical pages targeting different cities or industries before you've earned the authority to rank them. We covered the doorway-page line in industry landing pages without doorway risk.

6. A worked example: structuring 4 services + supporting content

Let's make this concrete. Suppose you run a B2B services firm with four offerings: website design, SEO retainers, paid media management, and conversion rate optimization. Domain is 3 years old, modest authority, ranking for some long-tail terms.

The architecture we'd build:

Hub: /services — a category page explaining how the four services relate, who each is for, and how a buyer decides between them. Targets the broad category term.

Spokes: /services/website-design, /services/seo, /services/paid-media, /services/cro — one page per service, each 1,000-1,800 words, each with its own proof, pricing logic, FAQ, and service schema. Each links up to the hub and laterally to the one or two services most often bought alongside it.

Supporting content: blog posts, case studies, and comparison pieces, each linked up to the most relevant spoke. A piece on Webflow vs WordPress for B2B sites links up to /services/website-design. A case study on a paid-media engagement links up to /services/paid-media. Roughly 4-8 supporting pieces per spoke is a reasonable target over the first 12 months.

Internal linking discipline: every spoke links to its hub in the first 100 words. Every supporting piece links to its spoke at least once in the body and once in a related-reading block. The hub links to each spoke with descriptive anchor text, not learn more.

That's a defensible service page SEO strategy. It satisfies the Whitespark factor without triggering Mueller's warning, because no two URLs are competing for the same intent and each page has enough depth to stand alone.

FAQs

Should each service have its own page if the services are very similar?

Only if buyers search for and decide on them differently. If two services share the same keyword cluster, the same competitor set, and the same proof points, one page handling both with internal sections will outperform two thin pages. The Whitespark 2026 finding rewards distinct pages, not duplicated ones.

Does Whitespark's 2026 ranking factor apply to non-local businesses?

The survey focuses on local SEO, so the #1 ranking applies most directly to businesses with a service-area or storefront component. The underlying logic — that dedicated pages let you align intent, proof, and schema — applies broadly, but the specific weighting was measured in a local context.

How long should each service page be?

Long enough to handle the intent without padding. In our client work, service pages typically land between 900 and 1,800 words once proof, FAQ, and pricing context are included. Anything under about 400 words reads as a stub and tends to trigger the consolidation case Mueller describes.

What if I'm a new site with no authority — should I still split?

Probably not yet. Build one strong services page, earn links and rankings against it for 6-12 months, then split into a hub-and-spoke once the domain has shown it can rank. Splitting too early produces several pages that rank nowhere, which is the exact failure Mueller warns about.

How do I avoid keyword cannibalization across split service pages?

Map each page to a primary keyword cluster before writing, and check overlap in your rank tracker monthly. If two pages start ranking for the same query and trading positions, that's the signal to either consolidate them or sharpen their intents. Hub-and-spoke linking with descriptive anchor text also helps Google pick the right canonical.

Where to start this week

Pull your top 5 service URLs. For each, write down the primary intent in one sentence and the keyword cluster it owns. If two pages have the same sentence, consolidate. If one page is carrying three different sentences, split. Ship the change Monday, measure rankings Friday, decide what to keep on Sunday.

If you'd rather have us map the architecture with you, get in touch.