When a website no longer represents the brand, generates fewer opportunities, or no longer supports content operations, changing colors, typography, and images can create a sense of renewal without addressing the underlying problem.
A website redesign starts with defining the level of intervention. In some cases, a visual refresh is enough to resolve the misalignment. In others, the project needs to revisit messaging, information architecture, user journeys, content, UI design, and technology. SEO (Search Engine Optimization) migration must also be part of the planning process.
That decision should be based on evidence. Navigation and conversion data, user research, stakeholder interviews, website audits, and technical indicators reveal which problems need to be addressed. With this diagnosis in place, user experience (UX), branding, content, marketing, and engineering teams can align around shared priorities.
Throughout this article, you’ll learn how to determine the right scale for a website redesign, build the business case, evaluate a website redesign agency, protect organic visibility during migration, and measure whether the new website has improved the results that prompted the project.
Define the Level of Intervention Before Setting the Budget
The initial diagnosis helps distinguish a visual refresh from a structural redesign.
The Challenges That Lead Companies to Question Their Website’s Effectiveness
The need to revisit a website often arises when different problems begin to accumulate. The brand has evolved, the portfolio has expanded with new solutions, user journeys have become more complex, or the platform can no longer keep up with the needs of content, marketing, and technology teams. These signs, however, do not always mean the entire website needs to be rebuilt.
Navigation difficulties, declining conversion rates, content publishing limitations, performance issues, or a visual experience that no longer aligns with the brand can have different causes and require different levels of intervention. Identifying where these limitations lie helps distinguish isolated problems from structural issues and determine the scale of the redesign before defining the investment, technology, or timeline.
Three Levels of Website Redesign for Different Problems
A website redesign can involve very different levels of intervention. An initial classification helps prevent companies from commissioning a comprehensive overhaul to fix interface issues or limiting the project to UI design when the underlying problems are structural.
Level | What Changes | When It Makes Sense |
Visual refresh | Colors, typography, imagery, spacing, and component styles | The brand needs visual alignment, while navigation, content, and technology remain effective |
Structural redesign | Information architecture, user journeys, templates, responsiveness, and conversion paths | Users struggle to find information or complete tasks, but parts of the existing foundation can be preserved |
Strategic overhaul | Positioning, messaging, content, UX, technology, integrations, and governance | Changes in audiences, portfolio, business model, or operations have made the current website insufficient |
A visual refresh is also referred to as a cosmetic refresh, while a broader strategic transformation may be described as a strategic overhaul. These terms can help companies compare proposals from website redesign agencies, provided each agency clearly specifies which workstreams are included.
Redesign and technical reconstruction, or rebuild, are not synonymous. Redesign addresses the experience, structure, and presentation. A rebuild replaces code, the platform, or the underlying architecture. A company can redesign its website within the same content management system or replace the entire technology stack and reproduce the same old problems.
Building a corporate website from scratch makes it possible to define its structure without an existing legacy to preserve. In a redesign, existing pages, rankings, integrations, and operational workflows need to be evaluated before changes are made.
Website Signals Need to Become a Business Case
The age of a website does not determine whether it needs a redesign. The decision becomes more grounded when problems affect the brand, user experience, business results, or the ability to evolve.
The Signs That Warrant Investigation
Brand and credibility: the design no longer reflects the positioning, the offering has changed, or messaging is inconsistent;
Navigation and conversion: menus are confusing, important pages are difficult to find, forms are abandoned, or traffic fails to generate the expected actions;
Operations and technology: bugs keep recurring, the codebase accumulates patches, and publishing content frequently requires technical support;
Performance and visibility: the website performs poorly on mobile devices, loads slowly, or has issues with indexing, internal links, and SEO architecture.
Each signal needs to be investigated before determining the solution. A decline in conversions may result from traffic sources, seasonality, or the offering itself, rather than issues with the website. A drop in Google rankings may be related to competition or outdated content. UX analysis and technical data help identify the underlying cause.
The Business Case Defines What Improvement Means
The business case provides the executive justification for the investment. It connects each problem to a consequence, such as lost opportunities, campaign delays, increased support requests, or technical risk. It also documents the baseline so results can be compared after launch.
Metrics vary according to the objective. A B2B website may track qualified opportunities and engagement with service pages. An e-commerce website may monitor product discovery, add-to-cart actions, and completed purchases. A corporate website may measure how well visitors understand the offering, contact submissions, and content publishing autonomy.
Goals such as “having a modern website” do not guide decisions or make it possible to evaluate return on investment. The business case needs to turn that intention into measurable criteria for content, UX, technology, and operations.
What Are the Main Stages of a Website Redesign?
A website redesign involves decisions that range from initial research to post-launch performance evaluation. The depth of each stage depends on the problems identified, the business objectives, and the level of intervention defined. The process below outlines the main workstreams and shows how they connect throughout the project.
1. Discovery, Auditing, and Cross-Functional Alignment Prepare the Project
Discovery is the research phase that brings together business objectives, user needs, technical limitations, and data from the existing website. It helps define the problem before the first screens are designed.
Interview stakeholders: leaders and teams from Marketing, Technology, Sales, Customer Service, and Content share priorities, processes, integrations, and risks.
Research users: interviews and usability tests reveal how people look for information and where they encounter difficulties.
Audit the website: content, messaging, information architecture, user journeys, SEO, and the technical foundation are evaluated to determine what to retain, update, consolidate, remove, or create.
Consolidate requirements: findings are translated into prioritized problems, critical user journeys, quality criteria, and responsibilities.
Data from Google Analytics, Search Console, customer relationship management (CRM) systems, interaction heatmaps, and customer service records help validate hypotheses. Performance should be interpreted according to each page’s purpose. A low-traffic page may be critical to conversion, while a highly visited piece of content may attract an audience that does not align with the commercial strategy.
Branding, content, UX, marketing, and engineering need to participate in decisions that affect their areas. When content is introduced after the layout is defined, messaging becomes constrained by predetermined blocks. When engineering receives finalized screens, accessibility and performance limitations may surface too late. When SEO is brought in close to launch, URLs and information architecture may already be compromised.
For this reason, a website redesign agency should be able to coordinate these disciplines from the beginning of the project rather than treating them as separate stages that only come together during development.
The Type of Website Changes the Priorities
Website Type | Redesign Priority |
B2B | Organize solutions, address different decision-makers, demonstrate authority, and generate qualified opportunities |
B2C | Make it easier to understand the offering, engage, get in touch, book appointments, or make a purchase |
E-commerce | Improve search, filters, product pages, cart, checkout, and integrations |
Small businesses | Focus investment on critical pages, local SEO, and the ability to manage updates independently |
Small businesses may operate in B2B or B2C markets. Their size often means a smaller team is available to manage the website, making maintenance costs an important consideration. Organizations operating across multiple countries, brands, or business units also need to account for languages, permissions, governance, and content volume.
Plan Your Redesign with an Integrated Approach
Dexa connects brand, content, experience, and technology to build a website aligned with business objectives and prepared to evolve.
2. CMS, Architecture, and Technical Quality Should Support Operations
A content management system (CMS) determines how teams create, review, and publish content. The technology stack brings together the technologies used across the front end, back end, and infrastructure. These choices should reflect editorial workflows, integration requirements, and the technical capabilities available.
Traditional, Decoupled, or Headless CMS
In a traditional CMS, content management, administration, and presentation are handled within the same platform. This configuration works well for corporate websites and operations that prioritize editorial autonomy and centralized maintenance.
In a decoupled model, the CMS manages content while a front end built with another technology receives that content through APIs, which enable communication between systems. A headless CMS is a form of decoupled architecture in which the content management system acts as a repository for websites, applications, and other digital channels.
A headless architecture can support operations across multiple channels, specific integrations, or highly customized interfaces. This configuration also creates separate responsibilities for front-end development, hosting, deployment, preview, security, and monitoring. The added flexibility needs to justify the increased complexity.
Technical Criteria Need to Be Verifiable
Performance
Core Web Vitals measure loading performance, responsiveness to interactions, and visual stability. Google considers LCP of up to 2.5 seconds, INP of up to 200 milliseconds, and CLS of up to 0.1 to be good, measured at the 75th percentile of visits.
Accessibility
The W3C recommends evaluating accessibility from the earliest stages of a redesign. The project can adopt the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, and test keyboard navigation, focus, contrast, alternative text, forms, and screen reader compatibility.
Responsiveness and Security
Menus, images, tables, buttons, and forms need to work across different screen sizes and input methods. Updated dependencies, permissions, authentication, APIs, data handling, and monitoring should be included in the acceptance criteria.
3. SEO and Content Migration Start Before Development
The term SEO-safe migration refers to planning changes to URLs, content, and site structure to reduce avoidable losses in organic visibility. The process does not guarantee complete stability. Google explains that significant changes can cause temporary fluctuations while pages are recrawled and reindexed.
“In a website redesign, SEO needs to be involved in decision-making before the migration begins. Changes to information architecture, URLs, and content can affect how search engines discover, interpret, and index pages. Planning these changes from the outset helps preserve relevant signals from the existing website and reduces risks during the transition.” — Tainá Aquino, Content Strategy and SEO Specialist at Dexa
The migration plan should be developed alongside the information architecture:
Create a URL inventory: gather URLs identified through the CMS, sitemaps, Analytics, Search Console, backlinks, and server logs;
Define destinations: preserve relevant URLs whenever possible and map each old URL to an equivalent new page;
Configure 301 redirects: permanent redirects should take users and search engines directly to the final destination, avoiding redirect chains or generic redirects to the homepage;
Review technical signals: canonical tags, which indicate the preferred version of a page, need to point to the new URLs. Internal links, sitemaps, indexing rules, language versions, and structured data should also be updated to reflect the changes;
Validate and monitor: crawls help identify response code issues, broken links, redirects, and blocked resources. Search Console, Analytics, and server logs help monitor indexing and traffic after launch.
Google recommends preparing a mapping of old and new URLs, updating internal links, and testing the website before the move. When a company plans to change its domain, CMS, and layout, separating these changes can make it easier to identify problems.
Migration Is Also an Editorial Review
The content inventory determines what will be retained, updated, consolidated, removed, or created. Pages that generate traffic or backlinks, or play an important role in user journeys, require attention even when the new architecture changes how they are presented.
Migrating the entire content library without review carries outdated information and redundancies into the new website. The migration process creates an opportunity to improve clarity, refine messaging, and align each page with search intent without losing the value already built.
4. QA, Launch, and Measurement Are Part of the Same Delivery
QA, short for Quality Assurance, is the process of verifying quality across functionality, content, integrations, devices, accessibility, performance, security, and SEO before and after the website goes live.
Phase | Main Checks |
Before launch | Test forms, search, filters, logins, links, messaging, integrations, browsers, and devices; classify issues by severity |
During deployment | Verify backups, redirects, canonical tags, sitemaps, indexing, Analytics, and the rollback plan in the production environment |
Post-launch | Monitor 404 errors, forms, indexing, traffic, conversions, Core Web Vitals, and technical logs; prioritize fixes |
Issues affecting critical user journeys, security, accessibility, or measurement may prevent launch. Minor visual adjustments can be documented for later correction, provided they do not interfere with usability.
Results are evaluated by comparing the baseline with data collected after the stabilization period. Conversion rates and lead quality indicate commercial impact. Engagement and task completion help assess user journeys. Organic traffic, search queries, and indexed pages track search performance. Publishing time, support requests, and the frequency of technical issues indicate the impact on operations. These indicators can also inform ongoing conversion rate optimization (CRO) after launch.
A redesign should not be evaluated using a single metric. Traffic growth accompanied by a decline in opportunity quality may not meet the business case. Improved technical performance without progress in user journeys also indicates that further work is needed. Evaluating these indicators together helps avoid premature conclusions and guides future improvements.
How Should Timeline, Budget, and Agency Selection Reflect the Level of Intervention?
The timeline and budget depend on what needs to change and the risks involved. The number of templates, pages, languages, integrations, access roles, and connected systems influences the estimate. Research, content production, migration, accessibility, security, and stakeholder availability for reviews and approvals also affect the schedule and investment.
Visual refreshes can be completed within a few weeks when the existing structure has already been validated. Redesigns involving research, information architecture, a new CMS, integrations, and migration typically take several months. A website redesign agency should break down discovery, content, UX, UI design, development, migration, QA, and stabilization in its proposal, making dependencies and responsibilities clear.
Service packages should reflect meaningful levels of intervention. A visual refresh may focus on the interface and existing components. A structural redesign includes information architecture, user journeys, and templates. A strategic overhaul requires research, content, technology, and governance. Packages based solely on page count can obscure significant differences in the work involved.
How to Choose a Website Redesign Agency
A website redesign agency needs to demonstrate its ability to investigate the underlying problem and coordinate the disciplines involved. During the selection process, evaluate:
How it conducts discovery, user research, and website audits;
Who is responsible for content, UX, UI design, SEO, and technology;
How it defines information architecture, requirements, and acceptance criteria;
How it selects the CMS, technology stack, and integrations;
How it plans SEO migration, QA, and post-launch monitoring;
Which deliverables, responsibilities, and approval cycles are included in the proposal.
Website redesign agencies may have strong UI design capabilities while relying on partners for content or engineering. Others operate with integrated teams. Both models can work, provided coordination, ownership, and limitations are clearly defined.
Case Studies and Results Should Allow for Comparison
A website design portfolio demonstrates visual quality. Case studies provide a broader view of a website redesign agency’s reasoning and delivery capabilities when they present the initial problem, supporting evidence, the intervention carried out, and results over a defined period.
Expected results should reflect the business case. A project may aim to increase qualified opportunities, reduce abandonment, improve organic visibility, advance Core Web Vitals, or shorten publishing time. The agency needs to explain how each indicator will be measured without promising rankings, conversions, or revenue that depend on factors beyond the website.
Pactum: Website Redesign as a Foundation for Organic Growth
In the Pactum project, the challenge of expanding organic visibility began with the website’s structure. Dexa developed a new website, revised the information architecture, and built the technical SEO foundation before moving forward with the content strategy. From there, keyword research guided content clusters around the company’s services, tax-related challenges, and different stages of the decision-making process.
In the first six months, Pactum recorded a 93% increase in organic clicks and a 378% increase in search impressions. The case study shows how website redesign results can depend on the integration of diagnosis, technology, information architecture, content, distribution, and measurement.
Some warning signs deserve attention when evaluating proposals:
UI design defined before discovery;
Technology selected without analyzing requirements;
Content and SEO treated solely as operational migration tasks;
Accessibility, performance, or security offered as optional extras;
No clear ownership of QA and post-launch activities;
An unusually short timeline without a corresponding reduction in deliverables;
Case studies that showcase visuals without explaining the problem, methodology, or results.
The agreement should serve as a governance reference throughout the project. Anything left unclear before the work begins is likely to resurface as uncertainty, delays, or additional costs during delivery.
A Successful Redesign Preserves What Works and Addresses What Holds the Website Back
A website redesign does not need to replace the entire existing structure to deliver results. The diagnosis may reveal pages, content, technologies, and user journeys worth preserving. The intervention becomes more precise when the company distinguishes valuable assets from accumulated limitations.
The expected outcome also goes beyond appearance. A high-converting website depends on clear messaging, intuitive paths, relevant content, stable technology, and reliable measurement. The right combination varies according to the business model and the objectives defined in the business case.
When discovery, content, UX, engineering, and migration teams work toward the same criteria, project success extends beyond launch. The new website goes live with a foundation for tracking performance, addressing issues, and guiding its continued evolution.
If your company needs to define the right level of redesign and turn its website into a platform that supports brand, content, and growth, talk to Dexa about how a website redesign agency can support your project.
