A redesign should make your business easier to understand and contact. It should also account for the useful pages and search context you already have. Changing the colours or framework does not establish that a website will attract more relevant customers.
Before approving a rebuild, identify the problem: unclear services, an awkward mobile experience, broken forms, outdated content, slow delivery or a site that no longer reflects the business. Some problems need targeted fixes rather than a complete replacement.
1. Record the current website before changing it
Build a list of existing pages and the purpose each serves. Use the sitemap, content system, relevant analytics and Search Console data where you have access. Identify service pages, contact pages and resources that attract relevant visitors or have links from other websites.
- Record the existing URL, page topic and desired action.
- Note useful content, approved images and evidence worth retaining.
- Identify pages to keep, improve, combine or retire.
- Record a baseline for relevant search visibility and qualified enquiries.
Do not assume an old page has no value because its design looks dated. Do not keep a page only because it contains a keyword. The decision should reflect usefulness, evidence and the business's current offer.
2. Plan URLs and redirects before launch
Keeping a useful existing URL can make a redesign simpler. Where a page genuinely moves, map its old URL to the most appropriate new destination. Avoid sending every retired URL to the homepage when that does not answer the original visitor's need.
Google's site-move guidance recommends preparing a URL mapping, implementing the move and monitoring the result. Temporary ranking fluctuations can happen while pages are recrawled and reprocessed. A migration plan manages the change; it cannot guarantee unchanged rankings. See Google's site-move documentation.
3. Check the content customers use to make a decision
Every main service needs a clear explanation of who it helps, what is included, where the business delivers and how to enquire. Keep claims and contact details accurate. Use genuine project examples and approved testimonials; label illustrative work as a concept.
Plan headings, titles, descriptions and internal links alongside the visible page. For JavaScript websites, check the content delivered in the initial response and after rendering. A browser screenshot alone does not show what a crawler receives. See Google's JavaScript SEO guidance.
4. Test the whole enquiry journey
On a phone, can a visitor understand the service, find the right contact action and submit a useful brief? Check required fields, validation messages, saved enquiries and failure states. A form should not claim successful delivery when storage fails.
For WhatsApp, verify the destination business number and prepared message. The visitor must still press Send. A WhatsApp click is different from a received conversation, and a conversation is different from a qualified opportunity. Agree who responds and how follow-up is recorded.
5. Verify the released site
Staging and production need separate checks. Confirm that temporary access controls or indexing restrictions have not accidentally carried into the public release. Check canonical URLs, sitemap entries, appropriate redirects, genuine 404 responses, internal links and media resources.
Test representative mobile and desktop layouts. Review loading, responsiveness and layout stability under appropriate conditions. Distinguish a laboratory performance score from real-user Core Web Vitals. Do not promise a universal speed result based on a mockup.
6. Review the first weeks after launch
Monitor important pages, indexing and enquiry delivery. Compare relevant search queries and qualified enquiries against the baseline, accounting for seasonality and changes to advertising. Investigate broken paths and unexpected drops before making further large changes.
Keep the migration map and agreed support responsibilities available to the team. Record what was released, when it changed and which issues remain open.
Use a concept to start the conversation
SAVHN's website preview reviews accessible public homepage HTML and composes an illustrative direction from that material and your brief. It does not perform a full migration audit, measure rankings or publish a replacement site.
Explore our website redesign approach, or new website design if you are starting fresh. Discuss the full scope with SAVHN on WhatsApp. Clinics, hospitals and other medical centres can continue through ClinixSync's medical website request.