When should a business replace its website?

In that situation, the highest-return work may be new service pages, better proof, form improvements, local SEO, performance fixes or a visual refresh rather than a migration.

• The site is technically stable and mobile-friendly.
• Important pages can be edited without breaking the layout.
• The service structure is mostly correct.
• Forms and analytics can be improved without rebuilding the platform.
• The site has useful indexed URLs or content that should remain intact.

• The site cannot clearly represent the business's current services or positioning.
• Mobile visitors struggle to navigate, contact or submit an enquiry.
• The platform cannot support required forms, integrations or content without brittle workarounds.
• No one can safely update the site or dependencies are creating security and maintenance risk.
• The site has major migration debt: duplicate domains, broken URLs, unmanaged plugins or inconsistent analytics.
• The business needs a customer or workflow layer that turns the site into part of a larger system.

Before replacing anything, inventory indexed URLs, backlinks, ranking pages, analytics, forms, downloadable files, customer-facing language, photographs and integrations. The new site should deliberately keep, improve or redirect those assets.

Write down what is currently failing, what the redesign must improve and how you will observe the change. Useful measures include qualified enquiries, form completion, calls, search impressions, mobile engagement, content-update time, error rate and staff effort around repetitive website tasks.