When should you redesign your website?

Begin with an observable problem, not the age of the theme. A prospective customer cannot distinguish two services; an editor cannot publish a required page without a developer; keyboard users cannot reach a form; or an unsupported component prevents necessary maintenance. Record the route, task, affected user and available evidence. Support conversations and a short observation of someone attempting the task can reveal more than an internal preference about colors. Separate confirmed problems from assumptions that still need checking.

Group problems into content, navigation, interaction, performance and underlying platform constraints. A confusing service page may need a clearer explanation and better links. Repeatedly duplicated content may indicate a broken content model. A platform that cannot receive necessary maintenance can justify deeper work. Estimate a focused repair and a broader redesign against the same outcome. Include the disruption of moving content, retraining editors and testing integrations in the broader option, not just the new interface.

Build an inventory of useful pages, downloads, inbound links and important search landing pages. Decide which content remains, which is combined and which genuinely no longer serves a purpose. If URLs change, plan their destinations as part of the project. Google recommends mapping old URLs to corresponding new locations and avoiding irrelevant redirects. A visually successful redesign can still break a useful technical guide, bookmarked support page or document linked from an existing customer’s records.

Consider a business whose service pages receive relevant visits but visitors repeatedly ask which offering fits their situation. Its CMS is maintained and editors can already update the pages. A useful first experiment is to clarify the service distinctions, add a comparison and simplify the contact step, then observe whether the same confusion persists. If the investigation instead finds that every service page is an unmaintainable copy with incompatible navigation, a shared content structure and broader redesign become a stronger response.

Write criteria that can be observed. An editor can create a service page using agreed fields; a visitor can find the relevant offer and next step; essential content works on a narrow phone; and keyboard navigation reaches and leaves interactive controls. Keep approved facts, contact information and search identities in the acceptance record. Establish representative pages and journeys before implementation so reviewers do not spend the entire review debating the homepage while overlooking search, support and long-form content.

Check the released website, not only design files. Revisit the tasks that justified the project and compare equivalent evidence where available. Search traffic can fluctuate after a move; a new appearance is not proof of improved discovery or conversion. Record remaining issues and distinguish defects from new ideas. Keep maintenance, measurement and content ownership assigned after launch, otherwise the new site can acquire the same problems as the old one. A successful decision has an explainable improvement, not merely a recent launch date.