Start with the problem you need to solve
An old visual style does not prove the whole website needs replacing. Identify what prevents people from understanding the offer, finding pages or contacting you. A rebuild also involves content, migration and URL review, so the effort needs a clear purpose.
When optimisation can make sense
If the structure supports content changes, the system can be maintained and core functions work, prioritise copy, navigation, performance and forms. Retain pages that already attract traffic and assess them before changing addresses.
When to consider a new foundation
Consider rebuilding when the system cannot be maintained, blocks essential changes or has dependencies that prevent progress. Separate practical limitations from visual preferences. Define integrations, languages and business processes the replacement must support.
What to review before deciding
Inventory pages, search queries and enquiries, and test the mobile experience. Clarify access, domain ownership, content and tools. Ask for a scope that separates essential work, optional improvements, external costs and maintenance.
Protect continuity during a rebuild
Map old addresses to new equivalents. Redirect only to relevant replacements, retain useful content and check links, sitemap, canonical tags, languages and forms before launch. Keep a recoverable backup and review landing pages afterwards. A visual change alone does not guarantee traffic or sales.