Contents＋
Every box is green. The form never arrives. That sort of ‘small detail’.
01 / Direct answer
A redesign reallocates trust; it is not a reskin
Website rebuilds most often fail at handoffs. Design says the client supplies content; the client assumes the agency rewrites it. Development assigns analytics to marketing; marketing assumes old tracking migrates automatically. Every party finishes its task while nobody owns the system.
02 / Asset inventory
First preserve the assets the website already owns
Illustrative scenario, not a client case: A Hong Kong professional-services firm launches on schedule and passes desktop acceptance. Two weeks later it discovers that Simplified Chinese canonicals point to Traditional pages, WhatsApp events are absent, every case URL changed and form emails enter spam. No single bug is dramatic, but four handoff failures are enough to remove enquiries.
An acceptance list needs failure conditions, not just ticks
“Mobile complete” is not an acceptance criterion. A useful test starts from an old search URL on a named phone and browser, switches language without losing the service, checks an invalid-field message, submits successfully, verifies delivery and confirms only one success event. Each step is reproducible and observable.
03 / 2026 requirements
A 2026 website must be understood by people, search and AI
Google's migration guidance treats URL mapping, server redirects, internal links, verification and ongoing monitoring as one process.
Its multilingual guidance requires language versions to reference each other. These are not technical attachments to add after launch; they are part of rebuild scope.
A website serves three systems at once. Buyers must understand and act; search and AI systems must retrieve, identify and connect information; internal teams must receive, follow up, update and own it. Visual acceptance tests only one third of the product.
04 / Management error
Long checklists fail when nobody owns the checks
Most checklists contain dozens of yes-or-no items: logo, SSL, sitemap, mobile layout. The real risk is whether each item is correct and owned. A form that emails the wrong person, hreflang without reciprocal links or a backup never restored can all receive a tick and still fail.
‘Should be fine’ is a worrying final release note. It isn’t a test record, either.
05 / Nine layers
Work backwards from outcomes to acceptance tests
- Commercial: define the buyer, risk answered and measurable next action for every important page.
- Assets: export URLs, traffic, enquiries, links, cases, images and language relationships; mark each keep or merge.
- Technical: validate status codes, redirects, canonicals, hreflang, indexing, schema and real mobile performance.
- Operations: test forms, WhatsApp, calls, CRM, spam handling, permissions, backups and incident ownership.
- Launch: preserve a baseline, schedule 24-hour, 7-day and 30-day checks, and define rollback conditions.
| Acceptance layer | Must be tested | Do not ask only |
|---|---|---|
| Buyer | Can they understand, compare and contact? | Does it look attractive? |
| Machine | Can it retrieve, map and index? | Is the plugin installed? |
| Operations | Receipt, routing, response and backup | Was an email address entered? |
| Migration | Old URL to new URL | Do all new pages exist? |
Separate release blockers from later refinements. Missing enquiries, noindex on important pages, broken payment or widespread misdirected redirects can block launch. An imperfect image position on a low-traffic page can wait. When everything has equal priority, teams tend to fix the easiest thing to demonstrate.
06 / Migration process
A launch process that does not collapse on launch day
Assign an owner, acceptance evidence and a failure response to every check. A checklist without ownership becomes a collection of assumptions in the final hours before launch.
- Inventory commercial goals, audiences, priority services and valuable existing URLs.
- Lock language, content, metadata, schema, measurement and redirect specifications.
- Test on real phones with real forms, payments, WhatsApp and user permissions.
- Prepare rollback, monitoring and an eight-week post-launch issue rhythm.
07 / Measurement
Use separate pre-launch and post-launch baselines
| Layer | What to record | What it means for management |
|---|---|---|
| Launch integrity | Pass rate for forms, languages, measurement, redirects and indexing | Confirms the basics were not missed |
| Asset preservation | Retention of traffic, links and enquiries on valuable pages | Prevents the redesign erasing history |
| Maintainability | Time required for one routine content update | Proves the new system is easier to operate |
Test the handover too. Have a non-developer change a course date, restore a version and update three languages in staging, then verify the cached output. The site must remain coherent when someone edits it next month, not merely on launch day.
08 / FAQ
Three common redesign questions
Should everything launch at once?
For large, multilingual or transactional sites, staged release makes problems easier to isolate. Even small sites need rollback plans.
Is approving the design file enough?
No. Acceptance testing must use live URLs, real devices, real forms and realistic permissions end to end.
When is the launch truly complete?
After priority pages are reprocessed, measurement is stable, legacy URLs show no large failure pattern and the team completes a routine update.
09 / Limits and conclusion
Completion means the team can keep improving
A checklist cannot replace judgement. A five-page local consultancy and a fifty-thousand-product retailer carry different risks; regulated financial content also needs approval, records and disclosures. Prioritise the most expensive failure rather than attempting a perfect score everywhere.
A rebuild is not complete when the new homepage appears. It is complete thirty days later when old entrances still work, enquiries are received, three languages remain connected and the team knows who owns the next change.
If someone can change a date next month without a rescue call, the handover has actually happened.
10 / Sources