xcoder - 3:18 am on Nov 30, 2012 (gmt 0)
I guess the only way to confirm or debunk this issue is to run a human/bot test on each and every page affected.
Can anyone suggest a non intrusive (as much as possible) *must* pass human/bot test. An DHTML message box with a couple of questions that must be answered in order to proceed and view the page in question... or something along these lines.
Message box will leave a cookie if human test was passed successfully and will not reaper if the viewer happens to continue to next page.
That would be the only real/confirmed/factual way of putting this matter to sleep...or not.
So the coders among us, lets get creative and start suggesting some code ideas for the bot/human test.
They look like a duck, they walk like a duck... I'm itching to check if they ga ga too....