Many services pages are, in practice, a list: design, development, SEO, consulting. Each item gets an icon and two lines of text. Someone who arrives with a concrete question — does this fit my case, how long does it take, how does it work — leaves without an answer and has to write in to ask the basics. Many people simply don't.

A good service page does the opposite: it answers the questions a client would ask in a first conversation, so the contact starts further along. This post is about that specific page. The structure of the site as a whole is covered in company websites.

One page per service, when the services are different

If you offer things that serve different audiences, problems or timelines, each one deserves its own page. Its own address allows a clear title, a specific description in search results and copy that speaks to one person instead of trying to please everyone at once.

The reverse is also true. If two "services" are really stages of the same job, splitting them only creates thin pages. My rule of thumb is simple: if a client would hire one without the other, they're probably different pages.

What the page needs to answer, in order

The order follows the reasoning of someone who is evaluating.

Who it's for

Start with the client's situation, not the name of the service. "For businesses that need to leave the generic site behind and earn trust on the first screen" says more than "professional web design". If there are cases where the service isn't a good fit, say that too. It filters out inquiries that wouldn't go anywhere.

What's included

List concrete deliverables — what the person gets at the end. "Copy structured with you", "domain and launch set up" and "editing handover" can be verified; "complete solutions" can't.

How it works

Three to five steps, each with one sentence on what happens and what's expected from the client. This is where questions about effort and involvement get resolved. I describe mine in the website creation process.

Timeline and how it's billed

Not everyone wants to publish prices, and that's fine. But you can state typical timelines, what the price depends on and how payment works. On my websites page, for example, I make it clear that a landing page usually takes 5 to 10 business days and a company website 2 to 4 weeks, and that the exact timeline and price go in the written proposal.

What happens afterwards

Support, the adjustment period, who keeps the files, how to edit the content. These questions rarely come up in the first contact, but they weigh on the decision.

Objections are information

Every question you answer over and over on WhatsApp is a sign that something is missing from the page. It's worth keeping notes for a few weeks: "do you work outside the city?", "do I need the copy ready?", "is the domain in my name?". Each answer can become a line in the copy or an FAQ item.

That doesn't mean hiding limitations. If the service doesn't include something many people expect, saying so on the page avoids frustration on both sides.

The next step should be obvious and light

At the end of the page, one main call to action, not four competing paths. And next to it, a sentence on what happens next: who replies, on which channel, what will be asked. Something like "tell me what exists today and what should happen; I'll reply in writing with the questions that are missing" lowers the sense of commitment.

If contact goes through a form, ask only for what's needed for a useful first reply, and give each field a clear label that stays visible while the person types. Long forms push away people who are still just evaluating.

A concrete example

The websites page on this site follows this structure: who it's for, what's included, how it works in four steps, typical timelines and frequently asked questions. It's not a template to copy — every business has different questions — but it shows how the blocks fit together. To write each block without overselling, see copy for service websites.

On the technical side, each service page can also carry Service structured data, which describes in a standard format what is offered, by whom and in which area. It's a way to make that information explicit for search engines and AI assistants, without relying only on how they interpret the text.

A simple test

Show the page to someone who doesn't know your work and ask them to explain, in their own words, what you offer, for whom and what the next step is. Wherever they hesitate, the page is still leaving unanswered a question it should answer.

If your services page is currently a list of names and you'd like it to actually answer questions, write to me.

References