A redesign can improve speed, credibility and conversion while still damaging search performance if valuable URLs, content signals and internal links are treated as disposable. Migration planning must start before new templates are finalised.
Build an evidence-based inventory
Export existing URLs from the CMS, analytics, Search Console, backlink tools and server logs. These sources reveal pages that users and search engines value even when they are hard to find in the current navigation.
- Current indexable URLs
- Organic landing pages and conversions
- External links and referral traffic
- Canonical and redirect behaviour
- Structured data and media assets
Decide what each URL becomes
Every valuable page needs an explicit destination: retained, improved, consolidated or retired. Redirect old URLs to the closest relevant replacement, not automatically to the home page.
Keep established URLs where there is no strong user or technical reason to change them. A cleaner-looking slug alone is rarely worth the migration risk.
Protect the content that explains expertise
A visually lighter design can accidentally remove the specific service detail, evidence and terminology that earned rankings. Rewrite for clarity, but keep the substance that answers the searcher’s question.
Validate before launch
Crawl the staging build, verify titles and canonicals, test redirects and compare the new internal linking structure. Staging must remain blocked from indexing, while production must not inherit that block.
- No broken internal links
- One self-referencing canonical per page
- Correct robots directives
- Sitemap contains only preferred URLs
- Analytics and consent tested
- Core forms and conversion events verified
Monitor the first weeks
Submit the sitemap, inspect key URLs and monitor crawling, rankings, conversions and server errors. Some movement is normal, but persistent drops around one page group usually point to a specific migration decision that can be corrected.