Navanem guide · 03.10.2026

Fix or redesign

A redesign makes sense when problems reinforce one another. Targeted fixes are often enough when structure, content and technology remain usable.

This guide helps you choose a next step.

A decision framework for targeted fixes, progressive improvement or a full redesign while preserving what already works.

Begin with a diagnosis

Separate visible symptoms from their causes. Weak conversion may come from the message, journey, speed, a form or the traffic received. Measure errors, important pages, mobile use, dependencies and the team’s publishing capacity before deciding.

Choose targeted fixes

Improve the existing site when its URLs, CMS and components remain maintainable. A short work package can address navigation, templates, performance, accessibility and calls to action. Every fix needs an acceptance criterion and a before-and-after check.

Choose progressive improvement

A staged approach works when service continuity matters and effort must be spread over time. Start with the pages carrying the most value, stabilise shared components, then migrate remaining sections. The plan should avoid leaving two inconsistent systems in place indefinitely.

Choose a full redesign

A redesign is justified when architecture blocks objectives, maintenance has become risky or content can no longer be structured properly. It requires an inventory of URLs, data, integrations, access and retention obligations.

Protect SEO continuity

Keep useful URLs wherever possible. For every change, prepare a redirect to the closest equivalent, update internal links, canonicals and the sitemap, then monitor server responses after launch. A blanket redirect to the homepage does not replace this work.

Written and reviewed by · .

Primary sources

GO TO THE SOURCE.

Related guides

KEEP GOING.