[139202] in North American Network Operators' Group
Re: IPv6 SEO implecations?
daemon@ATHENA.MIT.EDU (Arturo Servin)
Tue Mar 29 12:53:01 2011
From: Arturo Servin <arturo.servin@gmail.com>
Date: Tue, 29 Mar 2011 18:41:09 +0200
In-Reply-To: <5F63749D-6CFC-4723-89F3-3129D30888C2@bsdboy.com>
To: "nanog@nanog.org Group" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 29 Mar 2011, at 00:18, Wil Schultz wrote:
> 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
Twitter said:
http://twitter.com/#!/look4ipv6/status/24639157611528193
Al least you would have a better page-rank in www.example.com =
than in ipv6.example.com with the same content.
.as=
