When should you redesign your business website?

The short answer: redesign when the gap is structural

A business website redesign is justified when the site repeatedly misrepresents the business, obstructs a valuable customer task or makes essential changes unusually slow and risky. Age alone is weak evidence. A five-year-old site that explains the offer clearly and supports enquiries can be more useful than a recent site built around visual trends.

Begin with one sentence: “The website currently causes or fails to prevent this business problem.” Examples include attracting requests for a service you no longer prioritise, forcing staff to explain basic differences after every enquiry, or losing mobile users before they complete a contact form. If you cannot name the problem, spend a week collecting evidence before discussing layouts.

A small business website redesign should improve a defined customer journey and make the current business easier to recognise. It should not become a substitute for deciding which customers, services and actions matter most.

• Write the business change that the current site does not reflect.
• Choose one primary visitor and one valuable action to investigate first.
• Collect examples of confusion from sales, support and customer-facing staff.

Seven signals worth investigating

Treat each signal as a prompt for investigation, not an automatic instruction to replace the site. One weak page may need focused homepage copywriting. Several connected failures across navigation, content, forms and the content system usually point toward a broader redesign.

The most persuasive evidence comes from different sources agreeing. If sales colleagues report that prospects misunderstand the offer, search terms bring visitors to obsolete services, and the homepage still leads with those services, the diagnosis is stronger than any one metric.

• The business model, service mix or priority market has changed but the site has not.
• Visitors cannot explain what you do, for whom and why it is relevant after scanning the homepage.
• Qualified prospects repeatedly ask questions the site should answer before contact.
• The main enquiry path has avoidable steps, unclear labels, failures or poor mobile behaviour.
• Important pages compete with one another or sit in a navigation structure based on internal departments.
• Publishing a case study, changing a service or correcting a translation requires developer intervention.
• The site cannot be maintained safely because ownership, access, dependencies or documentation are unclear.

Refresh, targeted improvement or full rebuild?

A refresh changes presentation while preserving most of the structure and technology. Targeted improvement changes a specific journey or page group. A rebuild reconsiders content structure, templates, design system and often the underlying platform. The right choice depends on how coupled the problems are.

Use a refresh when the offer and journeys are sound but the visual system looks inconsistent or dated. Use targeted improvement when one high-value path can be isolated, such as a service landing page and its enquiry form. Choose a rebuild when fixing one area exposes dependencies across navigation, templates, multilingual content, integrations or governance.

Beware the false economy of reskinning a weak structure. New typography cannot clarify overlapping services. Equally, do not rebuild a functioning platform merely because a stakeholder dislikes the colour palette.

Run a two-week evidence sprint before choosing

A short evidence sprint prevents a subjective redesign debate. It is not a full audit. Its purpose is to establish whether the main issue is message, journey, technology or operating ownership. Assign one decision-maker and gather enough evidence to choose the next investigation.

Review recent qualified and unqualified enquiries, interview two or three customer-facing colleagues, and attempt the primary task on a phone and laptop. In analytics, define the actions that matter to the business. Google Analytics calls these key events and reports how often users trigger them. A form submission is useful only if the form works and the resulting enquiry is relevant, so pair measurement with a manual delivery check and sales feedback.

Record observations in a simple log with evidence, impact, confidence and likely scope. Avoid turning every preference into a requirement.

• Day 1: define the primary audience, task and business outcome.
• Days 2 to 4: collect enquiry themes and stakeholder observations.
• Days 5 to 7: review five priority pages and complete the journey on real devices.
• Days 8 to 10: inspect measurement, form delivery, content ownership and technical constraints.
• Days 11 to 14: classify findings and decide refresh, targeted work or rebuild.

Turn the diagnosis into a useful agency brief

A useful brief describes decisions and constraints rather than prescribing a homepage layout. It gives a website redesign agency enough context to propose a sound route while preserving room for discovery. Attach evidence and distinguish confirmed requirements from assumptions.

State the commercial priority, primary audiences, priority journeys, current content and systems, required languages, integrations, approvals and ownership. Include what must be preserved, particularly valuable URLs and content. Google recommends preparing an old-to-new URL map when URLs change and using permanent server-side redirects for permanent moves. Migration planning therefore belongs in scope before build estimates are compared.

Ask every supplier to identify exclusions, client responsibilities and acceptance criteria. “SEO included” is too vague. A stronger response names responsibilities for URL inventory, mappings, redirects, metadata, analytics, testing and monitoring.

• Business context and the change that triggered the project.
• One primary audience and the action the website should make easier.
• Evidence of current failures and known constraints.
• Content creation, migration, translation and approval responsibilities.
• Technical integrations, access, privacy and hosting requirements.
• Deliverables, review rounds, acceptance tests and post-launch support.

Evaluate concepts with customer tasks, not taste

A concept review should answer whether the proposed direction solves the diagnosed problem. Give reviewers the brief and ask them to assess the same scenario. For example: “A managing director has heard our name, lands on the homepage and needs to decide whether we handle multi-site projects in Switzerland. Can they find credible evidence and a sensible next step?”

Score clarity, relevance, evidence, next-step visibility, mobile logic and feasibility. Ask the designer to explain hierarchy and tradeoffs. A dramatic hero may be attractive yet consume the space needed to qualify the offer. A compact page may feel efficient while omitting the proof a cautious buyer needs.

Keep feedback observable. “The service distinction disappears below the first screen on mobile” gives the team something to solve. “Make it pop” does not.

Know when to pause the redesign

Pause if leadership has not agreed which services or markets matter, because the website team cannot resolve a business strategy conflict through design. Pause if nobody can approve content, provide access or own the finished site. Pause if a critical system replacement will soon change requirements.

Pausing does not mean doing nothing. Stabilise broken forms, correct misleading claims, document access and gather customer questions. These low-regret actions protect the current journey and improve the eventual brief.

Also pause a full rebuild when the evidence supports a smaller intervention. A focused homepage and enquiry improvement can reveal whether the message is the constraint before the organisation commits to a broader programme.

Choose the next step

If the evidence points to one contained issue, specify and test that improvement. If several priority problems share structural causes, prepare a rebuild brief and compare approaches on scope, ownership and acceptance criteria. If the evidence is still weak, conduct the evidence sprint before seeking proposals.

A tailored concept is useful at this stage because it makes the homepage hierarchy and mobile direction discussable. Treat it as a way to test the diagnosis, not proof that implementation details, migration and ongoing services are already included.

• Bring the current URL, primary audience and main business problem to the discovery call.
• Identify the one customer action the concept should support.
• List three constraints the direction must respect.