The noindex value of an HTML robots meta tag requests that automated Internet bots avoid indexing a web page. Reasons why one might want to use this meta tag include advising robots not to index a very large database, web pages that are very transitory, web pages that are under development, web pages that one wishes to keep slightly more private, or the printer and mobile-friendly versions of pages. Since the burden of honoring a website's noindex tag lies with the author of the search robot, sometimes these tags are ignored. Also the interpretation of the noindex tag is sometimes slightly different from one search engine company to the next.
Noindexing entire pages
Don't index this page
Possible values for the meta tag content are: "none", "all", "index", "noindex", "nofollow", and "follow". A combination of the values is also possible, for example:
Bot-specific directives
The noindex directive can be restricted only to certain bots by specifying a different "name" value in the meta tag. For example, to specifically block Google's bot, specify:
It is also possible to exclude part of a Web page, for example navigation text, from being indexed rather than the whole page. There are various techniques for doing this; it is possible to use several in combination. Google's main indexing spider, Googlebot, is not known to recognize any of these techniques.
tag
The Russian search engine Yandex introduced a new tag which prevents indexing of the content between the tags. To allow the source code to validate, alternatively can be used:
Do index this text. Don't index this text. Don't index this text.
Other indexing spiders also recognize the tag, including Atomz.
There is a 2005 draft microformats specification with the same functionality. The Robot Exclusion Profile looks for the attribute and value class="robots-noindex" in HTML tags:
Do index this text.
Don't index this text.
Don't index this text.
Don't index this text.
A combination of values is also possible, for example:
In 2007, Yahoo! introduced similar functionality to the microformat into its spider. However, Yahoo!'s spider is incompatible in that it looks for the value class="robots-nocontent" and only this value:
Do index this text.
Don't index this text.
Don't index this text.
Don't index this text.
SharePoint
2010’s iFilter excludes content inside of a
tag with the attribute and value class="noindex". Inner
s were initially not excluded, but this may have changed. It is also unknown whether the attribute can be applied to tags other than