How do you migrate a website without losing organic visibility?
The biggest migration risk is not the new design. It is breaking the relationship between old URLs, content, redirects and the way search engines understand the new site. A safer migration starts with mapping and testing—not with changing DNS.
This checklist is useful for a domain move, platform change, URL restructuring or hosting migration. It does not promise that rankings will remain unchanged; it focuses on preventable technical failures.
Before the move: build a URL map
- Export important URLs from the old site: pages, articles, images and files that receive traffic or links.
- Assign one relevant new destination to every old URL. A blanket redirect to the home page is not a substitute for mapping.
- Prepare the new site in a test environment and remove accidental robots.txt or noindex blocks before launch.
- Check that titles, content and internal links moved—not only the visual template.
Google recommends preparing a URL map and using permanent server-side redirects, typically 301 or 308, when URLs change. Read Google’s site-move guidance.
Launch day: four checks you should not skip
- Redirects: old URLs reach relevant destinations without long chains or loops.
- Canonicals: each new page points to the correct canonical URL, not a staging or old URL.
- Links and forms: internal links, images and lead forms work on the new environment.
- Crawling: the new site is accessible to crawlers and the sitemap contains the updated URLs.
After launch: monitor and fix
Use Search Console to watch crawl errors, missed URLs, unusual changes in indexed pages and search performance. You can request a recrawl, but it does not guarantee immediate inclusion. Google’s recrawl documentation explains the available process.
Also monitor server logs, redirects, lead forms and user traffic. A short-term fluctuation is not automatically a failure, but persistent errors on important URLs need fast attention.
A handover checklist
- The old-to-new URL map is saved and reviewed.
- 301/308 redirects were tested on priority URLs and samples.
- No unintended noindex or crawl block remains.
- Canonicals, sitemap, images, links and forms point to the new environment.
- A monitoring plan exists for the days and weeks after launch.
A sound migration decision is not “does the new site look ready?” It is “are all the signals that users and search engines need still present?”
Sources
Google Search Central: Site Moves and Migrations · Google Search Central: Redirects and Google Search
For a related review, see EzraTech’s business website UX audit checklist and why a website gets traffic but no leads.