[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IPv6 SEO implecations?
- Subject: IPv6 SEO implecations?
- From: owen at delong.com (Owen DeLong)
- Date: Mon, 28 Mar 2011 15:55:31 -0700
- In-reply-to: <[email protected]>
- References: <[email protected]>
On Mar 28, 2011, at 3:18 PM, Wil Schultz wrote:
> I'm attempting to find out information on the SEO implications of testing ipv6 out.
>
> A couple of concerns that come to mind are:
>
> 1) www.domain.com and ipv6.domain.com are serving the exact same content.
> Typical SEO standards are to only serve good content from a single domain so information isn't watered down and so that the larger search engines won't penalize. So a big concern is having search results take a hit because content is duplicated through two different domains, even though one domain is ipv4 only and the other is ipv6 only.
>
> 2) Not running ipv6 natively, or using 6to4.
> This (potentially) increases hop count and will put content on a slower GRE tunnel and add some additional time for page load times.
>
> 3) ??? Any others that I haven't thought of ???
>
> So basically I'd love to set up some sites for ipv6.domain.com via 6to4 as a phase one, and at some point in the near future implement ipv6 natively inside the datacenter, but I'm somewhat concerned about damaging SEO reputation in the process.
>
> Thoughts?
>
> -wil
If you're worried about SEO, go with native IPv6 and then deploy AAAAs for WWW.domain.foo.
It's been working just fine for www.he.net for years.
Owen