Eight tests for whether a contractor website is helping the work or hiding it.

Clarity supported by proof. A buyer should understand what the contractor builds, where the firm works, and whether the project level fits within one screen, then immediately see evidence that supports the claim. A perfect gallery cannot rescue unclear positioning, and a strong headline cannot rescue weak work. Start with the relevant finished project and a precise proposition. Every later section should reduce a real uncertainty about fit, trust, process, or contact.

Use the smallest structure that answers distinct decisions. A focused company may need a homepage, projects, services, process, about, and contact. Add individual service, project, or location pages when each contains unique proof and analysis. Do not buy page count as a proxy for search quality. Ten thin pages are weaker than five useful ones. Map every page to an intent, a buyer question, a body of evidence, and contextual internal links.

Enough to explain several representative jobs without repetition. Each featured project should include an establishing view, craft or material details, and images that clarify the delivered scope. A coherent story with six to ten strong images can outperform a large mixed gallery. Remove duplicates and images that are hard to read on a phone. The standard tests whether a buyer can understand judgment and range, not whether the media library reaches an arbitrary count.

Use signals tied to the buyer's risk: specific reviews, named ownership or team responsibility, licenses where relevant, insurance, warranties, associations, project process, communication expectations, and real contact details. A logo wall without explanation does little. Choose reviews that mention site care, schedule, crew conduct, responsiveness, and follow-through. Every trust signal should be attributable and visible. Never invent ratings, customer counts, awards, or testimonials to fill a layout.

Detailed enough to improve the first response, short enough to finish on a phone. Ask for project type, location, budget band, timing, readiness, and optional photos when those variables change fit. Explain why the information helps. Use a separate route for maintenance or support if those inquiries differ. Do not make a serious prospect reproduce a full scope of work before speaking to anyone. Qualification should reduce wasted calls, not create a status test.

Pages are useful when they combine real demand, relevant proof, distinct market or site conditions, accurate service coverage, and buyer guidance that cannot be copied onto another location. A page for every suburb is not a strategy. Start with one core market page and service pages. Use Search Console impressions, customer demand, and project evidence before expanding. Keep city and community terminology accurate and never imply offices or completed work that the contractor cannot substantiate.

Aim for Google's good Core Web Vitals thresholds: LCP at or below 2.5 seconds, INP at or below 200 milliseconds, and CLS at or below 0.1 at the 75th percentile. The practical design rule is simpler: the headline and poster should appear before video, layout should not jump, and the inquiry should respond immediately. Optimize images, load motion after critical content, keep JavaScript limited, and test on a real phone connection.

The contractor should control the domain and have a documented right to the finished content, media, design deliverables, and working website agreed in the contract. Platform software may remain licensed and some hosted builders do not expose source code. That can be acceptable if the tradeoff is understood. The unacceptable state is ambiguity. Record account owners, renewal contacts, exports, backups, hosting, analytics, maintenance, and what happens when the provider relationship ends.

Update when something material changes: services, area, team, contact details, pricing, process, reviews, credentials, platform facts, or the body of work. Add strong completed projects when they improve the proof, not on a fixed content treadmill. Review core pages and external claims at least periodically, and monitor forms, links, analytics, and search performance. A static site can remain technically current through deployments; content freshness should reflect reality rather than an automatic date change.

Open it on a phone. Identify the work and service area, inspect three project stories, locate the person responsible, read two specific reviews, test the inquiry, check whether important text exists without interaction, and note any layout movement or obstruction. Then confirm the domain and account ownership. Mark each of the eight Coxswain dimensions Critical, Weak, Adequate, Strong, or Best in class. Fix the first commercial break, not the easiest cosmetic detail.