Think you have read up on 301’s and how to do a Domain Name change with out losing your rank in the search engine?
Ready to make the move? For sure?
Have you checked that the new domain doesn’t have penalties attached to it? Are you sure you sure?
Got your 301 redirects set up correctly? Are you sure?
Google has an official “Step list” for making the move, which Matt Cutts wrote.
- Test the move process by moving the contents of one directory or subdomain first. Then use a 301 Redirect to permanently redirect those pages on your old site to your new site. This tells Google and other search engines that your site has permanently moved.
- Once this is complete, check to see that the pages on your new site are appearing in Google’s search results. When you’re satisfied that the move is working correctly, you can move your entire site. Don’t do a blanket redirect directing all traffic from your old site to your new home page. This will avoid 404 errors, but it’s not a good user experience. A page-to-page redirect (where each page on the old site gets redirected to the corresponding page on the new site) is more work, but gives your users a consistent and transparent experience. If there won’t be a 1:1 match between pages on your old and new site, try to make sure that every page on your old site is at least redirected to a new page with similar content.
- If you’re changing your domain because of site rebranding or redesign, you might want to think about doing this in two phases: first, move your site; and second, launch your redesign. This manages the amount of change your users see at any stage in the process, and can make the process seem smoother. Keeping the variables to a minimum also makes it easier to troubleshoot unexpected behavior.
- Check both external and internal links to pages on your site. Ideally, you should contact the webmaster of each site that links to yours and ask them to update the links to point to the page on your new domain. If this isn’t practical, make sure that all pages with incoming links are redirected to your new site. You should also check internal links within your old site, and update them to point to your new domain. Once your content is in place on your new server, use a link checker like Xenu to make sure you don’t have broken legacy links on your site. This is especially important if your original content included absolute links (like www.example.com/cooking/recipes/chocolatecake.html) instead of relative links (like …/recipes/chocolatecake.html).
- To prevent confusion, it’s best to make sure you retain control of your old site domain for at least 180 days.
- Add your new site to your Webmaster Tools account, and verify your ownership of it. Then create and submit a Sitemap listing the URLs on your new site. This tells Google that your content is now available on your new site, and that we should go and crawl it.
- Finally, keep both your new and old site verified in Webmaster Tools, and review crawl errors regularly to make sure that the 301s from the old site are working properly, and that the new site isn’t showing unwanted 404 errors.
If you follow these directions, and don’t have any domain penalties your domain "*SHOULD* go smoothly, but what Matt doesn’t tell you is the time line, or how to check that each step was done correctly.
BlackwaterOps can help you make the move, and verify that each step is going smoothly. Yes you can do this yourself, but be aware that if you mess it up, there is no “redo” if this goes horribly wrong, so if your site is small, follow Matt’s advice, if your business depends on it get help from a professional.
The Analogy I like to use, is that I am more than capable of doing my on brake shoe replacements, but if I screw it up bad things will happen so I pay the money to a pro, so that nothing goes wrong.