The classic WordPress handover failure: a beautiful builder page, edited once by the client, never beautiful again. The cure isn’t training videos — it’s structure. WordPress custom post types and custom fields separate content from design so clients edit data, not layouts.
The principle: content as data
Team members, services, case studies, locations, testimonials — these aren’t “pages”, they’re records with consistent parts (name, photo, role, blurb). Model each as a custom post type with defined fields, design the template once, and every entry the client adds inherits the design automatically. Nothing to break, nothing to misalign.
What this looks like in practice
- Case studies: fields for client, sector, challenge, result metrics, gallery. The template arranges them; the marketing exec just fills in boxes. (This site’s own case studies follow exactly this philosophy.)
- Services with local pages: service CPT × location CPT generates consistent, SEO-friendly combinations without cloning pages.
- Team page: add a person, they appear everywhere they should — correctly formatted, automatically ordered.
Tooling: ACF, Metabox or CMB2
All three do the job; ACF’s ecosystem and UI make it the default for agency work, while CMB2 suits leaner code-first builds. The tool matters less than the discipline: field groups documented, naming consistent, templates rendering fields rather than hardcoding content.
Why agencies should care commercially
Structured builds cut support tickets (“the homepage broke again”) to near zero, make content migrations scriptable, and let non-technical client teams publish confidently — which is what clients think they’re buying when they say “easy to edit”. It’s also what separates a £1,500 build from a £4,500 one, and clients pay the difference happily once they’ve lived the alternative.
Want your next build client-proof — or an existing site restructured? Let’s scope it.
