Consultation Landing Pages: Defining Success Without Promising a Fixed Conversion Increase

Define consultation landing page success before redesigning the page: agree what a visitor should understand, which completed action matters and how you will review the quality of the resulting enquiries. A fixed promise such as “this redesign will increase conversions by 30%” skips the evidence needed to support it.

The page influences the journey, but so do the offer, traffic sources, appointment availability and follow-up. A useful brief separates what the design must deliver, what you will observe and what would justify the next decision. That gives the project an accountable purpose without presenting an uncertain commercial result as a guarantee.

Separate launch requirements from business outcomes

Some success criteria can be checked before launch. Visitors should be able to identify the consultation, understand the commitment and reach the agreed contact route. The page should work at its intended screen sizes, have clear headings and support keyboard navigation through its controls.

Other questions need evidence over time. Are suitable people getting in touch? Do they understand the session before it begins? Are appointments attended? Does the business have the capacity and follow-up process to handle the enquiries?

Write those as different kinds of criteria. A working booking link is an acceptance requirement. An increase in suitable appointments is a business aim. Passing the first does not prove the second, and a temporary increase in enquiries does not excuse a broken interface.

Start by aligning the page’s opening with the actual first conversation. Measurement becomes more useful once everyone agrees which service and commitment the visitor is being offered.

Choose one primary action and define completion

“Conversion” is too broad to use as an unexplained project objective. A button click, a received enquiry and an attended consultation represent different stages. Choose the main action the page is meant to support and state exactly what counts as a completed instance.

For a reviewed enquiry process, completion might mean a valid request has been received. For direct scheduling, it might mean the booking system has confirmed an appointment. If you count requests, do not label them booked meetings. If the calendar requires approval, distinguish a requested slot from a confirmed one.

Keep secondary observations, such as CTA clicks, for diagnosis. They can help identify where attention or progress changes, but they do not automatically represent a completed enquiry.

Google Analytics’ explanation of key events and conversions distinguishes important recorded events from conversion reporting used with advertising. Whatever labels your tools use, document the real-world action behind each metric. Marking an event as important does not establish that it represents a qualified customer.

Use a small measurement dictionary

A short shared table is more useful than a dashboard whose labels different people interpret differently. Agree the counting unit, data source, exclusions and period before comparing a baseline with a revision.

Measure	Working definition	Limitation to record
Contact-link activity	Eligible measured sessions with at least one click on the contact action	A click may not lead to a sent or received message
Received requests	Distinct valid enquiries received for the consultation	Duplicate messages, spam and tests need a consistent rule
Confirmed appointments	Distinct appointments actually confirmed by the booking process	Some requests may still be awaiting review
Suitable enquiries	Reviewed requests meeting the agreed service-fit criteria	The team needs a consistent definition of suitability
Attendance	Attended appointments divided by confirmed appointments due in the same cohort	Cancellations and reschedules need explicit treatment

Not every business needs all five measures. Choose those you can record reliably, with someone responsible for checking the data. If a measure cannot be observed, state the gap instead of substituting a convenient click count.

An email link is a common example. Clicking it may open a mail application; it does not prove that an email was sent or delivered. An inbox can establish that a message arrived, but connecting it to a particular page visit requires additional evidence. Keep unmatched enquiries separate instead of inventing attribution.

Define the denominator as carefully as the result

A percentage needs a clear population. “Enquiries divided by visitors” leaves several questions open: unique people or sessions, all website traffic or this landing page, and which dates? Different definitions can produce different percentages from the same activity.

For a session-based completion measure, one possible definition is: eligible measured landing-page sessions with at least one verified completion, divided by all eligible measured landing-page sessions. Count a completing session once. Only use this definition if your setup can reliably connect the completion to that session.

If it cannot, report received enquiry counts and traffic counts separately, with their limitations. Do not silently combine an inbox total from every channel with visits to one page.

GOV.UK’s completion-rate guidance explains the importance of defined starts, completions and a consistent denominator for government transactions. The relevant lesson here is to define your own consultation journey clearly; its public-service reporting rules are not requirements for a private business website.

Record how internal tests, bots, duplicate actions and missing measurement are handled. Consent choices or third-party booking tools can leave gaps. Use the same rules before and after the change, and keep names, contact details and enquiry messages out of general analytics event data.

Read changes in percentages without overstating them

Here is a hypothetical arithmetic example, not a project result. Suppose one period contains 100 eligible measured sessions, with five sessions completing the defined action. Another contains 100, with eight completions.

The measured rates are 5% and 8%. The difference is three percentage points. The relative increase is 60%, because the three-point difference is divided by the original 5%. Those descriptions refer to the same counts, but the relative number sounds much larger.

Neither calculation establishes why the change occurred or predicts what will happen next. With small counts, a few additional enquiries can move the percentage substantially. Report the counts, dates and definition alongside the rate.

A defensible note would say: “We observed eight completing sessions out of 100 under this definition, compared with five out of 100 in the earlier period. The comparison does not isolate the page change.” It would not say the design has proved a permanent 60% improvement.

Review enquiry quality and the surrounding conditions

More requests are not automatically more useful requests. Agree what “suitable” means for this consultation: the relevant service, project type, location where applicable and a realistic match with what the business can provide. Review against those criteria rather than changing the definition to flatter the result.

Record reasons for unsuitable enquiries in broad, useful categories. Repeated requests for a deliverable the session does not include may point to unclear copy. Requests from an unsupported location may point to missing eligibility information. Avoid collecting unnecessary personal detail for this review.

Check the advert-to-page alignment if a new campaign changes the expectations people bring. Also note changes to spend, targeting, seasonality, prices, appointment capacity, response time and measurement. These can affect the observed result without any change to the layout.

Allow for the time between enquiry and appointment. Comparing newly received requests with attended sessions from an earlier group mixes different cohorts. Agree when each group is mature enough to review, and explain how outstanding enquiries are treated.

Make the review plan useful when traffic is limited

Low traffic does not prevent useful design work. You can inspect whether the page explains the offer, observe people attempting a realistic task and check the contact journey for errors. These activities answer questions a small conversion count cannot resolve.

The guide to testing a first-time visitor’s understanding describes a qualitative approach. Record what people misunderstand and whether a revision addresses that problem. Do not turn a handful of successful sessions into a forecast for every visitor.

If you consider an A/B experiment, agree the hypothesis, random allocation, primary measure and analysis plan with an appropriate analyst before launch. A comparison between last month and this month is not the same as a controlled experiment. Avoid declaring a winner whenever an early dashboard happens to look encouraging.

Write a success brief that leads to decisions

Use a compact brief with an aim, acceptance checks, measurement definition, review owner and decision rule. For example, a fictional studio might aim to help suitable clients request an introductory discussion while reducing enquiries that expect a completed design in that session.

Its launch checks could cover comprehension and the working enquiry route. Its ongoing review could examine received requests and the proportion of reviewed requests that expect the wrong deliverable. The owner would record changes in campaigns and availability, then decide whether to revise the explanation or collect more evidence.

Specify a review date and what evidence would trigger a change, but allow the conclusion to be “insufficient evidence.” If you are preparing the wider site brief, the five-customer-question homepage framework helps connect these objectives with the offer, proof and next step.

Common questions about landing page success

Can a designer guarantee a fixed conversion increase?

A designer can agree deliverables, review methods and technical acceptance criteria. A fixed commercial increase would require evidence and conditions that a design alone cannot control. Ask how the outcome will be measured and which assumptions it depends on.

What if I have no reliable baseline?

Document the current journey, check the measurement setup and begin a clearly labelled observation period. You can still correct known content or accessibility problems. Do not invent a baseline or present unmeasured earlier performance as a comparison.

Is a lower enquiry count always a failure?

No. Clearer suitability information may reduce enquiries the business cannot serve. Review the intended audience, enquiry quality and subsequent handling alongside the count. A lower total is not automatically evidence of improvement either; investigate the reasons.

When discussing a redesign, separate visual recognition from evidence of business usefulness. The guide to business website effectiveness beyond design awards offers a practical way to evaluate that distinction.

Give your landing page a clear and measurable brief

SavianoDesign’s Web Design service starts with the audience, content and purpose of the page, with design and front-end deliverables agreed around the project. Explore the Web Design portfolio to see how that approach informs real interfaces and self-initiated concepts.

Contact SavianoDesign to discuss your landing page with your current URL, the consultation you offer and the action you want visitors to take. Bring any existing observations so the brief can distinguish verified problems from assumptions.