Before redesigning a website: identify the problem being solved
“We need to redesign the website” can be an accurate diagnosis.
It can also be an elegant name for very different problems: hard-to-find content, duplicated pages, unclear journeys, fragile performance, an unmanageable backend, inconsistent identity or a commercial process the website can no longer support.
Before choosing a new layout, identify which of those problems is real.
Design is not always the starting point
A redesign makes sense when it clarifies what a website needs to explain or enable. But when the problem sits in data, workflows or editorial structure, changing the surface alone can make the same confusion look more polished.
Useful early questions are simple:
- which pages genuinely matter and which exist by habit;
- what people look for before contacting, buying or applying;
- which content changes most often, and who changes it;
- where the website forces the same data to be duplicated;
- which integrations, forms or processes depend on it;
- what fails on mobile, in accessibility or in performance;
- which elements should remain because people already recognise them.
They are not prompts for an endless workshop. They are the fastest way to avoid rebuilding the same thing twice.
Inventory before inspiration
An audit of pages, templates, search, forms, redirects, analytics and content often reveals a less dramatic problem than “an old website”, but a more useful one to solve. Sometimes the answer is simplification. Sometimes it is structuring content that currently lives in many pages. Sometimes it is keeping the visual system and improving performance, language or conversion paths.
On the CGM Consulting redesign, the corporate website was connected to dynamic service, recruiting and communication content: job templates, structured fields, Google Jobs data, SEO, analytics and visual materials. The value was not a new background. It was making the digital presence more coherent with work that needed to keep evolving.
The boundary between restyling and redesign
A restyle can be right when architecture, content and functions are still sound. A redesign is needed when hierarchies, data, roles or flows must change too.
Confusing the two creates impossible expectations: asking a new homepage to fix a backend nobody can update, or asking a new plugin to fix a brand promise that was never clarified.
In the FacileAutoRicambi case, e-commerce restyling was accompanied by SEO, performance, tracking and management components because growing enquiries and operational work could not be treated as separate problems.
The better question
Before asking how a website should look, ask what it should make easier, for whom, and how you will know it is working.
From there, it becomes possible to decide whether the work needs an advanced WordPress website, a technical review, a new editorial system or a more focused intervention. The best result is not a website that looks newly launched. It is one that stops obstructing the people who use and maintain it.