Website redesign: improve the current site or rebuild it?

A website redesign does not always require a complete rebuild. If the problem is limited to a few screens, a form or the way the offer is explained, focused improvements may be the better investment. A rebuild becomes sensible when the current structure, technology or content workflow blocks the business and every new change needs another workaround.

The decision should follow a short audit, not the age of the website or a general feeling that it looks dated. You need to know where users struggle, which pages attract useful search traffic, how the mobile experience behaves and whether the existing platform can support the next stage of the offer.

Refresh, redesign or rebuild?

These labels are often mixed together, but they describe different scopes.

• A visual refresh improves selected design elements and content without changing the foundation. It may cover typography, colour, imagery, buttons and a few sections.
• A redesign revisits the user journey, information structure and visual system. Some of the existing platform may remain, but the interface is planned again around current goals.
• A rebuild replaces the architecture, design and implementation. It is justified when old code, the CMS or integrations make safe development unnecessarily difficult.

Choosing the largest option simply for more creative freedom wastes budget. Adding another cosmetic layer to a platform with known structural limits wastes it too. The right scope comes from diagnosing the problem.

7 signs that your website needs work

1. The business has changed more than the website

Your company may have entered a new market, changed its sales model or prioritised different services. If the homepage still leads with an offer from several years ago, new colours will not solve the mismatch. You probably need a different content hierarchy and new routes towards contact or purchase.

2. The main action is difficult on a phone

Test the website on several real devices. Can people read the copy comfortably? Do the menu, form, basket and buttons work without zooming? Individual defects can be fixed. If the whole desktop layout has simply been squeezed onto a narrow screen, a deeper redesign is usually more effective.

3. Customers keep asking about information that is already there

This often signals a structure problem rather than a content shortage. Important details may sit behind unclear labels, be split across unrelated pages or appear without enough context. Before adding more paragraphs, review the order of sections and the language customers use in sales conversations.

4. Every content update needs a developer

Not every part of a website needs an editing panel. However, if changing a price, project, team member or article requires a code change, the current system may not fit the way the business operates. A well-planned CMS can sometimes be added. In other cases, rebuilding the content layer is cleaner and cheaper to maintain.

5. The site feels slow or unstable

Do not rely on one overall test score. Review how quickly the main content appears, how promptly the page responds after an interaction and whether elements move while loading. Core Web Vitals describe these areas through LCP, INP and CLS. web.dev maintains the current definitions and measurement guidance.

Slow images or one heavy script can often be optimised without a rebuild. Performance problems spread across a theme, many plugins and several third-party tools may point to a weak technical foundation.

6. The platform blocks required features

If the store needs inventory integration, the website must connect to a CRM or the enquiry form should feed a sales workflow, assess the limits and quality of the current system. An integration plan should not depend on stacking unrelated add-ons with no clear maintenance owner.

7. Nobody knows whether the website produces enquiries or sales

Missing measurement does not automatically justify a rebuild. Start by configuring analytics for form submissions, phone clicks and key stages of the checkout. The data can then show whether the problem sits in traffic quality, the offer, the interface or the follow-up process.

When focused improvements are enough

Keeping the current website is reasonable when its foundations are sound and the problem can be described precisely. Common examples include:

• an unclear first screen,
• a long or awkward enquiry form,
• weak presentation of completed work,
• no clear primary action,
• outdated copy and photography,
• several isolated mobile defects,
• oversized images or poorly loaded fonts.

A useful improvement project has a baseline and a finish line. Instead of asking to “make the website feel modern”, define the job: shorten the form, restructure the offer, fix the mobile layout and measure successful enquiries.

If content is the main weakness, begin with our guide to preparing content for a business website. A new visual layer cannot rescue an unclear offer.

When a full rebuild is the better option

A rebuild is usually easier to justify when several problems are connected:

1. the structure no longer represents the offer or its audiences,
2. most pages need substantial mobile repairs,
3. the CMS is difficult to use, outdated or hard to secure,
4. the code obstructs integrations, analytics and continued development,
5. the interface has no consistent component system,
6. old URLs and content were created without a coherent architecture,
7. the cost of repeated repairs is approaching the cost of a planned implementation.

Technology should be selected only after these needs are clear. If a platform change is under consideration, read our practical comparison of Next.js and WordPress.

What to audit before the first design

A redesign should begin with an inventory, not a mood board. Collect:

• every current URL,
• landing pages that attract traffic or enquiries,
• queries reported in Google Search Console,
• sources of valuable visits,
• common form and checkout failures,
• content that should be kept, improved or removed,
• integrations, accounts, consent tools and scripts,
• requirements of the people who will edit the website.

Review keyboard access, colour contrast, alternative text, form labels and behaviour when text is enlarged. The official reference is the Web Content Accessibility Guidelines 2.2. Automated testing is useful, but it cannot replace a person checking the most important journeys.

This is also a good point to review selected AMCompany projects, not to copy their appearance but to see whether the design approach changes with the audience, content and job of each website.

How to redesign without creating avoidable SEO losses

The greatest risk appears when the new website changes or removes URLs that already receive search traffic and links. Before development, create a map. Every important old URL should remain in place or lead to the most relevant new destination.

Google recommends steps including:

1. testing the new website thoroughly,
2. mapping old URLs to their new equivalents,
3. using permanent server-side redirects, commonly 301 or 308,
4. updating internal links, canonicals and hreflang annotations,
5. submitting an updated sitemap,
6. removing temporary noindex rules and incorrect robots.txt blocks,
7. monitoring indexation and crawl errors after launch.

The full process is documented in Google Search Central's site migration guidance. Sending every removed page to the homepage is not a safe shortcut. Each old URL needs a destination that continues to satisfy its original purpose.

How to define the redesign scope with a supplier

Bring three things to the first conversation: the business goal, known problems and technical constraints. Agree on:

• which parts of the current website will remain,
• which content and URLs must be preserved,
• which user actions will be measured,
• who owns copy, SEO, integrations and migration,
• how mobile behaviour and accessibility will be tested,
• what support is included after launch.

If you are comparing proposals, our guides explain what a business website costs and how to choose a web design company.

An old website does not automatically need a revolution. The first job is to separate local defects from system-wide constraints. As part of AMCompany's website design and development service, we can review the existing site, identify what is worth keeping and define a scope without rebuilding everything by default. To discuss a specific case, send the current URL and a short description of the goal.