A service page can support a buyer's decision when it identifies the service and fit, explains scope and process, shows relevant evidence, answers practical objections, gives pricing context and presents a clear enquiry step. Treat this as a structure to test, not a conversion guarantee. Check that Google Analytics 4 (GA4) records your form correctly before using form events, and track qualified enquiries in a CRM or another internal record.

Updated 5 November 2026: refreshed GA4 form-event guidance, privacy notes and form-accessibility checks.

Use a service page to answer the questions a prospective customer needs to settle before making an enquiry. This structure is a planning aid, not a formula that guarantees a conversion rate. The right order depends on the service, the buyer and the evidence the business can show.

1. Confirm the service and problem immediately

At the top of the page, tell the visitor:

  • what service this page covers;
  • who it is for;
  • what problem it solves;
  • what the next step is.

Example:

Website redesign for service businesses losing enquiries Rework the pages, forms and contact journey that visitors use before they call, email or WhatsApp your team.

The heading does not need to contain every keyword. It needs to orient the buyer.

Avoid opening with a slogan that could belong to any industry.

2. Show who the service is for and who it is not for

State fit criteria so a visitor can judge whether the service matches their need and your team can respond with the right context:

  • business type;
  • project stage;
  • location or service area;
  • minimum scope where relevant;
  • technical requirement;
  • whether you work with existing websites or only new builds.

Use plain language such as “This service may fit if…” and explain any genuine limits. Avoid implying a prospect is unqualified just because they do not match a preferred profile.

3. Explain the work in customer language

Describe the work in terms the buyer can use to decide whether it fits:

Instead of:

UX, UI, CRO, technical SEO, analytics, schema.

Explain what changes for the customer:

A provider reviews the pages people land on, clarifies what each service includes, repairs the enquiry path, improves phone usability and sets up measurement for agreed actions.

Keep technical terms when they help a buyer compare scope or understand the deliverable. Define acronyms on first use.

4. Put scope before vague benefits

Describe the actual deliverables included in the service. A list might include:

  • discovery or audit;
  • page planning;
  • copy support;
  • design;
  • development;
  • form integration;
  • analytics;
  • launch checks;
  • handover.

Follow each deliverable with the buyer-facing result it is meant to support. Match the list to the provider’s real scope. For example, if form integration is part of the project, explain that a working enquiry form gives a prospect a direct way to send project details. Include this example only if it matches the work you deliver; it does not promise more submissions.

Avoid promising a conversion lift unless you have reliable evidence for that specific claim. Explain what the work changes and how the business will judge the result.

5. Show evidence beside the claim

Place relevant evidence beside the claim it supports. Depending on what the business can substantiate, that may include:

  • case study;
  • before/after journey;
  • client quote with permission;
  • screenshot of a completed page;
  • verified measurement;
  • process document;
  • relevant experience.

Do not put ten client logos in a row and expect the visitor to infer what you did for them.

Link to a case study when a buyer needs the context, scope and result behind the example. Get permission before using a client quote or identifying information.

6. Explain the process before asking for commitment

Describe the real steps, who is responsible and when the buyer must make a decision. For example, a provider may review the current site, agree scope and price, complete the work through named review points, then test and hand over the result. Change the example to match the provider’s actual workflow, including approval dependencies and delays the customer controls.

7. Give pricing context where you can

Give the pricing information the business can support. Depending on how the service is sold, that could be:

  • starting price;
  • package price;
  • typical range;
  • minimum engagement;
  • factors that change the quote.

If the page says only “Contact for price”, explain what information you need to quote accurately.

If there is no fixed price, explain what changes the quote and what details you need to prepare it. Check whether pricing context changes enquiry quality using your own enquiry records; do not assume it will affect every visitor the same way.

8. Answer the objections that block the enquiry

Use questions customers actually ask. For a web project, they might include:

  • Can you work with our existing website?
  • Who writes the content?
  • Do we own the site after launch?
  • Is hosting included?
  • How many revisions are included?
  • Can you connect WhatsApp or business email?
  • How long does the project take?

Answer a question where the related decision comes up, or link to a fuller explanation if it needs more detail.

Do not hide every important term inside a final FAQ accordion.

9. Use one primary call to action (CTA)

Choose one main action your team can handle. Make the link or button name the next step. Examples include:

  • Describe your website project;
  • Request a conversion audit;
  • Ask about this service on WhatsApp;
  • Book a discovery call.

Repeat that same action after sections where the buyer has enough information to act.

If you offer another route, such as WhatsApp or a phone call, explain when it is useful and keep the primary action clear.

10. Keep the form proportional to the decision

For a first enquiry, ask only for information needed to respond or assess basic fit. POPIA requires personal information to be adequate, relevant and not excessive for its purpose; the right fields depend on the enquiry and the business’s lawful processing. See section 10 of South Africa’s Protection of Personal Information Act.

For a website-service enquiry, relevant first-stage fields may include:

  • name;
  • email;
  • service;
  • existing website if relevant;
  • short project context;
  • budget or timing when it materially affects fit.

Do not request identity numbers, payment credentials or detailed company histories unless the stated purpose and applicable requirements justify them. Keep contact-form data out of Google Analytics: Google’s policy prohibits sending personally identifiable information such as names, email addresses or phone numbers to Analytics. Review the privacy notice and consent requirements that apply to the site. Google’s PII guidance

11. Make the page work on a phone

Test the page on a phone and with keyboard navigation. Check:

  • heading wrapping;
  • CTA visibility;
  • form labels and instructions;
  • keyboard access to controls and error messages;
  • card stacking;
  • readable paragraph width;
  • suitable input types for email addresses and phone numbers;
  • sticky elements covering content;
  • WhatsApp links;
  • performance on mobile data.

W3C recommends labels and instructions that help people identify what to enter in a form. Keep visible labels associated with each control and make required formats or errors clear. W3C form-label guidance and form-instruction guidance

12. Measure the service page as a journey

Start by defining the action that counts as an enquiry for this service. Google Analytics 4 can measure page visits and, when Enhanced Measurement’s form interactions are enabled and detect the form, form_start and form_submit. Check that the events fire for your actual form.

If a custom form that submits in the background (an AJAX form) does not send a native submit event, have the maintainer send a custom event only after the form’s success response, such as when the download or confirmation appears. Google lists generate_lead as a recommended event for form or information-request submissions. To count only the relevant form as a key event, configure a form-specific event instead of treating every form submission as a lead. Google’s lead-generation guide, event setup and recommended event list

Keep stages separate in your reporting:

  • Page views and configured CTA interactions show visits or actions, not enquiries by themselves.
  • Form starts and submissions show activity if the event setup records them correctly.
  • A CRM or sales record can show whether a submitted enquiry qualified, reached a proposal stage or became a sale.

Use an internal record to evaluate enquiry quality. Keep personal details out of Analytics and follow the applicable privacy and consent guidance in section 10.

If submissions happen but few enquiries fit the service, review the offer, scope and fit information with sales staff. If visitors do not reach or start the form, check the page and measurement setup before attributing the drop-off to the copy.

Download the service-page planning sheet

Use the service-page wireframe below to map each section to a buyer question, the evidence or content needed, the primary action and any implementation notes. Treat the sequence as a draft to validate against real customer questions and enquiry records.

IDJoy uses this decision-first structure when planning a website design or redesign project.