Website Redesign or Full Rebuild? How to Tell Which One Your Business Needs

Most businesses reach a point where the website no longer feels right. It looks dated next to competitors, the marketing team complains that simple edits take days, or leads have quietly dropped. The usual reaction is "we need a new website", but that phrase covers three very different projects with very different costs and risks.

Choosing the wrong one is expensive in both directions. A rebuild is wasted money if the real problem was tired visuals, and a new coat of paint is wasted money if the platform underneath is slow, insecure or unsupported. Any provider of web development services should be able to tell you which project you need before quoting for it. This guide covers the signs that point to each, what to audit first, and how to protect search traffic along the way.

Refresh, Redesign or Rebuild: Three Different Projects

A visual refresh updates the surface: colors, typography, imagery, button styles and perhaps the homepage layout. The page structure, the URLs, the content management system (CMS) and the code underneath stay the same. It is the smallest and lowest-risk option.

A redesign on the same platform goes further. Navigation, page templates, user journeys and content are rethought, but the site stays on its current CMS or framework, with its existing hosting, data and integrations.

A rebuild replaces the foundation: a new CMS or framework, a new data structure, often new hosting, and every page and integration moved across. It is the only option that fixes platform-level problems, and it carries the most cost and the most risk to search traffic.

Signs a Refresh or Redesign Is Enough

If the complaints are about how the site looks and not how it works, start small. A refresh fits when the design looks dated but pages load quickly, editors can update content without help and visitors still convert at a steady rate.

A redesign fits when the problems are structural but not technical: visitors cannot find key pages, the navigation grew by accident over several years, service pages no longer match what you sell, or the mobile layout is awkward to use. If the platform is still supported and developers can work with it comfortably, none of this requires replacing it.

Signs You Need a Full Rebuild

A rebuild is justified when the platform itself is the obstacle. The clearest signs are:

• The CMS, framework or language version is no longer supported, so security fixes have stopped.
• Pages stay slow after reasonable optimization because of the theme, page builder or plugin load.
• Routine content edits need a developer, or editors avoid the CMS because it breaks layouts.
• The site cannot connect to the CRM, payment, booking or inventory systems the business now depends on.
• Each small change is slow and risky because of years of patches and abandoned plugins.

Support status is the easiest of these to check objectively. PHP, the language behind WordPress, Laravel and Magento, supports each release branch for two years of active fixes and two further years of security fixes only. After that the branch is end of life, and the PHP project warns that unsupported versions may be exposed to unpatched security vulnerabilities. The official PHP supported versions page lists the dates; at the time of writing, security support for PHP 8.2 ends on 31 December 2026. A site that cannot be upgraded to a supported version without breaking has a platform problem, not a design problem.

What to Audit Before You Decide

Opinions about the site are not evidence. Four short audits will usually make the decision for you.

Traffic and conversions

Find out which pages bring in search visitors and which produce inquiries or sales. These are the pages a project must not damage. If traffic is healthy but conversions are weak, the issue is likely messaging and layout, which a redesign can fix.

Content

List every page and mark it keep, improve, merge or remove. The size of this list also tells you how much migration work a rebuild would involve.

Technical health

Check software versions, plugin and dependency updates, hosting, and loading speed. Google's Core Web Vitals give you concrete targets: according to Google's documentation, a good experience means the main content loads within 2.5 seconds, the page responds to interactions in under 200 milliseconds, and the layout shift score stays below 0.1. For the security side, our web application security checklist covers what to review.

Accessibility

Test the site with a keyboard only and with a screen reader, and check color contrast and form labels. The current standard is WCAG 2.2, published by the W3C in October 2023. Legal duties differ between the US and the UK and by type of organization, so take advice on what applies to you; this is not legal advice. Some accessibility problems are simple fixes, while others are built into a theme and only go away when it is replaced.

Protecting Search Traffic During the Project

Lost search traffic is the most avoidable damage in a redesign or rebuild, and changed URLs are a frequent cause. Keep URLs exactly as they are wherever you can. A refresh should change none, a redesign may change some, and a rebuild often changes many because the new platform builds addresses differently.

Where URLs must change, Google's guidance on site moves with URL changes sets out the process: prepare the new site, map each old URL to its new equivalent, implement redirects, then monitor. Google recommends server-side permanent redirects such as 301 and 308, and advises keeping them for as long as possible, generally at least one year. It also warns against redirecting many old URLs to a single irrelevant destination such as the homepage, a tempting shortcut when the redirect map is left until launch week.

Even a well-run move is not invisible. Google states that you may see ranking fluctuations while it recrawls and reindexes the site. Plan the launch away from your busiest sales period, and agree in advance who watches Search Console and analytics afterward.

Content Migration: The Work That Gets Underestimated

In a rebuild, content is often what holds up the launch. Every page, image, document, form, page title and meta description has to be moved, checked and often rewritten to fit new templates. Blog archives, product data and user accounts may need scripted imports and a trial run.

Use the content audit to shrink the job. Migrate what earns its place, merge thin pages, and redirect what you remove to the closest relevant page. Decide early who owns content on your side, because an agency can move text but cannot decide what your business wants to say.

How to Phase the Work

You do not have to do everything at once. A sensible order is to fix urgent risks first, such as unsupported software or a broken checkout, then deal with structure and content, and leave visual polish for last. That stops you from paying to decorate a site that is about to be replaced.

For the launch itself, Google suggests that smaller sites move everything at once, while larger sites may move in sections, at the price of more complicated monitoring. A large rebuild can therefore go live in stages, for example the blog first and the store later.

Common Mistakes to Avoid

The most common mistake is redesigning for taste instead of goals. "The director dislikes the homepage" is not a brief. A brief names a measurable outcome, such as more quote requests from service pages or fewer abandoned checkouts, and judges every design decision against it.

Other mistakes are just as avoidable: rebuilding because a developer prefers a newer framework when the current one serves the business, deleting old pages without checking whether they bring in traffic, leaving redirects, analytics tracking and form testing until launch day, and handing over a site that editors cannot maintain.

What to Do Next

Before you ask anyone for a quote, spend a week gathering facts:

• Write down the two or three business results the site must improve.
• Export your top landing pages and converting pages from analytics and Search Console.
• Record your CMS, language and plugin versions and check whether each is still supported.
• List the edits your team cannot make without a developer.

With that in hand, the choice is usually clear, and any agency you speak to can give a far more accurate estimate.

Conclusion

A refresh fixes how a site looks, a redesign fixes how it is organized, and a rebuild fixes what it runs on. Match the project to the actual problem, base the decision on an audit and not on opinion, and treat URLs, redirects and content migration as core work, not afterthoughts.

If you would like a second opinion on which route fits your site, Entrant Technologies builds websites and web applications and can review your current setup. You can request a quote with your audit notes attached.