: The easiest thing to do would be to tell your server (I'm assuming Apache, but this is true for Lighttpd and Nginx as well) to use the same folder as the document root for both domains.

@Fox8124981

The easiest thing to do would be to tell your server (I'm assuming Apache, but this is true for Lighttpd and Nginx as well) to use the same folder as the document root for both domains.

The right thing to do is to redirect domain1.com to domain2.com and only use domain as canonical. There isn't any advantage to using 2 domains simultaneously and it increases your maintenance workload (even if only slightly). I would send out an email to any clients or users that a change is coming, and that domain1.com will be your new domain, while domain2.com will continue to work for a set period of time and then be discontinued.

If you take this step and only go forward with one domain, instead of simply shutting the old domain off, set up a proper redirect (using the proper HTTP 301 redirect type for all of your old domain's URLs. This will keep users that are still referencing your old domain in the right place. You can do this for every individual URL you have (like every specific article of a blog), just the major ones (like domain1.com/users/content/), or only for your domain as a whole (which leads domain1.com/* to domain2.com/).

You'll also want to make sure that you take steps to rank one of the domains as the original content source, as Google will see your duplicate content as syndicated content. It won't negatively affect your ranking, according to the Google but your content may be detected as original for some on one domain, and original for some on the other, leading to potentially confusing search results.

Vote Up Vote Down

Login to post a comment!