On 7 Jun 2006, at 17:32, Eelco Hillenius wrote:
I have read quotes on Matt Cutts blog that session ids should be avoided. Also quotes from GoogleGuy such as these: "Google can do some smart stuff looking for duplicates, and sometimes inferring about the url parameters, but in general it's best to play it safe and avoid session-ids whenever you can." "I've been aching for a long time to mention somewhere official that sites shouldn't use '&id=' as a parameter if they want maximal Googlebot crawlage, for example. So many sites use '&id=' with session IDs that Googlebot usually avoids urls with that parameter.
Are you suggesting that if you want Google to crawl your site you should use another framework? I was hoping for a suggested workaround! Currently I do use Webwork for the pages in my site that need to be well indexed by search engines but I would love to use Wicket for the whole thing. Would it not be possible to have some kind of method like Session.shouldPersist() that defaults to true but could be overriden by the developer? |
_______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
