Forum Moderators: open
It will be interesting to watch if Google takes any action as well.
From:
[agerhart.com...]
Andrew has the screen shots on his site with this highlighted.
Looks like Yahoo acted fast, and changed the live page to the one that was cached.
This is a problem webmasters run into all the time - do you show the user a natural looking list of pages, or do you show them the ones that is good for searching. Yahoo found a solution that I would never dare.
well, ok I guess I would.
But the page that is up now is the one that was alleged to be keyword stuffed cloaked. So that doesn't add up.
I wonder if it was a dueling split a/b page test before flipping to the new version full time and AG just caught it in the middle of that flip over.
Andrew, what was the page a month ago?
Yahoo, Google, MSN, and ask all four custom feed se's to avoid geo/psycho/daypart/local/browser/host/isp/platform targetting issues.
I suppose this is possible, but I HIGHLY doubt it. My guess is that someone at Yahoo! noticed the discussion and removed the agent delivery.
>>>Andrew, what was the page a month ago?
Unfortunately I don't know if they were serving the different page to the bots, but I do know that the non-keyword stuffed page was up a month ago. The one that is currently being served with the large number of "used cars" references was not up.
Update: Tim Mayer of Yahoo! has confirmed on May 22nd edition of The Daily Search Cast that Yahoo Autos has changed the page since this has been reported. So, Yahoo Autos was cloaking.
.a11y,legend{position:absolute;left:-5000px;width:100px;}
.....
.....
<h3 class="a11y">Popular Yahoo! Properties</h3>
.....
I never did check it with IE - they weren't browser delivering too were they?
[edited by: Brett_Tabke at 7:32 pm (utc) on May 22, 2007]
If this is truly for usability then they would want to add "personals" after every state here right? [personals.yahoo.com...]
I never did check it with IE - they weren't browser delivering too were they?
I tested for different variations of both IE and FireFox browser user-agents and I also tested to see if the page was language cloaked. The same page was delivered in each case. I could only get the cloaked page using bot agents. They weren't just cloaking for Googlebot but apparently a number of bots.