Solution to the Web site replacement domain name causes the page URL cannot access the method

Hope this migration for users is not aware of the occurrence, and hope that Google will know that the new page should be the same as the original site page to receive the same quality approval. When you migrate sites, those annoying 404 error prompts (files cannot be found)

Not only will it hurt the user experience, but it will also negatively affect the performance of your site in google search results.

This article describes how to securely move your site to a new domain name:

The main steps for Web site migration are as follows:

Start by moving the contents of a directory or subdomain to test the entire site's migration process. Then use the 301 redirect feature to redirect the original Web page to your new site. Google and other search engines can be told by this method: Your site has been permanently migrated.

Once you've done this, check to see if your new Web site can appear in Google's search results. If you are satisfied with this small-scale migration, you can migrate the entire site. Do not redirect the traffic from all pages in the old site to your new home page, which, while avoiding 404 errors, does not provide a good experience for the user. Although page redirection (where every page in the old site is redirected to the corresponding page of the new site) can create a greater amount of effort, it also gives your users a more coherent and lucid experience. If you don't have a one-to-one page match in your old and new Web site, make sure that every page in your old site is at least redirected to a new page with similar content.

If the site is to be renamed or redesigned to change the domain name, you can do it in two stages: Phase one, move your site; the second stage, start the redesign. This will not only control the extent of the changes that users feel in each phase, but will also make the process smoother. Controlling change at a minimum can make it easier for you to find and solve various contingencies.

Check the internal and external links of your site's Web pages. Ideally, you should contact each administrator who links to the other sites on your site and have them point the link to the appropriate page for your new domain name. If this is difficult to implement, make sure that all pages that contain links to other sites in the original site are redirected to your new site. You should also check and update the internal links in all old sites to point to the new domain name. Once your site content is ready for the new server, you can use a link checker such as Xenu to confirm that there are no legacy links on your new site. This is particularly important.

To prevent confusion and confusion, you should continue to hold control over the original site domain name for at least 180 days.

Add your new Web site to the Webmaster Tools account and verify your ownership of the site. Create and submit a sitemap to display all the URLs of the new site so that Google knows that your new site is now available and can be crawled.

Finally, make sure that your new and old sites are validated in Webmaster tools and periodically check for crawl errors to ensure that 301 redirects from the old site are working and that the new site does not display 404 error prompts that we don't want to see.