A business does not always need a completely new website. Sometimes the right decision is to retain the platform, useful content, and established URLs, then redesign the parts that limit trust, usability, bookings, enquiries, sales, or search performance.

Quick answer

Choose a new website when the current platform, structure, or functionality cannot support the business properly. Choose a redesign when the foundations remain usable but the design, content, and visitor journey need substantial improvement. Choose focused development when the problem is limited to specific templates, features, forms, performance, or responsive behaviour.

What is the difference between web design, website redesign, and website development?

New web design

A new web design project normally begins with a fresh structure, design system, content plan, and build. It may use a new platform or a clean installation where the existing website no longer provides useful foundations.

Website redesign

A redesign begins by assessing what already exists and deciding what can be retained, improved, removed, or rebuilt. Useful content, URLs, rankings, functionality, and business knowledge should not be discarded without a reason.

Focused website development

Development is the better route when the website is fundamentally sound but needs specific technical work, such as a new template, form, integration, responsive fix, performance improvement, or controlled feature.

Use these situations as a practical starting point when deciding whether the current website should be repaired, redesigned, or replaced.

Situation	Likely route	Reason
Old unsupported platform and weak structure	New website	The foundations cannot support the required work safely
Useful pages and rankings, but dated design and unclear journeys	Redesign	Valuable assets can be retained while the experience is improved
One broken form, template, or feature	Focused development	A full redesign would be unnecessary
Business model has changed completely	New website or major redesign	The structure and content may no longer match the offer
Ecommerce catalogue needs migration and restructuring	Audited rebuild or redesign	Product data, URLs, collections, and operations need careful planning

Signs that a new website may be the better route

The platform is no longer supported or practical to manage
The page structure prevents important services, booking routes, or product categories from having clear destinations
Core functionality is unreliable or cannot be extended safely
The website is difficult to use on mobile
Security, performance, or update problems are persistent
The business model has changed so substantially that the current site no longer fits
There is no clear way to preserve the existing system without carrying its main problems forward

The platform is creating operational risk

An outdated theme, unsupported plugin, inaccessible account, or proprietary system can make routine improvements difficult. If every small change creates a new failure, a controlled rebuild may be more economical than repeated repairs.

The information architecture cannot support the offer

A business may outgrow a website that was built around one service or a small product range. Adding more menu items does not always solve the problem. The underlying page relationships, navigation, and visitor routes may need to be rebuilt.

The business now needs ecommerce, bookings, or memberships

Adding a major new commercial function can affect the platform, data, legal content, payment flow, email communication, analytics, and ongoing operations. The decision should be based on the full workflow, not only the appearance of the front end.

Signs that a website redesign may be enough

The platform and hosting remain suitable
Useful pages, content, links, or rankings should be preserved
The main problems are visual consistency, content order, navigation, and visitor journey
Forms, templates, calls to action, booking routes, or product discovery need focused improvement
The business identity has changed, but the website’s underlying system still works

The content has value but needs better structure

Existing pages may already answer useful questions or attract relevant search traffic. A redesign can improve headings, proof, internal links, layout, and calls to action without replacing every word.

The website looks dated but remains technically sound

A dated visual system can weaken trust even when the platform is stable. New typography, spacing, imagery, components, and responsive behaviour may be enough if the navigation and content remain fit for purpose.

The commercial route is unclear

A redesign can clarify whether visitors should enquire, book, buy, compare products, or visit a location. This often requires changes to page order and content hierarchy, not only colours and fonts.

When is focused WordPress development enough?

Focused development may be the most efficient route where the requirement is narrow and measurable. Examples include:

Creating one new page template
Repairing or replacing a form
Improving mobile navigation
Adding a suitable integration
Resolving layout or performance problems
Building a controlled content block
Improving accessibility in a specific component

The risk is allowing a series of isolated fixes to become an unplanned redesign. If the problems affect the whole structure, a broader project is usually more honest.

What should be audited before deciding?

Current traffic, conversions, and indexed pages

Record which pages attract visitors, generate enquiries, lead to bookings, support sales, or appear in search. Pages with useful rankings, links, or commercial value should not be removed casually.

Content quality and search intent

Some content may contain useful evidence or answers but need clearer structure. Other pages may be thin, duplicated, outdated, or aimed at the wrong search intent. The decision should be made page by page.

Technical condition

Review the theme, plugins, platform version, hosting, performance, accessibility, mobile behaviour, security, forms, and integrations. A visually dated website can have sound foundations, while a polished site can hide significant technical problems.

Navigation and visitor journey

Follow the routes a real visitor takes from the landing page to a service, booking, product, proof, and conversion. Note where the next step becomes unclear or where important information arrives too late.

Business operations

For ecommerce and booking websites, review the systems behind the page. Product data, stock, delivery, payment, appointment availability, cancellations, customer emails, and reporting must continue to work during and after the change.

Brand and content assets

Identify which logos, photography, videos, documents, reviews, and case studies remain usable. A redesign is a good time to remove weak or inconsistent assets, but replacement work must be agreed separately.

What should an ecommerce redesign review?

An ecommerce redesign must protect more than the appearance of the store. It should review:

Product and collection URLs
Product data, variants, images, and stock
Navigation, search, and filtering
Delivery, returns, and tax settings
Payment methods and checkout
Customer accounts and order history
Structured data and Merchant Center feeds
Analytics and ecommerce events
Redirects from changed products and collections

Launching a new visual theme without testing these areas can interrupt sales even when the pages look better.

What should a booking-website redesign review?

Booking flows should be tested from the visitor’s first selection through to confirmation, reminders, cancellation, and rescheduling. Check staff calendars, locations, deposits, recurring sessions, mobile usability, and the handover into the business’s operational system.

How do you protect SEO during a website redesign?

Search visibility should be part of the redesign plan from the beginning. Before changes are made:

Export the current URLs
Record important titles, headings, canonicals, and indexation
Review Search Console landing-page and query data
Identify pages with links, rankings, traffic, or conversions
Map every changed or removed URL to the best relevant destination
Preserve useful content and internal-link relationships

During the build, use a staging site that search engines cannot index. Before launch, test redirects, canonicals, robots settings, sitemaps, navigation, internal links, and forms. After launch, monitor Search Console, crawl errors, rankings, and important conversion routes.

Will a redesign always affect rankings?

Some movement is possible when pages, content, internal links, templates, or performance change. A well-planned redesign reduces avoidable risk, but no responsible supplier should guarantee that every position will remain unchanged.

Should old website content be kept?

Keep content because it is useful, accurate, trusted, or commercially valuable, not simply because it already exists. A content inventory can classify each URL as keep, improve, merge, redirect, archive, or remove.

Deleting weak content can improve clarity, but removing a useful page without a redirect or replacement can harm both visitors and search performance.

Should you change platform during a redesign?

Changing platform can be justified when the current system limits functionality, management, performance, ecommerce operations, or ownership. It should not be done only because the designer prefers a different tool.

Before migrating, assess content portability, product data, orders, accounts, subscriptions, booking records, integrations, licences, redirects, and staff training.

How much does a website redesign cost?

DSM website redesign projects start from £1,250. The existing site is reviewed before the agreed work is confirmed because the amount of reusable content, number of templates, technical condition, migration work, and required functionality all affect the price.

A redesign can cost less than a complete rebuild when the foundations remain useful. It can also become a larger project when the audit reveals major structural, technical, content, booking, or ecommerce problems.

How long does a website redesign take?

The schedule depends on the number of pages and templates, content changes, platform, migration, integrations, approvals, and testing. An established ecommerce or booking website normally needs more planning and launch control than a small brochure site.

What should happen on redesign launch day?

Take a current backup and confirm the restoration plan
Deploy the approved files and content
Check robots, canonicals, and sitemap settings
Test redirects and priority URLs
Submit forms, bookings, and test orders
Check payment, delivery, and customer emails where relevant
Confirm analytics and conversion events
Test desktop and mobile navigation
Monitor server, crawl, and Search Console issues

Common questions about redesigning a website

Can a website be redesigned without changing the URL?

Yes. Many redesigns retain the same domain and important page URLs. Where URLs change, redirects should be mapped and tested.

Can I keep my existing website content?

Useful, accurate content can be retained and improved. The audit should identify which material still supports the business and which should be rewritten, merged, or removed.

Will the website need to go offline?

A redesign is normally built and tested on a staging environment, then deployed in a controlled release. A short maintenance window may be required depending on the platform and migration.

Should I redesign the website when I rebrand?

Often, yes, particularly when the identity, positioning, audience, or offer changes. A light visual update may be enough where the structure and content still fit.

Can you redesign a Shopify or WordPress website?

Yes, but the process and technical boundaries differ. Shopify, WordPress, and other platforms should be assessed according to the existing theme, data, apps, plugins, ownership, and required functionality.

How often should a business redesign its website?

There is no fixed timetable. Redesign when the website no longer supports the business, not simply because a certain number of years has passed.

Which DSM service fits each situation?

Web Design for a new website or a project that needs a fresh structure and build
Website Redesign when useful foundations can be retained
WordPress Development for focused fixes, templates, or functionality without a full redesign
Ecommerce Websites when the main requirement is a new or substantially restructured online store
Digital Consultancy when the right route is not yet clear

Not sure which route fits?

Start with an honest assessment of the current site.

We’ll review the platform, content, visitor journeys, search position, and commercial priorities before recommending focused development, a redesign, or a new build.

View Website Redesign