[139203] in North American Network Operators' Group
Re: IPv6 SEO implecations?
daemon@ATHENA.MIT.EDU (Wil Schultz)
Tue Mar 29 12:55:15 2011
From: Wil Schultz <wschultz@bsdboy.com>
In-Reply-To: <C9B811EE.EAE%fmartin@linkedin.com>
Date: Tue, 29 Mar 2011 09:54:27 -0700
To: Franck Martin <fmartin@linkedin.com>
Cc: "nanog@nanog.org Group" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Mar 29, 2011, at 3:51 AM, Franck Martin wrote:
>=20
>=20
> On 3/29/11 10:18 , "Wil Schultz" <wschultz@bsdboy.com> wrote:
>=20
>> I'm attempting to find out information on the SEO implications of =
testing
>> ipv6 out.
>>=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
>> Thoughts?
>>=20
>=20
> Do we know which spiders run on IPv6?
>=20
> After all an IPv6 only site may not be indexed at all...
>=20
I haven't published any hostnames, so I don't have the entire picture... =
with that being said, here's what I have seen. The only big search =
engine I've seen at this point is google, here are the user agents I've =
seen to date:
Googlebot-Image/1.0
Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
DoCoMo/2.0 N905i(c100;TB;W24H16) (compatible; Googlebot-Mobile/2.1; =
+http://www.google.com/bot.html)
SAMSUNG-SGH-E250/1.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 =
UP.Browser/6.2.3.3.c.1.101 (GUI) MMP/2.0 (compatible; =
Googlebot-Mobile/2.1; +http://www.google.com/bot.html)
-----------
Just FYI, Google bots all have an ipv6 suffix of 6006:1300:b075 (Google =
Bots, how 1337 of them!)
Here are the addresses seen from google:
2001:4860:4801:1302:0:6006:1300:b075
2001:4860:4801:1303:0:6006:1300:b075
2001:4860:4801:1401:0:6006:1300:b075
2001:4860:4801:1402:0:6006:1300:b075
2001:4860:4801:1404:0:6006:1300:b075
2001:4860:4801:1405:0:6006:1300:b075
2001:4860:4801:1407:0:6006:1300:b075
2001:4860:4801:1408:0:6006:1300:b075
-----------
And here's a breakdown of which user agents are seen on which ip, as you =
can see the user-agent doesn't exactly match IP range.=20
Googlebot-Image/1.0
2001:4860:4801:1404:0:6006:1300:b075
2001:4860:4801:1405:0:6006:1300:b075
2001:4860:4801:1408:0:6006:1300:b075
Mozilla/5.0 (compatible; Googlebot/2.1; =
+http://www.google.com/bot.html);=20
2001:4860:4801:1302:0:6006:1300:b075
2001:4860:4801:1303:0:6006:1300:b075
2001:4860:4801:1401:0:6006:1300:b075
2001:4860:4801:1402:0:6006:1300:b075
2001:4860:4801:1404:0:6006:1300:b075
2001:4860:4801:1405:0:6006:1300:b075
2001:4860:4801:1407:0:6006:1300:b075
2001:4860:4801:1408:0:6006:1300:b075
DoCoMo/2.0 N905i(c100;TB;W24H16) (compatible; Googlebot-Mobile/2.1; =
+http://www.google.com/bot.html)
2001:4860:4801:1404:0:6006:1300:b075
2001:4860:4801:1405:0:6006:1300:b075
2001:4860:4801:1407:0:6006:1300:b075
2001:4860:4801:1408:0:6006:1300:b075
SAMSUNG-SGH-E250/1.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 =
UP.Browser/6.2.3.3.c.1.101 (GUI) MMP/2.0 (compatible; =
Googlebot-Mobile/2.1; +http://www.google.com/bot.html)
2001:4860:4801:1302:0:6006:1300:b075
2001:4860:4801:1401:0:6006:1300:b075
2001:4860:4801:1404:0:6006:1300:b075
2001:4860:4801:1405:0:6006:1300:b075
2001:4860:4801:1407:0:6006:1300:b075
2001:4860:4801:1408:0:6006:1300:b075
-----------
Again, I don't have the entire picture because I've not published my =
hostnames. The above information is just what I've seen on my selective =
testing.
-wil=
