Programmatic Web Development for Trades & Home Services — The Practitioner’s Playbook.

SectionThe honest reframe most agencies won't tell you

Most trades and home-services websites are built like printed leaflets pinned online. A homepage, an About, a single Services page that lists "Electrical, Plumbing, Heating" in three short paragraphs, and a Contact Us form that nobody picks up under an hour. Then the agency wonders why the site doesn't appear in the local pack and why the leak buyer in BH8 typing "emergency plumber near me" calls the competitor instead.

Trades and home services is a postcode-by-service, mobile-first, emergency-driven buying journey. The buyer searching "boiler engineer BH9" is not the same buyer as "roof leak BH9" — different urgency, different qualification, different regulator, different objection. Treating them all as one audience with one Services page is exactly why brochure-style trade sites convert at 2–5% and properly-built sites convert at 9–14%.

This playbook fixes the structure. It is not about a redesign — it is about service × postcode programmatic architecture, real-job photography with the right schema, trade-association markup that Google and the buyer both look for, and a mobile journey that puts the call button under the thumb. Read it, run it yourself, or hand the build over on retainer.

SectionThe eight-point audit we run on day one

Score your own site red / amber / green this week.

1. Service × postcode programmatic page set with LocalBusiness schema — One indexable page per service × postcode area you actually cover (e.g. /electrician-bh8/, /emergency-plumber-bh9/, /roofing-bh10/), each with its own LocalBusiness JSON-LD block referencing the service area, area-specific testimonials, and area-specific job photos. This is the single biggest organic lever in the category and the most-skipped one.
2. Per-service pillar pages with Service schema — A separate, indexable, schema-marked pillar page for every distinct service you offer — emergency plumbing, boiler installation, rewiring, fuse-board upgrades, EICR, roof repairs, full re-roofs, glazing, lock replacement, and so on. Each with its own Service JSON-LD, FAQ schema, real-job gallery, and quote form. Services pages aren't a content exercise; they are the indexable surface area.
3. Trade-association schema in JSON-LD — NICEIC, Gas Safe, FENSA, NAPIT, Trustmark, MasterBond and OFTEC memberships referenced inside Service.provider.identifier and a footer trust strip with inline-SVG logos rather than lazy-loaded images. Google reads it; the buyer trusts it. Most trade sites declare the badge visually and miss the structured-data layer entirely.
4. Real-job photography library with ImageObject + contentLocation — A growing library of real install / repair / before-and-after photos, each with ImageObject schema carrying caption, creator, dateCreated and contentLocation. Stock photography tells Google you don't do the work; tagged real-job imagery tells Google you do.
5. Click-to-call CTA above the fold + sticky on mobile — Phone number wired to tel: link, visible without scrolling on mobile, plus a sticky bottom-of-screen call bar on phones. For emergency categories the click-to-call CTA outconverts every form on the page; if it isn't sticky on mobile you are leaving paid traffic on the table.
6. Quote-form with photo-upload + postcode routing — A quote form that accepts a phone-camera photo, asks for the postcode, qualifies on trade-specific fields (boiler make + age, property type, supply type), and routes to the correct on-call trade by postcode. Photo-uploaded leads close 1.5–2× higher because the trade can pre-quote without the on-site survey.
7. Per-engineer Person schema where named — If you publicly name engineers, surveyors or directors on the site, mark them up with Person schema referencing their qualifications and trade-body identifier. Increases entity authority for Google and converts on the buyer's "is this a real person who'll turn up" question.
8. Mobile CWV under 2.5s LCP on the converting page — LCP under 2.5s, INP under 200ms, CLS under 0.1, specifically on the page where the buyer converts (the postcode service page or the quote form), not just on the homepage. Mobile is 70%+ of trades traffic and emergency buyers don't wait for a 6-second hero video to render.

Three or more reds — fix the foundation.

SectionSix productised deliverables we ship per cycle

Service × postcode programmatic page architecture. One indexable page per service × postcode area you cover, generated from a single template and a structured data set, each with LocalBusiness schema, area-specific testimonials, area-specific real-job photos and a postcode-aware quote form. For a six-service trade covering fifteen postcode areas this is ninety indexable pages from one template, vs. one Services page in a brochure build. Time to first signal: 30–60 days. Owned by you, exportable to Notion + PDF.

Per-service pillar pages with schema. A pillar page for each distinct service — emergency plumbing, boiler service, EICR, rewiring, roof repair, full re-roof, glazing, lock change, and similar — each with Service + FAQ schema, internal-link structure to the supporting postcode pages, real-job gallery and a service-specific quote form. The pillars rank on the unmodified head term; the postcode pages rank on the long-tail; together they form the indexable engine.

Trade-association schema + footer trust strip. NICEIC, Gas Safe, FENSA, NAPIT, Trustmark, MasterBond, OFTEC where applicable, declared in JSON-LD Service.provider.identifier on every page plus a footer trust strip rendered as inline SVG (no late-loaded images that drop CLS). The combined effect is a measurable lift in SERP click-through and a hard increase in the buyer's trust at the conversion moment.

Real-job photography programme. A monthly cadence of real install / repair / before-and-after photos, processed and uploaded with ImageObject schema (caption, creator, dateCreated, contentLocation), tagged with the service and the postcode, and surfaced on the relevant programmatic pages. Time to first signal: 14 days for newly tagged imagery to appear in Image search.

Quote-form with photo-upload + postcode routing. Phone-camera photo upload, postcode field, trade-specific qualification fields, postcode-based routing to the correct on-call trade in your CRM, post-submit SMS confirmation to the buyer with a one-tap call-back link. The structural form change typically lifts quote-to-job conversion 30–50% in cycle one.

Mobile CWV + click-to-call optimisation. LCP under 2.5s, INP under 200ms, CLS under 0.1 on the converting page, plus a sticky click-to-call bar on phones, plus Lighthouse CI in your build pipeline so future deploys can't regress these without you noticing. Hosting on managed WordPress (Kinsta, WP Engine or Pressable depending on traffic and budget) with Cloudflare in front of it is the default configuration.

SectionWhat to do this week

Three actions, ranked by leverage. Same first three steps we ship in week one of a Foundation retainer for an electrician, plumber, roofer or boiler engineer.

1. Run mobile Lighthouse on your quote-form page. Owner: marketing manager or developer. Time: 5 minutes. Note the LCP, INP, CLS scores. If any sits in orange or red, this is your highest-leverage fix. The quote-form page is where the budget converts; it has to be the fastest page on the site, not the slowest.
2. Count your service × postcode pages. Owner: founder. Time: 15 minutes. Open your site, count separate, indexable pages per service × postcode area you actually cover. If you offer six services across twelve postcode areas you should have around seventy-two indexable pages. If you have one combined Services page, you are undershooting by an order of magnitude on indexability and the local pack will reward your competitor for it.
3. Decide DIY, DWY or DFY for the next 90 days. Owner: founder. See the three ways.

SectionFive questions electrician / plumber / roofer operators ask us about web development

WordPress vs a DIY-builder like Wix or Squarespace — what's right for a trade? WordPress for the vast majority. The plugin ecosystem (Yoast or RankMath for SEO, Schema App or Schema Pro for JSON-LD, WP Rocket for caching, Cloudflare for the edge, Gravity Forms or WS Form for the photo-upload quote form) is unmatched, the team is hireable everywhere and the programmatic page generation we run on it is straightforward. Wix and Squarespace ship a clean homepage but cap out fast: limited schema control, limited programmatic generation, no proper version control, no rollback, brittle on Core Web Vitals at scale. They look fine for ten pages and break for ninety.

How many postcode pages do we actually need? Count the postcode areas you genuinely service (not the radius your van will drive in an emergency) and multiply by your distinct services. A six-service electrician covering BH1 through BH25 is 150 postcode-area pages. Most operators we audit have between zero and four — which is why their competitor with a programmatic build is sitting in the local pack on every postcode query.

How often do we need to add real-job photos? Ten to twenty new tagged photos a month is the canon for most trades. We supply a one-page photo SOP for the engineers — rough framing, before/after pairs, postcode tag, no faces of customers without consent — and a dropbox folder that ingests automatically into the CMS with ImageObject schema attached. The compounding effect on Image Search and on trust on the postcode pages is significant within 60–90 days.

Does a photo-upload quote form actually lift conversion? Yes, materially. Photo-uploaded leads in this category close 1.5–2× higher than no-photo leads because the trade can pre-quote off the photo without doing an on-site survey, which removes the highest-friction step in the buyer journey. Particularly impactful for roofing, exterior work, repairs and visible electrical issues. The lift typically shows in the first cycle.

Can we run this ourselves with the playbook + £750 audit? Yes. The full programmatic page architecture, schema deployment, trust-strip footer, photo programme and CWV tuning is shippable in-house with a marketing manager plus one developer for a focused half-week per cycle. The £750 audit gives you a written red/amber/green of all eight points plus named-owner / dated next steps and a list of the schema gaps to close. Credit toward the first cycle if you sign for DWY or DFY within 30 days.

SectionWhere to go from here

If you want this shipped end-to-end on a productised retainer, book a 30-minute discovery call.

If you'd rather have a senior practitioner reviewing your team's build each week, the coaching plans start at £750/month. If you have a hard deadline — a service-area expansion into a new set of postcodes, or a post-storm-season demand surge that will break the current site — the two-week embedded sprint lands a senior practitioner inside your stack for ten working days at £3,000 fixed.

Or run it yourself. Eight-point audit + one deliverable a month + twice-quarterly office hours.