About Services Tools Blog Contact us

Technical Services Website

A multi-page marketing site for a technical contractor, with service pages, galleries, news, recruitment and an enquiry form. New content arrives as dated batches.

  • Websites & CMS
  • Water utilities
  • Website
  • Productised
  • Hybrid
  • 2026

The problem

A contractor's services, project galleries and policies were spread over old pages and inboxes. Adding a service, a privacy clause or a recruitment notice should not mean a redesign. And when a page was replaced, the earlier wording had to stay recoverable.

What it does

Each page is its own content file placed in a shared page layout, so the site loads as ordinary web pages that search engines can read. The layout carries the page titles, descriptions, search data and the enquiry form. New work arrives as a dated batch that can be compared with the previous one.

Outcomes

  • Search engines can read every service page.
  • A new range or policy is a content update and needs no rebuild.
  • News, galleries and vacancies share the same layout.
  • An earlier version of a page can be pulled up when it needs checking.

Simplified mockup

Interactive preview with sample data. Nothing is sent to a server.

Public site

Shared shell
holt-process.example/
Holt Process

Water process contractor

Mains, valves and leakage

Service pages, galleries and policies share one shell. A new drop replaces a page without a redesign.

42Live schemes
18Years in the field
6Regions covered
Rehabilitation

Scrape, reline and return a main to service.

Leakage

Night surveys and step-testing on rural mains.

Valves

Chamber repairs, lids and isolations.

Dated drops

14 Mar 2026 Live

Rehabilitation page. Adds a recruitment line and a chamber photograph.

2 Nov 2025 Previous

Original method statement. Three steps, no vacancy.

holt-process.example/rehabilitation

Live drop

Mains rehabilitation

  1. Isolate the length and warn the street.
  2. Scrape and reline, then pressure-test.
  3. Return to service and photograph the chamber.
Technicians wanted for leakage surveys this spring.

Enquiry path

From the contact page
What the shell does
Nothing is emailed

Sitemap and schema

Public addresses
PathPage
/Home
/rehabilitationService
/galleryWorks
/newsNews
/contactEnquiry
/privacyPolicy
/recruitmentVacancy
Structured data on every page
{ "@type": "Organization", "name": "Holt Process", "areaServed": "United Kingdom", "makesOffer": ["Rehabilitation", "Leakage", "Valves"] }

Titles and descriptions come from the same content file as the body.

How it works

  1. Use a shared layout for navigation, page titles and the enquiry form, which Google reCAPTCHA protects.
  2. Make each service page a separate piece of content placed into that layout.
  3. Build galleries, testimonials, news, recruitment and policy pages the same way.
  4. Publish search data and a sitemap that describe the public pages.
  5. Keep each dated batch so earlier copy can be recovered when a page is replaced.

Pipeline

flowchart LR
  Copy[Service copy] --> Shell[Shared page shell]
  Shell --> Pages[Service pages]
  Pages --> Schema[Titles and schema]
  Schema --> Forms[Enquiry path]
  Forms --> Live[Public site]