After changing the official website domain, how should old links be handled?
This article introduces the migration process after a Web3 project changes its official website domain, covering SEO settings, updates to third-party materials, and the secure maintenance of the old domain to reduce the risk of information distortion.
First complete the official website migration
Changing the domain name is not just about updating a link. The old domain should be retained and set up with a 301 redirect; the correct canonical should be set on the new website; update the sitemap and search engine webmaster tools; publish a migration announcement on the new official website, explaining the relationship between the old domain and the new domain.
Then update key public information
Update in the order of "official website, product documentation, official social media, data platform, partner pages, media resource pages." When submitting updates, attach the new official website link, the relationship with the old domain, and the formal announcement for third-party verification.
Avoid security vulnerabilities
Expired domains that are not renewed or redirected may be registered by others and used to mislead visitors. The project should continuously monitor the old domain, old social media profiles, and common search results, and issue risk warnings when necessary.
Expectations should be reasonable
The refresh rates of third-party platforms and search engines vary. Completing updates does not guarantee immediate changes in rankings, traffic, or all old pages, but it can reduce the risk of ongoing distortion of public information.
Next steps
Modify information:
https://www.rootdata.com/projects/submit?ft=modifi
Create project:
https://www.rootdata.com/projects/submit?ft=create
RootData Boost:



