A website redesign should not begin with a new homepage mockup.
It should begin with a diagnosis.
If the current website has weak navigation, unclear messaging, poor user journeys or technical limitations, changing the visual design alone will not solve the underlying problems.
A redesign is an opportunity to fix what is preventing the website from doing its job.
That means asking:
What should we keep, what should we improve, and what needs to be rebuilt?
Spinta’s Technology practice focuses on architecting and enhancing digital ecosystems while improving human experiences and interactions. Its officially listed capabilities include UI/UX and Website Development, making the relationship between experience and implementation central to the work.
What is a website redesign?
A website redesign is the process of improving an existing website’s structure, experience, visual presentation, content, functionality or technical foundation.
The scope can vary significantly.
A redesign might focus on:
- User experience
- Navigation
- Information architecture
- Visual identity
- Content
- Conversion paths
- Mobile experience
- Performance
- Technical architecture
- Integrations
Not every website needs to be rebuilt from scratch.
The right approach depends on what is actually broken or limiting the business.
Before the redesign: audit the current website
The first step is understanding the existing website.
Do not start by asking:
“What should the new website look like?”
Start by asking:
“What is the current website failing to do?”
Review the website from several perspectives.
Business
- Does the website support current business goals?
- Does it communicate the right services or products?
- Does it reflect the current positioning?
- Does it generate the right enquiries or actions?
User
- Can visitors find what they need?
- Is the navigation intuitive?
- Are important actions easy to complete?
- Does the website answer key questions?
Content
- Is the information current?
- Is there duplicated or outdated content?
- Are important pages missing?
- Is the messaging clear?
Technology
- Is the website easy to maintain?
- Does it integrate with required systems?
- Can it support future requirements?
- Are there technical limitations?
This initial audit creates the foundation for the redesign.
Website redesign checklist
1. Revisit the purpose of the website
Before changing the design, define what the website needs to accomplish.
The primary objective could be:
- Generate leads
- Sell products
- Explain services
- Build credibility
- Support existing customers
- Generate enquiries
- Provide information
- Enable transactions
There can be multiple objectives.
But the team should understand which ones matter most.
A website redesign without a clear objective can quickly become a collection of design preferences.
2. Check whether the website still reflects the business
Businesses evolve.
Services change.
Products expand.
Target audiences shift.
Market positioning develops.
The website should reflect the business that exists today, not the company that launched the original site.
Check:
- Company information
- Services
- Products
- Target audience
- Positioning
- Messaging
- Brand identity
- Calls to action
If the website communicates an outdated version of the business, the redesign needs to address the content and structure, not just the interface.
3. Audit the navigation
Visitors should not have to guess where to go.
Review:
- Main navigation
- Dropdown menus
- Page hierarchy
- Breadcrumbs where relevant
- Search
- Footer navigation
- Calls to action
Ask someone unfamiliar with the website to find important information.
If they struggle, the problem is probably not obvious to the internal team because internal teams already know where everything is.
That is precisely why external user testing can be valuable.
4. Review the information architecture
Information architecture determines how information is organised.
A redesign is a good opportunity to ask:
- Which pages are essential?
- Which pages can be combined?
- Which pages are outdated?
- Which pages are missing?
- What should sit under each navigation category?
- What should users see first?
Do not simply reproduce the current sitemap.
The existing structure may be one of the reasons the website is underperforming.
5. Identify the most important user journeys
Not every visitor follows the same path.
Map the journeys that matter most.
For example:
Homepage → Service → Proof → Enquiry
or:
Product → Details → Comparison → Cart → Checkout
or:
Article → Related service → Contact
Then ask:
- Where do users drop off?
- Where do they become confused?
- Where are important actions missing?
- Which pages need stronger connections?
A redesign should improve these journeys rather than simply rearrange individual pages.
6. Review the calls to action
Every important page should give users a logical next step.
Review whether calls to action are:
- Clear
- Relevant
- Visible
- Consistent
- Appropriate to the user’s stage
Avoid giving every page the same generic CTA.
Someone reading an educational article may not be ready for the same action as someone evaluating a service.
The CTA should match the user’s intent.
7. Audit your content
A redesign is one of the best opportunities to clean up content.
For each page, ask:
Keep, improve, combine, redirect or remove?
Look for:
- Outdated information
- Duplicate pages
- Thin content
- Confusing messaging
- Weak headlines
- Missing information
- Old offers
- Old contact details
- Inconsistent terminology
A new design cannot compensate for unclear content.
8. Review the mobile experience
Do not treat mobile as a smaller version of desktop.
Check:
- Navigation
- Text size
- Buttons
- Forms
- Images
- Tables
- Interactive elements
- Page hierarchy
- Spacing
- Checkout or enquiry flows
Ask:
Can a user complete the important tasks comfortably on a mobile device?
If not, the redesign needs to address the experience rather than simply make the layout responsive.
9. Review visual hierarchy
A page can contain all the right information and still be difficult to use.
Visual hierarchy helps users understand:
- What is most important?
- What should they read first?
- What should they do next?
- Which information supports the main decision?
Review:
- Headlines
- Subheadings
- Body text
- Images
- Buttons
- Cards
- Whitespace
- Navigation
- Supporting information
The goal is not to make the page visually impressive.
It is to make the important information easier to understand.
10. Check whether the brand identity still fits
Sometimes a website redesign reveals a broader branding issue.
The website may use:
- Outdated colours
- Inconsistent typography
- Old photography
- Multiple logo versions
- Inconsistent messaging
- Visual elements that no longer represent the business
If the identity itself has changed, the redesign needs to reflect that.
If the broader brand is the problem, a website redesign alone may not be enough.
Spinta’s Branding capabilities include Brand Identity Design and Rebranding and Brand Refresh, which can be relevant when the website is exposing a wider brand identity issue.
11. Review conversion paths
A website should make important actions easy.
Depending on the business, those actions might include:
- Requesting a quote
- Booking a consultation
- Contacting sales
- Buying a product
- Registering
- Downloading information
- Starting a conversation
Review every major conversion path.
Ask:
- How many steps are required?
- Is the value clear?
- Are there unnecessary fields?
- Are users given enough information?
- Are there distractions?
- Does the experience work on mobile?
The goal is not always fewer clicks.
The goal is less unnecessary friction.
12. Review technical requirements
A redesign is a good time to evaluate technical limitations.
Consider:
- CMS requirements
- Integrations
- APIs
- Forms
- Search
- Analytics
- Authentication
- E-commerce
- Performance
- Security
- Hosting
- Maintenance
The development architecture should support the redesigned experience.
Spinta’s Technology capability includes Website Development and Web Application Development, among other digital development services.
13. Audit integrations before development
This is an area that can cause major redesign problems when ignored.
Create a list of everything connected to the existing website.
For example:
- CRM
- Analytics
- Marketing automation
- Payment systems
- Inventory
- Customer databases
- External APIs
- Forms
- Search tools
Then determine:
Keep, replace, remove or rebuild.
Do this before development begins.
14. Protect valuable existing content
A redesign should not accidentally discard content that already serves a useful purpose.
Before changing URLs, page structures or content, identify important existing pages.
Review:
- High-value landing pages
- Organic search traffic
- Backlinks
- Frequently visited pages
- Conversion pages
- Important resources
Where URLs change, plan appropriate redirects.
The goal is to improve the website without unnecessarily destroying the value the existing site has already built.
15. Define what success looks like
A redesign should have measurable objectives.
Depending on the website, useful measures might include:
- Enquiry completion
- Conversion rate
- Product purchases
- Engagement with important pages
- Task completion
- Search visibility
- Mobile usability
- Qualified leads
The exact metrics should follow the business objective.
Do not measure success simply by whether stakeholders like the new design.
A redesign should improve the website’s ability to perform its job.
What not to change during a website redesign
Not everything needs to be rebuilt.
Preserve elements that already work.
That could include:
- Effective content
- Strong landing pages
- Recognisable brand elements
- Useful functionality
- Valuable search pages
- Successful conversion paths
The redesign should be selective.
Change because there is a reason to change.
Common website redesign mistakes
Starting with visual design
A new interface cannot solve unclear strategy or poor content.
Rebuilding everything
Sometimes the problem is concentrated in a few areas.
A complete rebuild may introduce unnecessary complexity.
Ignoring mobile
A website that looks good on desktop but frustrates mobile users is still a poor experience.
Forgetting existing search value
Changing URLs and removing pages without a migration plan can create avoidable SEO problems.
Treating content as an afterthought
Design and content need to work together.
Adding features because they seem impressive
More functionality does not automatically create a better experience.
Measuring success by aesthetics
A redesign should be judged by business and user outcomes, not screenshots.
The website redesign process
A practical redesign process can look like this:
Phase 1: Diagnose
Audit the current website.
Phase 2: Define
Clarify business objectives, audiences and user journeys.
Phase 3: Structure
Review information architecture, navigation and content.
Phase 4: Design
Develop the visual and interaction system.
Phase 5: Build
Translate the experience into the appropriate technical architecture.
Phase 6: Test
Test usability, functionality, mobile experience and important journeys.
Phase 7: Launch
Deploy the new website with appropriate technical and content migration planning.
Phase 8: Improve
Use real user behaviour and business data to identify the next improvements.
A redesign should not be considered finished simply because the new website goes live.
Website redesign checklist: the short version
Before approving the new website, confirm:
- Business objectives are clearly defined
- Target audiences are understood
- Key user journeys are mapped
- Navigation has been reviewed
- Information architecture has been reconsidered
- Content has been audited
- Calls to action are clear
- Mobile experience has been tested
- Brand identity has been reviewed
- Conversion paths have been reviewed
- Technical requirements are documented
- Integrations have been mapped
- Important existing pages have been identified
- URL changes have been planned
- Success metrics have been defined
Final takeaway
A website redesign should not be treated as a cosmetic exercise.
It is an opportunity to reassess the relationship between business goals, user experience, content and technology.
Before rebuilding, identify what is actually limiting the current website.
Then decide what should be kept, improved, rebuilt or removed.
The strongest redesigns do not simply produce a newer-looking website.
They create a website that is easier to use, clearer to understand and better aligned with what the business needs to achieve.
Diagnose first. Redesign second.
Spinta’s practice includes UI/UX and Website Development, with a broader focus on improving digital ecosystems and human experiences.
For businesses considering a website redesign, the most useful first step is to identify whether the real challenge is UX, content, structure, technology, brand identity, or a combination of these.
