Links Badge and Other Yahoo! Site Explorer Updates

It’s nice to see Yahoo! Site Explorer launching new services aimed to empower its users.

From its Yahoo! Search Blog entry, additional features were introduced.

  1. Links Badge. Instead of going through the text box and typing in site:www.mydomain.com, Yahoo! provides a badge that shows the number of links pointing to www.mydomain.com site or the page that contains the badge. It reminds me of the Alexa Site Rank that shows traffic rank, links in and user rating. (An example appears at BuildingBrands Stats page.)

Yahoo! Search Marketing Update Imminent

I received an email from Yahoo! Search Marketing (Overture) last Wednesday informing me of the changes to take place on its Paid Search product.

It said that beginning the 5th of February (next Monday) in the US, changes on its pay-per-click advertising will commence:

Bid amount and ad quality will determine the placement of ads.

Contrary to the past that only the highest bidder gets the best position of their PPC ads, Yahoo! now will also look at the quality of its ads. If the ads are more relevant to whether they are relevant to search queries more than the others, these ads get preferential treatment by Yahoo! Search Marketing. Therefore, for every target keyword, an appropriate ad must be placed in order to secure a notable place on search results. Of course, money still is a big factor in the placement of ads.

Yahoo! Adds Wildcard Entries for robots.txt

Yahoo! has recently updated its search engine robot Slurp to recognize wildcard specifications on file naming found within robots.txt file.

The supported characters are * (asterisk) and $ (dollar sign, obviously). As we knew from Disk Operating System of Microsoft, asterisk is used to denote an indefinite number of character so that s* can represent seo or search. As an example:

User-Agent: Yahoo! Slurp
Allow: /public*/
Disallow: /*_print*.html

Second line allows the crawling of all folders beginning with public regardless of character length such as public_html or public_image.

Third line directs Slurp to ignore any html filename that contains _print.

On the other hand the $ directive indicates any match that is found towards the end of the URL. For example:

User-Agent: Yahoo! Slurp

Disallow: /*.gif$
Allow: /*?$

The Disallow statement simply tells Slurp to ignore any filename that ends with a .gif. One thing to note is that if we remove the $ sign, the instruction tells Slurp to ignore any file that contains the expression .gif.

The Allow statement tells Slurp (or other engines that support this command) to allow any file that contains a ? (question mark) character in the end and NOT any filename that contains the ? character elsewhere.

Soon: No Yahoo! Directory directive

As a follow up to an earlier release about Yahoo’s support on the NOODP tag, it will now offer the feature to exclude Yahoo! Directory when extracting the description snippet on search results.

I have been asking about it when I posted the news on Yahoo’s NOODP support release. From a WebmasterWorld thread, there seems to be a buzz going on. Tim Mayer of Yahoo! says they are working on it but sought the advise of fellow forum members on what works best on handling the issue.

Hands down I prefer that everytime a NOODP tag is detected, it should exclude not only Open Directory but also also the Yahoo! Directory.

Yahoo! Now Supports NOODP Tag

Yahoo! Search Blog has recently announced that it now supports the NOODP tag:

<META NAME=”ROBOTS” CONTENT=”NOODP”>

or

<META NAME=”Slurp” CONTENT=”NOODP”>

This tag was earlier adopted by Google and MSN search engines as a means to address webmaster preference of their meta descriptions embedded on a web page instead of using the brief description that appears on Open Directory. With Open Directory descriptions appearing on search engine results snippets, there is little (perhaps none at all) control of what content webmasters want to see once their pages are displayed as results.

I noticed though that the descriptions they place on search results do not depend on either Open Directory listings or META Tag specifications. For example, searching for hong kong property agents in Yahoo! displays the Yahoo! Directory entry of Sallmanns Residential. While that listing is at number one, the purpose of NOODP is not addressed because Yahoo! picks its results elsewhere not named META Description and DMOZ. So do we need to ask Yahoo! for a NODIR or NOYAHOODIR tag then? Anyway, this is not a big concern for Sallmanns especially that it is prominently placed on Yahoo! for that search query. What about the others?