Metatags.ca http://www.metatags.ca Meta Tags Explained Sat, 03 Dec 2011 18:53:29 +0000 en hourly 1 http://wordpress.org/?v=3.2.1 Meta Tags Explained http://www.metatags.ca/archives/13 http://www.metatags.ca/archives/13#comments Sat, 12 Nov 2011 03:02:46 +0000 xpctechnology http://www.metatags.ca/?p=13 Continue reading →]]> What are meta tags?

Meta tags provide information about your Web page to search engine robots so that the search engine can better understand what your site is about. Meta tags provide this information in a format that the web crawlers/spiders that visit your site can understand.

Meta tag code is inserted into your html code at the head of the document between theand. Meta tags are used by many search engines, and those that choose to ignore certain portions of the meta tags field, may at any time change their algorithms to include it.

Some people say meta tags are dead…ask them if that is the case, did they remove them from their site? Meta tags are not magic bullets for search engine ranking, but they are far from being dead.

There are meta tags for page title, page description, and page keywords and a range of other fields for not only classifying your website, but controlling how, where and when a web robot indexes your site. These tags help web indexing robots better understand your website for the purpose of assigning it a ranking in their database under specific search terms.

Standard tags that no site should be without:

 [ code ]
<title>Meta Tag Information</title>
<META name="description" content="Information on the creation and deployment of meta tags. Links to free meta creation tools">
<meta name="keywords" content="metatags,keywords,robots.txt,search engine submission,marketing optimization, registration, professional, meta tag generator, Canada, Vancouver">
 [ /code ]

Be sure that your meta tags are within the head of the html document.

To see where to insert your tags click this image

 

It is always important that your meta tags not be to short or to long. If they are to short they won’t be effective, and if they are to long they may be considered spam. An advanced meta maker and checker on sitesubmit.ca can help you with that. Don’t repeat the same keywords over and over as this to will look like ‘keyword stuffing’ and be treated as search engine spam. If this is found in your meta tags your site might be penalized by the search engines with a lower ranking. Many times we will check a sites keywords and find multiple of the same word such as “Parts”, “parts”, “Part” …don’t do this!. If we were to choose a word we would choose “parts” because it includes the word “part” in it. Why does that matter? Search engines use a technique called word stemming, in other words it can find the word “part” within the word “parts”, so to add both would be redundant and may be looked upon as keyword spam.

Be sure that the keywords you do use are actually the ones people are using to search with. Take your time and do your research! A good place to get help with researching top words is with the keywordpopularity.ca free keyword popularity tool. Further more it is also important to make sure that your tags have good relevancy to the actual text on your webpage and that gets down to checking your keyword density, which is a very important and often overlooked area of designing a well balanced website for the search engines.

And lastly if you think its a good idea to use copyright terms such in your title tags…think again…you may end up with irate corporate lawyers on your doorstep. Think about it, if you put a Nationally recognized franchise sign over your deli with the hopes of luring in their hard one foot traffic, you could rest assured corporate lawyers would be all over you in short order protecting their clients name and interest (and rightfully so). The same applies in the online world.

Advanced information:
Official Meta Tag Specs from W3C.org – This come from the larger HTML 4.01 specs. The article can be found here

7.4.4 Meta data

Note. The W3C Resource Description Framework (see [RDF10]) became a W3C Recommendation in February 1999. RDF allows authors to specify machine-readable metadata about HTML documents and other network-accessible resources.

HTML lets authors specify meta data – information about a document rather than document content — in a variety of ways.

For example, to specify the author of a document, one may use the META element as follows:

<META name="Author" content="Dave Raggett">

The META element specifies a property (here “Author”) and assigns a value to it (here “Dave Raggett”).

This specification does not define a set of legal meta data properties. The meaning of a property and the set of legal values for that property should be defined in a reference lexicon called a profile. For example, a profile designed to help search engines index documents might define properties such as “author”, “copyright”, “keywords”, etc.

Specifying meta data

In general, specifying meta data involves two steps:

  1. Declaring a property and a value for that property. This may be done in two ways:
    1. From within a document, via the META element.
    2. From outside a document, by linking to meta data via the LINK element (see the section on link types).
  2. Referring to a profile where the property and its legal values are defined. To designate a profile, use theprofile attribute of the HEAD element.

Note that since a profile is defined for the HEAD element, the same profile applies to all META and LINK elements in the document head.

User agents are not required to support meta data mechanisms. For those that choose to support meta data, this specification does not define how meta data should be interpreted.

The META element

<!ELEMENT META - O EMPTY               -- generic metainformation -->
<!ATTLIST META
%i18n;                               -- lang, dir, for use with content --
http-equiv  NAME           #IMPLIED  -- HTTP response header name  --
name        NAME           #IMPLIED  -- metainformation name --
content     CDATA          #REQUIRED -- associated information --
scheme      CDATA          #IMPLIED  -- select form of content --
  >

Start tag: required, End tag: forbidden

Attribute definitionsFor the following attributes, the permitted values and their interpretation are profile dependent:
name = name [CS]
This attribute identifies a property name. This specification does not list legal values for this attribute.
content = cdata [CS]
This attribute specifies a property’s value. This specification does not list legal values for this attribute.
scheme = cdata [CS]
This attribute names a scheme to be used to interpret the property’s value (see the section on profiles for details).
http-equiv = name [CI]
This attribute may be used in place of the name attribute. HTTP servers use this attribute to gather information for HTTP response message headers.
Attributes defined elsewhere

The META element can be used to identify properties of a document (e.g., author, expiration date, a list of key words, etc.) and assign values to those properties. This specification does not define a normative set of properties.

Each META element specifies a property/value pair. The name attribute identifies the property and the contentattribute specifies the property’s value.

For example, the following declaration sets a value for the Author property:

<META name="Author" content="Dave Raggett">

The lang attribute can be used with META to specify the language for the value of the content attribute. This enables speech synthesizers to apply language dependent pronunciation rules.

In this example, the author’s name is declared to be French:

<META name="Author" lang="fr" content="Arnaud Le Hors">
Note. The META element is a generic mechanism for specifying meta data. However, some HTML elements and attributes already handle certain pieces of meta data and may be used by authors instead of META to specify those pieces: the TITLE element, the ADDRESS element, the INS and DEL elements, the title attribute, and thecite attribute.
Note. When a property specified by a META element takes a value that is a URI, some authors prefer to specify the meta data via the LINK element. Thus, the following meta data declaration:

<META name="DC.identifier"
      content="http://www.ietf.org/rfc/rfc1866.txt">

might also be written:

<LINK rel="DC.identifier"
         type="text/plain"
         href="http://www.ietf.org/rfc/rfc1866.txt">
META and HTTP headers

The http-equiv attribute can be used in place of the name attribute and has a special significance when documents are retrieved via the Hypertext Transfer Protocol (HTTP). HTTP servers may use the property name specified by the http-equiv attribute to create an [RFC822]-style header in the HTTP response. Please see the HTTP specification ([RFC2616]) for details on valid HTTP headers.

The following sample META declaration:

<META http-equiv="Expires" content="Tue, 20 Aug 1996 14:25:27 GMT">

will result in the HTTP header:

Expires: Tue, 20 Aug 1996 14:25:27 GMT

This can be used by caches to determine when to fetch a fresh copy of the associated document.

Note. Some user agents support the use of META to refresh the current page after a specified number of seconds, with the option of replacing it by a different URI. Authors should not use this technique to forward users to different pages, as this makes the page inaccessible to some users. Instead, automatic page forwarding should be done using server-side redirects.
META and search engines

A common use for META is to specify keywords that a search engine may use to improve the quality of search results. When several META elements provide language-dependent information about a document, search engines may filter on the lang attribute to display search results using the language preferences of the user. For example,

<-- For speakers of US English -->
<META name="keywords" lang="en-us"
         content="vacation, Greece, sunshine">
<-- For speakers of British English -->
<META name="keywords" lang="en"
         content="holiday, Greece, sunshine">
<-- For speakers of French -->
<META name="keywords" lang="fr"
         content="vacances, Gr&egrave;ce, soleil">

The effectiveness of search engines can also be increased by using the LINK element to specify links to translations of the document in other languages, links to versions of the document in other media (e.g., PDF), and, when the document is part of a collection, links to an appropriate starting point for browsing the collection.

Further help is provided in the section on helping search engines index your Web site.

META and PICS

The Platform for Internet Content Selection (PICS, specified in [PICS]) is an infrastructure for associating labels (meta data) with Internet content. Originally designed to help parents and teachers control what children can access on the Internet, it also facilitates other uses for labels, including code signing, privacy, and intellectual property rights management.

This example illustrates how one can use a META declaration to include a PICS 1.1 label:

<HEAD>
 <META http-equiv="PICS-Label" content='
 (PICS-1.1 "http://www.gcf.org/v2.5"
    labels on "1994.11.05T08:15-0500"
      until "1995.12.31T23:59-0000"
      for "http://w3.org/PICS/Overview.html"
    ratings (suds 0.5 density 0 color/hue 1))
 '>
  <TITLE>... document title ...</TITLE>
</HEAD>
META and default information

The META element may be used to specify the default information for a document in the following instances:

The following example specifies the character encoding for a document as being ISO-8859-5

<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-5">

Meta data profiles

The profile attribute of the HEAD specifies the location of a meta data profile. The value of the profileattribute is a URI. User agents may use this URI in two ways:

  • As a globally unique name. User agents may be able to recognize the name (without actually retrieving the profile) and perform some activity based on known conventions for that profile. For instance, search engines could provide an interface for searching through catalogs of HTML documents, where these documents all use the same profile for representing catalog entries.
  • As a link. User agents may dereference the URI and perform some activity based on the actual definitions within the profile (e.g., authorize the usage of the profile within the current HTML document). This specification does not define formats for profiles.
This example refers to a hypothetical profile that defines useful properties for document indexing. The properties defined by this profile — including “author”, “copyright”, “keywords”, and “date” — have their values set by subsequent META declarations.

 <HEAD profile="http://www.acme.com/profiles/core">
  <TITLE>How to complete Memorandum cover sheets</TITLE>
  <META name="author" content="John Doe">
  <META name="copyright" content="&copy; 1997 Acme Corp.">
  <META name="keywords" content="corporate,guidelines,cataloging">
  <META name="date" content="1994-11-06T08:49:37+00:00">
 </HEAD>
As this specification is being written, it is common practice to use the date formats described in [RFC2616], section 3.3. As these formats are relatively hard to process, we recommend that authors use the [ISO8601]date format. For more information, see the sections on the INS and DEL elements.

The scheme attribute allows authors to provide user agents more context for the correct interpretation of meta data. At times, such additional information may be critical, as when meta data may be specified in different formats. For example, an author might specify a date in the (ambiguous) format “10-9-97″; does this mean 9 October 1997 or 10 September 1997? The scheme attribute value “Month-Day-Year” would disambiguate this date value.

At other times, the scheme attribute may provide helpful but non-critical information to user agents.

For example, the following scheme declaration may help a user agent determine that the value of the “identifier” property is an ISBN code number:

<META scheme="ISBN"  name="identifier" content="0-8230-2355-9">

Values for the scheme attribute depend on the property name and the associated profile.

Note. One sample profile is the Dublin Core (see [DCORE]). This profile defines a set of recommended properties for electronic bibliographic descriptions, and is intended to promote interoperability among disparate description models.

Copyright © 1999 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal
]]> http://www.metatags.ca/archives/13/feed 0