Existing content and journeys
Inventory pages, service groups and enquiry flows. Identify accurate content, duplication and information visitors cannot find.
Website redesign
Refresh your website and make its content easier to find.
Make your business website in Vietnam easier for customers to use, with the right information for local and international audiences and a plan for existing URLs, forms and data.
Structure to review
An organised structure
SAMPLE PAGE
ABOUTClear information.
Find what you need.
Find what you need.
Approved content, organised around the reader’s needs.
ContentNavigation
Scope to agree
- 01Decide what to keep, change or remove
- 02Plan the new site one URL at a time
- 03Accountable release and follow-up
Review the current site before choosing targeted changes or a rebuild. Identify gaps in English and Vietnamese content where relevant. Record what stays, which functions change, how the new version is introduced and when to roll back.
AT A GLANCE
Review the site, improve what needs attention and plan the release.
- Inputs
- Current site, essential functions and management access.
- Delivery
- Agreed improvements, a URL plan and release guidance.
- Agree
- Backups, new data and rollback conditions.
Review
Decide what to keep, change or remove
Decide what should stay or change before design.
Functions and access
Review forms, administration, external systems and technical access. Essential functions need testable checks, not just screenshots.
Priorities and boundaries
Distinguish visual changes, restructuring, platform migration and new functionality. Choose a scope with clear acceptance criteria.
AN IMPLEMENTATION EXAMPLE
Plan what happens to each old URL.
A sample URL map and release plan; the paths below are illustrative.
Structure to review
An organised structure
SAMPLE PAGE
ABOUTClear information.
Find what you need.
Find what you need.
Approved content, organised around the reader’s needs.
ContentNavigation
An illustration of reorganising content and navigation.
| Old path | Action | Destination |
|---|---|---|
/gioi-thieu/ | Keep the URL and relevant content | /gioi-thieu/ |
/dich-vu-cu/ | Redirect to the matching page | /dich-vu/ |
/uu-dai-het-han/ | Review before retiring or replacing | Decide after review |
- Before the switch
Back up, test the preview and approve paths and stop criteria.
- After the switch
Check live URLs, forms and connected systems.
- If rollback is needed
Reconcile new data, restore according to the plan and verify again.
A static example for discussing your project’s structure and workflow.
Replacement
Plan the new site one URL at a time
Reconcile content and paths page by page.
Old-to-new URL mapping
Record pages that stay, move to relevant content or are retired. Do not send every old path to the homepage without considering its purpose.
Design and content transfer
Approve layouts and content before migration. Check titles, images, internal links and contact details after transfer.
Checks before replacement
Review a separate preview, reconcile URLs and test essential flows. Keep the preview distinct from the version customers are using.
Release
Accountable release and follow-up
Prepare checks, backups and follow-up after the switch.
Backups and rollback conditions
Prepare site and data backups, owners and stop criteria. Reconcile new data created during migration before a rollback.
Checks after release
Check live URLs, redirects, forms, tracking and access. Record errors and dependencies outside the agreed editing scope.
A quote based on the current site
The quote reflects the current platform, content, functions and migration work. It specifies checks before and after release and the agreed follow-up period.
HOW WE WORK
Clarity at every step.
Review the current site
Inventory pages, functions, data and access.
Approve the new plan
Choose layouts, content and the URL map.
Build and reconcile
Check the preview against agreed requirements.
Release and follow up
Use the approved release plan and retain a rollback option.
PRICED BY SCOPE
Define the work before the quote.
Send your requirements and sample material so we can define a suitable scope.
Request a quoteWhat determines the cost
- Page count, supplied content, content management, languages and integrations. For an existing site, we review its structure and functions; technical access is agreed where needed.
- Booking systems, payments, data synchronisation and paid plugins are quoted where needed; domain and hosting are separate.
FAQ
Before we begin.
A few useful answers to help define the right scope.
Does every redesign require a full rebuild?
No. Structure, design or one workflow may be all that needs attention. The proposal explains the chosen scope.
Will redesign preserve SEO exactly?
Rankings and traffic cannot be guaranteed unchanged. We map URLs, retain useful content, check technical details and agree post-release monitoring.
Can we keep our domain and old content?
We can assess this where you control the domain and have content rights. Data, hosting and platform transfers are reviewed separately.
Will the website be unavailable during the work?
Where possible, prepare the replacement separately. Agree the switch time, expected interruption and handling of new data beforehand.
What do you need for a proposal?
Share the site, problems, essential functions and platform if known. Tell us which customers you serve in Vietnam, which language versions exist and who can approve their content. Technical access follows an agreed process during assessment.
Website redesign
Let’s define the work you need.
Share your goals, available material and preferred timing. We will clarify the work, deliverables and cost.