Define the enquiry you actually need
Write down who the service is for, which markets you can serve and the minimum information needed for a useful reply. An enquiry can be genuine yet outside your scope. Separate a delivery problem, such as a lost submission, from a fit problem, such as requests for a service you do not offer.
Choose a short review period and keep its definition consistent. Record the landing page, the requested service and the human decision about fit. A page view, a contact click, a received message and a qualified enquiry answer different questions.
Check what the visitor expected to find
Google recommends useful, reliable content and links that help people and search engines understand pages. That supports clear information architecture; it does not establish that any particular layout will produce enquiries.
Review the entry page
Look at the queries or referral context you can actually observe. Is the visitor researching a topic, comparing suppliers or trying to contact a provider? Mark missing source data as unknown.
Match the page to that task
An explanatory article can lead to a service page without pretending every reader is ready to buy. A service page should explain the audience, scope, useful deliverables and a relevant next step.
Use the language of the buyer
Check that a visitor can describe what you do after reading the page. Technical labels such as agents or automation need a concrete task alongside them.
Official reference: Google Search: SEO Starter Guide
Make the decision before the form easier
Show what happens after someone gets in touch. Explain whether the first step is a scope discussion, a diagnostic or a proposal, and what information is useful at that stage. Only state response times, prices or service coverage that the team can support.
Use relevant evidence close to the decision: a concise, approved case, a clear sample deliverable or a description of the work. Remove unsupported growth claims. A generic “Contact us” link may be sufficient in a familiar context; elsewhere, name the next step so the visitor knows what they are choosing.
Test the complete path with a clearly labelled sample
Use non-sensitive test data and a controlled destination. Submit from a phone as well as a desktop, then ask the responsible person to retrieve the same record. A success message on the screen is only one part of the check.
MDN describes a form as a request to a server; the server must handle and validate the submitted data. Our practical acceptance check goes further: confirm the saved record, the notification state and who can take the next step.
| Check | What to verify |
|---|---|
| Valid submission | The record is saved once and a reference or accurate confirmation is returned. |
| Missing or invalid information | The problem is explained next to the field and useful input is preserved. |
| Slow response or network interruption | The visitor can recover without creating multiple identical enquiries. |
| Notification failure | The saved enquiry remains available to the team; the page does not invent delivery. |
| Phone and keyboard use | Labels, errors, buttons and the next step remain visible and usable. |
Official reference: MDN: Sending form data
Measure receipt and qualification separately
Use a small funnel you can explain: service page viewed, contact started, submission accepted, enquiry reviewed and a later commercial outcome. Decide how to exclude tests and duplicates. Keep personal details and free-text enquiries out of analytics events.
Google Analytics defines generate_lead for a generated lead and qualify_lead for a lead judged to meet qualification criteria. Neither is a synonym for revenue. If your team cannot yet reconcile the stages, start with a simple controlled record instead of reporting a single conversion number.
Official reference: Google Analytics: lead events
Illustrative example: a service team with a general contact form
Imagine a professional service team receiving requests that rarely say which service is needed. First check whether the service pages explain their scope and lead to the right form. A service selection may help, but adding many required questions could make an early conversation harder.
Try one limited change: carry the selected service into the contact page, explain the next step and verify receipt. Review whether the resulting messages are easier to assess. This is a generic example, not a client case or a measured result.
Choose the next change from the evidence
Keep the service facts stable while reviewing a change. A short before-and-after period may reveal a useful problem, but seasonality, traffic mix and other edits can also affect the result. Use that uncertainty to plan the next test rather than promise a fixed enquiry increase.
| What you observe | What to investigate next |
|---|---|
| Visitors arrive for a different purpose | Search intent, the entry page and the service being offered. |
| Relevant visitors cannot explain the offer | Scope, language, evidence and the next step. |
| People try to contact you but records are missing | The receiving path and failure recovery before increasing acquisition spend. |
| Messages arrive but are not a fit | Audience, qualification criteria and which questions belong before or after first contact. |
Sources & next steps
Continue reading
- Website Builder or Custom Website? A Service Team’s Decision Guide
- Inquiry-ready websites for service businesses