[139170] in North American Network Operators' Group
Re: IPv6 SEO implecations?
daemon@ATHENA.MIT.EDU (Wil Schultz)
Mon Mar 28 19:25:41 2011
From: Wil Schultz <wschultz@bsdboy.com>
In-Reply-To: <1EEAC599-1156-490C-B597-241FE84CAE4A@delong.com>
Date: Mon, 28 Mar 2011 16:21:48 -0700
To: Owen DeLong <owen@delong.com>
Cc: "nanog@nanog.org Group" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Mar 28, 2011, at 3:55 PM, Owen DeLong wrote:
>=20
> On Mar 28, 2011, at 3:18 PM, Wil Schultz wrote:
>=20
>> I'm attempting to find out information on the SEO implications of =
testing ipv6 out.
>>=20
>> A couple of concerns that come to mind are:
>>=20
>> 1) www.domain.com and ipv6.domain.com are serving the exact same =
content.=20
>> 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.
>>=20
>> 2) Not running ipv6 natively, or using 6to4.=20
>> This (potentially) increases hop count and will put content on a =
slower GRE tunnel and add some additional time for page load times.=20
>>=20
>> 3) ??? Any others that I haven't thought of ???
>>=20
>> 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.=20
>>=20
>> Thoughts?
>>=20
>> -wil
>=20
> If you're worried about SEO, go with native IPv6 and then deploy AAAAs =
for WWW.domain.foo.
>=20
> It's been working just fine for www.he.net for years.
>=20
> Owen
>=20
So far the consensus is to run dual stack natively.
While this definitely is the way things should be set up in the end, I =
can see some valid reasons to run ipv4 and ipv6 on separate domains for =
a while before final configuration. For example, if I'm in an area with =
poor ipv6 connectivity I'd like to be given the option of explicitly =
going to an ipv4 site vs the ipv6 version.=20
I'd also like to not damage SEO in the process though. ;-)
-wil=
