Skip to content

Odduel

We put the odds in your favour

Insights

Refresh or rebuild website: how to decide

Refresh or rebuild your website? A four-layer decision test, a side-by-side comparison, the hidden costs of each route and how to stage the work.

Printed page layouts and a laptop on a studio table during a review of whether to refresh or rebuild a company website

The refresh or rebuild website decision comes down to one question: is the problem on the surface or in the foundations? Refresh when the structure, platform and code still serve the business and only the look, content or a few templates have aged; rebuild when the platform, the information architecture or the code itself stops you from doing what the business needs. This guide gives a practical decision test, a side-by-side comparison, the hidden costs on each side and what to do when the answer is “both, in stages”.

Last updated: 17 November 2026.

What is the difference between a refresh and a rebuild?

A website refresh is a change to what visitors see and read, made on the existing foundations: new visual design, updated copy and pictures, improved templates and small functional fixes, with the same platform, the same content structure and most of the same addresses.

A website rebuild is a new site made from the foundations up: a new or upgraded platform, a new content model, new code and usually a new structure of pages and addresses. The old site is retired rather than reworked.

Between the two sits the redesign, a term people use for both. In practice, a redesign can be a deep refresh or a full rebuild, which is why the word alone does not tell you the size of a project. The useful question is not “redesign or not” but “which layers must change”.

At Odduel, a creative and technology agency in Barcelona and São Paulo, our website redesign service starts with exactly that question, layer by layer, before anyone opens a design file.

In short: look at four layers, from surface to core: visual design, content, structure and platform. If only the first two are failing, refresh. If the structure or the platform is failing, rebuild. If you are not sure, an audit of the platform and the content answers it in days, not weeks.

Should I redesign or rebuild? The four-layer test

Every website has four layers. Each one ages at a different speed, and the deepest failing layer decides the size of the project.

  1. Visual design. Typography, colour, layout, pictures, motion. It ages fastest and is the cheapest layer to change. A brand update often only touches this layer.
  2. Content. Copy, pictures, case studies, product data, articles. It goes stale when the offer changes, but it can be rewritten without touching code.
  3. Structure. The page types, navigation, content model and addresses. When the business adds services, markets or languages that the structure was never planned for, pages get forced into places they do not belong.
  4. Platform and code. The CMS or framework, hosting, plugins, integrations and the code written on top. When this layer fails, every change becomes slow, risky or impossible.

Score each layer honestly: does it still serve the next two or three years of the business? The answer for the deepest layer that fails tells you what to do.

Deepest failing layerTypical symptomsRecommended route
Visual design onlyLooks dated, off-brand after a rebrand, weak on phonesRefresh
ContentOffer has changed, pages are thin or outdated, poor search visibilityRefresh with a content rewrite
StructureNew services or markets do not fit, navigation keeps growing, duplicate pagesRebuild, or a structural redesign on the same platform if it is sound
Platform and codeUnsupported versions, fragile plugins, slow editing, security worries, integrations breakRebuild
The four-layer test for deciding whether to refresh or rebuild a website

When is a refresh the right choice?

A refresh is right when the foundations are sound and the gap is mostly perception. Typical signals:

  • The platform is supported, updated and easy for your team to edit.
  • Page speed and accessibility can reach a good level with template changes rather than new code.
  • The site structure still matches how customers look for your services.
  • Most of your search traffic lands on pages that will keep their addresses.
  • The brand has evolved, and the site simply needs to catch up visually.

A refresh keeps what already works: the addresses that rank, the integrations that run, the editing habits of your team. It is usually faster, carries less search risk and costs a fraction of a rebuild.

Its limit is that it inherits every constraint of the old site. If editors already fight the CMS, a new coat of paint will not change that, and you may pay for a second project within a year or two.

The Nothing To Eat website by Odduel on a laptop, a site built on a sound platform that can be refreshed without rebuilding

When does a rebuild make more sense?

A rebuild is right when the foundations block the business. Typical signals:

  • The platform, theme or main plugins are no longer maintained, or updates keep breaking the site.
  • Simple changes need a developer, and small fixes take weeks.
  • The site cannot meet current accessibility expectations without rewriting templates; in the EU, the European Accessibility Act has applied to many consumer services since 28 June 2025.
  • You need features the platform cannot support well: customer accounts, a Shopify store or another online store, multilingual content, bookings, integrations with your CRM or ERP.
  • The content model is so tangled that a new structure would mean rebuilding most templates anyway.

A rebuild costs more and takes longer, and it carries real migration risk for search traffic. In exchange, you get a site planned for the next stage of the business rather than patched from the last one. Our website redesign cost guide explains what drives the budget on each side.

Refresh or rebuild website: pros and cons side by side

The table below compares the two routes on the points buyers usually weigh.

FactorRefreshRebuild
ScopeVisual design, content, some templatesPlatform, structure, code, design, content
TimeWeeksMonths
BudgetSmaller shareLargest share
Search riskLow if addresses stayHigher; needs a full redirect plan
Disruption for editorsLittleNew tools and training
Fixes deep problemsNoYes
Life before the next big changeShorter if foundations are ageingLonger, if planned well
Refresh or rebuild website comparison of scope, time, budget and risk

Neither route is better by default. A rebuild done when a refresh would have been enough wastes money and search equity; a refresh done on failing foundations wastes the refresh.

Which option suits a small or mid-sized business?

For most small and mid-sized businesses, the honest answer starts with the platform audit, not with the design. Three situations come up again and again.

The site is a few years old on a mainstream platform

If the CMS is current and editors can work with it, a refresh is usually the sensible choice. Spend the budget on content, photography and conversion paths rather than on new infrastructure.

The site was built on a page builder or a heavily customised theme

These sites often look fine but become slow and hard to change. If page speed, accessibility or editing are the problems, a rebuild on a cleaner setup usually pays back faster than repeated patching.

The business has changed shape

New service lines, a move into e-commerce or new countries change the structure the site needs. Here a rebuild is often unavoidable, because the content model is the part that no longer fits. If you are unsure what changed, our article on the signs a website needs a redesign helps you name the symptoms first.

What are the hidden costs of each route?

Both routes carry costs that do not appear in the first quote.

Hidden costs of a refresh:

  • Workarounds for platform limits, which add development time to every template.
  • Plugins and old code that stay in place and still need maintenance and security updates.
  • A shorter useful life, so the rebuild is postponed rather than avoided.

Hidden costs of a rebuild:

  • Content migration: moving, cleaning and rewriting pages always takes longer than planned.
  • Redirect mapping and search monitoring after launch.
  • Training editors on the new tools.
  • Integration work with CRM, booking, payment or stock systems that were wired into the old site.

When you compare quotes, ask each supplier to list these lines explicitly. A quote that leaves out migration and redirects is not cheaper; it is incomplete.

How do you protect search traffic in either case?

A refresh that keeps addresses carries little risk, but titles, headings and content of pages that rank still deserve care. A rebuild changes much more, and the search work must be planned before the design is approved.

The essentials are the same either way: benchmark traffic and rankings, keep the content of pages that rank, map every changed address to its new equivalent with permanent redirects, and watch indexing closely after launch. Google’s documentation on site moves with URL changes sets out the mechanics. Our website migration checklist turns this into a step-by-step list for launch.

Can you refresh now and rebuild later?

Yes, and for many businesses it is the best plan, provided the refresh does not deepen the problems a rebuild must later solve. A staged approach works like this:

  1. Audit the platform and content to confirm the foundations will hold for at least another year or two.
  2. Refresh the surface where it matters most: the home page, key service or product pages and the conversion paths.
  3. Clean the content as you go: remove thin pages, merge duplicates, rewrite what ranks poorly. This work carries straight into a future rebuild.
  4. Plan the rebuild’s structure in parallel, so new pages fit where they will eventually live.
  5. Rebuild when the trigger arrives: a platform end of life, a new market, a new product line.

The opposite order rarely works. Rebuilding on a structure you have not yet worked out simply moves old confusion onto new code.

How do you make the decision in practice?

Run a short, structured decision process rather than choosing on taste.

  1. Write down what the site must do in the next three years: markets, services, languages, sales channels, integrations.
  2. Audit each of the four layers against that list, with your editors and your developer in the room.
  3. Check the platform’s support status and the health of its main plugins or modules.
  4. Measure the basics: page speed on key templates, accessibility on main journeys, search traffic by page.
  5. Estimate both routes, including the hidden costs above, and compare their useful life, not only their price.
  6. Decide and record why, so the next project starts from a clear history.

Questions people ask

Should I redesign or rebuild my website?

Redesign on the existing foundations when the platform, structure and code still serve the business and only the look and content have aged. Rebuild when the platform is unsupported, editing is slow and fragile, or the structure no longer fits your services and markets. The deepest layer that fails decides the size of the project.

What is the main difference between a refresh and a rebuild?

A refresh changes what visitors see and read, such as design, copy, pictures and some templates, while keeping the platform, structure and most addresses. A rebuild replaces the foundations: platform, content model, code and usually the page structure. A refresh is faster and lower risk; a rebuild solves deeper problems and lasts longer.

Is a website refresh enough for a small business?

Often, yes. If the platform is current, your team can edit it easily and the structure still matches how customers find you, a refresh focused on content, photography and conversion paths gives most of the benefit at a fraction of the cost. It stops being enough when the platform itself makes changes slow or risky.

Can I refresh my website now and rebuild it later?

Yes. Audit the platform first to confirm it will hold, refresh the pages that matter most, and clean the content as you go so the work carries into the future rebuild. Plan the new structure in parallel and rebuild when a clear trigger arrives, such as a platform end of life or a new market.

Does rebuilding a website hurt SEO?

It can, if addresses change without planning. Search traffic is protected by keeping the content of pages that rank, mapping every old address to its new equivalent with permanent redirects, preparing titles, sitemaps and hreflang before launch, and monitoring indexing and errors closely for the first weeks. Done properly, a rebuild often improves search performance.

Score your site on the four layers this week, with your editors and developer, and the answer usually becomes clear. If you want a second opinion or a plan for either route, see our website redesign service or tell us about your site.

More articles

More from our Insights.

Explore all insights

Get in touch

Let’s change your odds.

Odds do not change on their own. If you have something to build, launch or fix, tell us about it and we will show you how we would approach it.

    Need an NDA before you share details? Start a project

    Chat with us