What a contractor's website actually needs

Most contractor sites fail for the same reason: they look fine but don't do anything. A truck-wrap photo, a paragraph about "quality craftsmanship," and a contact form with seven fields is not a website strategy.

One clear service per page

If you do foundations, seawalls, and excavation, each service needs its own page with real project photos, plain-language scope, and a call-to-action above the fold. One generic "Services" page doesn't rank and doesn't convince.

Service area pages for every town you work in

Homeowners search "[service] + [town]." A page that says you serve Lawrencetown, Dartmouth, and Bedford gives Google something to match. Copy-paste town names into one paragraph doesn't count — each page needs unique proof and local context.

Speed and accessibility aren't optional

Builder templates load dozens of scripts on a single page. On mobile, over a job-site connection, that means bounces. A static site with optimized images, one deferred script, and contrast that passes WCAG isn't vanity — it's whether someone can read your phone number at noon in bright sun.

A short form that respects the buyer

A ground-screw contractor doesn't need your mailing address on first contact. Name, phone, project location, and a sentence about the job is enough. Every extra field filters out people who were ready to call.

Structured data Google can read

LocalBusiness schema, a sitemap, canonical URLs, and meta that matches your Google profile — this is the plumbing that gets you into rich results. It's included in every build I do, not sold as an add-on after launch.