Start your redesign by modelling content as fields: what a case study always contains, what a service page always answers, who updates each and how often. Do that first and the design phase gets faster, the CMS stays usable, and the same content can power your website, your proposals, and AI answers without a rewrite. Start with the look instead, and you'll spend month six fighting your own layouts.
Where redesigns go wrong
The classic failure sequence runs like this. The team picks a look. The build starts from the homepage down. Somewhere around week six, the real content arrives and doesn't fit: headlines too long for the hero, case studies that each need a different layout because nobody ever agreed what a case study contains, a services section where every service was written to a different shape. The design flexes to accommodate, the system fragments, and six months after launch the editors are fighting the design instead of publishing. Design debt is visible in the mockups. Content debt is invisible until it's expensive.
What structured content means in practice
Structured content is the difference between a page stored as one big rich-text blob and a page stored as named fields. A structured case study isn't a document; it's a client, a sector, a problem statement, the work delivered, an outcome with numbers, a pull quote, and credits. Once the substance lives in fields, the layout becomes a decision you can change later, and the same case study can render as a full page, a card in a grid, a slide in a proposal, and a quotable claim in an AI answer, all from one source. Taken to its architectural conclusion, that's what a headless CMS is.
Model the content first, and the visual layer lands faster and lasts longer.
Why the machines care too
Search engines and answer engines consume structured data, not aesthetics. A page whose facts live in labelled fields (the price, the timeframe, the outcome number) is a page a machine can lift claims from cleanly and attribute to you. A page where the same facts are woven through designed prose gets skimmed and skipped. As more buying journeys start with a question to an assistant, the structural decision you make in the CMS quietly becomes a visibility decision. This is the least discussed reason structured content pays for itself.
The four modelling questions
Before any design work, answer four questions per page type. What entity is this page about: a service, a project, a person, an idea? What fields does it always have, and which are optional? What question does it answer for a visitor, in one sentence? And who updates it, how often? Write the answers down for every page type on the site. That document is your content model, and the design brief largely writes itself from there, because every layout decision now has something concrete to lay out. That one-question discipline is the heart of liftable content.
Who this helps on an ordinary Tuesday
The daily beneficiary is whoever publishes. In a structured CMS, adding a case study means filling in fields, and the design takes care of itself; nobody needs a designer to ship content, and nobody can accidentally break the layout with an ambitious paste. Consistency stops being a discipline problem and becomes a property of the system. That's what keeps a site looking designed in year three, long after the launch team stopped watching.
A practical starting point
List your ten most valuable pages. For each, split the content into fields you'd want to reuse elsewhere: the one-line summary, the proof points, the FAQ, the credits. If a piece of content only makes sense on one page, it's layout. If it repeats across pages, it's a model. This single exercise, an afternoon with a spreadsheet, usually removes half the surprises from a rebuild and most of the arguments from the design phase.
To be fair to the blob: not everything deserves a model. One-off pages, editorial essays, and genuinely bespoke moments are fine as free-form content, and over-modelling is its own disease, producing CMSs with forty fields nobody fills in. Model what repeats. Free the rest.
If you're briefing an agency, ask to see the content model before you approve a design direction. An agency that can't show you one is planning to discover your content problems on your budget, in month six, when they're most expensive to fix. Our website relaunch guide walks through the whole sequence, content model first.
