Website Redesign: Rebuild the Journey, Not Just the Look
- Wix Solutions
- Jul 16
- 7 min read
A weak redesign changes the surface and preserves the friction. The colours are fresher, the hero is larger and the animation is new, but visitors still cannot compare services, understand the offer or complete the form. The project looks finished while the customer journey remains unresolved.
Website Redesign should be treated as controlled business change. It alters information, interface, technology and search signals at the same time. That makes evidence, scope and release discipline more important than visual novelty.
This guide uses a forensic approach: establish what exists, identify the failure mechanism, redesign the journey, protect valuable assets and prove the new system before traffic is moved.
Website Redesign begins with evidence
Before drawing a new page, record the current state. Capture the page inventory, URLs, organic landing pages, internal links, conversions, form completion, search queries, device patterns, performance issues and recurring customer questions. Add qualitative evidence from sales, support and real task testing.
The baseline prevents two expensive mistakes. First, it stops the team removing a plain-looking page that quietly attracts qualified search traffic. Second, it stops the project declaring success because the new interface feels modern. A redesign is successful when a defined problem improves without unacceptable losses elsewhere.
Business baseline: enquiries, bookings, sales, assisted conversions, lead quality and manual recovery work.
Journey baseline: entry pages, common paths, exits, search use, form starts and completion.
Content baseline: useful pages, duplication, outdated claims, missing evidence and ownership.
Search baseline: indexed URLs, rankings, backlinks, metadata, canonical rules and structured data.
Technical baseline: mobile behaviour, accessibility, performance, integrations and tracking reliability.
Our Website Redesign service can support this diagnostic work in Wix Editor or Wix Studio. The Website Redesign glossary entry gives a concise definition for internal briefs.
Define the redesign problem precisely
“The site looks old” is an observation, not a project objective. Translate it into consequences. Perhaps the visual system weakens trust in a high-value service. Perhaps the navigation reflects an internal department chart rather than customer tasks. Perhaps editors create one-off layouts because the component set cannot express new content.
Write a redesign hypothesis: if we change a specific part of the journey for a specific audience, a measurable behaviour should improve because a known barrier has been removed. This statement gives designers, writers, developers and stakeholders one testable direction.
Separate required outcomes from preferred treatments. “Customers can compare three service levels” is an outcome. “Use three cards in one row” is a treatment. The first allows responsive and accessible solutions; the second can become a constraint before the problem is understood.
Protect URLs, search equity and measurement
A redesign is not automatically a migration, but it often changes pages, templates or platform structure. Create a URL inventory and decide for every public address: retain, consolidate with a relevant redirect, intentionally remove, or exclude from indexing for a documented reason. Never launch with an improvised redirect list.
Retaining a valuable URL is usually safer than changing it for cosmetic consistency. Where change is justified, map old to new by intent—not all deleted pages to the home page. Preserve relevant on-page content, internal links and metadata, then test every redirect and canonical rule.
Review our definitions of website migration, technical SEO and noindex before creating the release plan. For Wix settings, the Wix SEO Basics guide is a practical companion.
Redesign the information architecture before the interface
A strong sitemap groups information by user intent and business priority. Audit labels in the language customers use. If visitors distinguish between problems, industries or outcomes, a navigation built only around internal service names may force unnecessary interpretation.
Sketch the primary journeys as sequences of decisions: recognise the need, understand the offer, assess suitability, find evidence, resolve risk and act. Different audiences may share components while needing different entry points or proof.
Use card sorting, search logs, sales questions and task testing to challenge the proposed structure. The aim is not the fewest possible pages. It is the clearest relationship between distinct questions, answers and actions.
Make content a redesign workstream
Content cannot be poured into finished layouts without consequence. Headings determine hierarchy; evidence changes section length; comparison needs structure; policies require accuracy; real images change crops and focal points. Writing and interface design must progress together.
For each page, define purpose, audience, question, primary action, supporting evidence and owner. Decide which content is retained, rewritten, combined, created or retired. Assign approval deadlines and future review dates.
A content model is especially useful for services, case studies, teams, locations or resources. Reusable fields create consistency without making every page identical. If the current site contains strong information buried in weak presentation, preserve the substance and improve the delivery.
Wix Solutions can connect redesign with content writing and website copy rather than treating copy as a late placeholder.
Design a system that survives launch
A redesign should reduce future inconsistency. Define tokens or rules for colour, type, spacing, states and imagery; then build reusable patterns for navigation, calls to action, cards, accordions, forms, proof, comparison and editorial content.
Test components with difficult content: long headings, missing images, translated labels, validation errors and large text settings. A component that works only with the demonstration copy is not reusable.
In Wix Studio, responsive rules and breakpoints can support more fluid behaviour; in Wix Editor, mobile-specific adjustments remain important. In either case, inspect reading order, keyboard order, targets, focus, image alternatives and form messages. Use the Wix Mobile Editor Guide and Wix Image Settings guide during quality assurance.
Three illustrative redesign case studies
The following composite cases are diagnostic examples, not claims about named clients. Each shows why the visible design was not the whole problem.
Case study 1: a professional-services lead journey
The site had a polished home page but grouped every offer under one vague Services page. Prospects arrived through referrals, searched for a specific capability and abandoned the form because it asked for a detailed project brief before explaining the next step.
The redesign created distinct service pages, a comparison path, evidence close to relevant claims and a short qualification form with a clear response promise. Existing useful URLs were retained. The lesson: conversion improved through information and expectation design, not a more dramatic hero.
Case study 2: an e-commerce collection system
The shop looked dated, but the deeper failure was product discovery. Categories reflected stock administration, filters used inconsistent attributes and product photography changed scale between items. Customers could not confidently compare.
The redesign standardised product data, rebuilt collection logic, established image rules and placed delivery and returns information at decision points. Visual refinement followed the content model. The lesson: an e-commerce redesign begins in taxonomy and operations.
Case study 3: a training organisation moving into Wix Studio
The organisation needed responsive layouts and easier editing, so redesign and migration happened together. The highest risk was not the new interface; it was losing established course URLs, event links and campaign measurement.
The team created an old-to-new URL map, rebuilt course content from structured fields, validated redirects and tracking, and released with a rollback plan. The lesson: platform change requires a release process, not only a design handover.
For further patterns, read Responsive Web Design: A User-Experience Framework for Every Screen, Basingstoke Brands: Build a Digital Home That Feels Like You and Creating User-Friendly Websites for Better Engagement. Explore the Website Designer Agency Case Study for a broader project view.
Test the release, not isolated screens
Freeze the release candidate. Define exactly which pages, components, integrations and tracking rules are in scope.
Run task-based testing. Ask representative users to find, compare, decide and complete key actions without coaching.
Check content and claims. Verify names, prices, policies, proof, contact details and page ownership.
Validate accessibility. Review structure, keyboard use, focus, contrast, zoom, alternatives and errors.
Test devices and content extremes. Include mid-range phones, long text, missing media and slow connections.
Crawl the staging or preview state. Check links, titles, descriptions, canonicals, index rules and structured data.
Validate measurement. Prove analytics, form events, campaign parameters and conversion definitions.
Test redirects after launch. Confirm old addresses resolve to the intended destinations without chains or loops.
Monitor a defined window. Watch errors, organic visibility, key journeys and enquiries; assign owners for corrections.
Website Redesign launch gate
Every existing public URL has a documented outcome and owner.
Primary journeys can be completed on representative mobile and desktop devices.
Navigation, search and page hierarchy use language customers understand.
Forms, bookings, payments, email notifications and integrations have passed end-to-end tests.
Titles, descriptions, canonicals, index rules, structured data and redirects are verified.
Content claims, evidence, policies and contact information are approved.
Keyboard use, focus, contrast, zoom and error handling meet the agreed accessibility standard.
Analytics and conversion events have been tested with real submissions.
A monitoring, rollback and correction plan is assigned before release.
Questions and answers
How do we know whether a site needs redesign or smaller updates?
Choose smaller updates when the structure, component system and content model can support current goals with contained changes. Redesign when repeated exceptions, unclear journeys or platform constraints make local fixes fragile or more expensive than system change.
Will redesign improve search rankings?
Not automatically. It may improve clarity, performance and content, but it can also damage visibility if valuable URLs, internal links or index signals are lost. Protect the baseline and monitor after launch.
Should every old page be kept?
No. Keep pages that serve a current user or search purpose. Consolidate overlap where one stronger page can satisfy the same intent, and redirect carefully. Remove content deliberately, with evidence and a documented destination.
How long should a redesign take?
Duration depends on inventory, decisions, content, integrations, approvals and testing—not page count alone. A smaller site with unresolved stakeholders can take longer than a larger site with a clear model and prepared content.
Can a redesign happen while the current website stays live?
Yes. Build and test in a controlled draft, duplicate or staging workflow, then schedule the release. Protect live forms, campaigns, domain settings and tracking until the switch is ready.
What should be measured after launch?
Compare the agreed baseline: task completion, enquiry quality, conversion, organic landing-page performance, crawl errors, engagement with key content and manual support work. Allow for normal short-term fluctuation while investigating material changes.
Redesign is a release discipline
A successful redesign makes the website easier to understand, operate, maintain and extend. Visual change matters, but it earns its place by supporting clearer decisions and a stronger system.
If your current Wix website is accumulating workarounds or no longer supports the customer journey, contact Wix Solutions. We can help audit the existing site, define the redesign scope and plan a controlled release.
Bibliography
Krug, Steve. Don’t Make Me Think, Revisited: A Common Sense Approach to Web Usability. 3rd edition, 2014.
Rosenfeld, Louis; Morville, Peter; and Arango, Jorge. Information Architecture: For the Web and Beyond. 4th edition, 2015.
Halvorson, Kristina, and Rach, Melissa. Content Strategy for the Web. 2nd edition, 2012.
Redish, Janice. Letting Go of the Words: Writing Web Content that Works. 2nd edition, 2012.
