Since the introduction of HTML, the link element “a” is one of the oldest elements most commonly used in web development. Included in HTML 2 initially, it still exists in HTML 5. However, even though this tag was enhanced multiple times with different attributes over the years, most webmasters still stick to what they’ve learned, not realizing there were many more options available, or preferring to avoid new attributes like “rel” altogether.
The rel attribute had its fifteen minutes of fame in 2005 when Google announced that they would be ignoring links with the rel=”nofollow” attribute when ranking websites in search results. Unfortunately, 2005 was the “golden age” in the rise of SEO marketing companies and webmasters took that announcement to heart – avoiding the rel attribute altogether or thinking it was only for “nofollow”.
Also, Google’s “nofollow” announcement was greeted with applause by famous blog software makers because it helped to fight spammers who used to abuse blog comments and create site trackbacks using the rel attribute.
However “nofollow” behavior has changed lately.
So, what is really wrong with the rel attribute? Can we use it without “nofollow” effectively?
A hyperlink connects two HTML pages; the rel attribute is supposed to identify the type, relationship or value of the link itself. Since the introduction of microformats and the XHTML Friends Network (XFN) many more rel values have appeared in the web developer’s toolbox. Multiple values can be used on the same link tag, like this: <a rel="home me contents" href="http://example.org">.
A few of the most popular/appropriate uses for the rel attribute are included here. But compare that list with what is available in HTML 5. So much more than “nofollow”.
What about rel’s cousin – the “rev” attribute?
Rev is less popular than rel and is about to die a slow death since it is being phased out in HTML 5. Since the rel attribute defines the link target’s relationship to the current page, rev’s purpose is to define the current document’s relationship to the link target (the reverse). For example, <a rev="help" href="example.org">. This example indicates that the current document is the help manual for the site/page specified in the href attribute.
These types of HTML features have existed for many years, yet webmasters are very slow to adopt and use them with confidence. Taking a more informed approach to HTML can have two main benefits: it would help many search engines to identify what’s really important and the end user would benefit with new and exciting features (that would not be blocked out automatically). For example, tags like rel=”payment” can be used in RSS feeds. If you are media/text publisher, you can ask your readers for a comment or tip without asking them to click away and visit your page. What features could you introduce by gaining control over your rel attributes?




