A targeted refresh may be enough when the platform is usable and problems are limited to content, selected pages or mobile usability. A rebuild may be appropriate when the underlying system cannot support the required work maintainably. An old appearance alone is not enough to decide.
Separate symptoms from causes
Describe what customers encounter: a service is hard to find, a form fails, mobile text is unreadable, or information is outdated. Identify what needs checking before choosing a remedy. Changing colours and imagery will not repair a form that sends enquiries to the wrong address.
Review pages that already attract visits or enquiries before removing them. Gather available performance information, platform details and domain and hosting ownership. Do not send passwords through a public enquiry form.
When targeted improvements may be enough
- The structure and files or editing access are available and usable.
- The main service pages remain suitable, but copy or organisation needs work.
- Problems are limited to responsiveness, navigation, particular links or forms.
- The requested functions do not require a fundamental change in how the site operates.
For example, a site with accurate services but an outdated form recipient may need a delivery correction, receipt test and clear confirmation message rather than a complete rebuild.
When to assess a rebuild
A rebuild deserves consideration when the platform cannot support essential requirements maintainably, the available source is insufficient, or the planned expansion requires a different structure. Decide through a technical review and defined scope, not appearance alone.
Compare the cost of targeted repairs with rebuilding, migration and ongoing operation. Existing pages, content and branding may still be worth preserving even when the implementation changes.
Plan URLs and launch before making changes
List current URLs and decide which pages stay, change or merge. Where an address changes, map it to the appropriate replacement. Review internal links, the sitemap and language versions as part of that work.
Google’s site-move guidance recommends URL mapping, testing the new site and redirects, and monitoring performance. These steps reduce migration problems; they do not guarantee unchanged rankings.
Keep a rollback copy and test forms, email delivery, tracking, analytics consent and important pages before launch approval. Email, DNS and useful content do not need to change simply because the design is being refreshed.
Request a scope you can evaluate
A useful starting brief is: “Review our services page, enquiry form and mobile experience, preserve existing URLs, and explain what requires repair or rebuilding”. That produces clearer deliverables than an undefined request for a complete makeover.
WJAZ website review is SAR 690 for a prioritised report; implementation is separate. A refresh starts from SAR 2,790 after platform review, while a full rebuild starts from SAR 3,490 according to scope. Hosting, licences and integrations are assessed separately.