A redesign should make a website more useful—not erase what already works. Before moving a WordPress site, changing navigation or replacing every page, establish what needs improvement and which existing assets must be protected.
1. Identify the business outcome
Are you trying to attract better-fit enquiries, make products easier to find, improve mobile usability or reduce administration work? Write down the main problem. An attractive new aesthetic can support that outcome, but it shouldn’t be the entire brief.
2. Audit the existing website
Record important pages, contact paths, navigation, forms, integrations, analytics and search-performance baselines. Capture screenshots of the current desktop and mobile experiences. Check which pages visitors actually use and which content needs updating.
3. Preserve URLs that already matter
Existing URLs may have earned links, bookmarks and search visibility. Where practical, keep them. When a URL must change, plan a relevant permanent redirect from the previous location to the new one. Don’t point every removed page to the homepage by default.
4. Review content before redesigning it
Decide what to keep, rewrite, consolidate or remove. Strong design will not rescue unclear service copy. Involve the person who knows the business and its customers, rather than filling every section with generic marketing language.
5. Check the technical dependencies
List forms, email delivery, booking tools, payment processing, CRM integrations, analytics, ecommerce workflows and user permissions. Identify any confidential data that should never be used in public screenshots or on a staging site.
6. Build and test on staging
A staging copy allows the team to test layout, mobile navigation and integrations away from the live site. Protect staging from public access and indexing. Don’t treat staging as production-ready merely because the homepage looks good.
7. Run a pre-launch QA checklist
- Verify desktop and mobile layouts.
- Test every important menu link, button and enquiry form.
- Review page titles, descriptions, canonicals and indexing rules.
- Check redirects, sitemaps and robots directives.
- Test performance and accessibility on key page types.
- Make a full backup and confirm who approves the launch.
8. Monitor after launch
Check Search Console for indexing or crawl changes, monitor real enquiries and review issues reported by customers. Small corrections in the first few weeks are normal. Avoid judging long-term SEO performance from the first day.
Bottom line: a successful redesign protects working assets while making the website easier to use, find and maintain. Plan the migration as carefully as the visuals.