This specification is (C) 2005-2023 by the authors. However, the authors intend to submit (or already have submitted, see details in the spec) this specification to a standards body with a liberal copyright/licensing policy such as the GMPG, IETF, and/or W3C. Anyone wishing to contribute should read their copyright principles, policies and licenses (e.g. the GMPG Principles) and agree to them, including licensing of all contributions under all required licenses (e.g. CC-by 1.0 and later), before contributing.
- Tantek: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
- Kevin Marks: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
- When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.
RelNoFollow is an elemental microformat, one of several microformat open standards. By adding
rel="nofollow" to a hyperlink, a page indicates that the destination of that hyperlink SHOULD NOT be afforded any additional weight or ranking by user agents which perform link analysis upon web pages (e.g. search engines). Typical use cases include links created by 3rd party commenters on blogs, or links the author wishes to point to, but avoid endorsing. For more specific endorsement (or lack thereof) semantics, see VoteLinks.
This profile is hosted as a separate XMDP file on microformats.org:
Profiles are referenced in (X)HTML files in the <HEAD> tag, e.g.:
<dl class="profile"> <dt id="rel">rel</dt> <dd><p> <a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel"> HTML4 definition of the 'rel' attribute.</a> Here is an additional value as defined in the <a rel="help start" href="http://microformats.org/wiki/rel-nofollow"> rel-nofollow specification</a> .</p> <dl> <dt id="nofollow">nofollow</dt> <dd>Indicates that the referred resource was not necessarily linked to by the author of the page, and thus said reference should not afford the referred resource any additional weight or ranking by user agents. </dd> </dl> </dd> </dl>
examples in the wild
This section is informative. Note: There are numerous uses of rel-nofollow in the wild, this is very much an incomplete list. If your site marked up with rel-nofollow, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page (rel-nofollow-examples-in-wild).
- FunAdvice supports using the rel-nofollow tag to prevent users posting content simply for the search engine benefit, to improve the quality of the advice giving community.
bad examples in the wild
This section is informative. There are now numerous abuses of rel-nofollow, in particular, where it is used on *2nd party* links, rather than the original intention of *3rd party* links such as in blog comments. The primary abusers of rel-nofollow are content hosting / social network sites.
- Flickr puts "nofollow" on comments by the content publisher themselves (should only be on 3rd party comments), e.g. http://www.flickr.com/photos/tantek/2344425887/ as well as on profile links e.g. website: http://www.flickr.com/people/microformats/
- Twitter puts "nofollow" on account holders' profile links, in the "description" and "web site" fields, e.g. http://twitter.com/indiewebcamp (links in posts do not have "nofollow" yet are wrapped with "t.co" URLs).
- ... nearly every other content hosting / publishing site - please add more specific examples with direct URLs to pages abusing "nofollow".
It may seem odd to explicitly list *non* examples in an examples in the wild section, but such non-examples may be useful to help convince the bad examples in the wild to change their behavior:
- Blogspot does NOT put "nofollow" on content publisher links, e.g. http://epeus.blogspot.com/2012/03/when-youre-merchandise-not-customer.html
- Tumblr does NOT put "nofollow" on content publisher links, e.g. http://adactio.tumblr.com/post/27135731578/the-web-unusually-came-with-a-view-source
- ... (let's hope we find more such non-examples)
- VoteLinks can be used by an author to explicitly state their support for or against, or neutrality toward the destination of a link. Implementers implementing rel="nofollow" and VoteLinks should similarly not afford any additional weight or ranking to links with either
- Contributed from http://developers.technorati.com/wiki/RelNoFollow
These are open issues that have been raised about rel="nofollow" that have been raised in various forums, in particular, on the public W3C www-html mailing list. Once the list grows too big, we'll make a separate wiki page (rel-nofollow-issues). The issues have been grouped into four areas.
- Definition. nofollow indicates a behavior rather than a relationship from which the behavior should be inferred as appropriate for the useragent. rel values should be nouns that indicates what the resource being referenced is in relation to the source.
- Name. nofollow is a bad name.
- overloading. does not mean the same as robots exclusion standards (robots.txt, meta robots) nofollow.
- does not mean what it says. does not mean "do not follow this link", rather it means " do not add weight from this link". Asbjørn Ulsberg
- not a noun. see above.
- suggested alternatives:
- Efficacy. nofollow will not affect spamming behavior.
- Collateral Damage. If tools automatically add nofollow to all 3rd party links, then many legitimate non-spam links will be ignored or given reduced weight, and thus the destination of such links will be unfortunate casualties.
additional lists of issues
Additional lists of issues raised against rel="nofollow" can be found at the following site(s):
Matt Cutts Says No to Nofollow On Internal Links:
- 2013-09-13 Matt Cutts on YouTube
When this section gets too big, we can move it to rel-nofollow-articles.