This checklist is for New Zealand builders, renovation companies, and trade contractors reviewing an existing website or planning a new one. A useful construction website should make it easy for a prospective client to understand what work fits, where the team works, what evidence is available, and what information to provide next. It should not pretend to calculate a reliable construction price from a few marketing questions.
The quick test: can a visitor understand your services, project fit, service area, proof, and enquiry process in under two minutes on a phone?
The 20-point construction website checklist
| Area | Pass condition |
|---|---|
| Service fit | A visitor can tell what work you do, what does not fit, and where you work |
| Project proof | Every project, review, credential, and result is real, current, and permitted for public use |
| Enquiry quality | The form collects enough information for a useful reply without pretending to quote |
| Mobile use | Services, proof, contact details, and the main action work on a small screen |
| Ownership and maintenance | The business knows who owns the domain, content, source files, hosting, and updates |
| Software fit | The website, estimating, quoting, job management, custom software, and workflow roles are not confused |
Score each item as clear, needs work, or not applicable. A missing proof item should stay missing until evidence and permission exist. Do not fill the gap with stock project claims, invented reviews, or generated before-and-after images.
1. Explain the work and project fit
1. Name the actual customer and job types
Use the terms customers use when deciding whether to enquire. For example, a residential builder, renovation company, commercial fit-out contractor, electrician, plumber, roofer, or landscaping contractor should not all share the same generic "construction solutions" description.
2. Separate services that require different decisions
Give major services enough space to explain the work, likely project stage, information required, and next step. Do not create dozens of near-duplicate location or service pages if the only change is a keyword.
3. State the real service area
Name the cities, regions, or travel boundaries the business actually serves. If availability changes by project size or type, explain that constraint rather than publishing a long list of unsupported suburbs.
4. Say what the business needs before it can respond
Tell the visitor whether a useful first enquiry needs a site address, project type, current stage, drawings, photos, target timing, or an existing scope. This improves the handoff without implying that the website can assess feasibility or price.
2. Make project proof inspectable
5. Use real project examples with permission
For each public project, identify what can safely be shown: project type, location at an appropriate level, scope, photos, business role, and completion status. Do not imply responsibility for work performed by another contractor.
6. Give photos enough context
A gallery should say what the visitor is looking at and why it matters. Use accurate captions and alt text. Before-and-after images need matching views and permission. Generated or stock imagery can support layout, but it is not evidence of completed work.
7. Keep reviews and credentials exact
Publish a review only with the approved wording and attribution. Name licences, memberships, awards, years in business, guarantees, or insurance only when they are current and verifiable. The Commerce Commission's guidance on accurate claims says businesses need a reasonable basis for claims about their goods or services.
8. Show process when outcome proof is not available
If written permission for construction projects is not available, explain a factual process instead: what information is collected, who reviews it, how scope changes are handled, and what the customer can expect after an enquiry. Process is useful, but it must not be presented as a customer result.
3. Improve the enquiry without pretending to estimate
9. Keep the first form focused
A practical starting form may ask for contact details, general location, project type, current stage, approximate timing, and a short description. Only collect information the business needs for the next step. New Zealand's Privacy Principle 1 says personal information should be collected only when it is necessary for a lawful purpose connected with the organisation's activities.
10. Treat uploads as a separate risk decision
Drawings, site photos, contracts, and customer records may contain personal, commercial, or security-sensitive information. Do not add uploads until storage, access, retention, deletion, file limits, and the privacy notice have been reviewed. A simple first enquiry can ask what documents are available without collecting them immediately.
11. Do not turn a marketing form into a false quote
Budget bands or project filters can help triage when the business has approved them. They are not a construction estimate. Plan takeoff, quantities, labour, materials, subcontractor inputs, overhead, risk, margin, tax treatment, and scope assumptions belong in a controlled estimating process with qualified people.
12. Explain what happens after submission
The confirmation should say what was submitted and what the next human step is. Do not promise a response time, site visit, booking, price, or project acceptance unless the business has an operating process that can support it.
4. Check the mobile and local buying path
13. Test the first screen on a phone
The business type, main service, service area, and enquiry action should be visible without waiting for animation or opening a chat widget. The navigation, language switcher, phone link, and form controls need usable labels and target sizes.
14. Keep proof and contact paths fast
Compress project images, reserve their layout space, and avoid loading a large video before the page becomes understandable. Test on an ordinary mobile connection, not only office Wi-Fi.
15. Keep business details consistent
The business name, contact details, service area, and opening or response information should agree across the website and public business profiles. If there is no public street address or fixed response window, do not invent one for search visibility.
16. Make the next action fit the page
Use descriptive actions such as "Discuss a renovation website", "Ask about project fit", or "Send a general enquiry". A builder researching estimating software should not be pushed straight into a generic automation sale.
5. Protect ownership and search foundations
17. Record who owns each website asset
Confirm ownership and access for the domain, DNS, hosting, source code, content, images, business profiles, forms, and email notifications. Record the renewal and handover path before a supplier relationship ends.
18. Give every useful page one canonical URL
Use one permanent URL for each service or guide. Internal links, sitemap entries, canonical tags, and language alternates should agree on that form. Preserve intentional redirects and keep account, checkout, admin, and other private routes out of the public index.
19. Keep structured data equal to visible facts
Schema can identify the organisation, service, article, or breadcrumb structure. It cannot turn an unsupported service area, rating, price, credential, or project result into a fact. Everything in structured data should be visible or traceable to an approved source.
20. Plan maintenance before launch
Decide who updates services, project examples, team details, credentials, and contact information. After a release, verify the live page, sitemap, robots policy, canonical, language alternates, structured data, and key internal links. Search performance should then be reviewed over a meaningful period rather than judged from a single week.
Website, estimating, quoting, job management, or workflow
These tools solve different problems. Start with the broken stage, not the technology label.
| Immediate need | Start with | BestAI boundary |
|---|---|---|
| Explain services, show authorised proof, and collect better enquiries | A construction website | Website delivery is the commercial path |
| Measure plans or build labour, material, subcontractor, overhead, and margin costs | Specialist construction estimating software | BestAI is not estimating SaaS and should not replace this layer |
| Turn an approved estimate into a customer quote and track acceptance | Quoting or job management software | Use an existing product first; assess a narrow gap only if it remains |
| Schedule jobs, compare actual costs, invoice, and hold the financial record | Job management and accounting software | Keep the operational and financial systems of record with their named owners |
| Fill one defined requirement that suitable products do not cover | Focused custom software | Confirm the scope, source data, owner, permissions, and acceptance checks before building |
| Move approved information between inboxes, documents, people, and systems | A bounded workflow automation | Check native features first, then define approvals, exceptions, verification, and a separate live-use decision |
If takeoff or cost build-up is the main need, use the New Zealand construction estimating software guide and test specialist products against representative completed jobs. If the gap is online discovery, review BestAI's website building service and public website portfolio. If a narrow business tool or repeated handoff remains, compare custom software with the Digital Employee workflow method.
The public proof available from BestAI
BestAI's Website Building page links to live website work that is already approved for public display. The Rehab Studio website case study is an authorised example of website delivery and an owner update workflow. It is a healthcare project, not construction-sector proof, and no construction outcome should be inferred from it.
Construction-specific customer names, screenshots, quotations, rankings, lead results, or performance outcomes should remain unpublished until BestAI has written permission, a verified scope, and evidence that supports the exact claim.
Next step
Run the checklist with the person who answers new enquiries and the person responsible for website updates. If the main gap is the website, send a website enquiry with the current URL and the first three items that need work. If the main gap is takeoff or cost build-up, shortlist specialist estimating software. If the gap is a repeated handoff after the estimating decision, map one bounded workflow.
This checklist provides general website and operational guidance. It is not construction, quantity surveying, engineering, legal, tax, accounting, privacy, or health and safety advice.