Quick answer
A website redesign should make your site easier to use while keeping important pages, forms and system connections working. Before asking for quotes, list what to keep, what to improve and how you will check the new site before launch.
What should you check before redesigning?
Review your existing pages and the tasks customers complete. Keep useful content and identify problems with enquiries, bookings or purchases. Record current search traffic and enquiries so you have something to compare later.
- List old URLs, language versions and important downloads.
- Decide which pages to keep, combine or remove.
- Map each changed URL to a useful replacement.
- List forms, analytics and links to systems such as your CRM.
Agree the launch checks before design starts
Ask how the provider will check that information moves correctly to the new site. For an enquiry, check the staff mailbox, saved record and customer confirmation. Include any booking or payment tasks that need to keep working.
A new look and a replacement system involve different work. Make both parts clear in the quote. Do not send every removed page to the homepage just to hide an error.
Plan what happens if something goes wrong
Agree when content changes will stop, how recent records will move and who checks the launch. Choose who can restore the old service if an important task fails.
Ask who monitors errors, fixes faults and supports staff after launch. The recovery plan should explain how to avoid losing or duplicating records created during the change.
Your planning worksheet
Use this table to prepare the same brief for each provider. Add the person responsible and the current status for each item. Enter costs only from written quotes, in HKD, with the billing period.
| Item to plan | Details to give the provider | What to check |
|---|---|---|
| Existing URL | Old page, replacement URL and content owner | The correct replacement is reachable and redirects are mapped |
| Critical journey | Enquiry, booking or purchase, and the systems needed | An agreed test of the whole task passes before launch |
| Recovery | Who can restore service, when, and how records are checked | The team can explain recovery without losing recent records |
Example project scenario
Illustrative planning example; not a completed customer project.
A company replaces its website while keeping its enquiry connection to a CRM. It maps old URLs to new pages and uses sample enquiries to check delivery. The team assigns someone to watch for failures. Its recovery plan explains how to protect recent enquiries if the connection stops working.
Common questions
Will a redesign improve my Google ranking?
There is no guarantee. Keep useful content, handle changed URLs correctly, and check canonical URLs, language links and the sitemap. A canonical URL tells search engines which version of a page to treat as the main one.
Do we need to move every old page?
Review whether each page is still useful and accurate. Decide what to keep, combine or remove, and what visitors should see when they follow an old link.
Is copying the old appearance enough?
Check complete customer and staff tasks too. A familiar layout does not prove that forms, bookings or system connections still work.
Download the planning worksheet (CSV)
Find a provider through TechQuotations
TechQuotations connects Hong Kong buyers with IT service providers. Use your brief to discuss the work and compare proposals. You choose the provider and agree the terms directly. A request does not guarantee a quotation.
Explore suitable providers through TechQuotations