A practical starting point
Keep the credibility. Remove the friction.
Start with the pages and enquiries your existing website already supports. Agree the content, design, migration and launch checks before the rebuild begins.
- Content and page inventory
- Responsive design and mobile enquiry journey
- Old-to-new URL migration plan
- Metadata, language and form checks
- Launch and account handover
Choose a refresh, a focused repair or a full redesign
Keep the existing site when its content and structure still serve buyers and the problem is limited to a dated layout or a broken form. A full redesign becomes useful when the services have changed, key information is difficult to find or the current system cannot support the next release.
Send the current URL, the pages that bring enquiries and the tasks visitors struggle to complete. We use these to agree what to retain, rewrite, rebuild or remove before planning the new design.
Plan SEO migration before changing URLs
Create an inventory of existing pages and search landing pages. Keep useful URLs where possible; when a URL must change, map it to the closest relevant replacement and include the redirect in the launch scope.
Review titles, descriptions, canonical URLs, language alternatives and the sitemap alongside the visible content. At launch, check the agreed old URLs, remove staging restrictions from public pages, and confirm that important pages and forms work. Search rankings can still change after a migration.
Make the mobile enquiry journey part of acceptance
For a trading company, test the route from a product specification to a quotation request. For a service business, test the route from service details to an enquiry. Check both languages, navigation, document links, form errors and confirmation messages on a phone.
Record which checks passed and which need follow-up. Confirm receipt at the destination inbox and distinguish a successful enquiry submission from a contact-button click.
Agree the redesign scope, budget and handover
A quote should list the pages, content responsibilities, design and build work, migration, form testing and account handover. Confirm how future edits, backups, licences and support will be handled.
Use our project portfolio to review design and development examples, including clearly identified independent concepts. Discuss which parts apply to your existing site; examples do not establish a before-and-after traffic or revenue result.
Downloadable planning example
Decide what to keep, move or remove for each old URL
These fictional example.com URLs illustrate migration decisions. The statuses describe planned behaviour; they are not measured server responses.
| Old path | Action | Destination | Reason |
|---|---|---|---|
| /about/ | Keep | /about/ | The content and purpose remain relevant |
| /old-products/paper-insert.html | 301 | /products/paper-insert/ | Move to the same product at its new URL |
| /old-contact.html | 301 | /contact/ | Preserve the original contact purpose |
| /company-profile.html | 301 | /about/ | Company information moves to the About page |
| /expired-campaign/ | 404 / 410 | — | No relevant replacement for an expired campaign |
Download the bilingual decision table CSV · Load the three direct mappings in the checker
Kept and removed URLs belong in the inventory, separately from redirect rules. After implementing redirects, verify live responses, destination content, canonicals, internal links and the sitemap.