Summary: Follow the evidence through four stages: the visitor, the page, the enquiry and the response. Check tracking and delivery before assuming the website needs a redesign. Use the test log below to locate the first broken step.
A tradie website not getting leads does not always have a traffic problem. It may have a broken form, the wrong visitors or an enquiry sitting somewhere nobody checks. Buying more clicks before finding the failure can make the numbers look busier while the diary stays quiet.
The quickest useful diagnosis follows one real journey. Start with a service you want to sell, arrive on the relevant page as a customer would, and keep going until someone at the business receives the enquiry.
First, check what “no enquiries” means
Are there genuinely no calls or messages, or is the reporting system failing to record them? Ask whoever answers the phone. Look at the actual inbox. Check form records and any messages received through the website.
A click on a phone button is not proof that a call connected. A thank-you page view is not always proof that a useful enquiry was submitted. Decide what you are counting and name it accurately.
Use separate figures for website visits, contact actions, received enquiries and qualified enquiries. You do not need complicated software to distinguish those events; even a short manual log can expose an assumption.
Check whether the visitors want your work
Look at the pages receiving traffic and the search queries available in Search Console. Are people looking for your service in an area you cover, or reading general information with no need to hire anyone?
A fictional electrician may attract visitors to an article about changing careers while their switchboard-upgrade page receives little attention. That is not evidence that the upgrade page fails to convert. The traffic and the commercial question are different.
Also check whether old pages advertise services you no longer provide. A convincing page for an unavailable service can create enquiries that will never become suitable jobs.
Write down the intended visitor for the page: job type, area and stage of the decision. Then assess whether the content serves that person.
Find the first unanswered question
Ask somebody unfamiliar with the business to open the page on a phone. Give them a realistic task and watch without coaching.
Can they identify the service? Can they tell whether their area is covered? What makes them confident enough to contact the business? What do they think happens after pressing the button?
Useful observations sound like “I cannot tell whether you take small jobs” or “I thought this was only for builders”. They are more actionable than “the website feels old”.
Fix the missing explanation close to where the decision happens. If the uncertainty is about coverage, a new colour scheme will not answer it.
Use this symptom-to-test table
| Symptom | First test | What it can reveal |
|---|---|---|
| Visits appear in reports, but nobody contacts you | Review landing pages and available search queries | Traffic may not match the work you want |
| Customers say the form failed | Submit it on the same type of device | A field, upload or validation problem |
| Form shows success, but inbox is empty | Compare submission records with delivery | Broken routing or notification |
| Calls arrive, but callers want different work | Review the page’s service wording | An unclear or outdated offer |
| Enquiries are suitable but go cold | Check response ownership and timestamps | A follow-up problem after conversion |
| Mobile visitors struggle | Test layout, loading and interactions | A usability or performance obstacle |
Treat each finding as a hypothesis until the test supports it. Several symptoms can coexist, so start with the earliest confirmed failure.
Run one complete dummy enquiry
Use a name and contact details you control. Label the submission as a test so nobody books a job or contacts an unrelated person.
Record these checkpoints:
- Page opened: correct service page, device and time.
- Form completed: required fields, error messages and upload behaviour.
- Confirmation displayed: clear success or a useful error.
- Submission stored: visible in the intended system.
- Notification received: delivered to the correct person or shared inbox.
- Reply sent: the business can actually respond through the expected channel.
Here is a fictional result: the form is stored correctly, but the notification goes to an old email address. The fix is routing and ownership. Replacing the hero image would leave the failure intact.
Repeat the test after the repair. Do not assume changing a setting fixed the entire journey.
Remove friction without removing useful information
Ask for the details required to decide the next step. A service, suburb and short description may be more valuable initially than a full project specification.
Make labels and errors clear, preserve entries after a mistake and explain what happens after submission. These align with the W3C’s accessible forms guidance. A form that is easier to understand helps more than just visitors using assistive technology.
For page performance, distinguish loading speed, responsiveness and unexpected layout movement. Those are the areas covered by Core Web Vitals. A technical report can help your developer investigate, but it cannot tell you whether the service description makes sense.
Do not change five things because one test failed. Repair the confirmed obstacle, then observe the result.
Measure a useful outcome
For the next reporting period, record qualified enquiries and what happened to them. Keep the definition stable: for example, a genuine request for work you provide, in your area, with enough information to respond.
Note when campaigns, availability or seasonal demand change. An increase in enquiries immediately after a redesign does not prove that the redesign caused all of it.
If the website works but the enquiries still do not suit the business, return to targeting and the offer. If the enquiries suit but replies are slow, work on the process after the form.
For help with the website side of that journey, explore Tradie Local’s smart functional websites.
