Igor Vaynberg <igor.vaynberg <at> gmail.com> writes: > its pretty easy to create an encoder that will process regular url > formatted parameters. maybe that is a better default eventhough it is > not as crawler friendly as the other one. you can also change your own > implementation to the default by calling > applicationsettings.setpageparametersencoder.
Just thought I would share my recent experience using urls of the form: /action/param_name1/param_value1/param_name2/param_value2 I used this form in a website of mine to great success UNTIL november when Google started penalising any site that contains "duplicate content". If the parameters passed to the page do not result in a "significantly different" resulting page then google will assume that you have duplicate pages on your site and will penalise you. In November and December my site traffic dropped to 25% almost overnight after their "Jagger" update. After changing my URL's back to the more conventional form: /action?param_name1=param_value2¶m_name2=param_value2 My traffic has returned to normal. Lesson learned: don't assume you are smarter than Google to gain more traffic. Stick to statndard URL schemes. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
