WebsitesDecision guide
Redesign or a new website: how to decide, and when to leave it alone
Unhappy with your website? You have four options, and the right one depends on where the problem sits.
On this page
Refresh a website when the problem is the look or the words. Redesign it when the structure no longer fits how people buy from you, but the platform still works. Rebuild it, which means a new website, when the platform itself is the problem. And if the site still brings enquiries and only you are tired of it, leave it alone.
Redesigns and rebuilds of existing sites are part of our website design and development work. We'd rather you hear the case for doing less from us first.
Refresh, redesign or rebuild: which one you need
A refresh changes the look and the words on the pages you already have. A redesign also changes the structure: which pages exist, how the menu groups them and what each page asks a visitor to do. A rebuild is a new website, on a new platform or in new code, with your content carried across. Any address that changes needs a redirect, which forwards visitors and search engines from the old address to the new one.
| If this is true | Then |
|---|---|
| People still find what they need, but the site looks dated or the words no longer describe what you do | Refresh. Same platform, same pages and addresses. New look, new copy, better images. |
| Visitors can't find their way to an enquiry, or your services have changed shape. The platform is supported and your team can edit it | Redesign. Same platform. A new page plan, menu and layouts, with a redirect for any address that changes. |
| You can't edit what you need, the site is slow underneath every page, it can't run on supported software, or it can't do what the business needs | Rebuild. A new website on a platform that fits. Content carried across, addresses kept or redirected one to one. |
| Leave it aloneThe site still brings enquiries, loads well on phones and your team can update it | A fresh look alone is not evidence that a rebuild is needed. Fix the specific page or form that underperforms instead. |
Signs you need a new website, or only a redesign
You need a new website when the signs point to the platform. Most others point to a refresh, a redesign or a smaller fix.
| What you notice | Where the problem sits | What it points to |
|---|---|---|
| The site looks dated, but people find what they need | The surface: colours, type, images | Refresh |
| The words describe the business you were, not the one you are | The copy, and perhaps the page list | Refresh, or redesign if your services changed shape |
| Visitors phone to ask what the site should answer | The structure: page plan, menu, path to an enquiry | Redesign |
| Enquiries have dropped, or land in the wrong inbox | Often one form and where it sends | Test the form first; it may be a fix |
| Pages are slow on phones | Images and scripts, or the platform underneath | Measure, then fix the cause; rebuild only if it's the core |
| Every small change needs a developer, or the template fights you | How the site was built, or the platform | Redesign if it can be made editable; otherwise rebuild |
| The site runs on software past its supported life | The platform | Update; rebuild only if it can't run on a supported version |
| The business needs what the site can't do, such as bookings or a client login | The platform | Rebuild, or add a tool beside the site |
Two of these signs need measuring before you decide: speed and age. Both are often fixable on the site you have.
Slow: measure before you decide
Google's Core Web Vitals measure loading (LCP), interactivity (INP) and visual stability (CLS). A page counts as good when LCP is within 2.5 seconds, INP is 200 milliseconds or less and CLS is 0.1 or less. The guidance is to judge each at the 75th percentile of page loads, on mobile and desktop separately. In plain terms, at least three visits in four should meet it.
Search Console's Core Web Vitals report shows how your pages perform for real visitors. A page without enough real-world data is left out; test it live in PageSpeed Insights. Look at phones first, because Google uses the mobile version of a site's content for indexing and ranking. Heavy images, too many scripts and slow hosting can be fixed on the site you have. A theme or platform that is slow underneath every page is a reason to rebuild.
Old: check the dates, not the feeling
"Outdated technology" should be a date you can check. PHP, the programming language WordPress runs on, publishes support dates for every version. Version 8.2, for example, gets security fixes only until 31 Dec 2026. After that, PHP warns that users of such a release "may be exposed to unpatched security vulnerabilities".
On 25 Oct 2026, WordPress's release archive says only the latest 7.1 release is actively maintained, and WordPress recommends PHP 8.3 or greater. An old version is a reason to update, and a reason to rebuild only when the site can't run on a supported version.
When to redesign: four questions that decide it
Answer these four in writing before anyone opens a design file.
- What exactly is wrong? Write it as something a visitor or your team experiences. "It feels old" is a mood, while "people phone to ask whether we deliver to their area" is a problem a page can solve. If enquiries have fallen, test every form before you blame the design.
- Is it the surface, the structure or the platform? The surface is the look and the words, the structure is the page plan and the path to an enquiry, and the platform is the software underneath. Fix the problem at its own layer and no deeper.
- Who edits the site, and can they? If your team publishes every week, the editing screen matters more than the look. If every change needs a developer and that can't be fixed, it points to a rebuild.
- What must be kept? List what already works: the addresses that get visits, the forms and where they send, your analytics and the titles that perform. The longer that list, the stronger the case for the smallest change that fixes the problem.
What a redesign keeps and what a rebuild replaces
A refresh keeps everything but the surface, a redesign keeps the platform, and a rebuild keeps your content and, where possible, your addresses.
| What happens to | Refresh | Redesign | Rebuild |
|---|---|---|---|
| Platform and hosting | Kept | Kept | Replaced |
| Page addresses | Kept | Some change, each one redirected | Kept where possible, the rest redirected |
| Page plan and menu | Kept | Replaced | Kept or replaced, your choice |
| How your team edits | Unchanged | Mostly unchanged | A new editor and a new guide |
| Forms, analytics and connections | Kept; test them | Kept; test them | Set up again; test them |
A refresh is the quickest and safest. A rebuild removes limits at the root, but everything must be carried across and tested again.
Some platforms can only be left by rebuilding. Wix says the content you build on it belongs to you, but the site needs to be hosted and operated on Wix's servers. So leaving Wix means a new website, not a transfer. In return, Wix runs the hosting for you, which is a fair trade while the site fits.
If you rebuild, choose tools your next team can work with too. Our guide to WordPress or a custom-built website covers one common choice.
What must survive a redesign or a rebuild
Five things must survive any change. A refresh that keeps every address avoids most of the risk, though its forms and tracking still need a test.
- Addresses with value, kept or redirected one to one.
- Forms, still reaching the same person, with the same confirmation email.
- Analytics and Search Console, in your name and tracking every new page.
- Titles, descriptions and structured data that already perform, carried across on purpose. Structured data is a standardised format for describing a page and its content.
- Files, such as PDFs and images, at the addresses other sites link to.
If any address changes, Google's guidance on site moves with URL changes applies. Map each old address to its new one, and use server-side permanent redirects, such as 301 or 308. Keep them for as long as possible, generally at least a year, and update internal links and sitemaps. Google also says to expect temporary fluctuation in rankings during the move: good redirects reduce that risk but can't remove it. Our website migration checklist lists each item with how to check it.
How to brief a redesign or a rebuild
A useful brief names the symptom, the layer it sits in, who edits the site and what must be kept. It leaves the design to the people quoting. Our guide to writing a website project brief on one page has a template you can copy.
Settle in writing who writes the copy, who owns the content, who provides images, which pages are in scope and the timeline. A page plan comes before any design, so a redesign starts from the structure, not the colours.
- What's wrong
- People phone to ask whether pieces can be made to size. The site shows finished pieces only, and the enquiry button sits on the contact page.
- Where it sits
- The structure. The look is fine, and the platform is supported and easy to edit.
- Who edits
- The workshop manager adds new pieces and is happy with the editor.
- Must be kept
- Every piece page's address, the visit-booking form and where it sends, and analytics access.
- Option
- Redesign on the same platform: a made-to-order page, an enquiry button on every page and a clearer menu.
A hypothetical example, not a client. teakandtin.example is the site's sample business.
Next step: find your row in the table, list what must be kept, and tell us about the site. We'll reply within 24 hours, with a few questions or a time for a call. If it's better to rebuild, we'll tell you plainly.
Questions
Can you redesign a website without losing search rankings?
The risk can be reduced, not removed. Keeping or redirecting every address with value and carrying the titles across reduces it, but Google says to expect temporary fluctuation during a move.
How often should a website be redesigned?
On no fixed schedule. Redesign when a sign from the table appears; in between, keep the words current and the software supported.
How long does a redesign or a rebuild take?
It depends on the number of pages and how ready the content is. A rebuild has more to carry across and test, so it usually takes longer than a redesign.
Can you redesign a site someone else built?
Usually, after a short review of what's there. If you can't get into the site's accounts, start with what to do when your developer has left.
What does a redesign cost compared with a new website?
It depends on what you need. Tell us about the project and we'll send a written quote with the scope, timeline and what's included. The work grows with each layer that changes.
Sources
- Google Search Central: Site moves with URL changes (mapping, permanent redirects, how long to keep them, fluctuation) Checked 25 Oct 2026
- web.dev: Web Vitals (the three measures, thresholds, 75th percentile) Checked 25 Oct 2026
- Search Console Help: Core Web Vitals report (real-world data by device; pages without enough data left out; PageSpeed Insights for a live test) Checked 25 Oct 2026
- PageSpeed Insights (Google's page speed test) Checked 25 Oct 2026
- Google Search Central: Mobile-first indexing (Google uses the mobile version for indexing and ranking) Checked 25 Oct 2026
- Google Search Central: Introduction to structured data Checked 25 Oct 2026
- PHP: Supported versions (support dates; end of life) Checked 25 Oct 2026
- WordPress.org: Releases (which versions are maintained) Checked 31 Oct 2026
- WordPress.org: Requirements Checked 25 Oct 2026
- Wix Help Center: Exporting or embedding your Wix site elsewhere Checked 25 Oct 2026
Reviewed and edited by Online Scope before publishing. Something out of date? Tell us at info@onlinescope.in. How we write the Blog.
