Your website may be due for an update, but if it’s already bringing in customers through Google, you don’t want to lose that progress. The key is knowing what already works – which pages attract the right audience, which content performs well, and what needs to stay in place during the redesign.

In this article, we’ll look at how to combine design and technical improvements with SEO preservation, and which checks can help reduce risk before and after launch.

How to redesign a website without losing organic traffic

The point of a redesign is to help businesses get more profit from a website and make it more attractive for users, which in turn boosts conversions. To be more specific, the website redesign itself supports businesses in presenting services more clearly, simplifying the service order (or purchasing) process, and rolling out new features more quickly. But even a great-looking redesign can affect the search visibility that has been bringing customers to your site for years. Because Google search engines need some time to adapt to these changes and show those pages for relevant searches related to your services. It can affect page accessibility, useful content, internal links, and technical settings.

To reduce these risks, three things need to work together: design planning, development (design realization), and SEO.

For TRIARE, modernizing the existing website is an opportunity to combine improvements to the user experience with the development of its technical infrastructure. Below, we’ll look at what needs to be considered before, during, and after the redesign to protect search visibility and lay the groundwork for future growth.

When should you redesign an old website?

An old website redesign makes sense if the current website structure becomes a real bottleneck for users to take a target action and for the business to grow. The age of a website alone does not determine whether it needs to be updated. The more important thing is how well it fits with the company’s current services, customer expectations, and technical needs.

For example, a company has expanded its range of services, but the navigation still reflects the old business structure. Visitors can’t find the offering they’re looking for, despite the page having the same name. Or the website receives relevant traffic, but users don’t finish filling out the form because the fields are difficult to use on a smartphone. These are specific issues that should be investigated before changing the design.

Not sure if it’s time for a redesign? Your website can give you a few clear signals:

– Some problems arise with user flows, which create difficulties for users to compare services, find terms of service, or submit a request.

– Adding pages and updating content require constant developer intervention.

– Outdated dependencies and complex integrations make changes slow and risky.

– The website showcases outdated products, target audiences, or positioning.

But at the same time, drops off of some indicators (like incoming requests) doesn’t definitely mean that the reason is an outdated website and that it must be changed urgently. The reason can be hidden in changes in demand, a misaligned target audience, or analytical errors. What we want to convey is that a website redesign shouldn’t happen just because the site feels outdated or there is one indicator that drops. There should be more pressing business reasons behind it – issues that affect performance, user experience, organic conversions, SEO, and other key website metrics.

Thus, first, you should test the hypothesis, and then determine the scope of the work.

It’s also important to distinguish between interface updates and system modernization. If the problem lies in the architecture, new layouts won’t fix it. If the technical foundation is working well, a complete rewrite may be unnecessary as well.

At TRIARE, we specialize in CMS customization and legacy system upgrades, so the scope of changes can be determined based on the specific product’s condition. For a business, the right outcome of the first stage will be a well-reasoned decision: localized UX improvements, phased modernization, or a comprehensive redesign with a platform update. Each option must be based on a measurable problem and the expected business outcome.

What should you audit before redesigning a website?

Before redesigning UI/UX or website architecture, it’s crucial to define what is already working well and brings value to your business, then – what is broken and what design elements must be migrated to the new website version. If you skip this step, you risk changing or removing parts of the site that already work for your customers.

Start by auditing your URLs. Compare the results of your site scan with data from your CMS, XML sitemap, Google Search Console, Core Web Vitals, analytics, and external links. You won’t always find pages that have no internal links, even if they still appear in search results or get visitors from other places. So, there must be a comprehensive analysis with use of different tools. 

Then, combine all results you get into one single table.

Search Console shows how users find your site on Google, while Google Analytics helps you analyze their behavior after they land on your site. These systems complement each other but measure different things.

Don’t evaluate pages based solely on traffic volume. A highly specialized service may have few visits but generate high-quality leads. A useful technical article can attract backlinks and help clients assess the company’s expertise.

The result of the audit should be a list of solutions with priorities, responsible parties, and acceptance criteria. At TRIARE, we use this as a shared starting point for designers, developers, and SEO specialists. It helps us decide which pages need attention first, which user flows should be improved, and which technical limitations need to be addressed.

How to manage existing URLs and plan 301 redirects during a redesign?

We recommend keeping existing URLs if there is no clear reason to change them or if they work well. For those pages you plan to move, prepare a detailed map of permanent redirects. You can redesign the site or update the CMS without changing existing URLs.

The SEO website migration map should link each old URL to a decision regarding its future. Include the destination URL, the expected HTTP status, the reason for the change, and the checking results. This will help the SEO specialist and the developer be on the same page. 

There are some cases that may occur during page migration and solutions SEO specialists will provide. 

According to Google’s documentation, a permanent redirect signals that the target URL should be considered the canonical version. However, it does not make an irrelevant page a full-fledged replacement for the old one.

For example, always redirect a page for a specific service to its updated version. Having deleted content automatically redirected to the homepage is annoying and could be interpreted as a soft 404. Google also recommends keeping redirects in place for at least a year. If there are active external links, it’s often advisable to maintain them for longer.

Additionally, update internal links so that they lead directly to the final URLs. Eliminate loops and unnecessary chains of redirects. Check URL variations with slashes, parameters, and language prefixes if they were used on the old site.

For high-priority external links, ask the site owners to update the URLs whenever possible. At the same time, the redirects themselves should work regardless of whether they agree to do so. You need to check the entire migration map, not just a few of the most popular pages. Only after this, the work on redirects and page migration can be considered successful.

How to preserve content, structured data, and important SEO tags during a redesign?

To preserve the SEO value of high-performing content means transferring its useful message, ensuring it meets the audience’s needs, and preserving important technical elements. This doesn’t require copying all the old text word for word at all. Understanding the user’s needs can help the team improve the content.

Before working on mockups, identify which page parts help the client make a decision: service description, features, examples, FAQs, or terms of service. Omitting these sections in the name of a minimalist design can make the page less useful, so it is vital to keep its meaning and structure.

To migrate the content, prepare the following elements:

– Title and meta description. Make sure the new CMS doesn’t replace custom values with generic templates.

– H1 and H2 headers. Maintain a clear page topic and a logical section structure.

– Main content. Transfer important explanations, tables, images, and documents.

– Internal links. Keep relevant links to related services and materials.

– Structured data. Check the markup types, property values, and URL validity.

The title, visible heading, and other elements may be used by Google to generate the search result title. The meta description sometimes serves as the basis for the description that appears below it, but Google may choose a different snippet from the page. A change in H2 does not in itself mean a loss of ground. The risk may arise when, along with the structure, important explanations are lost or the main theme of the material changes.

Micro-markup must match the visible content. For example, you cannot leave the old price in the “Product” element if the page already displays a different price. Correct markup does not guarantee a rich result, but errors in it can disqualify the page from receiving one.

And don’t forget about the website’s mobile version. Google uses its content for indexing and ranking. Therefore, key explanations should not be hidden on smartphones. At TRIARE, we address these requirements and identify issues such as a poor mobile experience as early as the prototyping stage, before the new templates move into development.

How to test a redesigned website before launch

Once the work on website redesign is done, there is time to check the three core things: whether custom scripts are working, whether the content is accessible to search engines, and whether the data has been migrated correctly. Because simply reviewing mockups and opening the home page manually is not enough.

Testing must be conducted in a separate environment protected from unauthorized access, such as through authentication. The team must determine in advance which restrictions are intended for the test site and should not be included in the public version.

A standard list of checks includes:

– URLs and server responses. Check the migration map, destination URLs, and ensure there are no unexpected errors.

– SEO elements. Compare the content, title, headings, canonical tags, and indexing directives with the specifications.

– Rendering. Make sure the main text and navigation are available after JavaScript has executed.

– Micro-markup. Verify the types supported by Google using the Rich Results Test, including by inserting code.

– Business scenarios. Test forms, search, registration, and checkout.

– Analytics. Verify that events are tracked correctly and are not duplicated.

Google processes JavaScript, but blocked resources and runtime errors can prevent content from being displayed. Therefore, checking the rendered page is especially important after making changes to the front end. Evaluate performance on typical pages and mobile devices. Benchmarks for good Core Web Vitals: 

– LCP up to 2.5 seconds; 

– INP up to 200 milliseconds; 

– CLS up to 0.1. 

These apply to the 75th percentile of real-world visits. The launch should be tied to agreed-upon readiness criteria, and a backup copy and recovery plan should be prepared, taking into account new requests and orders. Immediately after publication, recheck indexing, forms, redirects, and analytics on the live domain: environment configurations may differ. 

What SEO mistakes can cause rankings to drop after a redesign?

Even when everything is done correctly, a finished redesign can affect website SEO. When Google loses access to pages, receives conflicting signals, or encounters less useful content. At the same time, a decrease in search queries may be the result of an inconvenient user interface, even without a drop in rankings. It is important for businesses to distinguish between these causes.

The common issues can be grouped according to their mechanism.

Another exposure hides in heavy images, excessive JavaScript, and an unstable layout. These can negatively impact Core Web Vitals. Cumbersome mobile menus and forms also create barriers to conversion.

As a result, customer engagement suffers in two ways: fewer people find the site, or fewer visitors complete a form. That’s why a redesign audit should look at both search visibility and how real users move through the site, not just a handful of keyword rankings.

TRIARE’s approach to redesigning legacy websites: from audit to launch

When redesigning a legacy website at TRIARE, we look beyond the visuals. Business goals, UX, technical modernization, and SEO all need to work together from the very beginning.

That actually means working not only with new pages, but also with the existing system behind them – the CMS, integrations, accumulated content, and technical dependencies that have built up over time.

Our website redesign services include CMS customization and legacy system modernization, so design and technical changes can be planned within one project. SEO requirements are also considered early, especially when valuable pages, content, or URLs need to be preserved.

We usually structure this work around five stages:

– Audit and goal setting. We assess the current technical state, identify valuable pages and weak points, and define the metrics we’ll use to measure the result.

– Architecture and migration planning. We decide what should stay, what needs to be modernized, and how content can be migrated without unnecessary losses.

– UX/UI design. We simplify navigation, user flows, and CTAs while keeping content and SEO requirements in mind.

– Development and testing. We implement templates, integrations, and redirects, then test performance (to detect slow loading and weak spots), rendering, and functionality.

– Launch and monitoring. We test the production environment and track what changes after release.

For example, if a company wants to restructure its services, we first compare the new structure with the existing landing pages. Only after that do we define navigation and URLs. This helps avoid unnecessary migration work and prevents important business areas from becoming harder to find.

The TRIARE team follows a structured approach where we combine UX redesign with technical modernization and work alongside the project’s SEO specialists to make sure those requirements are built into implementation. Clear ownership also matters – who approves page removals, checks redirects, and signs off on launch.

For us, a redesign isn’t complete just because the website matches the mockups we prepared. The final product should be easier to use, easier to scale, and supported by a controlled migration process with clear performance metrics. That gives the business a stronger foundation for future improvements.

How to monitor rankings and organic traffic after a website redesign?

Just right after a redesign, you need to monitor page accessibility and indexing, search traffic, and business results. There’s no way to tell if a service isn’t visible or if the mobile form isn’t working from one general traffic chart.

Before launch, keep the baseline metrics for a representative period. For seasonal businesses, include a comparison with the corresponding period from the previous year. Note the release date, URL changes, and a list of significantly redesigned pages.

Once the site is live, it’s important to track a few key metrics:

In the early days, it’s advisable to monitor critical errors daily; later on, a regular analysis of trends is sufficient. How often you check depends on the size of the migration and how important organic traffic is to the business. Temporary fluctuations are possible, but an explicit “noindex” tag, a broken redirect, or an inaccessible page must be corrected immediately, without waiting for things to “stabilize.”

Conclusion

A redesign that protects organic traffic starts with knowing what already works. Once you understand which pages, user flows, and search signals are bringing value, you can update the structure, UX, and technology with much more confidence.

Rankings can still move after a redesign, so the goal is to reduce unnecessary risk. That means planning the migration carefully, testing before launch, and watching performance closely once the new site goes live.

If your website is due for an update, TRIARE can help you assess the current setup, identify what should stay, and plan the redesign together with the technical modernization. We start with three simple questions: What’s already working? What’s getting in the way of users? And which changes can bring the most value to the business? 

Let’s get to work!