Re: 'meta http-equiv' vs. 'meta name='

by =?iso-8859-1?B?TGF1cmkgVuRpbg==?= <optima(at)hot.ee>

 Date:  Wed, 12 Jul 2000 00:24:27 +0300
 To:  <roan(at)roanbear.com>,
<hwg-basics(at)hwg.org>
 References:  roanbear
  todo: View Thread, Original
Hello Roan,
The HTTP-EQUIV attribute is a equivalent for HTTP headers. The HTTP
headers will be sent to your browser by the server after a request for a
page/file has been made. This information may direct/control how your
page will be displayed in a browser.

The NAME attribute is there to provide additional information about the
document (such as keywords, description, author information, copyright
information and so on).

There is still a disagreement between many people about with which
attribute the keywords should go, this is why you'll find duplicates on
some pages. I personally would recommend using

<meta name="keywords" content="your keywords in a comma and space
separated list">

Best wishes,
Lauri Väin
--
Lauri Väin
Your own .com .net .org domain name is the best
advertisement on the net. Click below to see if
your domain name is still available and register it!
http://www.virtualis.com/vr/lvin/domain_search.html



----- Original Message -----
From: Roan Bear <roan(at)roanbear.com>
To: <hwg-basics(at)hwg.org>
Sent: 11. juuli 2000. a. 21:06
Subject: 'meta http-equiv' vs. 'meta name='


> Hi,
>
> Can anyone explain to me the difference/origin/ of the tag  'META
> HTTP-EQUIV=' vs. the use of 'META NAME='
>
> I've seen both now on different web pages and am wondering if one is
older
> than the other, if both are supported etc.
>
> I've seen both used within the same page for search engine rankings
(both
> using 'keywords' as the value) and am wondering if the search engine
spiders
> read the tags differently, or if this is just another form of
misdirected
> search engine spamming.
>
> I'm on the digest version.
> Thanks in advance for any clarification.
>
> Regards,
>
> Roan
>
>
>

HTML: hwg-basics mailing list archives, maintained by Webmasters @ IWA

This page is part of a preserved archive of archives.hwg.org. The site is no longer active and its content is not maintained. For enquiries about this archive, write to archive(at)iwanet.org.