An older-looking website does not automatically need a complete rebuild. Start by identifying the task that feels difficult for a visitor and the part of the site responsible for it.
Check the message first.
Can someone unfamiliar with your business explain what you offer after reading the opening section? Can they tell whether the service is relevant to their situation?
If those answers are unclear, rewrite the introduction and service descriptions before deciding on a new visual direction. A new layout can present a message more effectively, but it still needs a specific message to present.
Follow one complete journey.
Choose a realistic task: understand a service, inspect an example, find the price, and enquire. Try it on a phone as well as a desktop screen.
Note where information is missing, where labels are confusing, and where a button takes you somewhere unexpected. Separate those observations from personal preferences about colour or style.
Match the size of the work to the problem.
| What you observe | A useful starting point |
|---|---|
| Accurate services, vague headings | A focused copy and hierarchy review |
| Useful pages, inconsistent presentation | A visual system and layout update |
| Difficult navigation or repeated pages | A structure and content review |
| Broken forms or mobile layouts | An implementation review |
| A substantially different business or offer | A broader website brief |
These are starting points for discussion. A technical review may reveal dependencies that change the scope.
Compare two illustrative situations
A focused update: A consultant’s services and contact form still work, but the homepage describes an old offer. Updating the introduction, service copy, and related links may address the immediate problem without changing the whole site.
A broader rebuild: A business has moved from one service to several, and visitors can no longer find the right offer. A revised page structure and navigation may be needed alongside new content and layouts. Review the existing implementation before choosing what to retain.
These examples illustrate differences in scope; they are not client case studies.
Keep what already serves the visitor.
Record useful content, working forms, important URLs, and existing integrations before changing them. Agree how they will be preserved or replaced.
A good redesign brief explains the problem, the desired behaviour, and how the revised site will be checked. That makes the work easier to assess than a request to make the site feel more modern.
