Yahoo! Cross-sell bug

In a recent release, Yahoo! made it possible to show cross-sells right on the product pages. Coupled with their auto-suggest feature (where products are automatically recommended based on past shopping history) this is a great conversion feature. There is, however, a minor bug in the way these on-page cross-sells are implemented. Here is the scoop:

As you may know, you can add the yahoo-generated cross-sells to your item pages by inserting <div id="ys_relatedItems"></div> anywhere in your pages' text or template. The bug occurs - in Internet Explorer only - if this ys_relatedItems div is the last child of its parent. In that case, and again, only in Internet Explorer, no cross-sell items will show up on the page.

In layman's terms, this means that if you have a closing tag after <div id="ys_relatedItems</div>, then this bug will cause your cross-sells not to show. So, for example, if you have a table and inside it the last element is your ys_relatedItems div, then this would trigger the bug.

Yahoo! Engineering is aware of the bug and it will be fixed in the next maintenance release. In the meantime, though, there is a very easy work-around: simply add something after your ys_relatedItems div so that it's not the last child of its parent. An empty div, for example, will do the trick:

<div id="ys_relatedItems"></div><div></div>

Comments

CPR for a Yahoo Store on Google's Supplemental Index

Recently a client of mine came to me and said that most of his store pages disappeared from Google, and he did not do anything to make this happen. I was a bit skeptical, so I went to Google, did a search on his store, and sure enough, there were only two pages indexed, his home page and his site map (ind.html) page. The rest were in the supplemental results, which means that Google thought the rest of the pages were not much different than these two pages. When I looked at the supplemental results, the little excerpts under each link were exactly the same, and I also noticed that what Google showed under each result was actually text from the ALT tags of the header image. I looked at some of these pages in my client's store, and they were actually different. This was a bit puzzling, but then I thought perhaps Google saw that the header and left navigation was the same throughout the site (which is pretty normal), but that the text that made each page different was too far down ins

What to expect when your redesign goes live

At Y-Times we roll out new designs, redesigns and other major upgrades to Yahoo stores on a fairly regular basis. Some of the main questions our clients ask are how to prepare for a roll-out and what to expect in terms of SEO and conversions when the changes go live? For any functional Yahoo store how well the site ranks and how well it converts are probably the two most important metrics. Since pretty much ANY change you make to any page can potentially alter either or both of these metrics, merchants may understandably feel nervous about far reaching alterations to their sites. However, when those functionality and design changes and additions are done right, there is really very little to fear. First off, what does it mean for a design or redesign to be "done right?" From the technical stand point, search engines look at the underlying structure of your site (the HTML, and increasingly also the CSS and JavaScript code) to try to extract information and meaning from i

Smaller is Better

You often hear the phrase "bigger is better". Sometimes it's true but not when it comes to JavaScript or CSS code in your Yahoo! Store pages. If you include JavaScript code or CSS either as linked files (the preferred method) or embedded inside your pages (obviously not preferred), making these files as small as possible should be your goal. Why? This is no rocket science: smaller files mean faster page loads = happy customers. Ok, so what bloats JavaScript code? In general, white space (tabs, carriage returns, non-used spaces), comments, and the actual code, such as variable and function names. You have control over all of these, however, if you don't use white spaces, carriage returns or comments, it will be immensely difficult to understand and modify your code. And not just for others, you too. There are many commercial JavaScript compression tools around, but I've been using this handy and free utility: http://www.andrewkesper.com/jscrush/ This little utilit

Search This Blog