A redesign or a targeted fix? | True Measure Web Design

Start with a specific visitor problem and what you want to preserve. A single symptom does not tell you whether the whole site needs replacing.

Separate a failure from a change in direction

A link going to the wrong page is a different starting point from an offer that no longer describes the business. Write down the behavior that fails, the information that is wrong and the visual decisions you want to revisit.

A website can look dated and still contain useful material. A new-looking page can leave someone uncertain about what is offered. Review the purpose, the content and the actual behavior separately before deciding the scale of work.

A targeted repair may address a specific difficulty while preserving useful content. If a necessary change reaches across the platform, the content and the way the business operates, a rebuild becomes a more serious option. The distinction comes from inspection, not the age of the site alone.

Record one example someone else can check

Name the page and the action you tried. Add what you expected, what happened and where you noticed it. If the problem happens only sometimes, say so rather than turning a partial observation into a universal claim. You do not need to diagnose the implementation yourself.

For a content problem, point to the section and the visitor question it does not answer. “The services page lists work we no longer offer” gives a clearer starting point than “The website feels wrong.”

A fictional contact problem

“On our phone menu, Contact opens an outdated page. The desktop link is correct. We want the phone link to reach the current contact details, while keeping the rest of the site.”

This defines an observation and a desired result. It does not establish the cause, price or whether other problems exist.

Agree what changes and what stays

List the parts that still serve a purpose: useful words, authentic photographs, page addresses and working contact routes. Record the evidence you have, such as links staff send or pages customers mention. If you lack traffic records, say so rather than inventing a performance story.

Before changing anything, save a recoverable copy where possible and make an inventory of important pages, files and services. Ask what a repair would solve, what would remain, how it would be tested and what finding would change the recommendation. Where a rebuild is appropriate, compare it against the same needs.

Where page addresses change, agree the mapping, testing and monitoring. Google’s site-move guidance covers that technical work; it does not recommend a rebuild for every site.

Suspected security problems, lost account access and unsupported components need qualified investigation. A new visual design alone does not establish that the underlying issue is resolved. An audit has a stated scope, not a guarantee that every problem has been detected.

Scope and price belong in the project discussion. This prepares a conversation, not a remote diagnosis or a promise that a small repair is sufficient. We agree the work and price before starting.

Put it into practice

Use Map your pages before a website redesign to record useful material. For a contact problem, use Test your website’s inquiry path. Keep the concrete observation and the material you want to preserve together.