For an organisation such as EEA, it is essential that we are easy to find on the Internet. It means search-engine friendliness is high on our agenda.
When you see a list of results on Google, each result is composed of a couple of items from the
page it shows as a hit.
The clickable title comes from the
<title> tag. The blurb under it is either constructed by
Google with sometimes messy results, or if available, it is taken from the
<meta name="description" content="..." /> tag in the HTML header.
It is essential that the title and description tags contain something
descriptive of the page—not the site.
We have experiences. There is nothing worse than seing identical titles for all hits from the same site
in a google result list.
A few browsers have begun to add buttons to their toolbars with links they get from the <link> tags in the <head> of the webpage. It is called link relations. Other browsers, such as Firefox and IE6 can do it via an extension. Here is an example of such links:
<link rel="author" title="About the Author" href="..."/>: a link to a page about the author
<link rev="made" title="Email Author" href="mailto:..."/>: a reverse link (note the "rev=" in place of the usual "rel="), offering an email connection to the author of the page
Explanation of attribute values
More common is the automatic detection of RSS feeds from a website. This is implemented by at least Firefox and Konqueror.
<link rel="alternate" type="application/rss+xml" title="Eionet headlines" href="http://www.eionet.europa.eu/announcements.rdf" />
One of the purposes of XHTML 2.0 is to make it easier to enter metadata into the webpage. With a simple parser systems will be able to "understand" facts about the statements made on the page, and harvest it in triples form to a Semantic Web database.
Document last modified: 2009/03/12 . Content in this portal is modified daily by a community of providers.