The problem is that:
1) GoogleBot will hit the same page with different JSESSIONID each time.
It'll think that these are different pages and lower your page rank
because (from its point of view) your website contains different page
URLs with the same content (looks like you're trying to trick it).
2) Secondly, since GoogleBot gets a different JSESSIONID each time, when
a remote website links to you, it'll give off a different JSESSIONID as
well. Which means your overall ranking goes down yet again because
instead of 1000s of websites linking to the same URL you get different
ones linking to different URLs.
I think there are other problems too but I forget off the top of my
head. You can't just get rid of JSESSIONID because browsers with cookie
support disabled will not be able to retain a session across multiple
pages. One possible solution we are looking into is dropping JSESSIONID
if GoogleBot is detected so only the crawler will keep on losing the
session, not normal users. As far as I can tell, Google warns against
this approach (showing different pages to users and crawlers) and I am
uncertain how reliable it is.
Maybe someone else has a better idea?
Gili
Nathan Hamblen wrote:
> Michael Day wrote:
>> If not, then wicket cannot be used for public web sites (news,
>> online store, etc) that need to be indexed in today's search engines.
>
> Johan Compagner wrote:
>> If you want a really stateless page/site. Then everything must be
>> bookmarkable/mountable links..and you can't use our
>> form components
> [...]
>
> Yes. Ample bookmarkable links are all you need for good indexing. Try
> googling "British Lemon Meringue Pie" and see that the second result is
> in fact a Wicket demo application.
>
> I wouldn't worry about forms too much since Google doesn't follow them
> anyway. As long as you can get to the content through bookmarkable
> links, it will be indexed. The fact that a session always exists is
> irrelevant and entirely normal. (Even ASP 3.0 created a session on the
> "very first hit.")
>
> My only wish is to get rid of that silly ;jsessionid=66kiemewvs53 but I
> don't think that's up to Wicket.
>
> Nathan
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Wicket-user mailing list
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user
signature.asc
Description: OpenPGP digital signature
