Website Redesign vs Refresh: How to Decide

A dated appearance does not always require a rebuild, and a fresh coat of paint will not fix a weak structure or failing platform. Diagnose the business and technical problems before choosing the project size.

A Refresh May Be Enough When

• The main page structure still matches the business.
• The platform is supported and maintainable.
• Forms and integrations work reliably.
• Problems are limited to copy, imagery, calls to action or selected layouts.
• Performance and accessibility issues can be corrected without replacing the foundation.

A Redesign May Be Better When

• Services, audiences or conversion goals have changed substantially.
• Navigation and content architecture are difficult to repair incrementally.
• The site relies on unsupported technology or fragile customisations.
• Mobile, accessibility or performance issues are structural.
• Ecommerce, bookings or other major integrations need replacement.

Protect Search Equity During Either Option

Inventory indexed URLs, page titles, internal links, analytics and pages that already attract enquiries. Preserve useful URLs where practical, map necessary redirects one-to-one and verify canonical tags, sitemaps and tracking after launch.

Practical note: Changing many URLs without a redirect map can create avoidable 404s and loss of useful signals. Do not redirect every removed page to the home page.

Sources & Further Reading

• Google Search Central: SEO Starter Guide
• W3C Web Accessibility Initiative: WCAG 2.2 Quick Reference

This guide provides general information, not a diagnosis, guarantee or substitute for advice based on your specific devices, systems, contract or site. Confirm scope, inclusions and pricing before making a service decision.