Website redesign
A website redesign is necessary when the current version no longer meets business needs: users find it difficult to navigate the structure, pages are inconvenient to use on smartphones, the design is outdated, conversion rates are declining, or technical issues are hindering the project's further development.
What is a website redesign and what does it include?
Work can affect the interface, page structure, user scenarios, functionality, CMS, loading speed, and SEO. Therefore, the price of a website redesign depends on the initial state of the project and the extent of the changes. Before estimating, it's important to understand which elements can be retained, which will need to be reworked, and which search results cannot be lost during the launch.
A website redesign is the reworking of an existing web project, preserving its useful foundation and replacing elements that hinder user experience or business performance. Sometimes, updating the visual style and mobile interfaces is sufficient. In other cases, a new website structure, prototypes, functionality changes, and extensive technical work are required.
Before commissioning a redesign, it's worth determining the reason for the changes. If the problem is simply an outdated design, rewriting the entire project makes no sense. If users get lost in the catalog, pages load slowly, and the CMS limits development, simply changing colors and fonts won't solve the problem.
How is a redesign different from a design refresh or building a new website?
A cosmetic update typically affects individual visual elements: typography, images, buttons, block design, and other interface details. The URL structure, user scenarios, features, and technical foundation remain unchanged.
A complete redesign covers more project levels. Navigation, page structure, UX/UI design, forms, mobile version, and some functionality can be changed. A new website is required when the existing architecture, CMS, or code is no longer suitable for further development and it's more efficient to build a new solution from scratch.
What parts of the site can be changed?
The scope of work is determined after a website audit. Some projects require updating a few templates, while others require reworking the entire logic of user interaction. Therefore, the cost of a website redesign cannot be accurately calculated based on the number of pages alone.
Visual design
A visual redesign includes typography, color scheme, graphics, images, card design, buttons, forms, and other elements. A design system helps maintain a consistent style across main and internal pages and simplifies future interface development.
When updating, the brand's corporate style and current requirements are taken into account. If a rebranding is underway, the new visual guidelines are immediately incorporated into the design layouts to avoid the need to redesign the website after launch.
UX and structure
UX is responsible for how clear the user's path is from landing on a page to taking the desired action. During a redesign, the menu, navigation, block order, section structure, forms, and CTA placement are reviewed.
If analytics data shows that people aren't finding the service they need, abandoning their cart, or not reaching the inquiry form, the problem may lie in the user flow. In this case, the redesign begins with the prototype and page logic, and the visual component is developed afterwards.
What is included in the website redesign service?
The scope of the service varies depending on the project, but the work typically begins with an analysis of the current state and concludes with a review of the published version. A website redesign cannot be properly commissioned without defining the initial constraints and the expected outcome.
The work plan may include the following stages:
- audit of current pages, UX, analytics and technical condition of the site;
- analysis of competitors and target audience behavior;
- design of the website structure and key user scenarios;
- development of prototypes of the main types of pages;
- creation of UI and design systems for desktop and mobile;
- responsive development of agreed layouts;
- transfer of content, functions and necessary integrations;
- SEO preparation before publishing a new version;
- functional and technical testing;
- monitoring of indexing and errors after launch.
The specific scope of work is determined before implementation begins. This approach helps compare contractors' bids for the same set of tasks, not just by the final price.
Audit of an existing website
An audit reveals which parts of the project are functioning properly and don't require changes. Web analytics data, structure, interfaces, technical errors, and organic traffic are analyzed.
The results help separate real problems from subjective wishes. This reduces unnecessary rework and provides a basis for setting tasks for the designer and developer.
Competitor and audience analysis
Competitors are studied to understand common niche scenarios, page structures, and user expectations. Copying someone else's interface without analyzing the task makes no sense.
At the same time, they study the target audience and their path through the website. The logic for choosing a service will be different for a B2B company, an online store, and a medical clinic, so identical templates don't work well.
Designing a new structure
If the current structure is hindering user experience or SEO, it is reviewed before design layouts are created. Sections, nesting, navigation, and page connections are determined.
At the same time, existing URLs with traffic must not be forgotten. The new information architecture must take into account search demand and previously accumulated visibility.
UX prototyping
A prototype shows the layout of blocks and the sequence of actions without the distraction of visual details. At this stage, it's easier to test an inquiry form, service page, catalog, or other key scenario.
Prototype changes are less expensive than reworking the finished design and code. Therefore, complex pages are first tested at the structural and interaction levels.
UI design
Once the logic is approved, visual mockups are created. The designer works on typography, grid, controls, button states, forms, and responsive versions.
The finished design should take into account real data, not abstract placeholders. This is especially important for long headings, tables, cards, and multilingual projects.
Development
The agreed-upon layouts are transformed into working templates. At this stage, forms, integrations, responsive behavior, and the necessary interface logic are enabled.
The development isn't just checked visually. It's also important to ensure that the pages work correctly on different devices, don't create technical errors, and meet speed requirements.
SEO preparation for launch
Before publishing a new version, the old and new structures are compared. URLs, meta tags, canonical tags, internal links, hreflang, sitemap.xml, and robots.txt are checked.
If pages change addresses, a 301 redirect table is prepared in advance. After the move, server responses and the availability of important pages for search engines are additionally checked.
Testing
Before launch, forms, links, menus, responsiveness, functionality, and content display are tested. Critical scenarios directly related to inquiries, purchases, or registration are tested separately.
After bugs are fixed, a re-test is performed. This reduces the likelihood that a user will be the first to discover a non-functional form or broken interface after release.
In redesign projects, I first document the current site structure, pages with organic traffic, meta tags, internal links, and rankings, and only then approve URL and template changes. The most dangerous situation is launching a beautiful new site but simultaneously losing pages that have been driving traffic from Google for years. Therefore, 301 redirects, canonicals, sitemaps, robots.txt, and indexation monitoring are as much a part of the redesign for me as the UX and a new interface.
How does a website redesign work?
The sequence depends on the project's scale, but it's best not to rearrange the key stages. If you start designing pages before the audit and structure design, some layouts will have to be redone after technical or SEO limitations are discovered.
The work proceeds from analysis to implementation. Each subsequent stage builds on the decisions agreed upon in the previous one.
Audit of the current site
Data is collected on structure, traffic, user behavior, technical errors, and existing templates. Strong pages that cannot be lost during the migration are identified separately.
After the audit, a list of issues and priorities is compiled. This helps determine whether a complete redesign is needed or whether changes to specific sections of the website are sufficient.
Defining goals and KPIs
The goal should be related to a specific project problem. This could be increasing the number of inquiries, simplifying the order process, improving the mobile interface, or reducing technical errors.
Metrics are recorded before launch. After the release, the data can be compared to determine whether the changes actually improved the desired scenario.
Development of structure and prototypes
Main pages, navigation, and interactions between sections are designed. For complex scenarios, prototypes are created that illustrate the user's journey.
At this stage, the structure's compliance with search demand is also checked. If an existing page is already ranking, it cannot be removed without analysis.
Creating a new design
Once the prototypes are approved, a visual system and layouts for the main page types are created. Mobile states and repeating elements are worked on separately.
The design is approved before mass development begins. This reduces the number of costly changes after the interface has already been coded.
Development and integration
Developers implement approved templates and enable functionality. Data migration or integration with external services is performed as needed.
Changes are tested in a testing environment. The new version should not be opened for indexing until technical and SEO testing is complete.
SEO preparation
Before the release, old and new URLs, meta tags, and internal links are compared. Redirects are prepared for pages whose addresses actually change.
Additionally, canonical, hreflang, sitemap.xml, robots.txt, and page accessibility are checked. These tasks should be completed before publishing, not after a drop in page rankings occurs.
Testing and launch
Page display, forms, links, menus, shopping cart, search, and other functions are tested. Errors are corrected before the new version is transferred to the main domain.
After launch, a technical crawl is performed. This helps quickly detect 404 errors, incorrect redirects, and pages accidentally blocked from indexing.
Post-launch control
In the first days after the release, Google Search Console, indexing, organic traffic, and server errors are monitored. Changes are compared with the metrics recorded before the redesign.
Monitoring continues even after the initial check. Some indexing issues only become apparent after the search engine crawls the pages again.
What we actually did
Dental clinic · Kyiv and Chernihiv
+44% clicks from search
A domain with no history and a site on a website builder. We built the semantic core for the services and both cities, reworked the landing pages and built the link profile from zero. In four months: 34.8k clicks, impressions 1.32 → 1.76M, DR 0 → 41.
E-commerce · international
+96% clicks in two months
A catalog of digital 3D models. We clustered the semantics, rebuilt the hub pages and fixed duplicates and indexing errors. Google users 247 → 532, CTR 2.4% → 4%.
Medical center · Ukraine
+68.75% visibility in the first month
Narrow visibility and a small semantic core at the start. Semantics, landing page structure, metadata and internal linking, then gradual link building.
How long does a website redesign take?
The time frame depends on the number of unique pages, the scope of research, the speed of approvals, and the complexity of the development. A small website can be redesigned more quickly than an online store or service with a user account and integrations.
The correct deadline is determined after an audit and work breakdown. A fixed promise without a project assessment poorly accounts for technical risks and the scope of approvals.
How much does a website redesign cost?
There's no single price for all projects. A redesign of a small landing page and an online store with a large catalog require different numbers of prototypes, design layouts, development, and testing. Therefore, a website redesign whose price is estimated in advance without reviewing the project is usually too approximate.
The cost of a website redesign depends on the number of unique templates, the current CMS, the depth of the UX/UI redesign, functionality, and SEO objectives. To obtain an accurate estimate, we first review the site, determine the scope of work, and only then prepare a budget.
| Project type | What may be required | Price |
|---|---|---|
| Landing page | UX, new visual style, responsive version, front-end coding | After evaluating the project |
| Corporate website | Structure, prototypes, template design, development | After evaluating the project |
| Online store | Catalog, cards, filters, cart, UX, development | Custom quote |
| Complex service | Interfaces, dashboards, integrations, frontend and backend | Custom quote |
If a user searches for "website redesign prices", they need a clear benchmark and explanation of the budget. The final price should be tied to specific work, not an abstract number of designer hours.
What determines the cost of a website redesign?
The depth of the changes has the greatest impact on the final cost. Even with the same number of pages, two websites can require completely different amounts of work if one project maintains the existing structure, while the other requires a new UX, development, and data migration.
Therefore, the cost is discussed after an initial analysis. A redesign without an assessment of the current website can only be ordered with a preliminary range, which is then refined after the task is defined.
Site type and size
A landing page typically contains several unique screens and one primary user flow. A corporate website can include dozens of templates for services, case studies, articles, team pages, and regional landing pages.
An online store also requires consideration of categories, product cards, search, filters, shopping cart, and checkout. The more unique page types and scenarios, the greater the amount of planning, design, and testing required.
Depth of change
Sometimes it's enough to maintain the current structure and update the interface. This project requires less work than a comprehensive website redesign with new architecture, prototypes, content, and functionality.
If the logic of sections changes, the information architecture must be developed separately. If URLs are affected, the redesign includes SEO migration and search signal migration control.
CMS and technical condition
An existing CMS may support new templates without major changes, or it may limit responsiveness, speed, and functionality. In the former case, updating the frontend and necessary components is sufficient.
If a system is outdated or poorly supported, migration is considered. This decision is made after a technical analysis, as changing platforms impacts development, data, URL structure, and search indexing.
Integrations and additional functionality
CRM, payment systems, APIs, user accounts, filters, and other integrations increase the technical complexity of a project. Even a visually simple page may depend on complex server-side logic.
Before the assessment, it's important to document existing integrations and understand which ones will be kept. This reduces the risk of a critical feature being discovered after the design has been approved.
SEO preparation
If a site receives organic traffic, SEO migration should be part of the plan before development begins. Valuable pages should be preserved, URL structure should be verified, redirects should be prepared, and meta tags should be migrated.
Additionally, internal linking, canonical, hreflang, robots.txt, sitemap.xml, and indexing are monitored. The more complex the current site structure, the longer a secure transfer will take.
How is the price of a redesign calculated?
The estimate begins with an audit of the existing project. Specialists determine the number of templates, technical limitations, UX issues, the need for structural changes, and the list of features to retain or add.
After this, design, UX/UI design, development, testing, and SEO tasks are assessed separately. This breakdown shows the components of the website redesign price in Kyiv or for a project in another region where all work can be performed remotely.
Why order a website redesign from Seo-Gen?
At Seo-Gen, work begins with an analysis of the existing website. Before modifying templates, pages that rank in search, URLs, technical limitations, and user experience issues are recorded. Therefore, the design takes into account the website's existing performance.
UX/UI, development, and SEO are considered within a single plan. This simplifies the coordination of the structure and reduces the risk of having to rework a completed design due to CMS limitations or SEO requirements.
Before launch, redirects, canonical, hreflang, sitemap.xml, robots.txt, internal linking, and key user scenarios are checked. After publication, the new version is re-crawled, and indexing status is monitored through Google Search Console.
To find out the cost of a website redesign, simply provide the URL of your current project and describe the main task. After an initial analysis, you can determine the scope of work and prepare a quote without adding unnecessary steps to the estimate.
Answers to your questions
How much does a website redesign cost?
The cost depends on the project type, the number of unique templates, the depth of the UX/UI redesign, functionality, and technical condition. A minor visual update requires fewer resources than a comprehensive redesign of an online store with a catalog and integrations.
The exact cost can be determined after the initial audit. Without a website analysis, the website redesign price remains approximate, as some tasks are hidden in the technical implementation and existing structure.
What is included in the cost of website redesign?
The estimate may include an audit, competitor analysis, structural design, UX prototypes, UI design, responsive development, testing, and SEO preparation. The specific scope depends on which parts of the current website are being retained.
Integrations, data migration, and complex functionality are taken into account separately. It's best to define the scope of work before the project begins so that the website redesign cost can be linked to a specific deliverable.
Is it possible to order only the design without development?
Yes, it's possible to commission a redesign at the UX prototype and UI mockup level only. This option is suitable if the client already has developers who will implement the agreed-upon interface.
Before starting the design, it's important to understand the technical limitations of the CMS and frontend. Otherwise, some solutions may prove too expensive or impossible to implement within the current architecture.
Is it possible to lose Google rankings after a redesign?
Yes, this is possible if the URL, content, or technical SEO settings change during launch without proper monitoring. Common causes of performance drops include deleted pages, incorrect redirects, missing meta tags, and indexing errors.
The risk is reduced if the SEO migration is prepared before the release. This involves documenting current pages, mapping redirects, and testing the new version before and after launch.
Do I need to change the CMS when redesigning?
Not always. If the existing CMS supports the new structure, responsive design, and required functionality, it can be retained and only modifications to the interface and templates can be made.
A platform change is justified when technical limitations hinder project development or when maintaining the current solution becomes too difficult. The decision is made after a technical analysis.
How is a redesign different from creating a new website?
When redesigning, the starting point is the existing project: its pages, content, data, rankings, and existing features. Useful elements are retained, while problematic ones are reworked.
A new website is often designed from scratch. This option is chosen when the old architecture is unsuitable for new tasks or when migrating an existing database requires more resources than a new development.
How do you know if your website needs a complete redesign?
A complete redesign is necessary when issues affect the structure, UX, mobile version, visual style, and technical aspects simultaneously. If the flaw is localized, it makes more sense to fix a specific component.
The decision should be made after an analytics and technical audit. This helps avoid increasing the budget for changes that don't impact user experience or website performance.
A redesign should begin with an analysis of the current website and the specific reason for the changes. This process helps determine whether a simple interface update is sufficient or whether a new structure, development, SEO migration, and functionality redesign are required.
If you need a website redesign, send Seo-Gen the address of your current project and a brief description of the task. After the initial audit, we can determine the scope of work, assess SEO risks, and calculate the project cost.
We reply within one business day. No newsletters, no “just a reminder” calls.
He will look at the site himself instead of passing it to a manager.
More on: Website redesign
When does a website need a redesign?
The decision to redesign a website is best made after analyzing data, not based on a subjective feeling that the design hasn't been updated in a while. Reasons may include issues with conversion, mobile version, navigation, technical condition, or the website's suitability for the current product.
Some deficiencies can be addressed with localized changes. A complete redesign is needed when problems are interrelated and affect multiple project levels simultaneously.
The design looks outdated
An outdated design alone doesn't mean the website needs a complete overhaul. First, consider legibility, visual hierarchy, image quality, interface design, and compliance with the current brand style.
If pages don't convey the company's positioning well, elements appear inconsistent, and new content doesn't fit neatly into existing templates, a visual update becomes a justified part of a redesign.
Users find it difficult to find the information they need
Confusing menus, lengthy navigation, unclear section names, and overloaded pages increase the number of unnecessary actions. Users may abandon the site even though the desired service or product is available.
During a redesign, the site structure and actual navigation patterns are analyzed. Based on this data, the path to landing pages can be shortened, unnecessary intermediate steps can be eliminated, and navigation can be made clearer.
The site doesn't work well on smartphones
Responsive design must consider the screen size, interaction method, and content priority. Simply shrinking a desktop page typically results in small elements, awkward forms, and excessively long screens.
When redesigning the mobile version, we check menus, buttons, forms, tables, product cards, filters, and other interactive elements. Loading speed and Core Web Vitals metrics are also monitored separately.
Conversion rate has decreased
A drop in leads or sales can't be automatically attributed to website design. First, you need to look at traffic sources, user behavior, entry pages, forms, and funnel stages.
If an audit reveals issues with the interface or user experience, a UX/UI redesign can address specific barriers. The results are assessed based on post-launch data, not a subjective assessment of the new layout.
The brand, product or business model has changed
After expanding your product range or launching new lines, the old structure may no longer align with your business. Users see outdated categories, old services, and inappropriate navigation.
In this case, a redesign helps align the website with the current product. Rebranding involves updating the visual system, content, images, and key interfaces simultaneously.
Technical and SEO problems have accumulated
Legacy code, slow templates, CMS limitations, and accumulated bugs make project maintenance difficult. New features have to be added through workarounds, and any change creates the risk of additional problems.
If technical limitations are already hindering the site's functionality, a redesign should be combined with a frontend overhaul or a migration to a suitable platform. Before doing so, it's important to conduct an SEO audit and determine which URLs, meta tags, and ranking pages should be retained.
What types of redesign can be ordered?
The type of work is chosen based on the current state of the website. There's no point in changing the technical platform if the problem is only in the interface. Likewise, a visual update won't fix a weak catalog structure or a slow CMS.
Before starting a project, it's helpful to categorize tasks into levels. This helps estimate the cost of the website redesign and eliminate work that doesn't impact the outcome.
Visual redesign
The visual version is suitable for websites with a working structure and a robust technical foundation. Fonts, colors, graphics, block design, cards, forms, and other interface elements are changed.
This format is often chosen after a brand identity update. User scenarios are preserved, so the project typically requires less research and development than a full redesign.
UX/UI redesign
UX/UI redesign begins with an analysis of user behavior and page structure. First, scenarios, prototypes, and interface logic are developed, followed by the visual design.
This approach is necessary when users have difficulty navigating, finding products, filling out forms, or moving between purchase steps. Changes should be based on analytics data and real business objectives.
Functional redesign
The functional option is used when an existing website lacks functionality. You can add search, filters, a user account, a calculator, new forms, or integrations.
In such a project, design is closely linked to development. Before creating the interface, the function's logic, data, and possible states must be described so that the mockup can be implemented without reworking.
Technical redesign
A technical overhaul is necessary when the code is outdated, the performance is low, or the current platform is limited. This may include a new frontend, reworking individual modules, or migrating to a different CMS.
The decision to undertake a technical redesign is made after an audit. Completely replacing a working platform without a clear reason increases the budget and creates additional risks during the migration.
Comprehensive website redesign
The comprehensive format covers structure, UX, visual interface, development, and SEO. It's chosen when problems accumulate simultaneously across multiple parts of the project.
This type of redesign requires consistent work, from audit to post-launch monitoring. It's more expensive, but all changes are designed within a single system and don't conflict with each other.
How to redesign a website without losing SEO rankings?
SEO should be considered even before changing the structure and templates. If you build a new website first and then try to migrate search settings, some important decisions will already be baked into the design or code.
The risk is especially high for projects with significant organic traffic. Page deletions, URL changes, and loss of internal links can impact visibility even with a high-quality new interface.
What needs to be recorded before work begins?
Before a redesign, a snapshot of the site's current state is created. This includes URLs, search traffic, rankings, meta tags, internal links, and technical settings.
This data is then used to validate the new version. Without baseline metrics, it's difficult to understand where the issue arose after launch and which pages require attention.
Current URLs and pages with organic traffic
It's necessary to collect all indexed URLs and identify the pages that receive search traffic. Particular attention is paid to commercial pages and content with stable visibility.
If an address needs to be changed, a relevant new page is selected for it in advance. Simply deleting the old URL runs the risk of losing accumulated search signals.
Title, Description, and H1
Optimized Title, Description, and H1 tags can't be automatically replaced with the template values of the new theme. First, you need to understand which pages are already ranking for the desired queries.
Meta tags can be improved when content changes, but decisions are made individually for each important page. Massive changes without analysis create unnecessary risks.
Internal linking
The new structure often changes menus, breadcrumbs, and links within content. After the migration, old URLs may remain in blocks, templates, or articles.
Before launching, a crawl of the new version is performed. All internal links should point directly to the final URL without unnecessary 301s or redirect chains.
Canonical, hreflang, robots and sitemap
Canonical should point to the correct canonical page, hreflang should link the appropriate language versions, and robots.txt should not accidentally close the new site after moving it from the testing environment.
The sitemap.xml is updated to reflect the current structure and contains only indexable final URLs. After launch, the sitemap is submitted to Google Search Console, and page processing is monitored.
When are 301 redirects necessary?
A 301 is needed when an old page is moved to a new permanent address. For each significant URL, the most relevant new page is selected, rather than redirecting all removed URLs to the homepage.
A redirect map is prepared before the release and tested after launch. It's best to remove chains of multiple transitions, and immediately replace internal links with final URLs.
What to check after launch?
After publishing, you need to ensure that search robots receive the same version of the site as the user sees it. This check begins with a technical crawl and basic Google Search Console reports.
In the first days, the following are monitored:
- server responses and the appearance of new 404 errors;
- correctness of 301 redirects and absence of chains;
- canonical and availability of indexed pages;
- relevance of sitemap.xml and robots.txt;
- hreflang for language versions of the site;
- internal linking and final link URLs;
- loading speed and Core Web Vitals;
- mobile version and operation of interactive elements;
- organic traffic, rankings and indexing status.
If a problem is detected, it is addressed at the root level. Mass redirects, closing sections, or deleting pages without analysis can increase the drop rather than resolve it.
What's the difference between redesigning an online store and a corporate website?
The general steps are similar, but the user scenarios for these projects differ. A corporate website often leads users to submitting an inquiry, making a call, or researching a service, while an online store must guide them from the category to placing an order.
Therefore, a one-size-fits-all approach to structure and cost estimation isn't appropriate. An online store typically requires more functional testing and template work.
Online store redesign
The focus is on categories, product cards, filters, search, cart, and checkout. These elements should work equally well on both desktop and smartphone.
When editing your catalog, consider SEO-friendly category pages, filters, pagination, and internal links. A poorly thought-out structure change can create duplicates or remove pages that already receive search traffic.
Corporate website redesign
For a corporate project, the service structure, case studies, contacts, forms, and trust blocks are essential. Users should quickly understand the company's specialization and navigate to the desired action.
If a website is being promoted in search results, service landing pages and their internal links are specifically preserved. When adding new services, the structure is expanded without creating competing pages with the same intent.
Functionality
A redesign may include new filters, forms, search, catalog, user account, calculator, or integrations with external systems. The scope of development depends on whether the required features can be implemented on the existing platform.
For an online store, the functional part usually takes more time than for a small corporate website. You need to check product cards, filtering, shopping cart, checkout, payment, and ensure all scenarios work correctly on mobile devices.
Technical and SEO part
Interface changes often affect code, loading speed, URL structure, and internal linking. If development is carried out without SEO control, 404 errors, incorrect canonicals, removed meta tags, or pages that are no longer indexed may appear after launch.
Before the release, a technical audit is conducted, checking robots.txt, sitemap.xml, canonical, hreflang, Core Web Vitals, and other elements that affect indexing. A 301 redirect map is created in advance for changed URLs.