1. Record the value of the existing site
Inventory current URLs and identify pages that attract relevant visits or enquiries. Export useful data from Search Console and Analytics before the redesign. Do not rely only on a visual review or memory of which pages perform well.
Include material your sales conversations depend on. A low-traffic page can still be commercially important. Give each page a decision: retain, improve, combine or remove, with a reason attached.
2. Give changed URLs a relevant destination
A new design does not require a new address for every page. Where the page’s purpose remains the same, retaining a useful URL can simplify the change.
Google recommends permanent server-side redirects for permanent URL changes. Map old addresses to relevant new ones rather than sending everything to the homepage. Google’s site-move guide.
3. Review content alongside appearance
A shorter page may be clearer, but it can also lose the answers that attracted visitors. Check whether the service, audience, key questions and next step remain understandable.
Plan internal links deliberately. Guides should lead to relevant services, and services should link to useful explanations. Test each language version independently. A working German page does not establish that its English equivalent is complete.
4. Use a launch acceptance checklist
Test the main journeys from landing page to enquiry or order. Check mobile layouts, navigation, error messages and form confirmation. Review page titles, descriptions, canonical links and indexing settings.
Keep staging content from becoming the public replacement prematurely. At launch, make sure a staging noindex instruction has not been carried over. Inspect the actual public page rather than treating an administrative setting as sufficient evidence.
5. Connect technical checks with business outcomes
After launch, check important old and new URLs and their redirect paths. Submit the updated sitemap. Monitor indexing and search performance alongside enquiries.
Ranking movement immediately after a change is not conclusive evidence of a technical failure. A reproducible missing page at an important old address is a clearer finding. Fix specific faults first and keep a record of the corrections.
6. Prepare a recovery path
Back up the files, database and configuration your setup uses. Decide who can authorise a rollback and how the previous version will be restored. Confirm access before it is needed.
Where practical, avoid changing the domain, hosting, functionality and every piece of copy simultaneously. A clear scope makes failures and improvements easier to investigate.
Your checklist
- Inventory important URLs and enquiry journeys
- Map changed addresses to relevant destinations
- Test redirects and internal links
- Check indexing settings on the public site
- Update the sitemap and measurement
- Prepare backup access and restoration
Frequently asked questions
Can a redesign guarantee unchanged rankings?
No. Careful migration reduces avoidable technical risks but cannot guarantee rankings.
Should every URL change?
No. Keep useful existing URLs unless there is a clear reason to replace them.
Created with AI assistance and checked against original sources. Examples are not client results.
