Redesigning a company website: fifteen things to get right

After a business website has been in use for a while, problems often start to appear:

The website no longer matches the current brand image, the mobile experience is poor, the content is getting harder to manage, and the business may even have developed new products and services while the website is still stuck where it was several years ago.

At this point, businesses usually start to wonder:

"Should we rebuild our website?"

But a website redesign isn't just about switching to a new visual design.

A complete business website redesign may involve site structure, content, user experience, SEO, technical architecture, features, and data tracking all at once. If you only change the look without addressing the problems that were actually holding back the website's performance, the new site may look more modern but won't necessarily produce better business results.

On the other hand, redesigning more often isn't necessarily better.

If the current website still meets the business's needs and only some content or pages need adjusting, ongoing optimization may be enough; you don't necessarily need to rebuild the entire site.

This is especially true for businesses that have already built up search traffic and content: they need to be even more careful with a redesign.

Changing URLs at will, deleting old content, or changing the site structure during a redesign can all affect the search performance you've built up. So before a redesign, besides planning the new site, you also need to take stock of which digital assets on the old site are worth keeping.

The real purpose of a website redesign shouldn't just be to make the site "look updated," but to take a fresh look at the website so it once again meets the business's current and future needs.

This article covers whether a website needs a redesign, what to assess beforehand, the redesign process, SEO and content migration, and common redesign mistakes, summarizing the key points businesses should keep in mind when redesigning their website.

If you just want a quick overview of what to watch out for in a business website redesign, start with these key points:

A website redesign means re-planning and adjusting an existing website so it better fits the business's current brand, user needs, and business goals.

A redesign can be small in scope or very comprehensive.

Some businesses only need to adjust the visuals; others need to reorganize the site structure, content, and features, or even replace the underlying technical architecture.

So a "website redesign" doesn't necessarily mean rebuilding the entire website from scratch.

A business should first identify what's wrong with the current website, then decide how far the changes need to go.

If the site's basic structure and features still meet your needs but the visuals no longer reflect the current brand, you can make visual-level adjustments.

For example:

This kind of redesign mainly addresses brand presentation and the user interface, and doesn't necessarily require rebuilding the whole website.

As a business's products, services, or content grow, the original site structure may no longer fit.

Common situations include:

At this point, you need to reorganize the information architecture.

For example, a site that originally had only:

Home → Company overview → Products → Contact us

may need to be re-planned as the business grows into:

Home → Solutions → Products/Services → Case studies → Resource center → About us → Contact us

The purpose of this kind of redesign is to bring the site structure back in line with the business's current content and customer needs.

Some websites' content and visuals are still usable, but the business's operational needs have changed.

For example, you may need to add:

In this case, the core of the redesign isn't the visuals but giving the website new business capabilities.

If the current site architecture can still support these features, you can simply extend it; only if the original platform is too limiting do you need to consider rebuilding.

When a website has been in use for a long time, it may also run into technical problems.

For example:

At this point, you may need to reassess the website's technical architecture.

A technical rebuild doesn't necessarily mean the website's look has to change completely; sometimes it's the opposite: keeping the existing brand and content while rebuilding the underlying system.

If a business is facing all of these at once:

a complete redesign may be the better fit.

In this case, you should treat the website as a new project and reconfirm:

Business goals → User needs → Site structure → Content → Design → Features → Technology

rather than patching the old site item by item.

So website redesigns can actually be divided into different levels:

Partial optimization → Visual redesign → Structure and feature adjustments → Technical rebuild → Complete redesign

Businesses should decide the scope of the redesign based on the actual problems, rather than assuming "redesign = redo everything."

That way, you can put your budget and time into the areas that really need improvement.

There's no fixed lifespan for a business website.

Some websites keep supporting the business's brand, content, and customer acquisition for many years; others need readjusting soon after launch because the business's strategy or needs have changed.

So rather than asking:

"How many years before a website needs a redesign?"

the more important question is:

"Can the current website still effectively support the business's needs?"

If any of the following apply, you can start assessing whether a website redesign is needed.

Businesses keep growing, and the brand may change along with them.

For example:

If the business has changed noticeably but the website still shows information from several years ago, potential customers may not get an accurate picture of the business today.

What needs adjusting then isn't necessarily just the visuals; it may also include the site's content, core messaging, and information architecture.

If the website was built a while ago, it may have been designed mainly for desktop computers.

Common problems include:

These problems directly affect how visitors use the website.

Google also currently uses mainly the mobile version of a site's content for indexing, so if the mobile version has obvious problems, it's worth fixing them first.

If the website frequently has:

and every fix takes a lot of time, it may mean the site's underlying architecture has started to become a maintenance burden.

At this point, you can compare:

The cost of continuing to patch the old system vs. the cost of building a stable new architecture

If long-term maintenance costs are already too high, a technical rebuild may make more sense than continued patching.

As a business accumulates more products, articles, case studies, and service content, an originally simple site structure may gradually become messy.

For example:

This usually means the site's content architecture or management approach no longer fits current needs.

In this case, the focus of the redesign should be reorganizing the content and management workflow, not just replacing the front-end design.

Once a business starts doing digital marketing, it may find the old website struggles to support the new strategy.

For example:

If the website has become a constraint on the business's SEO, advertising, or content marketing, you need to assess whether to adjust the structure or rebuild.

As a business grows, the website may need to take on more functions.

For example, a site that originally had only:

Company overview → Product showcase → Contact us

later needs to add:

If the current website can reasonably be extended, a full redesign isn't necessarily needed.

But if every new feature requires extensive changes, or is even blocked by the original platform's limitations, you can start assessing a new site architecture.

Another situation worth checking is this:

People are actually visiting the website, but it rarely generates inquiries, bookings, or other business results.

The problem may come from:

But this situation doesn't necessarily mean the whole site needs a redesign.

You should first identify the problem through website data and real customer feedback, then decide whether partial optimization is enough or the whole website needs redesigning.

Simply put, the real signal that a website needs a redesign isn't:

"This website looks a bit old."

but:

"This website can no longer effectively do what the business now needs it to do."

Once you've decided to redesign the website, the first step shouldn't be to start designing the new site right away.

If the old website has been running for a while, it has usually built up quite a few valuable assets, such as search rankings, site traffic, external links, articles, popular pages, and user data.

So before a redesign, you should first do a complete audit.

This not only helps a business identify the problems that really need fixing, but also avoids accidentally losing results it has already built up during the redesign.

First, make the reasons for the redesign concrete.

For example:

Different problems lead to different approaches to the redesign.

If the real problem is the content structure, you shouldn't put most of the budget into a visual redesign.

So before a redesign, it's best to set clear redesign goals that serve as the basis for every decision that follows.

If the website already has Google Analytics, Search Console, or other analytics tools installed, review the existing data before the redesign.

For example:

This data helps a business judge which content has real value.

If a page that looks very old still brings in search traffic every month, you shouldn't delete it just because the new website "doesn't want this page."

Before a redesign, you can organize the website's pages into a list, for example:

This keeps you from deciding what stays or goes purely based on the new website's structure.

What you should really consider is:

Does this page still have user, search, or business value today?

If the old site already has search visibility, record the important SEO information before the redesign.

For example:

The most important of these is building:

Old URL → New URL

a mapping table.

If URLs will change after the redesign, plan the corresponding redirects in advance rather than dealing with them only after the new site launches.

Don't assume all of the old site's content should be migrated, and don't assume all of it should be rewritten either.

You can sort the content into:

This way, the new website's content is usually more complete than if you simply "copy the whole site."

The customer needs at the time the business built its old site may differ from today's.

So it helps to reorganize:

Feedback from sales, customer service, and actual customers can often provide information that website analytics tools can't see.

This information can directly shape the new website's content and structure.

Only after finishing the audit of the old site should you go on to define what the new website should achieve.

For example:

At the same time, it's best to set measurable metrics.

For example:

Goal: Increase leads

You can track:

That way, once the redesign is finished, you can judge whether the new website is truly more effective than the old one, not just whether it "looks newer."

So before a website redesign, you can first complete three things:

Audit the old site → Find the real problems → Define the new site's goals

Once this work is done, planning the new site's structure and design is usually more solid than starting directly with a visual redesign.

If the old site has already built up organic search traffic, SEO should be part of the redesign from the early planning stages, not something you deal with only after the new site is finished.

That's because search engines already know the old site's:

If a redesign changes large numbers of URLs, deletes content, and adjusts the site structure all at once without building correct old-to-new mappings, search traffic may drop.

So during a website redesign, pay special attention to the following SEO points.

If a page meets these conditions:

there's usually no need to change its URL just because of the redesign.

For example, the original service page is: /website-design

If the new website still introduces the same service, you can consider keeping the original URL.

This reduces the work search engines have to do to understand the page again, and it also lowers the complexity of the site migration.

If the new website really does need to change URLs, you should build:

Old URL → New URL

mappings.

For example: /old-service

is changed to: /solutions/new-service

The old URL should then redirect to the most relevant new page.

Google recommends using permanent server-side redirects, such as 301 or 308, when a site permanently changes its URLs.

Don't redirect all the old URLs to the homepage.

Each important old page should redirect to the new page with the closest content.

A common practice during a redesign is to remove old articles or pages outright because they "don't look important."

But some pages may:

So check the data before deleting anything.

If the content still has value, you can:

Keep → Update → Merge → Recreate

If you're sure it's no longer needed, also assess whether there's a suitable replacement page to redirect to.

Before the new website launches, also confirm that important pages' SEO settings weren't lost during the move.

For example:

A redesign can of course re-optimize this content, but you shouldn't clear it all out or rewrite it without a strategy.

Especially for pages that already perform well in search, first understand why they get traffic before deciding how much to change them.

When the site structure changes, internal links need to be updated too.

For example:

If old articles still link to the old service URL, it's best to update those internal links directly to the new URL, even if a 301 Redirect is in place.

You should also check:

Make sure the site doesn't keep relying heavily on old URLs internally.

After the new website launches, the XML Sitemap should reflect the URLs you actually want search engines to index now.

Also confirm that Canonical is set correctly.

Common problems include:

These technical settings don't appear directly on the website's pages, but they affect how search engines understand the site.

After the website officially launches, keep an eye on the following through Google Search Console:

If you're also changing domains, Google Search Console provides a Change of Address tool to help with the site move.

Note that short-term fluctuations in search performance after a website redesign aren't unusual.

What really matters is ongoing monitoring to confirm that search engines can access the new site normally and that old pages have been correctly mapped to the new content.

If you can control the scope of the redesign, avoid making lots of unnecessary changes in the same migration.

For example, doing all of these at the same time:

makes it harder to pinpoint the cause when something goes wrong.

Google's site migration guidelines also recommend changing only one major thing at a time during a site move, where possible.

If the business had almost no organic search traffic to begin with, the redesign has more room for change.

But as long as the old site has built up search rankings, content, or external links, treat these as the business's existing digital assets and keep them when redesigning the website.

Not necessarily.

When businesses redesign their websites, they often take one of two extremes:

One is to move all of the old site's content to the new site unchanged; the other is to assume the old content is outdated and simply start over from scratch.

Neither approach is necessarily right.

If the old site has been running for years, it may contain a mix of:

So a website redesign is actually a good opportunity to reorganize the business's content assets.

If a page currently still:

there's usually no need to delete it for the sake of the redesign.

For example, an expert article published two years ago is still a valuable website asset if its content is still accurate and it keeps bringing in leads through Google.

This kind of content can be kept as is, or adjusted in layout and reading experience to fit the new website.

Some content covers topics that are still important, but parts of the information no longer reflect the current situation.

For example:

This kind of content is usually better updated than deleted.

Especially if the page already has search visibility, updating the content usually lets you keep its original topic and URL while improving the quality of the information.

The longer a website has been running, the more likely it is to have several pieces of content on very similar topics.

For example:

If the three articles overlap heavily and there's no clear difference in search intent between them, you can consider combining them into one more complete piece.

After merging, URLs that are no longer used should redirect to the new main page.

This makes the site's content structure more focused and reduces similar content competing with itself.

Not all old content is worth keeping.

For example:

If these pages have:

you can consider removing them.

But before deleting, you should still check whether there's suitable replacement content.

If there's a clear new page that can take over the original need, you can set up a redirect; if there's no related replacement content at all, there's no need to force every page to redirect to the homepage just to avoid a 404.

Some old pages don't get much traffic right now, but their topics are still very important to the business.

For example:

You can't conclude that this kind of content has no value simply because it "doesn't get traffic right now."

If it's closely tied to the business's current strategy, you can re-examine:

and then recreate it as a more complete page.

You can judge it from three angles:

Then decide:

Keep → Update → Merge → Recreate → Delete

rather than deciding what stays or goes based only on when an article was published.

So a website redesign is also a good opportunity for a business to reorganize its content strategy.

By keeping the content that truly has value, updating outdated content, merging duplicate content, and then removing content that serves no purpose, the new website won't just have a new look; it will have a healthier content foundation that's easier to manage over the long term.

A website redesign involves design, content, SEO, features, and technology. If you focus only on the new website itself, it's easy to overlook the content and data the old site has already built up.

Here are some common mistakes businesses make when redesigning their websites.

The most common approach to a redesign is to redesign the homepage, switch to a new color scheme, and adjust the site layout.

If the old site's real problems are:

simply changing the visuals won't make these problems go away.

So before a redesign, first confirm whether what really needs improving is the brand, content, structure, features, or technology, and then decide the scope of the redesign.

Even if the old site looks outdated, it may still have valuable pages.

If you re-plan the website without looking at Google Analytics, Search Console, or other website data, it's easy to accidentally delete:

So a website redesign should start by understanding the old site through data, and then decide which content to keep or adjust.

The new website may reorganize the information architecture, but that doesn't mean every URL needs to change.

If the original URL:

you can usually consider keeping it.

If it really does need to change, build a complete old-to-new URL mapping and set up appropriate permanent redirects.

Don't wait until the website officially launches to start figuring out where the old URLs went.

"The new website wants a fresh start" isn't a good enough reason to delete old content.

Old content may still have:

So first judge whether the content is best suited to:

Keep, update, merge, recreate, or delete.

Pages that already have organic search traffic and external links, in particular, should never be removed without assessment.

The opposite of deleting everything, another common mistake is copying the old site in full to the new website.

If the old site itself has:

moving everything over just brings the old site's problems to the new site.

A website redesign should include organizing the content, not just moving data from one place to another.

SEO shouldn't be a setting you add just before the website launches.

If you wait until the whole website is finished to start thinking about SEO, you may only then discover that:

So as long as the old site already has search traffic, SEO should be involved from the redesign audit and information architecture stages.

After a website redesign, if you don't confirm that analytics tools and conversion events are working properly, you may end up with:

"The website has launched, but we have no idea whether the new version is actually any better."

So before launch, confirm that:

are all still working properly.

Only by keeping data from before and after the redesign can a business compare the website's actual results.

A successful launch doesn't mean the redesign project is completely over.

In the early days after launch, you may still see:

So after the official launch, keep monitoring how the website is running and how it performs in search, and deal with any anomalies as quickly as possible.

Once a business has decided to rebuild its website, it's easy to start thinking:

"Since we're redesigning anyway, we might as well do everything at once."

So membership, AI customer service, booking, transactions, and all kinds of system integrations get added at the same time.

But if there's no clear need for these features, they will not only raise the budget but also increase the project's complexity and ongoing maintenance costs.

A redesign should still prioritize solving the most important problems right now, while keeping reasonable room to expand for future needs.

So before the website officially launches, a business can do one final check:

Did what was working before stay? Were the existing problems really solved? Can the new website's results be measured?

These three questions are better at judging whether a website redesign succeeded than "Does the new website look newer?"

A website redesign isn't just redesigning how a website looks; it's an opportunity to take a fresh look at the business website.

As a business's brand, products, customers, and business model keep evolving, a site structure and features that once fit may gradually stop meeting current needs.

But that doesn't mean a business needs to rebuild everything just because the website "looks old."

What really needs to be judged is:

Can the current website still effectively support the business's current goals?

If the problems are only some content, visuals, or user flows, start with partial optimization; only if the website has clearly become a constraint on content management, SEO, technical architecture, feature expansion, or customer experience should you go on to assess a complete redesign.

For a website that has been running for a while, there's one more very important thing during a redesign:

Don't throw away what the old site has already achieved.

Search rankings, popular pages, expert articles, external links, customer behavior data, and conversion records are all digital assets the business has built up over time.

So a complete website redesign should accomplish two things at once:

Keep the assets that were already working, and fix the problems that were holding back the website's growth.

So before starting a website redesign, a business can first complete:

Audit the old site → Find the real problems → Define the new site's goals → Protect existing assets → Plan the new site's structure

and then move on to content, design, and development.

A new website built this way isn't just "a new version of the old website," but a website that better fits the business's current needs and can keep supporting its future growth.

If you're assessing whether your business website needs a redesign but aren't sure whether to optimize parts of it, redesign it, or rebuild it completely, you can start by auditing the current website's brand, content, SEO, features, and business goals, and then decide the redesign scope that truly fits.