Find the right page.
Open the service page through a real route, such as a search result, a navigation link or a shared URL. The page should address the need that brought the visitor there.
For a website that is already live
Few enquiries? Find the break in the journey.
Before changing the design or buying more traffic, find out what has actually happened. A customer must reach a relevant page, understand it, get through the contact route and receive a reply. This guide helps you test those steps in an order that avoids guessing.
Start with a working route
Follow one enquiry all the way through.
Do not start by interpreting a conversion rate. First check whether a person can send a message and whether someone can act on it.
Finish the action.
On a phone, follow the visible next step and submit a labelled test. Check that the route remains usable if a chat widget is unavailable.
Receive and reply.
Confirm the test reaches the right inbox or dashboard, then check who will reply. A success message in the browser is only one part of this chain.
No analytics access? You can still test the route, inspect the page and check your own enquiry record. Mark discovery as unknown until you have reliable data. A short period with few visits cannot establish a design failure.
A private working sheet
Record what you can actually verify.
Choose a result for each check and write down what you saw. The worksheet stays in this browser, can be cleared, and is not sent to UpOnUp. Avoid customer names, messages and other private details.
01 / Message delivery
Does a real test enquiry arrive?
Send a clearly labelled test through the live contact route. Check the intended inbox and any form or booking dashboard. Record the time and where the message arrived. A thank-you screen alone does not prove delivery.
02 / Visitor journey
Can someone reach that route on a phone?
Start on a page a customer might land on. Ask someone unfamiliar with the business to find the relevant service, understand the next step and open the contact route on a phone. Record where they stopped, if anywhere.
03 / Relevant visits
Are the right people reaching this page?
Check the page and query views in Search Console for a stated date range. Compare them with your own enquiry record and any site analytics. Search Console shows Google Search activity, not every website visit or every lead.
04 / Page answer
Does the page settle the buyer’s next question?
Read the page as a first-time customer. Can you tell what the business does, who it helps, what happens next and which real evidence supports its claims? Record the exact missing answer, not a general impression.
05 / Human follow-up
Does a received enquiry get handled?
Trace one permissioned or test enquiry from receipt to reply. Check who owns the inbox, whether replies can be sent, and whether an out-of-hours message has a sensible next step. Do not put a customer’s private details in this worksheet.
Your entries stay on this device.
For Google Search, its Performance report can be viewed by query, page, device and date. Clicks and impressions are search signals, not a count of all visits or enquiries. Record the date range and do not infer a trend from a single small sample.
Your next move
Fix a verified fault first.
The finding below follows your selections. It is a work order, not a grade or an automated audit of your website. Unknown steps remain questions to test.
UpOnUp / Website enquiry diagnostic
Current finding
Start with a live test enquiry.
Check whether a message reaches the intended inbox before diagnosing page performance.
Observed issues
- No issue recorded yet.
Still to verify
- Message delivery and the rest of the visitor journey.
Record for your team
No page or period entered yet.
- Run the checks above and record what you observed.
After a fix, repeat the same journey and record whether the message arrives and is answered. If the technical route works but relevant visitors still struggle, use the exact question or point of hesitation to improve the page. Keep any client outcome or uplift claim tied to measured, permissioned evidence.
A first-hand UpOnUp test
Our chat route needed a way through.
We tested what happens when the site’s chat widget cannot open. In a local build with the widget URL deliberately made unavailable, the first click reached the contact form after a six-second fallback and the form was visible. In a separate local check with the normal widget URL, the consent and chat panel opened.
The fix was then included in a production deployment. These checks demonstrated the two interface paths. They did not send an enquiry or prove that an email arrived in the inbox, and they do not describe a client outcome.
Run the separate launch checksTEST CONDITIONChat unavailable
Widget URL deliberately unavailable in a local build.
OBSERVED PATHContact form visible
First click reached the form after the six-second fallback.
LIMIT OF TESTDelivery unverified
No enquiry was sent; inbox receipt was not proved by this test.
Work from the finding
Use the guide for the actual gap.
If you have a broken path, repair and retest it. If the route works, use the evidence to decide whether discovery, the page answer or follow-up needs attention.