In short
A practice redesigns its website without losing useful pages, email or the appointment journey. Old addresses receive deliberate destinations and the form is tested before and after launch. The design can change while a working route for patients remains protected.
Should you improve, redesign or rebuild your website?
Imagine your website looks dated, while its addresses are indexed, email works and several pages still answer useful questions. Deleting everything is rarely the first move. Start by separating what carries value from what blocks a visitor.
Imagine a practice that wants a fresh look while appointments still arrive through an old form. That form and mailbox are a business process before they are a design task.
The practice begins by following an ordinary appointment journey. A visitor lands on an old treatment page, reads the practical details and uses the appointment form. The confirmation reaches an established mailbox. That journey identifies what must not disappear by accident: page addresses, the form, its recipient, opening hours, travel details and the tap-to-call link used on a phone.
Protect the appointment journey
List important pages, forms, downloads, addresses, measurement tools and mailboxes. Mark what must keep working. A new design is different from a move: a move needs redirects, domain access and a check of the enquiry route.
Create a redirect list with old URL, new URL and reason. After launch, test a small selection in a private browser window and check that important pages do not return an error.
The old pages are then judged by usefulness, not only appearance. Some copy is outdated and can go. Other pages answer exactly what a person worries about before a first visit. Every URL gets a decision: retain, rewrite, combine or redirect. When two pages become one, the old address points to the most relevant new destination rather than an error page or a generic home page.
Decide the future of every old address
Improve when the foundation is understandable and the issue is mainly copy, structure or speed. Rebuild when the system cannot be changed safely or practically. Redesign when the foundation is sound but the visitor journey no longer makes sense.
Export copy, images and account details before work begins. Not everything must return to the new site, but removal should be a conscious choice.
Email needs a separate check. Website hosting and email may be supplied by different companies even though they use the same domain. Publishing a redesign does not require mail settings to change. The practice records who can access the registrar and hosting, who is allowed to edit DNS, and which mailbox should receive the form test before and after the switch.
Leave email alone where possible
Set aside a test before and after the change. Submit the important form, check the email it creates, and retain a list of old URLs. This protects useful routes without promising that search positions will remain unchanged.
The redesign can now be scoped around real friction. Navigation becomes shorter, treatment explanations calmer and the appointment route easier to find. Existing photography remains where usage rights are known. A custom booking system is not slipped into the project halfway through. If an external scheduling service is needed, its behaviour, data handling, ownership and support responsibilities are examined as a separate integration.
Test before and after the switch
The right decision is small enough to check and substantial enough to remove a real obstacle. Start with the page or step where people lose confidence, not with a cosmetic rebuild of every screen.
Before launch, someone who did not build the pages runs a concrete test. They open selected old links, use the website on a phone, submit the appointment form and inspect the received email. Error messages, privacy wording and confirmation details are included. The domain switches only after that route works, and the same checks are repeated on the public site after launch.
The practice keeps control
The result is not merely a practice with a newer look. Useful old material has been carried forward deliberately, email has stayed outside unnecessary changes, and appointment requests remain part of the acceptance test. No one can promise unchanged search rankings. The team can, however, account for every important old page, explain each redirect and name the person who will handle a fault after launch.
A week later, the receptionist checks the busiest pages and the appointment email again. She hears patients’ questions every day and may spot a confusing treatment name, direction or phone number faster than the developer. Small corrections use the editor as intended: save a draft, review the preview, then publish after confirmation. The practice therefore keeps practical ownership of the new site after the technical handover.
Sources
Questions people ask
What is the difference between build and recurring costs?
Build work is the agreed starting delivery. Recurring costs relate to being online, such as a domain, hosting or care; use the pricing page for current detail.
Can I edit text later?
In the VURM editor, change the text, review the change in preview, then publish it when it is ready. A free draft stays local in the same browser until you choose online use.
Will my domain and email stay safe during a change?
Record ownership, access and mailboxes. Do not alter MX records unless an authorised administrator is making an email change, then test the main form.
Does AI do the work automatically?
No. AI can prepare a draft. A person confirms facts, consent, prices and sending; AI services are delivered only after a separate agreement.