Short introduction
A redesign should solve an identifiable problem: confusing services, an awkward mobile layout, slow pages or a difficult enquiry route. Start by recording what works today so the replacement does not lose valuable content or break existing links.
Inventory the existing site
List current pages, important incoming links, enquiry forms and any booking or payment journeys. Use available analytics and Search Console data to identify pages visitors use; ask staff which pages they share with customers.
Save approved copy and original project images. Record domain, hosting and integration ownership. Before moving platforms, confirm which content and customer records can be exported and who is responsible for the move.
Map old pages to their new destination
Keep established URLs when the purpose of the page stays the same. Where a URL must change, map it to the closest relevant replacement and implement a permanent redirect. Sending every old page to the homepage is unlikely to help someone looking for a specific service.
Update internal links, canonical URLs and the sitemap together. Keep the old-to-new mapping in the project so redirects can be tested after launch. Avoid removing a useful page simply because it does not fit the first design mockup.
Design the content and enquiry route together
Test a simple journey: a customer lands on a service page, checks an example, answers a concern and submits an enquiry. Make the next step obvious at each point. Use descriptive links and concise form labels.
On mobile, check readable text, navigation, image weight and form fields. Ask someone outside the project to complete the journey with fictional details in a test environment. A beautiful homepage does not compensate for a broken contact form.
Plan launch and the first review
Before launch, check metadata, redirects, forms, analytics preferences and the final content. Keep a backup or rollback path. Confirm that production pages can be indexed and private preview pages are handled appropriately.
After launch, test the published URLs and contact delivery, submit the sitemap through Search Console if you have access, and monitor unexpected errors. Record a baseline rather than expecting a redesign to produce an immediate ranking or revenue increase.
Practical checklist
- Save the current page and URL inventory.
- Map changed URLs to relevant replacements.
- Test mobile navigation and enquiry delivery.
- Keep a rollback path and review the live site.
How J & K Web Collective thinks about this
J & K Web Collective starts with the business goal, current setup and constraints, then scopes a practical next step. Share your existing website or workflow and the outcome you need so we can discuss the right approach.
Sources
Further reading is linked in each article. Examples illustrate decisions; they are not promises of results.