One page per service. It's the simplest fix most expert sites skip.

The page is the unit

Search engines rank pages, not paragraphs. AI engines cite pages, not sections. Buyers email pages to their partners, not anchors halfway down a scroll. The page is the unit of being found, compared, and shared — and an offer that doesn't have one can't be any of those things.

When your assessment, your advisory retainer, and your build work all share one Services page, the machine reading it has to average them. The page is about everything, so it ranks for nothing. A buyer searching for exactly what your second paragraph describes will be sent to a competitor whose whole page describes it.

An offer without its own page isn't really on your website. It's mentioned there.

What splitting actually does

• Each offer gets its own search surface. A dedicated page can match the specific phrase its buyer types. Your diagnostic offer and your retainer have different buyers at different moments — one page can't face both directions at once.
• Each offer gets its own schema. Structured data can state plainly: this is a Service, here's who it's for, here's the price. That's what lets engines answer "what does this cost" with your number instead of a guess. One combined page muddies what describes what — schema for service businesses covers how this works.
• Each offer becomes a link target. Your answer pages, your emails, your proposals, other people's recommendations — they all need somewhere specific to point. "See the Services page, scroll down a bit" loses people that "here's the page for exactly this" keeps.
• You learn what buyers actually want. With one Services page, your analytics tell you people looked at services. With five offer pages, they tell you which offer is pulling — which is operating information, not just marketing information.

What belongs on a service page

A service page has one job: let the right buyer qualify themselves without booking a call. That takes six things, plainly stated:

1. Who it's for. Named specifically enough that the wrong buyer leaves and the right one feels seen.
2. The problem it solves. In the buyer's words, not your method's vocabulary.
3. What you get. The deliverables, concretely. A memo, a working session, a rebuilt system — nouns, not verbs.
4. How long it takes. A real timeframe. "It depends" is true of everything and useful for nothing.
5. What it costs. For fixed-scope work, the number. Public pricing filters mismatched buyers before they cost you a call, and it gives machines a fact to repeat instead of a blank to fill. Custom work can state where pricing starts.
6. What happens next. The one action, and what follows it. Then stop. A service page that keeps selling after the buyer is convinced starts unselling.

This site practices what it's preaching, for whatever that's worth: the Modern Operations Path™ is five offers, and each has its own page with who it's for, the timeline, and the price on it. Not because it's tidy — because each page has a different buyer at a different moment.

When splitting backfires

There's a failure mode, and engines have gotten good at spotting it: the same service photocopied across a dozen thin pages with the nouns swapped. "Consulting for dentists." "Consulting for lawyers." "Consulting for gyms." Same two hundred words, different audience label.

Split by genuinely different offers — different buyer, different outcome, different price. Don't split by keyword variation. If two pages would say the same thing, they're one page. Thin duplicates don't just fail to rank; they signal to engines that your site pads, which taxes the pages that deserve to rank.

And note what service pages don't replace: the pages that answer buyer questions before they're looking for a service at all. That's a different layer of the site — the content layer — and it's where strangers come from. Service pages convert them; they rarely attract them.

Naming and linking the pages

Two small decisions do outsized work once the pages exist. First, the URL: name it what the buyer calls the thing, not what you call it internally. /operations-assessment outworks /services/tier-1 forever, and the URL is itself a signal machines read. Keep it short, keep it stable — renaming a URL later means redirects and lost history.

Second, the links between pages: every service page should say where it sits. The diagnostic links to the build it feeds. The retainer links back to the build it maintains. If your offers credit into each other, say so on each page — sequence is exactly the kind of business fact buyers want and machines can only repeat if you state it. A set of offer pages that reference each other reads, to a machine and a buyer alike, as a system rather than a menu.

The prerequisite nobody mentions

Here's the uncomfortable reason many expert sites keep the single Services page: the offers aren't actually defined. The founder does "whatever the client needs," scoped call by call, priced engagement by engagement. You can't write six plain facts about an offer that changes shape every time it's sold.

If that's the real blocker, it isn't a website problem. It's an operating problem the website is faithfully reporting — the same one that keeps everything routing through you. Define the offers first. The pages then write themselves.