How to test website enquiries before a rebuild goes live
Follow an enquiry from its original service page to the CRM, confirmation and analytics. A practical acceptance checklist for a UK website rebuild.
A website rebuild is ready for customers when an enquiry reaches the right person with enough context to act. A confirmation screen alone does not prove that the record reached the CRM, that a notification arrived or that the original service page was recorded. Agree the expected journey before choosing a launch date.
This checklist is for UK service businesses commissioning a website with CRM integration. It covers a practical acceptance test, rather than a guarantee about conversion rates or search rankings.
Start with a written acceptance record
Pick one commercial page, one mobile device and one desktop browser. Record the starting URL, the expected destination, the person who owns new enquiries and the result observed at each step. Use clearly labelled synthetic details in an approved test environment so test activity cannot be mistaken for a sales opportunity.
Define success in operational terms: a stored enquiry, a responsible owner, a visible acknowledgement and the right attribution. Decide how the team finds an enquiry if its email notification fails. The CRM and the mailbox are separate destinations and should be checked separately.
Follow the buyer journey on a phone
Open the service page at a narrow mobile width and find the main contact action. Check whether navigation or a fixed banner obscures it. Follow the link and confirm that the form explains what happens next. Look for clear labels, sensible input types and a usable keyboard order.
W3C's forms guidance explains labelling, instructions, validation and feedback. Its validation tutorial also distinguishes browser checks from server validation: both are needed. These are practical acceptance checks, not an assertion that a short test establishes full accessibility compliance.
Preserve the original landing page
Use an approved test campaign link to the service page. Navigate normally to the form rather than manually copying tracking parameters into the contact URL. After a successful test submission, check the stored enquiry for the original page and campaign. Reload the form before a second test to check that a reload does not replace the original source with the generic contact page.
Illustrative example: a buyer arrives on a website development page and then opens Contact. The useful record identifies the website development page as the landing page and Contact as the submission page. Recording only Contact loses the service context.
Count submitted enquiries separately from clicks
A contact-button click, an attempted submission and a completed enquiry answer different questions. Keep them separate in reports. Trigger the submitted-lead event only after the receiving endpoint confirms success; revisiting a thank-you page should not create another lead.
Google's GA4 event guide describes sending events with parameters and inspecting them in Realtime or DebugView. Use that to inspect a test event, while keeping names, email addresses and message text out of analytics. Registration of a parameter for reporting is a separate configuration step; sending it does not automatically make it available in every report.
Test failure as well as success
Leave required input empty and try an invalid email address. The form should explain what needs correcting and preserve useful input. No successful-lead event should be emitted for a rejected form.
In a test environment, simulate a slow or unavailable receiving service. Confirm that the buyer gets an understandable retry message and that repeating the request does not create unintended duplicates. W3C's notification guidance covers communicating errors and successful completion clearly.
Include old URLs and the handover
Check known legacy service and contact links. Each should either reach the closest relevant live page through a deliberate redirect or return an honest not-found response. Do not send unrelated old URLs to the homepage simply to remove errors from a report.
Before launch, ask the person handling enquiries to check the record and acknowledgement. Record any unresolved issue and who owns it. After release, use one approved, labelled production test if needed, reconcile it across the form, receiving system and analytics, then remove or mark the test record according to the business's normal process.
For a rebuild that needs search, enquiries and operational systems to work together, discuss website development and CRM integration. Bring the current website, the CRM destination and one example of an enquiry that is difficult to follow up.
Reviewed 20 November 2026. Examples describe acceptance tests, not client results.
Website development and CRM integration
Scope a website rebuild around useful service pages, working enquiries and a clear handoff to your CRM.
