Before design starts.
Export the current sitemap, top landing pages, search queries, conversions and important backlinks. Record the content and functionality that customers or staff already depend on. A redesign brief without a before state cannot tell preservation from accidental loss.
If the site needs a full rebuild, see our website design and development service.
- Name the business outcome and the user tasks that support it.
- Identify every system touched by forms, bookings, payments or accounts.
- Separate content that must migrate from content that has earned removal.
- Agree who supplies copy, translations, photography and legal review.
Before release.
Crawl the candidate build and compare it with the approved inventory. Test keyboard use, contrast, reduced motion, mobile layout and the slowest expected network. Submit forms with realistic validation cases and verify that the record arrives where the operating team expects it.
At release.
Confirm the production deployment is built from the reviewed source. Check canonical URLs, robots rules, sitemap responses and redirects on the live host. Run the critical customer journey again after DNS and cache changes. The deploy succeeded message is not the end to end test.
After release.
Watch crawl errors, indexing, landing page traffic, form receipts and user behaviour against the baseline. Prioritise broken journeys before visual polish. A redesign is complete when the operating system around the site works, not when the final animation renders.
If a site is already hacked or broken, read website rescue in Bangkok.
What this looked like on ArchCath.
When we moved the ArchCath medical device site from WordPress hosting to Vercel, the design had to stay as it was. We restored the page for healthcare professionals from an archived copy of the old site and gave it the same navigation as the rest of the site. We also found an indexing restriction carried over from the preview build and removed it, then checked the core pages in Search Console. A preview setting that blocks Google is easy to ship by accident, which is why the checklist ends on the live URL and not the preview.
Who wrote this, how and why
Who: Written by the DLVX team under founder Wil Delvaux. DLVX sells the kind of work discussed here, so we have an interest in the topic.
How: Figures come from our published price list and the sources linked on the page, with the checked date shown. Research and drafting use AI assistance, and a person at DLVX checks the facts before publishing.
Why: Buyers ask these questions before a project starts. We wrote the answer down so it can be checked and cited.