Website migration
How to rebuild a website without losing search visibility
The practical controls that reduce migration risk when moving an established service-business website to a modern platform.
Published July 21, 2026 6 min read
A website rebuild can improve speed, ownership, and publishing. It can also damage years of accumulated search value if the migration is treated as a visual redesign only.
The safest approach begins with an inventory, not a homepage mock-up.
Preserve what already works
Before rebuilding, record:
- Every indexable URL
- Page titles and descriptions
- Important headings and content
- Images and downloadable assets
- Internal links
- Forms and conversion paths
- Analytics and search verification
- DNS records, especially email records
This baseline shows what needs to be preserved, redirected, improved, or intentionally retired.
Build redirects before launch
When a useful old URL changes, it should normally redirect to the closest relevant new page. Redirecting every retired page to the homepage is rarely helpful.
A redirect map should include:
- Old URL
- New destination
- Reason for the change
- Verification status
Test the map on the preview deployment before changing the live domain.
Keep the launch reversible
DNS changes should come after the new site has passed functional, mobile, content, and crawl checks. Record the original hosting records before editing them and use a rollback plan with clear decision points.
Email DNS records must be treated separately from website hosting records. Moving a website should not interrupt Google Workspace or another mail service.
Verify the live result
After launch, check:
- The homepage and all priority pages
- Redirects from important old URLs
- Forms and thank-you flows
- Canonical links and robots directives
- XML sitemap
- Analytics events
- Search Console ownership
- Mobile presentation and core performance
- Any unexpected 404 responses
Then monitor indexing, crawl errors, rankings, and enquiries through the settling period.
Migration is a managed change
The technology is only one part of the work. A sound migration protects business continuity, preserves useful search signals, and creates a cleaner foundation for ongoing content. That is why Bigstorm Tech treats migration as the first phase of a managed visibility system, not as a standalone design project.