On Mon, May 2, 2016 at 6:13 PM, Todd Lipcon <[email protected]> wrote:
> On Mon, May 2, 2016 at 5:38 PM, Mike Percy <[email protected]> wrote: > > > Looks good Todd. > > > > I don't think that having the HTTP redirect working is required in order > to > > report progress on the site migration. We can easily mirror the current > > site to kudu.i.a.o and talk about how we are in the process of winding > down > > the old domain with a redirect. > > > > I'm worried that having both domains active at the same time will hurt our > SEO mojo -- splitting the same site in two places, etc. Do you think > Google's smart enough to detect the > duplicate-but-not-hosted-by-the-same-server site and combine its ranking? > Well, I should preface by saying I don't keep up with all the latest SEO rules. However based on my old knowledge of SEO, you are right that Google will detect duplicate content and I think it will initially get punished until the 301 redirects go up. Then it will still get some penalty until more people have inbound links to the new web site. Changing domains isn't free in SEO terms. It will also hurt us going from a top-level domain kudu.io to a 4th-level subdomain kudu.a.i.o. I agree we should minimize the time it's up as dup content without the redirects, but in the long run I doubt it's going to make much of a difference. On the other hand, ultimately, having apache in the domain name will help if people search for Apache Kudu. Google likes that. Mike
