A Tradie Website Checklist for Better Enquiries

Make the service obvious before asking for an enquiry

Read the first screen as if you were a new customer. It should explain the trade, the work offered and the real coverage area. A statement such as ‘quality solutions you can trust’ gives someone little help choosing between businesses. A clear description of the job is more useful.

Separate services when the customer’s questions differ. An electrician’s switchboard upgrade page may need to explain access, assessment and disruption. A lighting installation page may need information about choosing fittings and supplying plans. Use normal customer language and explain any terms that matter to the decision.

• Name the service and who it is for.
• Explain genuine service coverage and availability.
• Show the next step and what information to prepare.

Show evidence that relates to the job

Choose a few real projects that resemble the work you want to win. Explain the original problem, what you delivered and any constraints that shaped the work. Before-and-after images are useful when the difference is visible and you have permission to publish them.

Keep testimonials attributable and accurate. List relevant qualifications or licences only when they are current and applicable. Avoid exposing a customer’s address, documents or other private information in project photos. A small, credible portfolio is more useful than a large gallery of stock images.

Make a quote request easy on a small screen

Test the website at ordinary phone size without zooming. The text should be readable, controls easy to tap and contact details easy to find. Check the actual phone and email links. Submit a test enquiry with the team’s knowledge and confirm it reaches the right person.

Ask only for information needed to take the next step. Service, approximate area, a short description and contact details may be enough. Photos can help for some jobs, but should not be mandatory unless the team truly needs them. Explain what the customer should expect after submitting.

Include search foundations in the build scope

Ask for descriptive page titles, one clear main heading, useful page addresses and links between related services and projects. Important text should be available as text rather than embedded only in images. Request a sitemap and confirm public pages are available to search crawlers.

For a replacement website, inventory the existing pages before changing addresses. Map important old URLs to relevant replacements and test the redirects at launch. Keep domain and email access in the launch plan. Rebuilding a site should not accidentally remove a useful page or interrupt customer emails.

Agree who owns the work after launch

Your brief should distinguish the website build from ongoing hosting, maintenance, content and SEO. Ask who can update project examples, how backups and software updates are handled, and what happens if you change providers. Record any recurring subscriptions and third-party licence costs.

Compare proposals using the same service list, content responsibilities and enquiry requirements. A lower quote may cover less work; a more expensive one may include features you do not need. Choose the smallest scope that answers customer questions well and supports the team receiving the enquiries.