A service page has a fairly fixed set of elements and the arrangement decides how it performs. The reliable structure puts the service and area first, a way to act immediately after, evidence in the middle, and a second way to act at the end, with the whole thing stacking sensibly on a phone.

The order that works

Not a creative decision. Visitors arrive at a service page with a fixed set of questions in a predictable order, and the layout that answers them in that order performs better than any arrangement that does not.

  1. What this is and where you do it, in one line at the top.
  2. A way to act, visible without scrolling.
  3. What the work involves, in enough detail to be useful.
  4. What affects the price.
  5. Evidence, meaning photographs of this specific work and a review mentioning it.
  6. The questions people always ask.
  7. A way to act again.

The content of each is a writing question. Where each sits, how much room it gets, and what it looks like on a phone is the design question, and that is what decides whether any of it gets read.

The action, placed twice

The most common layout fault on service pages is a single contact form at the bottom.

That arrangement assumes everyone reads the whole page before deciding, and a share of visitors arrive already decided. Making them scroll past everything to find the number loses some of them.

The reliable approach is a tappable number visible immediately, and a form or primary button both near the top and at the end. The one at the top serves the decided visitor; the one at the bottom serves the person who read and is now convinced.

Repeating it is not redundancy. Those are two different visitors at two different moments.

Where the form actually goes

Higher than most sites place it, and not necessarily at the very top.

On a desktop layout, a short form in a sidebar that stays visible while the page scrolls covers both cases at once. On a phone there is no sidebar, so it becomes a question of sequence: a button near the top that jumps to the form, and the form itself after the main explanation.

What does not work on a phone is a long form immediately at the top, which pushes the content down and asks for a commitment before anything has been explained.

Images, and where they belong

Reserving the space each image will occupy matters here, since images loading late shift the layout and cause mistaken taps on exactly the buttons you want pressed correctly.

How it stacks on a phone

The desktop layout is designed and the phone layout is what most people see, which is the wrong way round for how attention is usually allocated.

Three things to check specifically. The order elements stack in, since a sidebar can end up below the content or above it depending on the markup. Whether the primary action is reachable without a long scroll. And whether any element assumes hover, which does not exist.

The practical method is to design the phone version first and let the desktop version be the one with more room, which produces a better result than shrinking a wide layout.

Length

Longer than most owners expect, and structured so length is not a barrier.

A service page answering seven questions properly runs to a thousand words or more, and that is fine provided headings let a skimmer find their section. What loses people is not length but undifferentiated text, which is a spacing and heading problem rather than a word count one.

Cutting a service page to fit a screen removes the material that persuades and leaves the material that every competitor also has.

One page per thing people search

A design consequence rather than only a search one.

A page covering four related services has to compromise its structure for all four, so none of them gets the top-of-page clarity that makes the layout work. A page covering one can put that one service in the first line and organise everything beneath it.

This is why splitting a combined services page into separate pages frequently improves conversion even before it affects search visibility, and it is the same argument for giving each page one job in the homepage sections almost every site needs.

The check

Open the page on a phone and stop at the first screen.

Ask whether a stranger could say what the service is, where you do it, and how to reach you. If any of the three is missing, the top of the page is not doing its job, and everything below it is being read by fewer people than it should be.

Frequently asked questions

What order should a service page be in?

What the service is and where, a way to act, what the work involves, what affects the price, evidence, common questions, and a way to act again.

Where should the contact form go?

Higher than most sites put it, and repeated. A form only at the bottom assumes everyone reads the whole page, while a share of visitors arrive already decided.

Is repeating the call to action redundant?

No. The one near the top serves the visitor who already decided; the one at the end serves the person who read the page and is now convinced. Those are different people.

How long should a service page be?

A thousand words or more if it answers the questions properly. Length is not the barrier; undifferentiated text is, which is a heading and spacing problem rather than a word count one.

Should one page cover several related services?

No. A page covering four has to compromise its structure for all of them, so none gets the top-of-page clarity that makes the layout work.

What should I check on a phone?

Stop at the first screen and ask whether a stranger could say what the service is, where you do it, and how to reach you. If any is missing, the top of the page is not working.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Service pages that read well and produce nothing?

We rebuild the layout so the decided visitor can act immediately and the researching one finds their section without scrolling past it.

Start a Conversation