A website can look dated and still have a useful structure. Another can look polished while hiding the services customers actually need. Before buying a redesign, name the problems you can observe and decide whether focused changes can solve them.

A refresh generally improves parts of the current site. A redesign changes the experience more substantially; a rebuild may also replace the underlying platform or code. These are practical project labels, not fixed industry packages. Ask a provider to define what each means in the proposal.

01

Diagnose the problem before naming the project

Write down where customers get stuck. Is the offer unclear on the homepage? Are service details missing? Does the contact form fail? Does the mobile menu cover important information? A single broken component or missing explanation may not justify replacing the whole site.

Separate measured or observed problems from preferences. “Three customers asked whether we serve Pasadena” points toward a content or navigation fix. “I dislike the color” is a valid design preference, but it does not tell you whether the structure or technology must change. Both matter, for different reasons.

Use the lead audit to locate a weak step in the visitor journey. Website Not Generating Leads? A Practical Audit.

02

Choose a focused refresh when the foundation works

A refresh is plausible when the site is maintainable, the main pages still represent the business and the issues are contained. You might revise a headline, improve service explanations, update genuine photos and fix form labels or delivery. Define the exact pages and acceptance checks so “refresh” does not become an endless list of small requests.

Check the real constraints first. If the platform makes simple changes unusually risky or the content model cannot represent the current business, a patch may cost more over time than a planned rebuild. Ask the person who maintains the site to show the tradeoff rather than relying on appearance alone.

03

Consider a redesign when the journey or structure has changed

A broader redesign can make sense after a major change in services, audience or brand, or when pages and navigation no longer match customer questions. It may also be needed when mobile use, accessibility or integrations are difficult to repair within the existing implementation. Define what the new experience must let people do, not just how different it should look.

If existing pages are public, inventory their URLs, content and search data before removing anything. Keeping a useful URL is often simpler than changing it. Where a move is necessary, plan relevant destinations and test them after launch. Google says significant URL changes can cause temporary search fluctuations while pages are processed.

Plan the URL and content handoff before replacing an existing site. Website Redesign SEO Checklist: Protect Useful URLs.

04

Run a small decision exercise

Choose one important customer task and try to complete it on a phone. Record the exact obstacle, the pages involved and the smallest credible fix. Repeat for your top services and the contact path. If most obstacles are isolated, price the targeted fixes. If the same structural problem appears across the journey, scope a redesign.

Ask providers for both an immediate stabilization plan and a longer-term recommendation when the site has urgent failures. A broken form should be fixed promptly even if a redesign is later approved. Agree on what success looks like for the chosen scope, then check it with a real test rather than a screenshot review alone.

Use a full submission test when the inquiry path is one of the symptoms. Contact Form Checklist: Make Business Inquiries Work.

Summary

The practical takeaway

Buy the smallest scope that solves the documented customer problems. Broaden it when repeated structural or technical limits make focused fixes ineffective.

Free download · No email required

Refresh versus redesign decision sheet

A problem-first worksheet for scoping the next website project. Walk through the current site as a visitor. Record observed obstacles, not only preferred visual changes.

Download worksheet
Preview the worksheet
  • Customer task tested: ____________________
  • Device and page used: ____________________
  • Observed obstacle and evidence: ____________________
  • Business impact or customer question: ____________________
  • Smallest credible fix: ____________________
  • Can the current platform support that fix? ____________________
  • Pages or workflows affected by the same issue: ____________________
  • Existing URLs and content worth keeping: ____________________
  • Immediate failure to stabilize now: ____________________
  • Refresh scope and acceptance test: ____________________
  • Redesign scope and acceptance test: ____________________
  • Decision, owner and date: ____________________

Sources and further reading

Prepared with AI assistance using the linked primary sources and original planning worksheets. Examples are illustrative, not JNS client results. Platform rules can change; check the linked guidance before making account changes. This guide does not promise rankings, traffic or legal compliance.