What should a service page include before you ask for an enquiry?

The short answer

A service page should explain who the offer is for, what work is included, what needs a separate decision and how to take the next step. Give visitors enough detail to judge whether an enquiry makes sense. The page should also identify the information they need to prepare.

Visitors often arrive with a practical question: “Is this the right service for me?” If the page only says the work is high quality, they still have to email for the basics. Clear scope and a usable enquiry route help them make that decision.

Google's helpful-content guidance asks whether a page describes its subject substantially and leaves readers with enough information to pursue their goal. Applied to a service page, that suggests answering the questions a buyer needs resolved before contacting the business. It does not establish a conversion or ranking guarantee.

Name the service and the customer it helps

Use the heading and opening paragraph to identify the work, the audience and the problem being addressed. For example, “Website design for local service businesses” gives more context than a broad label such as “Digital solutions.”

Keep one coherent offer at the centre of the page. If the business also builds internal tools or automations, give those offers their own explanations where their audiences and scope differ. A reader comparing services should be able to tell which details apply.

Use headings that reflect the content hierarchy. W3C's guidance recommends avoiding skipped ranks when introducing nested sections, such as moving directly from an h2 to an h4. Returning from an h4 to an h2 is appropriate when the subsection has ended and a new main section begins. Headings also help assistive technology users navigate the page.

Explain included work and separate decisions

Describe the work the business actually offers. For a website project, this might include agreed pages, a responsive layout, an enquiry form, search metadata and a handover. Each item should have a meaning the customer can discuss.

Name features that require a separate scope decision. Appointment booking, payments, customer accounts, extra languages and complex integrations can change the work. State whether the business offers them and how they are agreed. Avoid presenting every possible feature as part of the standard service.

The website project brief guide provides a place to record those decisions before design starts.

Explain what the customer supplies: service descriptions, photographs, brand files, approved policy text and a person who can approve the copy. Identify anything the studio will prepare instead. This sets expectations without inventing a timeline; timing still depends on the agreed scope, content readiness and reviews.

Show the process a customer will experience

A short sequence is enough: clarify the problem, agree the pages, review a working version, then prepare launch and handover. Describe the real process used by the business. A public promise that differs from delivery creates avoidable confusion.

Mention the decisions needed at review points. Asking a customer to confirm service coverage or check an enquiry confirmation message is easier to act on than an open-ended request for feedback.

Include current, approved pricing when the business can state it meaningfully. Otherwise explain how a quote is prepared and which details affect scope. Use delivery estimates only when their assumptions are clear.

Make the enquiry action understandable

Label the link with the action it leads to. “Ask about a portrait session” tells a visitor more than “Click here.” Keep the enquiry easy to find after the scope explanation as well as near the top.

WCAG's link-purpose criterion allows the purpose to be clear from the link text itself or from text plus programmatically determined context. A description in the same sentence, paragraph or list item can provide that context. Text that merely sits nearby is not automatically associated with the link. Descriptive link text is a straightforward choice.

Explain which details the enquiry asks for and what happens after submission. State whether it begins a conversation, requests a quote or makes a booking. The label and confirmation should match that behaviour.

Hypothetical example of a portrait service page

A fictional photography business wants a page for portrait sessions. This example is not a Medivh Code client or a report of results.

Its page identifies individuals and families as the audience. It explains the session options the business actually offers and says that event coverage is a separate service. It describes how location, participants and image delivery are agreed.

The enquiry asks for the type of session, preferred dates and a contact method. Its link says “Ask about a portrait session.” The confirmation explains that the enquiry has been received and what the business will do next.

The business still needs to supply accurate details. A developer should not fill gaps with invented session lengths, availability or delivery promises.

Make claims and search copy checkable

Describe activities the business performs. If it checks headings, labels and keyboard access before launch, say that specifically. Those checks alone do not establish complete WCAG conformance. The website launch checklist is a useful companion for release checks.

Write a descriptive page title and a unique meta description that accurately summarise the offer. Google's title-link and snippet guidance explains that displayed search text is generated automatically and may differ from your preferred wording. Metadata influences that presentation; it does not guarantee it.

Use original descriptions of the offer. The page should give the reader useful information instead of repeating broad claims to reach a word target.

Service-page checklist

• The heading and opening identify the service and audience.
• Included work and separate scope decisions are concrete.
• Customer inputs and an approving person are identified.
• Process descriptions match the business's actual review steps.
• Prices, timelines and outcomes are accurate and approved.
• The enquiry action and confirmation explain what happens next.
• Headings reflect the section hierarchy.
• Accessibility and search claims have supporting evidence.
• Links and the enquiry route have been tested.
• A person has reviewed the copy before publication.