I forsee a problem as this inherently requires dual stacked www (et al) records and dual stacking is famously ropy where end users have broken or partial v6 implementation/visibility as is, sadly, very often the case.
(It is *important* to have dual-stack content *now* – so that the remaining issues can get fixed in time. Waiting until the big boom is not going to make the transition any smoother).
[…] to the fore. As a result, Jan Zorz and others have put together a proposal which can be seen at, http://go6.si/2010/08/suggestion-for-internet-search-engines-proposed-ipv6-impact-on-search-engine-s…. This proposal recommends the inclusion of IPv6 in the factors used by search […]
My thoughts on possible negative impact of the proposed change:
“Search engine is serving URLs in SERP regardless if they are A or A/AAAA recorded in DNS, so rewarding of A/AAAA record availability can’t currently impact on users search experience, but just reward content provider serving content on IPv4 and IPv6, making it possibly future proof.”
Hope that this thought goes into internal debates inside search engines 🙂
I first was a bit skeptic to use ranking to stimulate IPv6 growth. With normal normal native transport user experience to a particular website should be the same for IPv4 and IPv6. But when you think of the recent IPv6 trail of T-Mobile where they use NAT64 this changed for me. Users in this trial will get better performance when the web site that they are trying to reach is dual-stack. And when I was reading about stuff what Google is using to influence page ranking, performance is something they care about
I like the Google whitelist but search engines should announce AAAA records (without whitelists) before doing this. They can’t say that they don’t want 0.1% users with problems but we expect that you take it for granted. No flam..
[…] O pessoal do go6, da Eslovênia, tem uma proposta muito interessante para melhorar a adoção do IPv6 na Web. Bastaria que o Google e outros buscadores passassem a utilizar o IPv6 como um dos critérios para calcular o ranking das páginas. Ou seja, se a sítio Web responder corretamente em pilha dupla, ele aparece um pouco melhor colocado na resposta do buscador. Me parece algo que valeria a pena apoiar: http://go6.si/2010/08/suggestion-for-internet-search-engines-proposed-ipv6-impact-on-search-engine-s… […]
Podpiram to idejo.
I forsee a problem as this inherently requires dual stacked www (et al) records and dual stacking is famously ropy where end users have broken or partial v6 implementation/visibility as is, sadly, very often the case.
@Phil: As Lorenzo figured out, 0,2% (or something like that) of users may be impacted. Wouldn’t care…
Jan,
Great idea and good work putting it together.
It seems to me to be a reasonable proposal given that search engines already take into account factors other than the content of the web-site.
Of course I am biased as our web-sites are all IPv6 enabled!
Thanks,
David
David: Yes, transport factors are already taken into account…
http://googlewebmastercentral.blogspot.com/2010/04/using-site-speed-in-web-search-ranking.html
Hi,
great idea. Go for it!
(It is *important* to have dual-stack content *now* – so that the remaining issues can get fixed in time. Waiting until the big boom is not going to make the transition any smoother).
gert
[…] got massive feedback on proposed change, mostly very positive and some of brave fellows also left pubblic comment below the article […]
[…] to the fore. As a result, Jan Zorz and others have put together a proposal which can be seen at, http://go6.si/2010/08/suggestion-for-internet-search-engines-proposed-ipv6-impact-on-search-engine-s…. This proposal recommends the inclusion of IPv6 in the factors used by search […]
My thoughts on possible negative impact of the proposed change:
“Search engine is serving URLs in SERP regardless if they are A or A/AAAA recorded in DNS, so rewarding of A/AAAA record availability can’t currently impact on users search experience, but just reward content provider serving content on IPv4 and IPv6, making it possibly future proof.”
Hope that this thought goes into internal debates inside search engines 🙂
I first was a bit skeptic to use ranking to stimulate IPv6 growth. With normal normal native transport user experience to a particular website should be the same for IPv4 and IPv6. But when you think of the recent IPv6 trail of T-Mobile where they use NAT64 this changed for me. Users in this trial will get better performance when the web site that they are trying to reach is dual-stack. And when I was reading about stuff what Google is using to influence page ranking, performance is something they care about
I like the Google whitelist but search engines should announce AAAA records (without whitelists) before doing this. They can’t say that they don’t want 0.1% users with problems but we expect that you take it for granted. No flam..
Is this the businesses cause for IPv6?
[…] O pessoal do go6, da Eslovênia, tem uma proposta muito interessante para melhorar a adoção do IPv6 na Web. Bastaria que o Google e outros buscadores passassem a utilizar o IPv6 como um dos critérios para calcular o ranking das páginas. Ou seja, se a sítio Web responder corretamente em pilha dupla, ele aparece um pouco melhor colocado na resposta do buscador. Me parece algo que valeria a pena apoiar: http://go6.si/2010/08/suggestion-for-internet-search-engines-proposed-ipv6-impact-on-search-engine-s… […]