Website enquiry journey audit for European small businesses

Start with a business action, not a dashboard number. Write down what counts as a genuine enquiry for each service: a completed appointment request, a quote form with enough detail, a tap-to-call followed by a connected call, or a booking completed in an external system. A newsletter signup and a request for urgent repair should not share the same value or follow-up process.

Create a short measurement card for every main action. Record the page, button or form, expected confirmation, delivery destination, person responsible and response target. Also list test submissions, job applications, supplier messages and spam as exclusions. This prevents a rising event count from being reported as business growth before anyone checks what the events represent.

Use Search Console to inspect queries and landing pages, filtered by country and device when there is enough data. Its Performance report shows impressions, clicks and query or page groupings; it does not show whether the visitor later became an enquiry. Look for intent mismatches: a page may attract people seeking instructions, jobs or a different city when the business expects service requests.

Open the result and read the page as a new customer. The title and description should set an honest expectation. The first screen should confirm the service, area, language and next step. Link naturally to useful supporting pages such as pricing explanations, service details or the contact route. Compare trends over similar periods, and remember that Search Console omits some queries for privacy and may assign data to canonical URLs.

Complete the journey on a real phone and desktop browser. W3C guidance recommends a clear label for every control, helpful instructions, and concise feedback after success or error. Keep only fields needed to handle the request. Check that the keyboard type suits email and telephone fields, that required formats are explained before failure, and that an error does not erase completed answers.

Localisation goes beyond translating labels. Test names with accents, different telephone prefixes, postal formats and longer German or Scandinavian wording. Use the familiar local term for a quote or appointment, and state which areas and languages the team actually supports. The success screen must say what was received, what happens next and how to make urgent contact when appropriate.

Google Analytics can collect form_start and form_submit through enhanced measurement, and recommends generate_lead when someone submits a form or request for information. These names are useful only after verification. A click on “Send” may occur before validation fails, and some custom forms may not behave like a normal HTML submission. Trigger the important event from a confirmed success state whenever the implementation allows it.

Give forms stable names such as contact-general, quote-marine-repair or appointment-request so reports remain understandable. Test events in the real-time or debugging view, then make one successful and one failed submission on each form. Never send names, email addresses, message text or other personally identifiable information into Analytics. Record the event definition so a future redesign does not silently change the meaning.

A thank-you message proves only what the visitor saw. Confirm that the request reaches the correct inbox or customer system, carries enough context, and does not land in spam. Test any automatic acknowledgement, but do not let it imply that an appointment or price is confirmed when a person still needs to review the request. Keep a monitored fallback contact route on the page.

For one week, reconcile confirmed website submissions with received messages and the team’s enquiry log. Investigate differences rather than filling the gap with assumptions. Then sample the next step: was the request assigned, answered and classified as relevant or not? This connects website measurement to service delivery while keeping sensitive customer details out of the analytics tool.

A useful owner report can fit on one page: search impressions and clicks for priority service pages, confirmed enquiries by type and language, delivery failures, relevant enquiries, and median response time if the business records it consistently. Show counts and context, not a single conversion percentage without the small denominator. Annotate website changes, holidays, campaigns and service availability.

Finish each review with one testable action: clarify a misleading page, remove an unnecessary field, repair a missing success event or route one language to the right colleague. Repeat the end-to-end test after every form, email, analytics or booking-system change. The goal is a chain of evidence from customer need to a handled request—not a larger collection of disconnected numbers.