Yahoo Expands X-Robots-Tag: Supports NOINDEX, NOARCHIVE, NOSNIPPET, and NOFOLLOW

Dec 10, 2007 - 9:11 am 1 by
Filed Under Yahoo SEO

Yahoo recently announced that they are supporting four new types of exclusion tags in the robots.txt file: NOINDEX, NOARCHIVE, NOSNIPPET, and NOFOLLOW. The benefits of being able to declare these directives in the robots.txt file enables folks who store PDFs, Word Documents, and other files on the web and cannot easily place these directives in the header.

Google actually expanded its robots.txt protocol in July with the unavailable_after tag, and Sebastian discovered the Noindex: / directive to block Googlebot from crawling your entire site.

The downside to these changes is that you'll have to check the robots.txt file to see if link juice is passed.

Yahoo also announced that this is related to its most recent search update:

Along with this change, we'll be rolling out additional changes to our crawling, indexing and ranking algorithms over the next few days. We expect the update will be completed early next week, but you may see some changes in ranking as well as some shuffling of the pages in the index during this process.

Forum discussion continues at WebmasterWorld.

 

Popular Categories

The Pulse of the search community

Follow

Search Video Recaps

 
Google March Core Update Done, HCU Recoveries, Site Reputation Abuse & AI Topics - YouTube
Video Details More Videos Subscribe to Videos

Most Recent Articles

Search Forum Recap

Daily Search Forum Recap: May 8, 2024

May 8, 2024 - 4:00 pm
Bing Ads

Bing Tests Clear Distinction Between Free & Paid Search Results

May 8, 2024 - 7:51 am
Google Search Engine Optimization

Google: Having News In Your Site Name Is Fine

May 8, 2024 - 7:41 am
Bing Ads

Bing Ads Carbon Neutral Label Goes Green

May 8, 2024 - 7:31 am
Google

Google Product Review Summary Labels Snippet

May 8, 2024 - 7:21 am
Google Maps

Google Local Business Profile Reviews Listings Updated

May 8, 2024 - 7:11 am
Previous Story: Google AdSense Fixes Seven Day Phone Verification Bug